User Tools

Site Tools


solver:providing_additional_debugging_information_if_a_model_is_integer_infeasible

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
solver:providing_additional_debugging_information_if_a_model_is_integer_infeasible [2008/05/16 15:14]
support
solver:providing_additional_debugging_information_if_a_model_is_integer_infeasible [2008/05/16 15:15] (current)
support
Line 1: Line 1:
 ====== Providing additional debugging information,​ if a model is integer infeasible ====== ====== Providing additional debugging information,​ if a model is integer infeasible ======
-Q: //Is there any way to trace the infeasiblility cause by which equations/​constraints ( with =e=, =l= or =g= ), which set by the user, from GAMS when the modelstate = 10, ie 'No feasible integer solution could be found',​ has occurred? ​As whenever, modelstate = 10, GAMS simply terminated without knowing what exactly causing the infeasibility. ​//+Q: //Is there any way to trace the infeasiblility cause by which equations/​constraints ( with =e=, =l= or =g= ), which set by the user, from GAMS when the modelstate = 10, ie 'No feasible integer solution could be found',​ has occurred? ​ //
  
 Most MIP solver do not return a solution at all, if a problem is integer infeasible. If you check the lst file, you will see a messages like: Most MIP solver do not return a solution at all, if a problem is integer infeasible. If you check the lst file, you will see a messages like:
IMPRESSUM / LEGAL NOTICEPRIVACY POLICY solver/providing_additional_debugging_information_if_a_model_is_integer_infeasible.txt ยท Last modified: 2008/05/16 15:15 by support