-
Notifications
You must be signed in to change notification settings - Fork 42
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
Optimize twice #462
Optimize twice #462
Conversation
This reverts commit a5cde53.
…into optimize_twice
Let's focus on reformulation with Lines 378 to 385 in 4d32761
and it is populated a last time when Coluna does the reformulation (calls to To fix the bug, you must keep what is stored in MOI wrapper (because the model passes through MOI only once when |
I think for the first (with no reformulation and |
Codecov Report
@@ Coverage Diff @@
## master #462 +/- ##
==========================================
- Coverage 80.90% 80.84% -0.06%
==========================================
Files 51 51
Lines 4351 4354 +3
==========================================
Hits 3520 3520
- Misses 831 834 +3
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since optimize!(model)
returns nothing
, you don't test if it's really working. You should retrieve the objective value & the solution of the two runs and compare them.
For the reformulation, you can use the generalized assignment (using the call to ColunaDemos such as in full instance tests).
No description provided.