-
Notifications
You must be signed in to change notification settings - Fork 16
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
677-computation-of-the-effective-reproduction-number-in-the-secir-model #698
677-computation-of-the-effective-reproduction-number-in-the-secir-model #698
Conversation
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #698 +/- ##
==========================================
+ Coverage 94.22% 95.01% +0.78%
==========================================
Files 108 112 +4
Lines 8540 8928 +388
==========================================
+ Hits 8047 8483 +436
+ Misses 493 445 -48 ☔ View full report in Codecov by Sentry. |
…-the-secir-model' of github.com:DLR-SC/memilio into 677-computation-of-the-effective-reproduction-number-in-the-secir-model
…-reproduction-number-in-the-secir-model
*@returns The computed reproduction number at the provided index time. | ||
*/ | ||
template <class Base> | ||
IOResult<ScalarType> get_reproduction_number(size_t t_idx, const Simulation<Base>& sim) |
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.
I know/assume that this contains the derivative of the ODE so a lot of code-doubling happens. Generally it is just not a very good a idea to introduce redudant code parts. We should maybe think of how only one responsible code part returns for instance the mechanism of X and then this is used for get_derivatives and get_reproduction_number.
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.
Thank you for your work. Looks good. I made a few comments. We should also consider making the code more modular. In general we should avoid duplication of code. And increased modularity also creates a better opportunity for testing functionalities.
Im currently checking the equations separately and also try to verify the tested values.
Changes
Please briefly list the changes made:
[Describe here in 2-3 lines. For details, reference to issues to avoid redundant information.]
Merge Request - GuideLine Checklist
Checks by code author
Checks by code reviewer(s)
Additional context
Please list additional information or things a reviewer should look out for.