ANSYS Maxwell FAQs

-batchoptions "'Maxwell 3D/HPCLicenseType'='Pool'"

A sample Maxwell execution command containing the HPC pool license flag is shown below:

export TASKS_PER_NODE=8
for host in `cat $HOME/machinefile`; do echo "$host:$TASKS_PER_NODE:$RESCALE_CORES_PER_NODE:90%" >> $HOME/work/machinefile.maxwell; done
ansysedt -distributed -monitor -machinelist file=$HOME/work/machinefile.maxwell -batchoptions "'Maxwell 3D/HPCLicenseType'='Pool'" -ng -batchsolve my-maxwell-input-file.aedt

ANSYS Electronics has the option to specify the tasks manually or automatically for a distributed batch job. Please refer to the ANSYS Electromagnetics HPC Administrator's Guide for more information about automatic and manual mode.

Manual Mode

In this mode, users can specify the total number of cores and number of tasks per node (And hence, number of cores per task). In the command line, we can set the the environment variable, TASKS_PER_NODE to ' 2 ' , ' 4 ' , ' 8 ', ' 16 ' etc. Additionally, we need to delete the -auto flag.

For example, if we're using 8 cores for a job and we're setting tasks per node as 2, then each task will require 4 cores and this will result in a maximum of two tasks per host.

For the above example, the commands line on the Rescale platform will be as follows :

export TASKS_PER_NODE=2
for host in `cat $HOME/machinefile`; do echo ${host}:${TASKS_PER_NODE}:${RESCALE_CORES_PER_NODE}:90% >> $HOME/work/machinefile.maxwell; done
ansysedt -distributed -monitor -machinelist file=$HOME/work/machinefile.maxwell -ng -batchsolve rotational-actuator.aedtz

Automatic Mode

ANSYS Discourages the utilization of automatic task distribution on ANSYS Maxwell. Therefore Rescale suggests that users refrain from using the automatic option and maintain use of the manual function. Please refer to the ANSYS Electromagnetics HPC Administrators's Guide for more detailed information.

The default command line for ANSYS Electronics on Rescale platform has the placeholder . You can specfify one of the design option types in the placeholder by including the expression within quotes :

  • "[designName]" - batch solve all setups for design with the name given under the project.

  • "[designName]:Nominal" - batch solve all nominal setups for design with the name given under the project.

  • "[designName]:Optimetrics" - batch solve all Optimetrics setups for design with the name given under the project.

  • "[designName]:Nominal:[setupname]" - batch solve the specified nominal setup for design with the name given under the project. The setupname is case insensitive.

  • "[designName]:Optimetrics:[setupname] - batch solve the specified Optimetrics setup for design with the name given under the project. The setupname is case insensitive.

To solve only the nominal part given in the ANSYS Maxwell batch example, the command line will look like this -

export TASKS_PER_NODE=2
for host in `cat $HOME/machinefile`; do echo ${host}:${TASKS_PER_NODE}:${RESCALE_CORES_PER_NODE}:90% >> $HOME/work/machinefile.maxwell; done
ansysedt -distributed -monitor -machinelist file=$HOME/work/machinefile.maxwell -ng -batchsolve "Rotational_actuator:Nominal" rotational-actuator.aedtz

If the user is running Maxwell on Azure, the IB environment variables need to be set before the ansys command lines and additional batch options (-batchoption ” ‘<SOFTWARE>/MPIVendor’=‘Intel’ ”) need to be specified.

export I_MPI_DAPL_PROVIDER=ofa-v2-ib0
export I_MPI_DYNAMIC_CONNECTION=0
export I_MPI_DAPL_UD=0
export I_MPI_DAPL_TRANSLATION_CACHE=0
export I_MPI_FABRICS=shm:dapl
export TASKS_PER_NODE=2
for host in `cat $HOME/machinefile`; do echo ${host}:${TASKS_PER_NODE}:${RESCALE_CORES_PER_NODE}:90% >> $HOME/work/machinefile.maxwell; done
ansysedt -distributed -monitor -machinelist file=$HOME/work/machinefile.maxwell -batchoption ” ‘Maxwell 3D/MPIVendor’=‘Intel’ ” -ng -batchsolve rotational-actuator.aedtz