Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Report result_count in solution_summary by default #3138

Merged
merged 5 commits into from
Dec 9, 2022

Conversation

odow
Copy link
Member

@odow odow commented Nov 30, 2022

Closes #3136

The backstory to this is that https://discourse.julialang.org/t/mosek-does-not-give-the-optimal-value-derived-by-simplex-methods/90727 would have been a lot more obvious to debug if result_count was reported by default in solution_summary.

I'm open to other suggestions about how we could communicate this. The Solution #1 (default) comes from #3136, but it doesn't really apply when result_count = 0. Should we even report primal/dual status then?

@codecov
Copy link

codecov bot commented Nov 30, 2022

Codecov Report

Base: 97.68% // Head: 97.69% // Increases project coverage by +0.00% 🎉

Coverage data is based on head (e4d753f) compared to base (96f3477).
Patch coverage: 100.00% of modified lines in pull request are covered.

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #3138   +/-   ##
=======================================
  Coverage   97.68%   97.69%           
=======================================
  Files          33       33           
  Lines        4456     4460    +4     
=======================================
+ Hits         4353     4357    +4     
  Misses        103      103           
Impacted Files Coverage Δ
src/solution_summary.jl 97.50% <100.00%> (+0.13%) ⬆️

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report at Codecov.
📢 Do you have feedback about the report comment? Let us know in this issue.

@odow
Copy link
Member Author

odow commented Dec 8, 2022

@blegat suggests solution_summary(model; result::Int = 1)

@odow
Copy link
Member Author

odow commented Dec 8, 2022

@odow odow force-pushed the od/multiple-solution-summary branch from 0b1a0b5 to e4d753f Compare December 9, 2022 02:49
@odow odow merged commit 856dcc6 into master Dec 9, 2022
@odow odow deleted the od/multiple-solution-summary branch December 9, 2022 23:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

solution_summary should report multiple solutions
2 participants