-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ensure euc yi vars not erroneously being back-transformed #88
Comments
Note, related to: egouldo/ManyAnalysts#63 |
See also: https://github.com/metamelb-repliCATS/ManyAnalysts/issues/194#issuecomment-1624523475 we said we would log-transform them. |
OK yes, unfortunately it seems that the Euc variables are both back-transformed AND standardised, which explains why we were getting weird forest plots for the Eucs and had to log-transform the response... https://github.com/metamelb-repliCATS/ManyAnalysts/issues/194#issuecomment-1624523475 !! |
- #104 mv `assign_transformation_type()` and `convert_predictions()` out of `standardise_response()` into `back_transform_response_vars_yi()` - Call `back_transform_response_vars_yi()` in `prepare_response_variables()` for yi workflow (was not being called currently) #104 - #104 keep addition of `param_table` inside `standardise_response()`
- NOTE: dummy function for datasets not selected for standardising is currently applied - TODO: update dummy function - TODO: apply functions with map2
- prev approach with rlang::as_function() was taking the entire set of all previous input code including the wrapping mutate() calls
- correctly apply `fns` in list-col using `pmap()` approach on entire dataframe, with support of wrapper / parser fun that parses the required variables to either `standardise_response()` or `process_response()` - #97 delete comment
- for alternate to standardise_response()
- #102 Add `@details` section for `process_response()` and add heading for `@details` in `standardise_response()`
…argets - only standardise blue tit yi #88
Fix #88 conditionally apply standardisation to datasets
- #116 add checks for param table argument - update default behaviour description #102 - line linting / indentation #97 - #88 change default behaviour to `process_response()`, not `standardise_response()` when `is.null(dataset_standardise)`, otherwise function did not allow for case when all datasets should not be Z-standardised
|
Check that yi vars are not being back-transformed / standardised when they shouldn't be for Eucalyptus, which is what we explained in the manuscript.
Related to #80 #82
Note that this has implications for the manuscript:
Z_VZ_preds()
), however, we should continue logging the outcome variable.The text was updated successfully, but these errors were encountered: