Re: [Gurobi] Solve inetrrupted + error code 10005

[Sonja Mars]

Hi,

Maybe you want to take a look at our error code page:
http://www.gurobi.com/documentation/5.6/reference-manual/error_codes

10005 indicates Attempted to query or set an attribute that could not be accessed at that time.

This means that you tried to do something in your callback that is not possible. You should check at the Callback Codes page (http://www.gurobi.com/documentation/5.6/reference-manual/callback_codes) that you are in the right “where” and only use the “what” things that are available.

Best regards,
Sonja

-----------------------------------------------------------------
Dr. Sonja Mars
Gurobi Optimization



On 04 Mar 2014, at 13:36, Hadi Panahi <pan...@gmail.com> wrote:

> So, I'm getting this error which says "solve interrupted <error code 10005>"
> and also" best obj -, best bound -, gap -
> also it says unable to retrieve the objval.
>
> I had written a callback in which it was improving the solution of a heuristic and some cases callback terminates the run. the status message is 11 which means solve interrupted.
>
> Is this a case of infeasibility or infinity? If yes, why it doesn't say inf or unbound instead?
>
> I saw there were two previous posts in this forum, but nothing much constructive ....
>
> Thank you for your response .
>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups "Gurobi Optimization" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to gurobi+un...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.

[Hadi Panahi]

[Hadi Panahi]

Thank Sonja for your response, I had seen the error codes and I do know about the compatibility of the "whats" in "where". Actually I wrote the sub problem model in a separate file and solved it separately and it said its either unbounded or inf, and after checking the model, I found it was unbounded. I corrected the coefficients in the objective function and every thing is fine now :)

Thank you.