Differences

This shows you the differences between two versions of the page.

--- howto:su2 [2015/03/03 15:40]
ccrosby
+++ howto:su2 [2022/11/02 16:10] (current)
ccrosby [Sample PBS script]
@@ Line 1: / Line 1: @@
 ====== Running the open-source code SU2 on the CHPC system ======
 ===== Introduction =====
-Please refer to [[http://su2.stanford.edu|the SU2 home page]] for more information on SU2, an open-source code targeted at aerodynamics and adjoint shape development.  The code has been installed in '''/opt/gridware/non-supported/SU2'''.
+Please refer to [[http://su2.stanford.edu|the SU2 home page]] for more information on SU2, an open-source code targeted at aerodynamics and adjoint shape development.  The current version of the code is 6.2.0, and has been installed in '''/apps/chpc/compmech/CFD/SU2'''.  There are modules for the SU2 versions installed on Lengau.  ''module load chpc/compmech/SU2/6.2-intel'' will set up the environment for the latest version, compiled with the Intel compiler.  There are also versions compiled with gcc/mpich and pgi/mpich.
-===== Environment =====
+===== Sample PBS script =====
-To set up a suitable environment for running SU2, add the following lines to your .bashrc file and ensure that they are sourced:
+When running in an interactive environment, SU2 makes use of python scripting to automate
+tasks.  For cluster running, it is necessary to ''qsub'' a PBS script.  This example executes the classic
+Onera M6 transonic wing example from the TestCases/euler/oneram6 directory.
-<code>
+<file bash runSU2.qsub>
-#### Setup environment for SU2, uses some OpenFOAM stuff,
+#!/bin/bash
-#### therefore start by setting up OpenFOAM-2.3.0 environment
+# This example script requests 3 nodes of the cluster, each with 24 processor cores
-. /opt/gridware/applications/OpenFOAM/OF230_fhm
+#PBS -P projectid
-module load /opt/gridware/bioinformatics/modules/python/2.7.5
+#PBS -l select=3:ncpus=24:mpiprocs=24:nodetype=haswell_reg
-export SU2_RUN="/opt/gridware/non-supported/SU2/bin"
+#PBS -q normal
-export SU2_HOME="/opt/gridware/non-supported/SU2/SU2"
+#PBS -l walltime=01:00:00
-export PATH=$PATH:$SU2_RUN
+#PBS -o /mnt/lustre/users/username/su2Jobs/job01/stdout
-export PYTHONPATH=$PYTHONPATH:$SU2_RUN
+#PBS -e /mnt/lustre/users/username/su2Jobs/job01/stderr
-</code>
+#PBS -m abe
+#PBS -M user@wherever.co.za
+#### Set up environment for SU2
+module add chpc/compmech/SU2/6.2-intel
+# Set the working directory environment variable explicitly.
+export PBS_JOBDIR=/mnt/lustre/users/username/su2Jobs/job01
+# Change to the job directory
+cd $PBS_JOBDIR
+nproc=`cat $PBS_NODEFILE | wc -l`
+### Run the SU2_CFD solver
+### For the gcc/mpich and PGI/mpich versions, use mpirun -iface ib0 ....
+mpirun -np $nproc SU2_CFD inv_ONERAM6_JST.cfg > SU2_CFD.out
+### Check to see if the solution_flow.dat file exists.  If it does,
+###  use it to generate the necessary output files.  If it doesn't,
+###  copy the restart file to solution_flow.dat and generate the output.
+### Make sure that these two file names are consistent with what you have
+###  used in the .cfg file for the run.
+if [ ! -e solution_flow.dat ] ;
+ then
+  cp restart_flow.dat solution_flow.dat
+fi
+### Build the specified format output files
+SU2_SOL inv_ONERAM6_JST.cfg > SU2_SOL.out
+</file>
-The OpenFOAM settings are merely there to ensure that some more recent libraries and utilities that were compiled for OpenFOAM are available.  SU2 has nothing whatsoever to do with OpenFOAM.
+===== Postprocessing =====
+By default, the SU2 example cases write Tecplot format output files.  CHPC does not have a license
+for Tecplot, although it is possible to read Tecplot files into Paraview.  However, in the SU2 input file
+it is easy to specify Paraview format output files (VTK) directly.  Refer to [[howto:remote_viz|the instructions on Remote Visualization]] to obtain a graphics environment for post-processing with VirtualGL and [[howto:paraview|Paraview]] or [[howto:visit|VisIt]].
+===== Scaling =====
+SU2 scales reasonably well, down to about 50 000 cells per core.  Performance with the Intel compiler is better than GCC or PGI.  Refer to the following graph:
+{{:howto:su2_scaling_6.2.png|}}

wiki.chpc.ac.za

User Tools

Site Tools

Differences

Page Tools