Data synchronization #33
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
thanasibakis
approved these changes
Aug 20, 2024
|
This is nice! |
thanasibakis
force-pushed
the
afm-synch-data
branch
from
6abc5ff to
f22f2e2
Compare
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 makes it so that
present-day-forecasting/main.pygenerates its own dataset.Previously our workflow was to first download the data, then run the
present-day-forecasting/main.py. This allowed for the downloaded data to correspond to a time-horizon that was different from what was specified inpresent-day-forecasting/config.yaml.I refactored
linmod.datasuch that the functionality oflinmod.data__main__is now in a functionlinmod.data.main()whichpresent-day-forecasting/main.pycalls using the config it was provided.