NLMON

Format

(1)	(2)	(3)	(4)	(5)	(6)	(7)	(8)	(9)	(10)
NLMON	`MONID`	`ITEM`	`INT`

Field	Contents	SI Unit Example
`MONID`	Nonlinear Monitoring Entry ID. No default (Integer > 0)
`ITEM`	Result type being monitored. DISP Indicates that the displacement results are being output and monitored. NO Indicates that monitoring is not active. No default
`INT`	Determines the result monitoring intervals. INC Outputs and monitors the final result of every increment. ITER Outputs and monitors the result of every iteration of every increment (Tcl script can be used to debug the nonlinear run for this option). No default 4

Field

Contents

SI Unit Example

MONID

Nonlinear Monitoring Entry ID.

No default (Integer > 0)

ITEM

Result type being monitored.

DISP: Indicates that the displacement results are being output and monitored.
NO: Indicates that monitoring is not active.

No default

INT

Determines the result monitoring intervals.

INC: Outputs and monitors the final result of every increment.
ITER: Outputs and monitors the result of every iteration of every increment (Tcl script can be used to debug the nonlinear run for this option).

No default 4

NLMON output consists of two parts, nonlinear runtime results monitoring via the <filename>_nl.h3d file, and additionally convergence table information for the specified intervals which is output to the .out file (and visualized via the os_out_file_parser.tcl script in HyperView). The convergence table information is currently only supported for Large Displacement Nonlinear Analysis. For more information, see Runtime Monitoring.
NLMON is currently supported for Small and Large Displacement Nonlinear static and Large Displacement Nonlinear Transient analysis only. By extension to Nonlinear Transient Analysis, it is also supported for Structural Fluid-Structure Interaction (FSI). NLMON is supported for Nonlinear Optimization runs.
The monitoring results are output to a separate H3D file named <filename_nl>.h3d.
When the number of increments is equal to the number of iterations, then the content of generated monitoring H3D file is equivalent to that of the primary H3D file written in an analysis.