Execution settings:
| Name | Default value | Description |
|---|---|---|
| AEDT executable | for example, C:\Program Files\AnsysEM\AnsysEM21.1\Win64\ansysedt.exe (auto-detected, see additional notes) | Location of the AEDT executable. It is possible to use environment variables in the path string, e.g. ANSYSEM_ROOT241, and the marked names will be replaced by values at runtime. The variables expansion routine will detect and replace the two patterns %NAME% and ${NAME}, irrespective of the operating system optiSLang is currently working on. |
| Run mode | Single simulation |
The drop-down list of run mode options. They are described above under the section "Features in Detail". |
| Use a script snippet | False | Use a custom script snippet during the model solve routine. |
| Script snippet mode | False | Select from one of the following modes:
|
| Script path | False | Set the path to the script file. |
| No GUI | True | Define whether the AEDT analyses are running with open GUI or in the background |
| Solve via oProject.AnalyzeAll | False | When this option is active, the trigger for starting computations is not given for specific analysis or Optimetrics setups, but instead it is given globally in the form of the oProject.AnalyzeAll command. This means that any unsolved component in the project will be solved. |
| Wait for AEDT license | False | AEDT commands waiting for available license |
| Copy simulation results | Never |
This option determines whether to copy the *.aedtresults folder containing simulation data belonging to the reference project into the design folder before calculations start there |
| Copy further files | In this text field you can specify paths of files or folders to be copied along with the reference project into the design folder. Paths are expected to be relative to the folder containing the reference project, and only subdirectories are expected. Copied files will be placed under the same subdirectory path into the design directories. Multiple paths can be concatenated by commas. (Note: it is not necessary to specify AEDB folders here, as they will be copied automatically.) | |
| Copy geometrically equivalent meshes | False |
Sets the equally named flag in AEDT whenever creating Optimetrics variation tables in multi-design/DSO modes. |
| Save fields and mesh | False |
Sets the equally named flag in AEDT whenever creating Optimetrics variation tables in multi-design/DSO modes. |
| Design directory cleanup | None | This optional convenience cleanup function can cover either solely the .aedtresults folder or both the .aedt file and the .aedtresults folder. |
AEDT executable default value: While for other settings the default values are either coming from the ini files (see File Infrastructure for Default Values) or from hard-coded factory presets, the AEDT executable path setting is an exception to the pattern. The scheme is extended for this specific setting. If the corresponding ini file does not exist and a factory default value is required, there is not a simple fixed value being taken, but instead the value is supplied by a subroutine inferring the location of the AEDT executables based on scanning registry entries, environment variables, and most likely installation path options. If several installations are found, the latest is forwarded. A hard-coded default value comes only into play only as a last fall-back.
Flexibility when combining with scheduler submit modes: When AEDT computes simulations on cluster nodes, the program works in the same way as when running on your local machine, just with generally more resources. So, the run mode can be flexibly determined in pretty much the same way as if the execution takes place on your local computer. Therefore, in general, all run modes from the tab of Execution settings can be flexibly combined with options from the Scheduler tab.
Working with own run scripts in the custom run modes: See Features in Detail for more details to be found in and around the run mode breakdown schematic and particularly in Using Custom Scripts Snippets dedicated to the topic of custom run scripts.