Add actual constraint numbers to mfile #3038
Merged
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
Enables identification of constraints.
ajpearcey
approved these changes
Feb 5, 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.
Enables identification of constraints: rather than having
normres001, normres002, ..., constr007, constr008, use the actual constraint numbers, e.g.eq_constr001, eq_constr007, ..., ineq_constr010, ineq_constr009. This allows the constraint to be identified from theMFILE.DATalone, instead of needing to cross-check with theIN.DATto find thatconstr007is actually constraint number 10. This also preserves the order in which the constraints are defined in theIN.DAT.