On Apr 4, 2011 7:36pm, Marcelo Pinto <address@hidden> wrote:
> However, when I ran a script that I know that the best > solution is 0.1% away from the optimal solution, the optimization > doesn't stop, even configuring 'param.mipgap = 0.1/100'.
> I couldn't analise what is happening yet, but maybe you fix it more quickly.
Please, post the script or the simplest thing the patch misbehaves with (all ok with the script you posted already?). Without having access to the code that you refer to, all I can say is
1) make sure you've GLPK 4.36+, 2) if so, check whether the solution makes sense (i.e. satisfies the constraints), 3) if you've access to them, compare the solution with those generated by CPLEX or Gurobi.