eldo_user

Running Eldo
Performance Bottleneck Diagnostics
used on the network. More details are available in the Pyxis Project Manager User’s
Manual.
• INCLUDE
The optional INCLUDE keyword enables the inclusion of the contents of another file by
reference. The included files must not contain a header.
Examples
Here is an example mgc_location_map file, showing a soft pathname with no hard pathname, a
soft pathname mapped with two hard pathnames, and an include line:
MGC_LOCATION_MAP_2
#Here is a soft pathname with no hard pathname.
$REF_DIR
#Here is another soft pathname mapped with two hard pathnames.
$SOURCE_PROJECT
/home/user/projxxx
/mnt/remote_device/home/user/projxxx
#Here is an include file.
INCLUDE /usr2/home/maps/locmap2
For the soft pathname, $REF_DIR, with no hard pathname, there must be an environment
variable named REF_DIR; Eldo imports the hard pathname contained in that variable and maps
REF_DIR with that imported hard pathname.
Related Topics
Invoking Eldo
Performance Bottleneck Diagnostics
A set of diagnostics are available to help you understand why a circuit does not behave as
expected, or takes more time than expected to simulate.
These diagnostics can be triggered with the -diagmode command line argument as follows:
• -diagmode perf
Enables a set of performance diagnostics (command line argument -devcpu and
command .format_step_limiters) to help you understand why a circuit does not behave
as expected, or takes more time than expected to simulate. Equivalent to -debug.
• -diagmode conv
Enables the analysis of non-convergence issues. When Eldo stops because of a nonconvergence
a file is generated named .noconv, used as an input for the
convergence analysis. Supported by Eldo Classic only.
• -diagmode tstep
Eldo® User's Manual, 15.3 55