Skip to content

Temporarily Adjust NL Writer Feasibility Tolerance within PyROS#3280

Merged
blnicho merged 8 commits intoPyomo:mainfrom
shermanjasonaf:adjust-pyros-nl-writer-tol
Jul 9, 2024
Merged

Temporarily Adjust NL Writer Feasibility Tolerance within PyROS#3280
blnicho merged 8 commits intoPyomo:mainfrom
shermanjasonaf:adjust-pyros-nl-writer-tol

Conversation

@shermanjasonaf
Copy link
Copy Markdown
Contributor

Summary/Motivation:

Allow PyROS to temporarily adjust the NL writer feasibility tolerance before/after solving subproblems.

This change has been instituted to circumvent encounters with InfeasibleConstraintException arising from discrepancies between the Pyomo NL writer feasibility tolerance (pyomo.repn.plugins.nl_writer.tol) and the default feasibility tolerances for NL writer-based subsolvers, such as IPOPT, for which the default value of the (unscaled) feasibility tolerance is looser.

Changes proposed in this PR:

  • Allow PyROS to temporarily adjust the Pyomo NL writer feasibility tolerance.
  • Fix errors in PyROS restoration of IPOPT time limit specification for IPOPT >= 3.14.0.

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:

  1. I agree my contributions are submitted under the BSD license.
  2. I represent I am authorized to make the contributions and grant the license. If my employer has rights to intellectual property that includes these contributions, I represent that I have received permission to make contributions and grant the required license on behalf of that employer.

@blnicho blnicho requested a review from jsiirola June 4, 2024 19:04
Copy link
Copy Markdown
Member

@jsiirola jsiirola left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is fine, but we should add an issue to move the TOL from a module-level constant to a configuration option in the writer

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants