Infeasable assumptions are not reported #4110
Replies: 1 comment 1 reply
-
So, maybe this is a bug, not sure. The conditions to use assumptions are tricky. For instance, parallelism is not supported, objective are not supported. I do not understand.
what happens if:
|
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
What version of OR-Tools and what language are you using?
Version:
main
,9.9.3956
Language: Java
Which solver are you using (e.g. CP-SAT, Routing Solver, GLOP, BOP, Gurobi)
CP-SAT
What operating system (Linux, Windows, ...) and version?
Linux, x86_64
What did you do?
I use "enforcement" variables to track down invalid constraints during development. When solving normally, they are simply
model.trueLiteral()
, but if that is proved infeasible, the model is recreated with real variables that are added as assumptions andstopAfterFirstSolution
set. CheckingsufficientAssumptionsForInfeasibility
after the second solve shows me which constraint groups caused the problem.What did you expect to see
A model that is infeasible to start with will never be feasible if the enforcement literals are replaced with assumed variables.
What did you see instead?
The second model reports OPTIMAL, but the solution is invalid. These are the (zipped, binary) protobufs of the two models:
Infeasible: hard-assumptions.bin.gz
Optimal: soft-assumptions.bin.gz
Beta Was this translation helpful? Give feedback.
All reactions