User Guide

B
-
6 File Types Used by the PSpice Optimizer
File T
y
pe Summar
y
Table 8-2 briefly describes all of the file types that the PSpice
Optimizer uses directly.
Table 8-2
Summary of PSpice Optimizer-Related File Types
File Type Source Description
.cir
.net
.als
generated by Schematics or
user-entered with a text editor
Circuit file, netlist file, and alias file, respectively. Define
components and connectivity, analysis directives, and simulation
control directives for the circuit. Refer to your PSpice user’s
guide
for more information.
.mdp
user-entered with a text editor External data file. Contains measured data to which the
optimization must adhere. (You can use any file extension for an
external data file.)
.olg
generated by the PSpice
Optimizer when running an
optimization
Optimization log file. Contains an optimization audit trail that is
useful as a debugging aid when the optimization doesn't
converge. Have this file available when contacting Technical
Support.
.oot
generated by the PSpice
Optimizer when generating a
report
Optimization report file. Provides a formatted description of the
optimization specifications and parameters, and results including
derivatives and Lagrange multipliers.
.opt
generated by Schematics when
activating the PSpice Optimizer,
or by the PSpice Optimizer
when saving results
Optimization file. Defines the optimization settings for the
circuit. When an optimization is complete, the PSpice Optimizer
saves results (on command) to this file. Schematics also reads
this file (on command) to back-annotate the schematic.
opt_0.dat
opt_1.dat
generated by the PSpice
Optimizer for each simulation
in a run
Interim data files. Contain simulation results which are read by
Probe to evaluate performance.
.par
generated by Schematics when
activating the PSpice Optimizer
and updated by the optimizer
when running an optimization
Parameters file. Contains the latest optimization parameter
values.