The CHPC has an installation of Ansys-CFD along with a limited license for academic use only. The license covers use of the Fluent and CFX solvers, as well as the IcemCFD meshing code.
If you are a full time student or staff at an academic institution then you may request access to use Ansys-CFD on the CHPC clusters. Send your request along with motivation and description of the work in an email to
CFX version 5 is installed in
/apps/chpc/compmech/CFD/ansys_inc/v170/CFX. IcemCFD is installed under
CHPC has academic licenses for AnsysCFD. There are 5 “solver” processes, available as aa_r_cfd and 500 “HPC” licenses, available as aa_r_hpc. There is a license resource management system. If you request license resources (as in these example scripts), the scheduler will check for license availability before starting a job. License unavailability will result in the job being held back until the necessary licenses have become available. Although use of the license resource request is not mandatory, its use is strongly recommended. If you do not use the license resource requests, the job will fail if no licenses are available. A single aa_r_cfd license is required to start the solver, and includes up to 4 HPC licenses. Therefore you should request ($nproc-4) aa_r_hpc licenses.
On the CHPC clusters all simulations are submitted as jobs to the PBS Pro job scheduler which will assign your job to the appropriate queue and machine.
Example job script:
#!/bin/bash #PBS -P projectid #PBS -l select=4:ncpus=24:mpiprocs=24:mem=24GB:nodetype=haswell_reg #PBS -l walltime=2:00:00 #PBS -q normal #PBS -m be #PBS -V #PBS -o /home/username/testCFX/test.out #PBS -e /home/username/testCFX/test.err cd /home/username/testCFX #change to CFX case directory export CFX5RSH=ssh #force CFX to use ssh instead of rsh cfx=/apps/chpc/compmech/CFD/ansys_inc/v190/CFX/bin/cfx5solve #path to cfx5 solver $cfx -batch -def testCFX.def -par-dist $(tr "\n" "," <$PBS_NODEFILE) > runcfx.log
The “standard” process assumes that the user already has a local license for the software.
If your simulations files are too large, or your internet connection too slow, consider transferring geometry and script files only. This will require careful scripting and testing, but is certainly practical.
set term dumbto get funky 1970's style ASCII graphics.