DEBUG
The DEBUG statement outputs data that helps you debug a simulation.
Format
Arguments
DOF | Prints a degree-of-freedom table in the tabular output file. This table tells whether or not each of the six components of motion (that is, translation along the x-axis, y-axis, and z-axis and rotation about the x-axis, y-axis, and z-axis) is constrained for each part center of mass relative to the origin of the ground coordinate system (GCS). These are the degrees of freedom as input. Default: Off |
DUMP | Writes the internal representation of a dataset in the Tabular Output file after Adams Solver (FORTRAN) reads and checks the input. This facility essentially maps the equations and variables in the system and provides their numeric codes. Default: Off |
EPRINT | Prints a block of information for each kinematic, static, or dynamic step. This information helps you monitor the simulation process and locate the source of the error if there is a problem. Each step consists of two phases: 1) a forward step in time (the predictor for dynamics) and 2) the solution of the equations of motion (the corrector for dynamics). For the first phase, Adams Solver (FORTRAN) prints three or four pieces of information. The information includes: ■The step number. This is a running count of the number of steps taken and can be used as a measure of how hard Adams Solver (FORTRAN) is working. ■The order of the predictor for dynamics. This corresponds to the order of the polynomial Adams Solver (FORTRAN) uses to predict the solution at the end of the integration step. ■The value of time at the beginning of the step. ■The size of the step. For the second phase, Adams Solver (FORTRAN) prints out the cumulative number of iterations and a table of information about the iterations. The cumulative number of iterations is a running count of the iterations needed to solve the equations of motion and can be used as a measure of how many computations Adams Solver (FORTRAN) is performing. The table contains information about the largest equation imbalance (error) and maximum variable change for each iteration. For each iteration, Adams Solver (FORTRAN) prints out seven or eight pieces of the following information: ■The iteration number. This is one at the beginning of each step and increments by one until Adams Solver (C++) converges to a solution or exceeds the maximum allowable number of iterations. ■The absolute value of the largest equation residual error. Each equation should have an error value close to zero. This number is an indicator of how far Adams Solver (FORTRAN) is from a solution. This number should decrease after every iteration. ■The dataset element associated with the largest equation residual error. ■The equation that has the largest equation residual error for the above dataset element. ■The absolute value of the largest change in a variable. The final iteration should not need to change variables very much. This number is an indicator of how aggressive Adams Solver (FORTRAN) needs to change variables to approach a solution. This number should decrease after every iteration. ■The dataset element associated with the absolute value of the largest change in a variable. ■The variable with the largest change for the above dataset element. ■If Adams Solver (FORTRAN) has updated the Jacobian, YES appears under the new Jacobian header. Default: Off |
JMDUMP | Dumps the Jacobian matrix at each iteration. Default: Off |
REQDUMP | Dumps the REQUEST and MREQUEST statement output at each iteration. Default: Off |
RHSDUMP | Dumps the YY array (state vector), RHS array (error terms), and DELTA array (increment to state vector) at each iteration. Default: Off |
VERBOSE | Outputs to the screen such additional information as the name of the subroutine from which Adams Solver (FORTRAN) sends each diagnostic, explanations, and possible remedies (when available). When you do not include the VERBOSE argument, Adams Solver (FORTRAN) outputs only the basic error messages to the screen. In either case, Adams Solver (FORTRAN) outputs the information to the Message file. Default: Off |
MATLAB | When specified in conjunction with the RHSDUMP or JMDUMP flags it changes the output format to be such that the debug information can be easily imported into Matlab. Importing for example the Jacobian matrix in Matlab can be useful for purposes such as computing the condition number of the Jacobian, its norm and so on. |
Caution: | An indiscriminate use of the arguments JMDUMP and RHSDUMP can result in an extremely large tabular output file. If a dataset needs to be debugged, include these arguments in the DEBUG statement and execute only a brief simulation. |
Extended Definition
The DEBUG command section contains additional descriptions on the information returned by DEBUG/EPRINT command.
Examples
DEBUG/EPRINT
This DEBUG statement generates the information in Figure 4 that appears in the message file.
In this example, Adams Solver (FORTRAN) is printing the information for the third step of a dynamic analysis. For this step, Adams Solver (FORTRAN) uses a second-order polynomial to guess the solution. Using a time step of 7.25694E-04, the integration step goes from 6.458333333E-04 to 1.371527778E-03.
After the first iteration, the z velocity equation of PART/245330 has the largest error: its absolute value is 2E+00. The z coordinate of PART/245330 changes the most during the first iteration. The absolute value of the change is 8.E-04. Adams Solver (FORTRAN) updates the Jacobian before the first iteration, but not before the second or third.
Figure 4 Sample EPRINT Information
See other Analysis parameters available.