Cut callback
Hi folks,
I was using the gurobi cut callback via its C API and noticed some "wrong" results. For a given feasible model, when user cuts (they are valid cuts by design and we also check their validity using the optimal solution) were separated and added, we noticed that Gurobi declare this model is infeasible. While we turn off user cuts, Gurobi could identify the optimal solution. Attached below are the screenshots of our C++ codes about how we use the cut callback. Anybody has insights about this? I'm wondering, when user cuts are added to Gurobi, does Gurobi further process them (like strengthening them)? Any comments would be appreciated.
-
Official comment
This post is more than three years old. Some information may not be up to date. For current information, please check the Gurobi Documentation or Knowledge Base. If you need more help, please create a new post in the community forum. Or why not try our AI Gurobot?. -
Hi,
Can you also post some log files for these runs (of if they are to long snippets from the log)? I am wondering if this could be a numerical issue.
Additionally, please note, user cuts need to be globally valid. Gurobi does not support local valid cuts.
Best,
Sonja
0
Post is closed for comments.
Comments
2 comments