tie...@math2.rwth-aachen.de
unread,Apr 3, 2012, 3:41:07 AM4/3/12Sign in to reply to author
Sign in to forward
You do not have permission to delete messages in this group
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Gurobi Optimization
I used lazy constraints in the following way:
callback with where == GRB_CB_MIPNODE, GRB_CB_MIPNODE_STATUS_STATUS ==
GRB_OPTIMAL
In this callback, it is checked for a violated constraint (lazy
constraint, possibly cutting away integer solutions).
This solution is cut away by adding the violated constraint via
callback -> addLazy()
(during this callback, node information (e.g. current lp solution) are
accessible as usual (in the separation callback)).
The procedure is very similar to the separation procedure, which would
only differ in using the addCut function instead.
Best regards
Martin