-
Notifications
You must be signed in to change notification settings - Fork 3
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 51: Add ascertainment_dayofweek #253
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #253 +/- ##
==========================================
- Coverage 93.07% 92.90% -0.18%
==========================================
Files 43 44 +1
Lines 419 423 +4
==========================================
+ Hits 390 393 +3
- Misses 29 30 +1 ☔ View full report in Codecov by Sentry. |
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 looks great!
Wrt using softmax
, I think that would be cool after we clear #251 e.g. we might model a weekly process but then broadcast out the weekly observations to a day of the week in a way that respects the weekly average obs.
This implementation hit a different form of modelling and looks nice!
Note: this was part of analysis plan and should now be added to pipeline.
I made a new issue (#258 for the |
This PR closes #51 by adding a new helper function to
EpiObsModels
that gives semi-sensible defaults for specifying a day of the week ascertainment model (as a day of the week effect).It does this by introducing a new dependence on
EpiLatentModels
and slightly modifyingAscertainment
so that the transform has to be manually specified as vectorised (to allow for actually vectorised transforms to be supported).Note: We had discussed using a softmax but this doesn't make sense once a latent model has been broadcast. We could instead do so using a
TransformLatentModel
but to me (and as currently formulation is fairly common practice) what is here seems reasonable as a starting point.