Prevent multiple applications of the scaling transform #2979
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.
Fixes # .
Summary/Motivation:
@andrewlee94 noted that the scaling transform caused problems because the
scaling_factor
Suffix was not deactivated after applying the transformation, which caused the resulting model to be doubly-scaled when written out to Ipopt. This updates the transformation to deactivate thescaling_factor
Suffixes on the transformed model at the conclusion of the transformation.In addition, this PR refactors the logic for finding the suffixes into a general-purpose
pyomo.core.base.suffix.SuffixFinder
class (so that it can easily be reused elsewhere, e.g. in GDP). It also removes the require ment that the scaling factor suffix values are forcibly converted to floats so that clients can use other data structures (in particular, mutable Params).Changes proposed in this PR:
scaling_factor
suffixes after the transformationfloat
before using them to update constraints.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: