Analysis

The Analysis column in a testplan allows you to specify a literal simulation analysis directive. If an analysis statement begins with a period (.), DVM assumes that you have specified a valid simulation directive in the analysis field. The literal simulation directive is added to the appropriate section of the F11 window before the simulation is launched.

Valid analyses are:

  • .AC
  • .TRAN
  • .POP
  • .OP
  • .DC
  • .TF
  • .NOISE

Multiple-line analyses are supported with a \n to represent a new line.  For example, the following testplan entry:

.AC DEC 20 1k 1Meg\n.POP TRIG_GATE={TRIG_GATE} TRIG_COND=0_TO_1 MAX_PERIOD=1u\n.OPTIONS PSP_NPT=5001

Will be added to the F11 window as shown below:

.AC DEC 20 1k 1Meg
.POP TRIG_GATE={TRIG_GATE} TRIG_COND=0_TO_1 MAX_PERIOD=1u
.OPTIONS PSP_NPT=5001
Note: For time-domain waveforms to be generated, you must specify a .options PSP_NPT=n as in the example above. n is an integer greater than one. For more information see Controlling the Number of Data Points Output to the Data Group.

Use the following guidelines in constructing analysis statements:

  • If the specified analysis does not start with a period, it should be paired with an objective statement, and the value for the analysis must be one of the following:
  • If the specified analysis is not a recognized simulator analysis statement and is not paired with an Objective statement, no changes will be made to the analysis directives in the F11 window.
  • If either analysis or Objective is set to "NoSimulation," then no simulation will be run. Otherwise, the analysis should match up with the objective entry. The analysis statement can be left blank.