To debug errors in your user routines, you can use commands and other features not documented in the Command Reference. Use these commands only for extremely small models with few solution iterations (otherwise, they will generate an excessive amount of output). /TRACK and /DEBUG are described in detail below. Two other useful commands are OUTEQ and /NERR. The command OUTEQ,ON can be used to output results from all equilibrium iterations. The command /NERR,,,-1 causes errors to be reported as before, but the run continues anyway, normally terminating with either a) system abort or b) incorrect answers. The /NERR,,,-1 command is intended for program debugging and may generate erroneous results. You should remove this statement before generating solutions for production use.
The /TRACK command issues a message when the
program logic enters and leaves some of the higher level subroutines. Subroutines
TrackBegin and TrackEnd (see Subroutines for Your Convenience) set up the /TRACK
command. Then, issue the command using the format below
/TRACK,MonLevel,PrintLevel,SumLevelMonLevel
The level for timing monitoring.
PrintLevel
The level for enter/exit printout.
SumLevel
The level at which the timing sum is output.
Each of these arguments can be any value between 0 and 9 (default is 0).
You can use the /TRACK command to identify which section of code is causing the program to abort. For example, to flag up to eight levels of subroutines to determine when the program logic enters and leaves them, you would issue the command /TRACK,,8.
The /DEBUG command generates debugging at various points in the output. You can specify one of three formats for /DEBUG: solution debug format, element debug format, and general debug format.
Issue the command using this format:
/DEBUG,-1,F1,F2,F3,F4,F5,F6,F7,F8,F9F1
1 (provides basic solution control debugging)
F2
1 (provides transient debugging using Newmark constants)
2 (provides transient debugging using velocities and accelerations)
F3
1 (provides element matrix debugging and prints matrix + load vectors, before going into solve)
2 (provides element matrix debugging with load vectors only, before going into solve)
3 (provides element matrix debugging with matrix diagonals and load vectors, before going into solve)
F4
1 (provides auto time stepping debugging)
F5
1 (provides multifield debugging)
F6
1 (provides arc-length debugging)
F7
1 (provides basic Newton-Raphson debugging)
2 (provides Newton-Raphson debugging and prints out-of-balance forces or incremental displacement or each DOF)
3 (provides Newton-Raphson debugging and prints applied loads and n-r restoring force for each DOF)
F8
1,2 (provides displacement vector debugging with displacement pointers)
2 (provides displacement vector debugging with incremental displacement)
3 (provides displacement vector debugging with contact database)
F9
1 (provides temporary programmer debugging)
Issue the command using this format:
/DEBUG,-3,G1,G2,G3,G4,G5,G6,G7,G8,G9G1
1 (provides basic element pass debugging)
G2
1 (provides element displacement and coordinate debugging)
G3
1 (provides element matrix debugging and prints matrix + load vectors, after the element routines)
2 (provides element matrix debugging with load vectors only, after the element routines)
3 (provides element matrix debugging with matrix diagonals and load vectors, after the element routines)
G4
1 (provides element load information debugging)
G5
1 (provides element real constant debugging)
G6
1 (provides element saved variable debugging)
G7
1 (provides element material property debugging with linear material properties)
2 (provides element material property debugging with nonlinear properties)
G8
1,2 (provides element nonlinear debugging with plasticity)
2 (provides element nonlinear debugging with large deformation)
3 (provides element nonlinear debugging with contact database)
G9
1 (provides temporary programmer debugging)
Issue the command using this format:
/DEBUG,H1,H2,,H4,H5,,,,H9H1
1 (provides file header record information)
2 (provides input line (character))
3 (provides input line (decoded))
H2
1 (provides element reordering and element checking debugging)
2 (provides meshing debugging)
H4
1 (provides nodal coordinate system transformation debugging)
2 (provides displacement updating debugging)
H5
1 (provides pre-element debugging, element characteristics debugging, and element field load debugging)
H9
-1 (print the progress of the resume (or save) to isolate location of failure)
-99 (resume only the command log information for subsequent LGWRITE command)