Add test switching functionality #16
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…st was available as routine'
sandypreiss
commented
Mar 20, 2024
rjmorris
reviewed
Mar 28, 2024
…lso fix a few other small issues identified in code review.
|
@rjmorris I finally took this off the back burner today. Ready for another look. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Prior to this PR, the routine test used by each person is assigned at the start of their lifespan based on the
proportionparameters for each test. They use the same routine test throughout their lifespan.The goal of this PR is to enable us to simulate scenarios where a person uses multiple different routine tests throughout their lifespan. This is accomplished by specifying a single pattern of routine test availability that each person in the simulation uses. For example, in the default scenario in
parameters.json, everyone in the simulation has colonoscopy as their routine test from age 50 to 60 and FIT as their routine test from age 61 to 75.A tradeoff of this approach is that we lose the ability to probabilistically vary the routine test assigned to people within the simulation. Everyone in the simulation uses the same test-year pattern. Because we may still want to use the old test assignment functionality, a boolean parameter
use_variable_routine_testdetermines whether the test pattern parameters are used.