Study simulation #2
Open
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
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.
@dallas-hall-tl this is the dev branch I've been working off of and now has the latest state of the study design. Please take a look, and let me know if you have any questions.
I wrote it in a way so that it matches the pseudocode here: https://docs.google.com/document/d/10nUiwFA6HFJ7vvcEcUlM7cop0dTQq2H7xiRM-GDPNt4/edit?tab=t.qvbn6yu5b715
I think there should probably be a cleaner way to set up the logic in our main app that doesn't so closely match the pseudocode flow, but I'll leave that up to you!
Ultimately, we should be generating a schedule for each enrollment that looks like this: https://docs.google.com/spreadsheets/d/1Ape_bfOJbr1q_7dXGYIVq_FuvyxXcsQDEIGf7xVtlBg/edit?gid=408467949#gid=408467949