-
Notifications
You must be signed in to change notification settings - Fork 87
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
[Bridges.Constraint] add bridges in alphabetical order #2596
Conversation
I pulled out the I'll update this to focus only on |
a74fddc
to
950a540
Compare
c498e19
to
f0abce0
Compare
It's much cleaner like this, if we desire a priority over bridges, we should rely in explicit bridge cost, not bridge order. It also make sense that the bridges that we needed to add cost for are these soc to sdp ones. |
@@ -1751,13 +1750,13 @@ function test_bridge_selection() | |||
bridged_mock, | |||
MOI.VectorOfVariables, | |||
MOI.RotatedSecondOrderCone, | |||
) == MOI.Bridges.Constraint.RSOCtoPSDBridge{ | |||
) == MOI.Bridges.Constraint.RSOCtoSOCBridge{ |
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.
@blegat this test should have shown us the problem! It bridged RSOC to PSD, even though RSOC to SOC was available. It used to pick toPSD because that was the first bridge that was added.
No description provided.