Speed up state truth data-pulling by moving out of evalcast
#225
Conversation
This file contains hidden or 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
|
IIRC (it was a long time ago, though) all state truth data using this approach and using |
|
Test run in production failed. Update: Below changes should address this. |
|
After adding some fixes, a production run succeeded, with a run time of 4h 25m. This is a reduction of about 1.5h, in line with previous estimates of how long downloading truth data in |
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.
Create
evaluate_chu-like function for pulling truth data and scoring state predictions. Because the function bypassesevalcast's built-in data-fetching, this should be a lot faster.Haven't worked on this in a long time, though, so the code will need to be reviewed, and checked for correctness and speed compared to the current pipeline. This may be entirely ready to go as-is 🤞.