Specifying Options for Interactive Scheduler Jobs

Batch scheduler jobs use command line options for specifying options rather than GUI controls. For interactive scheduler jobs, options may be specified on the command line, using GUI controls, or obtained from the registry. The machines specified in the Configurations tab of the HPC and Analysis Options dialog will be ignored for interactive scheduler jobs. If the command line used to launch the product contains a list of specific machines (using option -machinelist list=...), then the job will use the specified machines and cores. If the command line used to launch the product does not contain a specific machine list, then the machines and cores allocated to the job by the scheduler will be used for the job. In general, the job distribution settings for interactive scheduler jobs should be specified on the command line, instead of using the HPC and Analysis Options dialog box.

• The UI shows the settings that will be used for analysis, even if they come from the command line, not the registry.
• If you make changes to the settings in the UI, and the changed settings will be used for the analysis, even if the changed settings conflict with the command line (including batchoptions).
• If you makes no changes to the settings in the UI, then the command line settings (including batchoptions) will be used for analysis.

Batchoptions settings which are automatically generated for batch jobs submitted using the Ansys Electromagnetics job submission GUI will need to be manually included in the product command line. Some use cases require that certain settings be made on the command line when the product is launched, rather than using the GUI.

Batchoptions for Interactive Scheduler Jobs

For interactive scheduler jobs, only a limited set of batchoptions are supported. These batchoptions include the DSO configuration options, the design-type-specific options, and the following additional design-type-specific options that are not currently listed in the user interface or command line help windows:

• CreateStartingMesh: Create the starting mesh only. Do not solve any other steps. Often used for multi-step jobs where the mesh creation is solved in a separate step using fewer resources than the rest of the analysis.
• NumCoresPerDistributedTask: Specifies the number of cores that are allocated to the job to use for each distributed task, used when running jobs under a scheduler. The scheduler communicates the number of cores allocated to the job on each host. This setting is used to determine how to allocate the cores to each task.
• RAMLimitPercent: Specifies the percentage of system RAM that the analysis is expected to use on each host. Running out of memory can cause processes to be killed by the Operating System or other failures. The analysis will be gracefully terminated if it requires more than this limit. Typical limits are about 90%, to allow some RAM for the Operating System and other services. If there are multiple jobs running on a single host, then the RAM limit should be reduced accordingly. For example, if there are two jobs running on a host, then the limit could be 45%, which would allow 10% of the RAM for the Operating System and other services.
• RAMLimitPerCoreInGB: This is an alternative way to specify the RAM limit, instead of using the RAMLimitPercent. In this case, the RAM limit is the limit per core multiplied by the number of cores allocated to the job on each host. Typically used for jobs running under a scheduler to ensure that the scheduler memory limit and the ansysedt memory limit are consistent.
• SolveAdaptiveOnly: Solve adaptive passes only. Do not solve any other steps. Often used for multi-step jobs where the adaptive passes are solved in a separate step using fewer resources than the rest of the analysis.
• TotalNumOfCores: The total number of cores for the job. This option is only used for EKM (Engineering Knowledge Manager).
• ValidateOnly: Only validate the specified setup, design, or project. Do not analyze the specified setup, design or project.

Any other batchoptions will result in a warning message and will be ignored.

Command Line Example:

desktopjob.exe" -cmd dso -jobid RSM_27086 -machinelist list=localHost:2:2:90%

-monitor -ng -batchoptions " 'LargeScaleDSO/MergeCsv'='acrossDPsAndTraces'"

-batchsolve TeeModel:Optimetrics:ParametricSetup2 E:\work\2018\LS_DSO\OptimTee.aedt

desktopjob.exe" -cmd dso -jobid RSM_25248 -machinelist list=localHost:2:2:90%

-monitor -ng -batchoptions " 'LargeScaleDSO/MergeCsv'='acrossDPsByRow'"

-batchsolve TeeModel:Optimetrics:ParametricSetup2 E:\work\2018\LS_DSO\OptimTee.aedt

ansysedt -batchoptions " 'TempDirectory'='C:\\TEMP'

'HFSS/SelectedDSOConfiguration'='Local'

'Desktop/Settings/ProjectOptions/DoAutoSave'=1

'LargeScaleDSO/MaxFolderInMB'=100"