Check if scenario file exists before attempting to load #993
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.
A very simple quality of life improvement. Useful when running the
create_scenarios
rule the first time.When wishing to generate a new scenarios files (say, "scenarios2.yaml"), one could change the corresponding config option (
run/scenarios/file
) and run thecreate_scenarios
rule. However, if say "scenarios2.yaml" doesn't exist yet, theget_scenarios
function fails. An awkward solution is to first create "scenarios2.yaml" manually (and put in some mock scenarios, otherwisescenarios.keys()
fails!), and then runcreate_scenarios
. With this check, that's not necessary anymore.Checklist
envs/environment.yaml
.config.default.yaml
.doc/configtables/*.csv
.doc/release_notes.rst
is added.