Closed rinde closed 1 month ago
@alexhoen
We already are aware of this issue but unfortunately we did not have a well conditioned instance where we could reproduce the issue. Since your instance only contains binary variables and integer coefficients this should be way easier to debug. Thank you very much for sharing.
To solve for problem for now you cannot think of disabling multiaggregation in Papilo until we can provide a fix. This should not impact the performance tremendously.
Just set the bool parameters presolving/milp/enablemultiaggr to false.
Glad I could help!
So the problem was that PaPILO suggested some substitutions that lead to immediate fixings. PaPILO would eventually detect them but in the meanwhile SCIP complained that PAPILO was trying to manipulate already fixed variables.
An example would be 2x +y = 2 with binary variables x,y. Only x=1 and y= 0 is a feasible assignment.
We fixed this now and PaPILO should find these fixings before applying the substitution. Could you please checkout https://github.com/scipopt/papilo/commit/b4051e3002abdc6a9a3042c985c1e6978437b0e3 and see if the error still persists.
With scip@f72aa6b0 this should also safely pass in optimized mode for previous PaPILO versions.
Scip errors on the input in this file problem2.cip.txt (I added the
.txt
for GitHub)The model was built programmatically, when I save it to
.mps
it doesn't error.Here is the log when running
scip -f problem2.cip
: