Update the PyROS Separation Priority Ordering Interface #3581
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
<
8000
/div>
7 tasks
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #3581 +/- ##
=======================================
Coverage 88.92% 88.92%
=======================================
Files 888 888
Lines 102347 102391 +44
=======================================
+ Hits 91009 91054 +45
+ Misses 11338 11337 -1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ 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
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.
Summary/Motivation:
Update the PyROS solver interface for specification of constraint separation priorities.
Changes proposed in this PR:
Suffixcomponents with local name"pyros_separation_priority"separation_priority_orderVarorConstraintcomponent declared on the model. Thus, for example, constraints derived fromVarbound specifications can be prioritized by mapping priorities toVarcomponentsNoneto be specified as a priority for equality and inequality constraints that are not to be robustly enforced. These constraints are enforced subject to only the nominal uncertain parameter realization, and are therefore excluded from the separation problems. Note also that equality constraints with a priority ofNoneare, therefore, not reformulated via coefficient matching or discretization, where otherwise applicableTODO
Legal Acknowledgement
By contributing to this software project, I have read the contribution guide and agree to the following terms and conditions for my contribution: