eldo_user

Eldo Control Language
Tasks
Tasks
This section details the scripting constructs available within the Eldo Control Language.
In this section:
Task Definition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 814
Task Instantiation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 817
Statement Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 820
Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 839
Defining and Running Simulations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 841
Library of Functions for Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 854
Simulation Dynamic Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1014
Extended Simulation Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1024
Parallel Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1039
Statistical Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1058
Advanced Simulation Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1114
Task Definition
Tasks are defined as a sequence of statements, and are similar to functions in C. As opposed to
simulator commands in a regular Eldo netlist (for example, .TRAN, .AC, .OPTION, and so on)
which are executed more-or-less in parallel, statements inside a task are executed sequentially,
much like in most sequential programming languages.
A task may return nothing, in which case it is similar to a “void” C function. A task that returns
a value is a function.
A task definition starts with the .define_task keyword, and finishes with a .end_define_task
command. A task can accept input and output arguments (except when called from the netlist, in
which case the concept of an output argument is meaningless). The number of arguments is not
limited; a task may have no arguments at all. The names of output arguments must be prefixed
with a “@”. See Example Two.
Tip
See “.DEFINE_TASK” in the Eldo Reference Manual.
The statements inside a task are executed sequentially whenever the task is called, using the
. command. A task can be considered a user-defined (sequential)
simulation command.
814
Eldo® User's Manual, 15.3