User Tools

Site Tools


gams:continuing_subsequent_solves_in_a_loop_after_gams_execution_error_abort

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
gams:continuing_subsequent_solves_in_a_loop_after_gams_execution_error_abort [2015/01/21 13:02]
tlastusilta
gams:continuing_subsequent_solves_in_a_loop_after_gams_execution_error_abort [2015/01/21 13:03] (current)
tlastusilta
Line 8: Line 8:
 To entirely ignore execution errors, one can also reset the number of execution errors found after the solve statement. For example, suppose execerr=[n] has been specified during the GAMS call (either from the command line or in the IDE parameter box). One can reset the number of execution errors found during the previous solve to 0 by specifying in the model after the solve statement ''​execerror = 0;''​. For example: To entirely ignore execution errors, one can also reset the number of execution errors found after the solve statement. For example, suppose execerr=[n] has been specified during the GAMS call (either from the command line or in the IDE parameter box). One can reset the number of execution errors found during the previous solve to 0 by specifying in the model after the solve statement ''​execerror = 0;''​. For example:
 <​code>​ <​code>​
-  ​loop(numsolves,​+loop(numsolves,​
   solve model using lp minimizing obj;   solve model using lp minimizing obj;
   execerror = 0;   execerror = 0;
 ); );
 </​code>​ </​code>​
IMPRESSUM / LEGAL NOTICEPRIVACY POLICY gams/continuing_subsequent_solves_in_a_loop_after_gams_execution_error_abort.txt ยท Last modified: 2015/01/21 13:03 by tlastusilta