-
Notifications
You must be signed in to change notification settings - Fork 0
Include run label in directory name #98
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
|
We should find a better solution than to trigger a complete rerun of everything if the label of a forecast run or baseline changes. This will come back to bite us when iterating to produce production-ready plots for papers, presentations etc. I totally see the need to render plots in showcases and experiments more easily identifiable and think using the label there is probably the low-hanging fruit, but can we please avoid doing this for the inference and verification in output/data/... |
|
new proposition is to distinguish more clearly between
meaning that there is no need for caching results. Each evalml run creates a new results folde ordered by timestamp and if something needs caching because it's expensive (eg plotting all frames for showcases) it can be moved to output/data. |
|
I won't have time to do a proper review, but I like the proposed changes. |

This pull request updates how run identifiers and output paths are constructed for run data and output results.
Summary of changes
forecaster-d084-91a251cd,interpolator-8d1e-on-forecaster-d084-1fa265c9,interpolator-8d1e-on-ana-1fa265c9