10.06.2016 Views

eldo_user

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Eldo Control Language<br />

Defining and Running Simulations<br />

Related Topics<br />

Defining and Running Simulations<br />

Generated Files<br />

When simulations are run, a number of files have to be generated on disk. By default, when the<br />

name and log parameters of the simulation command are not set, these files are generated in a<br />

temporary directory located in the Eldo outpath directory, named <strong>eldo</strong>_cl_simu_, with an<br />

automatically generated number appended, for example: <strong>eldo</strong>_cl_simu_12345.<br />

In this directory, you can find the generated netlist named by default, <strong>eldo</strong>_cl_simu.cir, and the<br />

simulation output log file named <strong>eldo</strong>_cl_simu.log. If the simulation failed, it is necessary to<br />

view this log file to understand why an error occurred. Any error listed in this log file will refer<br />

to the generated netlist <strong>eldo</strong>_cl_simu.cir.<br />

The generated netlist will be overwritten if many simulations are run successively (default<br />

behavior) which is contrary to the simulation output log file which is not overwritten<br />

(simulation log files of each simulation are appended). Therefore, backup files of the generated<br />

netlists are created in case it is necessary to find out which netlist was simulated. The first<br />

backup file is named <strong>eldo</strong>_cl_simu__1.cir, the second <strong>eldo</strong>_cl_simu__2.cir, and so on.<br />

For example, if a task defined in the file netlist.cir runs many simulations:<br />

.define_task many_simu<br />

set n = 0<br />

for (n=1; n

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

Saved successfully!

Ooh no, something went wrong!