-
Notifications
You must be signed in to change notification settings - Fork 7
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
Improve the prior interface for make_epi_model_inference
#45
Comments
Yes, atm I just use
I'm going to try and prototype this with the easy fix as back up. It shouldn't be very hard. Basic idea is to wrap the function that makes a The essential question is:
|
Yes I think this is a nice idea.
This seems cleanest to me and I think likely to have fewer failure states. |
My proposal is to create a struct to contain both the Proposed new model diagramflowchart LR
A["Underlying dists.
and specify length of sims
---------------------
EpiData"]
B["Choice of target
for latent process
---------------------
DirectInfections
ExpGrowthRate
Renewal"]
C["Observational Data
---------------------
Obs. cases y_t"]
D["Latent processes
---------------------
random_walk"]
E[Turing model constructor]
F["Latent Process priors"]
G[Posterior draws]
H[Posterior checking]
I[Post-processing]
DataW[Data wrangling and QC]
J["Observation models
---------------------
delay_observations"]
K["Observation model priors"]
A --> EpiModel
B --> EpiModel
EpiModel -->E
C-->E
D-->LatentProcess
F-->|default_rw_priors|LatentProcess
J-->ObservationModel
K-->|default_delay_obs_priors|ObservationModel
LatentProcess-->E
ObservationModel-->E
E-->|sample...NUTS...| G
G-.->H
H-.->I
DataW-.->C
|
As the title says we should be able to improve the prior interface. The simplest improvement would be to generalise the argument name for the latent process priors to reflect that it is used across all submodules. An additional improvement would be to think more deeply about the coupling of priors to model submodules.
This issue was discussed in #44
The text was updated successfully, but these errors were encountered: