Output management

Top  Previous  Next

GAMS modelers sometimes complain that they want a more concise output file.  All the program listings, limrow/limcol output, intermediate data displays, solver output, cross-reference maps etc are not always desirable.  One-way of managing this output is through save and restarts.

Suppose we add a fourth file (trandisp.gms) to the transportation system that contains only display statements.

 

GAMS trandata                  s=s1

GAMS tranmodl        r=s1      s=s2

GAMS tranrept        r=s2      s=s1

GAMS trandisp        r=s1  (note reuse of name)

 

with the trandisp.gms file looking as follows

 

OPTION DECIMALS=0;

DISPLAY MOVEMENT,COSTS;

OPTION DECIMALS=2;

DISPLAY DEMANDREP, CMOVEMENT, shipments.l;

 

This mechanism creates "to the point" LST files but allows other output to be resident in other LST files if needed.  Also one can activate or deactivate certain displays and rapidly choose relevant output for a study while maintaining other potential output in the system.