Hello everyone.
When using GAMS on Linux, it does not display “reading solution for model” if the solving process is interrupted.
Consequently, I must wait for the solver to finish to obtain the solution.
Is there a way to activate it for GAMS 47.2.0 using the SCIP solver?
Cordially.
I cannot reproduce this with model dice from gamslib:
+01 | 35.00%| unknown
0.4s| 1 | 0 | 1236 | - | 9226k | 0 | 120 | 114 | 230 | 164 | 16 | 4 | 0 | 2.700000e+01 | 2.000000e+01 | 35.00%| unknown
^Cpressed CTRL-C 1 times (5 times for forcing termination)
0.4s| 1 | 2 | 1236 | - | 9231k | 0 | 120 | 114 | 230 | 164 | 16 | 4 | 16 | 2.687223e+01 | 2.000000e+01 | 34.36%| unknown
SCIP Status : solving was interrupted [user interrupt]
Solving Time (sec) : 0.45
Solving Nodes : 1
Primal Bound : +2.00000000000000e+01 (2 solutions)
Dual Bound : +2.68722252325152e+01
Gap : 34.36 %
--- Reading solution for model xdice
--- Executing after solve: elapsed 0:00:00.625
--- dice.gms(94) 4 Mb
*** Status: Normal completion
--- Job dice.gms Stop 07/23/24 15:31:12 elapsed 0:00:00.625
Can you try if this works with dice? The code that SCIP executes might just ignore the signal and keep on going. The SCIP log mentions something about hitting Ctrl-C 5 times to force termination.
-Michael
Thank you, Michael, for your response.
I am encountering the same issue with the model dice:
No “reading solution” message exists when stopping or interrupting the solver.
However, I can get a “reading solution” when the solver finishes or if I set up a time limit.
Cordially.
Hi,
When using “Stop” it is actually expected, that you do not get the “reading solution” part, as “Stop” does a hard kill that should terminate everything immediately. With “Interrupt” this is a different story. It seems to behave the same as “Stop” on Linux, which is not correct. We need to check, how to improve this and will keep you updated about this.
Best,
Lutz