10.06.2016 Views

eldo_user

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Specifying Simulation Output<br />

Incremental Saving of the JWDB Database<br />

Thus the spacing of timepoints in the output file is generally non-constant. The<br />

maximum average density of timepoints in the output file is determined by the<br />

resolution parameter of the option. The minimum density is not guaranteed, neither<br />

locally, nor globally. This option is an interesting alternative, combining the certainty<br />

that the points in the output are computed points only (no interpolation error), and the<br />

ability to handle low activity periods efficiently. It is however, generally not well suited<br />

for simulations where an FFT must be computed, because of the non-constant spacing of<br />

the timepoints (this would result in interpolation errors when re-sampling for the FFT).<br />

• .OPTION INTERP=1 (in the Eldo Reference Manual)<br />

Both OUT_STEP and OUT_RESOL options dump only computed points to the output<br />

file. Sometimes it may be desirable to obtain equally spaced time points, but forcing<br />

timepoints (with OUT_STEP for example) would result in an unacceptable CPU<br />

penalty. In these cases, interpolating may be useful. An interpolation option is available<br />

to force Eldo to sample the output data along the parameter of the .TRAN<br />

command. If using the option INTERP=1, the transient output waveforms are<br />

interpolated, and the timepoints written to the file are aligned with multiples of <br />

exactly. For example, if using both the following:<br />

.tran 1ns 100ns<br />

.option interp=1<br />

the output waveforms will contain exactly 101 points (time 0 is always included),<br />

spaced by 1ns. Glitches shorter than 1ns may not be caught in the resulting waveform.<br />

This is a radical way to reduce the size of the binary output files (.wdb). However, the<br />

written data is obtained by interpolation, thus including an unpredictable amount of<br />

interpolation error. During low-activity periods, Eldo still picks the largest possible<br />

timesteps which enable the accuracy requirements to be met, and fills the output data<br />

with interpolated data (at no or little cost, as opposed to the OUT_STEP technique<br />

discussed previously).<br />

Related Topics<br />

Error and Warning Message Classification<br />

Error and Warning Messages<br />

Plotting, Printing and Probing<br />

Incremental Saving of the JWDB Database<br />

By default, Eldo sends simulation results to the JWDB server, which stores them in memory and<br />

then generates the .wdb file at the end of the simulation. To invoke incremental saving, forcing<br />

Eldo to save JWDB format simulation results in to a .wdb file before the end of the simulation,<br />

invoke Eldo with the -jwdb_threshold argument. Simulation results will be saved each time the<br />

simulation result size has reached threshold value (default is 100 MB).<br />

354<br />

Eldo® User's Manual, 15.3

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!