risk of bias metric key field #771
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
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.
Add a new risk of bias key field to match metrics across assessments. This way, we don't need to do fuzzy text-comparisons if metrics across assessments have the same key. The key is optional, and was not applied to existing data in HAWC.
Also reviewed the IRIS handbook and confirmed that all metrics in HAWC are consistent with the handbook.
Also created a jupyter notebook, hawc/scripts/client/rob-config.ipynb, which can be used to save study evaluation configuration to a JSON file compatible with our load approach method. This automated approach to generating the JSON changed some of the formatting in the documents, but we reviewed the underlying approaches to confirm they're consistent.