Map parameter functions to JuMP.Parameters #389
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
…levant unit tests
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #389 +/- ##
==========================================
- Coverage 99.69% 99.67% -0.02%
==========================================
Files 36 36
Lines 6810 6821 +11
==========================================
+ Hits 6789 6799 +10
- Misses 21 22 +1 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Currently, parameter functions are mapped to an array of scalar values corresponding to each of its supports. This array is not stored in the mappings, and values generated by the parameter function can only be updated by remaking the JuMP backend from scratch. This PR makes it easier to update the scalar values by transcribing them as
JuMP.Parametersinstead, avoiding the need to remake the JuMP backend.This builds off the JuMP.Parameter functionality developed in #387.