eldo_user

Nodes/Devices Impacting Time-Step Adjustment
Analyzing Simulation Results
Performance Diagnostics
The performance diagnostics records the nodes and/or devices which impact the Eldo time-step
adjustment. The .FORMAT_STEP_LIMITERS command formats the output of the
performance diagnostics report.
The performance diagnostics generates the following outputs:
• Statistics about time-step computation are returned in the ASCII .chi file output, for
example:
Rejection due to no-convergence
100% (11/11) due to Node 2
Rejection due to Local-Truncation-Error (fast variation of signal)
100% (48/48) due to Node 2
Step limitation due to Local-Truncation-Error (fast variation of
signal)
100% (147/147) due to Node 2
Step limitation due to time-synchronization
54.3% (19/35) due to Signal on node 1
Other items not dumped because 15% of total number reached
Summary of contribution per X instance
100% (241/241) due to Top circuit
The statistics generated are:
o
o
o
o
Rejection due to no-convergence.
Lists the nodes and/or devices which caused Eldo to not converge at a given time
step, and which force Eldo to take a smaller time-step.
Rejection due to Local-Truncation-Error (fast variation of signal).
Lists the nodes/devices for which Eldo has detected too steep a variation, which
caused a time step to be rejected.
Step limitation due to Local-Truncation-Error (fast variation of signal).
Lists the nodes and/or devices which caused Eldo to limit the increase of a time-step
due to variation on the nodes/devices because it anticipates that the variation on
these items will be large.
Step limitation due to time-synchronization.
Lists the nodes and/or devices on which an input signal is applied, and which cause
time-step adjustment. Typically, Eldo forces points on the time point of a PWL
statement.
In each of the above sections, the nodes/devices are listed by order of importance: Eldo
reports the first SORT_MAX items, or the list of items which would count for at least
Eldo® User's Manual, 15.3 381