Repository navigation
Centring status - #3456
Centring status#3456
Conversation
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## latest #3456 +/- ##
==========================================
+ Coverage 75.12% 75.13% +0.01%
==========================================
Files 460 460
Lines 112155 112175 +20
Branches 17779 17787 +8
==========================================
+ Hits 84254 84287 +33
+ Misses 27619 27606 -13
Partials 282 282 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
filikat
left a comment
There was a problem hiding this comment.
Looks good.
Centring is only available for IPX (at least for now). Maybe in the reasons why the status can be kCentringStatusNone we should mention that it can also happen if HiPO is selected.
Opt-Mucca
left a comment
There was a problem hiding this comment.
Looks good! Two small questions:
- The instance takes a bit to solve (8s on my machine). Do we want this overhead to our tests? I'm not strictly against, but thought I should raise it.
- The comment from @filikat about whether this changes the HiPO execution path. Do we now skip fixings if HiPO is used? Can we even reliably use HiPO for these fixings if it doesn't currently have centering?
Also: TIL one can actually say centring. It looks funny.
|
Interior point methods usually return well centred solutions (before crossover). With the current changes, |
Thanks, @filikat. I am fine with updating this PR to use a method for querying whether a solution is well centred. |
|
That would probably be better. |
jajhall
left a comment
There was a problem hiding this comment.
This addresses the issue well, without compromising the general good behaviour of this valuable technique
Description
CentringStatus.Checklist
latestbranch