read and validate config files for webevals #1
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
matthewcornell
approved these changes
Dec 19, 2024
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.
This PR does some first setup for config files for webevals.
These config files will be provided by a hub admin as part of the dashboard repo, and specifies settings for score computations: what targets to score, what metrics to compute for each target, and evaluation windows to use. Additionally, there is a section with mappings from task id variable value codes (e.g. FIPS codes for locations) to human-readable text, mirroring the setup for predtimechart.
There is a little bit of motivation about the config files in the "Acquiring the score data" section of the planning document for this project (note: link-sharing is set to read-only).