Update optimize model config output #2990
Closed
Conversation
This file contains 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
…S/2939-optimize-utilize-dill
…RPA-ASKEM/TERArium into TS/2938-optimize-output-model-config
This was referenced Mar 19, 2024
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.
Description
When running optimize the output should save some interventions in metadata. To be discussed post evaluation if we want to include any of this in rate laws (i suspect not) and how we want to utilize these
This means i get to clean up this disaster:
Blocked
Will want to look into our other solution for this utilizing model metadata timeseries that is currently being used and determine which solution is better long term.
Currently pyciemss-service of course only works with the timeseries solution
Running with multiple policy bounds is currently broken. Anirban is looking into this