Ext data export, Variable defaults, and Data File Scenario Filtering #38
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.
get_model_datato perform filtering of datafiles where one data_file_tag can specify multiple scenarios of datafiles. This is attached to this PR in plexosdb Adds datafile text field for Data File object query plexosdb#15NOTE: The current implementation for variable and data_file querying is due for a refactor and cleanse... I will make a GitHub issue to specify my thoughts on the best path forward. The current implementation works, with one funky artifact- fields which have datafile scenarios specified, will have their properties duplicated in the output of
get_model_data. This impacts very few fields since most scenarios are applied to variables instead of datafiles.No impact on results but I throw a warning when duplicate fields replace each others data, but its all correct data replacing other correct data.