Hello Andrew !
Thanks for reply !
The problem is that the GMPL is not informed/knows anything about the
warning/divergence in the results and goes blindly.
Te exit code of glpsol also doesn't reflect anything that could be
detected, only by visual inspection of the output or redirect the output
and scan it for possible warnings.
Somehow GMPL should have a way to acknowledge situations like these.
===
>Exit code: 0
===
Cheers !
On 29/8/20 0:46, Andrew Makhorin wrote:
While trying to implement multi solve statements I found that in GMPL
the display of an objective function after solving do not show the
optimal value.
BTW, glpsol warns about that:
[...]
38 lines were read
Generating Reduced_Cost...
Generating Width_Limit...
Model has been successfully generated
glp_mpl_build_prob: row Reduced_Cost; constant term 1 ignored
[...]
