When solving a model through pySMSpp/SMS++, solver progress is normally printed to the screen.
However, this does not seem to happen when using Gurobi through GRBMILPSolver: only the solver name is shown, and no further log/output appears.
By contrast, when using HiGHS through HiGHSMILPSolver, the full solver log is printed as expected.
Expected behavior
When using GRBMILPSolver, solver progress/log output should be visible on screen, similarly to what happens with HiGHSMILPSolver.
Actual behavior
With Gurobi, the only output shown is:
Solver: GRBMILPSolver
With HiGHS, the solver log is printed normally, for example:
Running HiGHS 1.13.1 (git hash: n/a): Copyright (c) 2026 under MIT licence terms
Solver: HiGHSMILPSolver
LP has 619503 rows; 329882 cols; 1388286 nonzeros
...
When solving a model through pySMSpp/SMS++, solver progress is normally printed to the screen.
However, this does not seem to happen when using Gurobi through
GRBMILPSolver: only the solver name is shown, and no further log/output appears.By contrast, when using HiGHS through
HiGHSMILPSolver, the full solver log is printed as expected.Expected behavior
When using
GRBMILPSolver, solver progress/log output should be visible on screen, similarly to what happens withHiGHSMILPSolver.Actual behavior
With Gurobi, the only output shown is:
Solver: GRBMILPSolver
With HiGHS, the solver log is printed normally, for example:
Running HiGHS 1.13.1 (git hash: n/a): Copyright (c) 2026 under MIT licence terms
Solver: HiGHSMILPSolver
LP has 619503 rows; 329882 cols; 1388286 nonzeros
...