-
Notifications
You must be signed in to change notification settings - Fork 33
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
Issue #408: Fit the susceptible population #904
base: main
Are you sure you want to change the base?
Conversation
I am minded not to do any of these unless you feel strongly |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is really nice!
- This doesn't address if we should be reporting the susceptibility adjusted or unadjusted Rt.
We already have a gen_R
in generated quantities (for the nonmechanistic model) - so we could in principle model unadj_R
and then always generate R in generated quantities?
I don't feel strongly - not quite sure what's best to report anyway. Probably worth a new Issue though as we might be calling stuff R when it's not actually R. |
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This is how benchmark results would change (along with a 95% confidence interval in relative change) if bafef0b is merged into main:
|
This is how benchmark results would change (along with a 95% confidence interval in relative change) if 6184ab9 is merged into main:
|
Co-authored-by: Sebastian Funk <[email protected]>
Co-authored-by: Sebastian Funk <[email protected]>
Co-authored-by: Sebastian Funk <[email protected]>
Co-authored-by: Sebastian Funk <[email protected]>
Co-authored-by: Sebastian Funk <[email protected]>
So had a bit more of a look at this and on a sight read it looks okay. However when trying to use it to fit models there are serious problems. In the old mode (i.e. forecast) all post data infection estimates are zero and in the all mode it just breaks. Clearly I am missing something so will circle back tomorrow. |
This is how benchmark results would change (along with a 95% confidence interval in relative change) if ec87d74 is merged into main:
|
This is how benchmark results would change (along with a 95% confidence interval in relative change) if bab5af7 is merged into main:
|
Might the issue be that every parameter gets initialised with a standard normal which in the case of population size is a very long way from any meaningful posterior density (and probably somewhere that the marginal likelihood surface is quite flat)? |
ah yes that could explain the initialisation errors for the all model but not why the infections are all nearly zero in the forecast only model |
I'm thinking if it's forecast only then the estimate of |
Also wondering if the use of
|
I have tested this as well as a few minor modifications and ran into serious issues. Is there some deep-rooted issue where the likelihood surface becomes really difficult to explore when you're in a situation where depletion of susceptilbles suppresses counts to zero whatever the other parameters? |
Description
This PR closes #408 by allowing for fitting the susceptible population using the new distribution interface.
Maybe to do:
Initial submission checklist
devtools::test()
anddevtools::check()
).devtools::document()
).lintr::lint_package()
).After the initial Pull Request