Command Line
If you wish to set up batch or script files to run your analyses overnight or at times of the day when the processing load is lighter, it is possible to use command lines to run em from a batch file. You should also be aware that it is possible to setup batch files and assign run times using the analysis monitor. For directions on how to do so, please see How do I create a batch file to run multiple analysis jobs?
You should be aware that running from the command line does not provide all of the status information that is provided in the analysis monitor while running an analysis.
The syntax of the command line is as follows:
em -[options] <project name> [external frequency file]
where:
[options] is one or more of the run options shown in the table below. Note that other run options may be set in the Analysis Setup dialog box for your project and will be used during the analysis.
|
Option |
Meaning |
|
-Dlicense |
Used for debugging em licensing problems. Displays all environment information relevant to licensing. |
|
-N |
Display number of subsections and estimated required memory. Em then exits without running a full analysis. |
|
-test |
Run em on a test circuit. Used to verify that em can get a license and run successfully. |
|
-v |
Display analysis information as the analysis is performed. The analysis information is output to the command prompt window or terminal from which the batch was executed. |
|
-SubFreqHz[value]] where [value] is the subsectioning frequency in Hz. Note there is no space before the value field. |
This option allows subsectioning frequency to be specified on the command line, thereby overriding the settings in the project file. |
|
-AbsCacheNone |
Disable ABS caching (overrides setting in project file) |
|
-AbsCacheStopRestart |
Enable ABS stop-restart caching (overrides setting in project file) |
|
-AbsCacheMultiSweep |
Enable ABS multi-sweep plus stop-restart caching (overrides project file) |
|
-AbsNoDiscrete |
Used when running ABS with pre-existing cache data. Tells the analysis engine not to do any more discrete frequencies. If pre-existing cache data is sufficient to get converged ABS solution, then that solution is written to output. Otherwise, no processing is performed. |
|
-64BitForce |
This option forces the analysis to use 64-bit processing regardless of how much memory is required to analyze your circuit; the memory threshold is not used. |
|
-64BitThresh<mem> |
Memory threshold in MB to enable the 64-bit solver where <mem> contains an integer value identifying the memory threshold at which 64-bit processing is used. If this command is not used the threshold is set to 3600 Mbytes (3.6 Gbytes). |
|
-32BitForce |
This option forces the analysis to use 32-bit processing regardless of how much memory is required to analyze your circuit; the memory threshold is not used. |
|
NOTE: When using 32-bit processing, em can only access up to 4 GB of RAM on 64 bit Windows and 2 GB on 32 bit Windows. If you try to run problems larger than this limit, the analysis will run out of memory (even if you have more RAM) and stop. |
|
|
-ParamFile <filename> |
where <filename> is the name of a file which contains the value(s) which you wish to use for parameter(s) in the circuit being analyzed. These values override the value contained in the geometry project for the analysis, but do not change the contents of the geometry project. The syntax for the parameter file is <parname>=fnum where <parname> is the name of the parameter and fnum is a floating point number which defines the value of the parameter for the analysis. |
<project name> is the name of the project which you wish to analyze. If there is no extension, then the extension ''.son'' is assumed. This field is required.
[external frequency file] is the name of an optional external frequency control file whose extension is ''.eff''. This extension must be included when specifying the control file. You may create an external frequency control file in the project editor. For details see Frequency Sweep Combinations in online help in the project editor. The frequencies in this file override the frequencies in the project.
For example, if you wish to analyze the project steps.son in a batch file using the -v option, the command line would be:
em -v steps.son
An example of a batch file which runs multiple analyses is shown below:
em -v steps.son
em -v filter.son filter.eff
em -v airbridge.son filter.eff
em -v -AbsCacheMultiSweep airbridge.son
To execute a batch file on the PC, you should create a text file containing the command lines with a ''.bat'' extension. Then open a DOS prompt window and type the filename at the prompt and press return.
To execute a batch file on UNIX, create a text file containing the command lines. The filename does not need any extension. Then change the permissions mode of the file to allow you to execute it. For example:
chmod a+x <filename>
where <filename> is the name of the batch file you wish to execute. Then, type the name of the file at the UNIX prompt and press return.
On UNIX systems there are several additions to the command line which are useful to know. Placing ''nice'' before the command runs it at lower priority. Placing ”&” at the end of the command runs it in background, so you get your cursor back. Entering ”nohup” before the command line allows you to log off while the em job(s) keep running. If you are using the ”&” or the ”nohup”, you might want to consider redirecting the output using ”> outfile”. See your system administrator for details on any of these options.
