DEBUG turns the DEBUG switch on. When this switch is on, TSP produces a great deal more printed output than it usually does. This output is normally not of interest to users, but may be helpful to a TSP programmer or consultant.
DEBUG ;
Usage
Include the DEBUG statement in your TSP program directly before the command(s) for which you want additional output. The DEBUG switch will remain on until a NODBUG statement is encountered. For DEBUG output during the compile phase of the program, see the ASMBUG statement.
Output
DEBUG should be used with care, since it normally produces a great deal of printed output. For example, every fetch and store to data storage (VPUT/VGET) is printed, which facilitates following the progress of the program, but can be voluminous. In the nonlinear procedures, all the input data and the results of the differentiation of the equations will be printed. For any estimation procedure, the matrices involved in the computations will be printed at every iteration.
Every input command line will be printed, before and after it has been interpreted for dates, dots, and lists. Several of the non-estimation procedures also produce special debug output when this switch is on.
DEBUG ;
LSQ (PRINT) EQNAME ;
NODBUG ;
This example causes debug output to be produced during the execution of a nonlinear least squares estimation.