You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: