Add pytem run command and basic notebook example#178
Merged
Conversation
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.
Context
There is a desire to have a easier way to manage scenarios with minimal installation and knowledge requirements about PyETM for less tech savy users or situations where there is no need to do anything other than manage scenarios with the from_excel+to_excel approach.
Implemented changes
Added pyetm run <excel_file> command which completes a round trip to the ETM based on the settings in the input excel and the export config tab. This allows users who are less comfortable with code editors and scripting to avoid interacting with notebooks etc at all.
There is also a basic Jupyter notebook that demonstrates this round trip functionality, with some minor additional details that demonstrate how to inspect the scenarios object.
Checklist