The ANSYS suite of programs is available on the ITS-RS HPC systems.
To use them, you will need to have access to a license server that will validate your right to use the software. The license servers are not run on the HPC systems so please check with your department for more information.
Use of the Ansys suite differs slightly between the two clusters. One difference is that on Neon, there is a "fluent" parallel environment. If running on Neon, this pe should be used.
Also, the command line flags used with Ansys have changed somewhat in version 18.x to accommodate a new interconnect called Omni-Path. Note the differences in the two scripts below:
#!/bin/sh # #$ -N Job_Name #$ -cwd #$ -j y #$ -pe fluent 32 #$ -S /bin/bash /opt/ansys_inc/v121/fluent/bin/fluent 3ddp -t$NSLOTS -g -cnf=$TMPDIR/machines -sge -pinfiniband -mpi=openmpi -i File.in > File.out
#!/bin/sh # #$ -N Job_Name #$ -cwd #$ -j y #$ -pe 56cpn 112 #$ -S /bin/bash module load ansys/18.0_impi-2017.4 fluent 3ddp -t$NSLOTS -g -cnf=$TMPDIR/machines -sge -pib.infinipath -mpi=intel -i File.in > File.out
On Neon, versions 15.0.7 and 17.2 of Ansys are available. Argon provides versions 17.2 and 18.0. When running Ansys programs on Argon, the -pib.infinipath must be explicitly stated for interconnect selection and the MPI implementation chosen must be mpi=intel. If these are not specified, the job will either fail outright or fall back to a much slower interconnect, severely curtailing performance. If using the Fluent application on Argon, you are free to choose any appropriate parallel environment, there is not a dedicated fluent PE as on Neon. In addition, the environment modules that set the necessary variables and paths on Argon are not currently the default Ansys modules. When loading environment modules on Argon, ensure that you are using either ansys/17.2_impi-2017.4 or ansys/18.0_impi-2017.4 for your jobs.