We currently archive key forecast outputs in part by tracking them in git (see output/forecasts). We should arguably do the same for archived configuration files, which currently live in the .gitignore-d input/config directory.
Steps
[ ] Make a decision on whether to track in git at all
[ ] If yes, make a decision on which runs to archive
[ ] If yes, make a decision on where to put the tracked, archived config files
My proposal
Yes, track
Track only for prod runs
Put the archived config files in output/forecasts
If we are going to archive them in input/config/, then at minimum the production subfolder should be tracked in git, imo. It's currently .gitignore-d
Goal
We currently archive key forecast outputs in part by tracking them in git (see
output/forecasts). We should arguably do the same for archived configuration files, which currently live in the.gitignore-dinput/configdirectory.Steps
My proposal
output/forecasts_Originally posted by @dylanhmorris in https://github.com/cdcent/cfa-forecast-renewal-ww/pull/521#discussion_r1516553690_
tagging @kaitejohnson @seabbs @afmagee42 @swo for visibility