-
Notifications
You must be signed in to change notification settings - Fork 4
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
Clean up Rt infections renewal model #204
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #204 +/- ##
==========================================
- Coverage 94.76% 92.51% -2.26%
==========================================
Files 40 40
Lines 898 895 -3
==========================================
- Hits 851 828 -23
- Misses 47 67 +20
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ 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.
Main comment: Why is the test image being removed?
|
Agree on point 3 unless there is something I am missing @gvegayon . |
I 100% Agree with both, so then, instead of removing the test completely, I would drop in a replacement test that checks the data under the figure. |
I'm just not yet sure what a good test would be. We don't test anything related to the posterior anywhere else, so I would be more inclined to push "develop tests related to posterior inference" to a separate issue. |
How about saving the data that it generates now? Just like the image approach, but with model outcomes |
Willing to try it, but I worry that we could get test failures based on very minor package updates. I'm also not sure if the rng would lead to the same output on all platforms. There is a Teams thread about this somewhere (for Stan). I'll try to find it. |
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.
Finished reviewing the remaining files. Other than what is mentioned in #206 and maybe just a reminder for us to address the plot testing or to make a final decision on testing the data directly instead of the plotted data, this PR looks useful and appropriate.
Based on the Teams discussion I referenced, I believe this could be merged (but I would need an approving review), and we can defer a wider discussion of testing posterior inference to some other time and place. Perhaps it would be a good topic for an STF team meeting? @dylanhmorris |
I agree on both counts. |
Can you open an issue for this in the team materials repo @damonbayer? |
Cleaning up this model in preparation for #202.