Skip to content
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

Better scenario metadata and file naming #61

Open
kellynm opened this issue Aug 12, 2022 · 0 comments
Open

Better scenario metadata and file naming #61

kellynm opened this issue Aug 12, 2022 · 0 comments
Labels
enhancement New feature or request

Comments

@kellynm
Copy link
Contributor

kellynm commented Aug 12, 2022

Is your feature request related to a problem? Please describe.
The output when using scenarios are not clearly named to distinguish the different scenarios, or from runs that do not use scenarios (BAU compared to management scenario runs). Currently the scenario list variable is output in the run metadata, but there is no easy way to tell the runs for different scenarios apart. Users may accidentally aggregate results from runs using different scenarios.

Describe the solution you'd like
Reevaluate the workflow for scenarios to identify best solution for tracking scenario runs. Maybe creating subfolders for scenarios, or adding str to file name. Need some way to distinguish the runs for difference scenarios.

Additional context
Workflow in notebooks 2-4 would be affected.

@kellynm kellynm added the enhancement New feature or request label Aug 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant