-
Notifications
You must be signed in to change notification settings - Fork 6
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
Postprocessing meta #238
Comments
Agree with the proposed roadmap |
I have done some initial light investigation into |
There is also https://marginaleffects.com/ |
Can we safely delete sensible-newdata-input or does it contain work we need? |
We can delete it. I will do so. |
I think that with the Ebola vignette up we have now demonstrated how to do the postprocessing tasks that we had scope / previously talked about, and this can be closed as completed. |
Tagging @seabbs @kgostic @parksw3 for feedback:
Background
The existing issues we have about postprocessing are as follows:
newdata
as sensible things (e.g. all strata) #213delay_summary
function built onpredict_delay_parameters
#215We have already implemented some postprocessing functionality, including including
add_mean_sd
function Issue 169: Natural scale postprocessing #170predict_delay_parameters
function Issue 188: Add delay samples functionality #210all_strata_newdata
function which would feed intopredict_data_parameters
https://github.com/epinowcast/epidist/pull/231/filesBy extension of the
all_strata_newdata
function I can see a path to achieving the postprocessing functionality that we intially agreed for 0.1.0 of the package. However, it'd be better if we don't have to write this functionality outselves. Therefore:Plan
My plan going forward is to follow Plan A until it seems like there are roadblocks that make it not possible or too difficult for some reason. At that point I'll follow Plan B.
Plan A
tidybayes
(or other packages) for all post-processingdelay_summary
function built onpredict_delay_parameters
#215Plan B
newdata
#231 in order to implement the functionality that we need for 0.1.0The text was updated successfully, but these errors were encountered: