Warn the user if the scenario.automated.yaml is outdated or non existent#85
Closed
Warn the user if the scenario.automated.yaml is outdated or non existent#85
Conversation
cpschau
pushed a commit
that referenced
this pull request
Jul 14, 2025
* export firs trade variables * add plotting for trade and issing policy variables * added Trade|Secondary Energy|Liquids|Hydrogen|Volume and Trade|Primary Energy|Gas|Volume * undo config changes * fix undo config changes * cleanup --------- Co-authored-by: Michael Lindner <michaellindner@posteo.de>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The goal of this PR is to warn the user about some errors that might occur when using the scenario management in pypsa-de incorrectly
Ideally the workflow wouldn't just print a warning, but fail but i did not find out how to do that yet (because it should only fail when
ariadne_allis called and not whenbuild_scenariosis called)Even more ideally, build_scenarios would be included in the default workflow, but that seems even more complicated to achieve as that means modifying the snakemake config in runtime.
Before asking for a review for this PR make sure to complete the following checklist:
ariadne_allcompletes without errorsexport_ariadne_variableshas been adapted to the changesChangelog.mdmainhas been merged into the PRYYYYMMDDdescriptive_title