Run AcuSolve on Linux Servers
AcuSolve can be run on Linux servers in the following ways.
- With AcuSolve environment sourced
- acuRun -pb <problem name> -np <number of processors> -nt <number of threads>
- Without AcuSolve environment sourced
- <Installation-Path>/altair/hwcfdsolvers/acusolve/linux64/bin/acuRun -pb <problem name> -np <number of processors> -nt <number of threads>
On servers with PBS/LSF/CCS, the PBS environment variables need to be set. They can be set in the command line or through a script. Here is an example of such a script.
#! /bin/sh -f
PBS -N <problem name>
PBS -o <problem name>.log.pbs
PBS -e <problem name>.error.pbs
PBS -l select=<np/ppn>:ncpus=<ppn>:mpiprocs=<ppn>
PBS -l walltime=00:2880:0
PBS -l place=scatter
PBS -l place=group=chassis
set -v
cd <working directory>
acuRun -pb <problem name> -np <number of processors> -nt _auto -do all -pbs_attach -pbs
On servers with PBS/LSF?CCS, acuSub is the most efficient way to run AcuSolve. Refer to the AcuSub section in the AcuSolve Programs Reference Manual for more information.
AcuSolve-MotionSolve Two-Way Coupling Job Submission on Linux Servers using Command Line Options
AcuSolve-MotionSolve two-way coupling can be executed through the terminal/command line or through shell scripts on Linux servers with various options.
< Installation-Path > hwsolvers/motionsolve/bin/linux64/acuMSI -aport <APORT> -mport <MPORT>
- -aport <integer>
- Specifies the communication port number for communication between AcuSolve and acuMSI. The default is 48000. If you need to change the default port for communication between AcuSolve and acuMSI, in addition to changing this argument, you also have to specify the changed port number in the AcuSolve input file.
- - mport<integer>
- Specifies the communication port number for communication between MotionSolve and acuMSI. The default is 94043. If you need to change the default port for communication between MotionSolve and acuMSI, in addition to changing this argument, you also have to specify the changed port number in an environment variable MS_AS_PORT. MotionSolve checks for this environment variable at the start of the simulation and changes its listening port accordingly.
- Through hwsolver.tcl
- < Installation-Path>/altair/hw/common/acc/scripts/hwsolver.tcl -solver MS -nt <MotionSolve threads> -file <MotionSolve input file>
- Through MotionSolve executable
- <Installation-Path>/altair/scripts/motionsolve -file <MotionSolve input file>
- With AcuSolve environment sourced
- acuRun -pb <problem name> -np <number of processors> -nt <number of threads>
- Without AcuSolve environment sourced
- <Installation-Path>/altair/hwcfdsolvers/acusolve/linux64/bin/acuRun -pb <problem name> -np <number of processors> -nt <number of threads> -ecport <APORT>
You can also create a script with PBS environment variables set to execute all of these commands. Here is an example of such a script.
#! /bin/sh -f
#PBS -N <problem name>
#PBS -o <problem name>.log.pbs
#PBS -e <problem name>.error.pbs
#PBS -l select=<np/ppn>:ncpus=<ppn>:mpiprocs=<ppn>
#PBS -l walltime=00:2880:0
#PBS -l place=scatter
#PBS -l place=group=chassis
set -v
cd <working directory>
<installation-path>/hwsolvers/motionsolve/bin/linux64/acuMSI &
<installation-path>/altair/scripts/acc -solver MS -nt <number of threads> <MotionSolve xml input file> &
acuRun -pb <problem name> -np <number of processors> -nt _auto -do all -pbs_attach -pbs