Skip to content

Conversation

@mrmundt
Copy link
Contributor

@mrmundt mrmundt commented Oct 21, 2025

Fixes #3753

Summary/Motivation:

As part of #3753 and #3754, we decided that iteration_count should be removed as a default piece of information on the Results object (particularly because it's not well defined for certain solvers, e.g., MIP solvers). This instead downgrades iteration count to being an extra_info declaration, if desired, and is specific to each solver.

Changes proposed in this PR:

  • Remove iteration_count from defaults Results object
  • Adjust each individual solver to move iteration_count into the extra_info ConfigDict
  • Report ALL iteration counts from highs rather than whatever subset, with appropriate key-value pairs

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.

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.

highs iteration count always takes simplex iteration count

1 participant