Differences

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

--- howto:ansys [2024/02/16 14:35]
ccrosby [Putting together a Fluent GPU job script]
+++ howto:ansys [2026/07/21 09:03] (current)
ccrosby [Exporting graphics during a run]
@@ Line 1: / Line 1: @@
 ====== ANSYS/Fluent ======
+===== Tutorial video - multi-node post-processing =====
+Up to v241 it is straightforward to do post-processing on a compute node, using the Mesa software-rendering library.  However, from v242 this is only possible with a GPU-equipped visualization node.  The process is illustrated in this [[https://youtu.be/MTlygZ9CpeA|tutorial video]].
 ===== Command line change required from v241 =====
-The v241 release of Fluent appears to parse the command line in a way that corrupts the text string returned from the ''$PBS_NODEFILE'' environment variable.  As a consequence, the slave MPI processes cannot be started up.  The simple fix is to "cat" the hostfile provided by PBS into a local file and then simply to use that instead.  This will also work for older versions.  Therefore, replace
+The v241 and later releases of Fluent appear to parse the command line in a way that corrupts the text string returned from the ''$PBS_NODEFILE'' environment variable.  As a consequence, the slave MPI processes cannot be started up.  The simple fix is to "cat" the hostfile provided by PBS into a local file and then simply to use that instead.  This will also work for older versions.  Therefore, replace
 <code>
 fluent 3d -t$nproc -pib -mpi=intel -cnf=$PBS_NODEFILE .....
@@ Line 56: / Line 59: @@
 v232 -> /home/apps/chpc/compmech/ansys_inc/v232
 v241 -> /home/apps/chpc/compmech/ansys_inc/v241
+v242 -> /home/apps/chpc/compmech/ansys_inc/v242
 </code>
@@ Line 170: / Line 174: @@
 </file>
+===== Exporting graphics during a run =====
+The CHPC gratefully acknowledges Alex Brocco for the following contribution.
+For very large parallel simulations, rendering and saving scenes natively within Fluent consistently fails, regardless of graphics driver or display settings. This occurs due to memory accumulation and host node bottlenecking.
+To bypass this bottleneck, it is recommended to set up Ansys EnSight DVS (Dynamic Visualization Store) export files using the following TUI command:
+<code> /file/transient-export/ensight-dvs-surfaces ... </code>
+This method is notably more memory‑ and CPU‑efficient than forcing the solver to render and save image files. It also supports real‑time monitoring of the simulation through Ansys EnSight via a live connection (currently untested on this cluster). Once the simulation has completed, scenes and animations can be visualized and saved by loading the DVS files into Ansys EnSight.
+Alternatively, if full flow-field data is required, one can use the following TUI command:
+<code>
+/file/transient-export/ensight-dvs-volumes...
+</code>
+However, this option is less efficient in terms of storage and I/O performance because data from the entire 3D volume is exported.
+**Note:** The trailing arguments of the TUI commands are case-specific. Below is a structurally valid journal execution sequence example for Ansys Fluent  2024  R1:
+<code>
+/file/transient-export/ensight-dvs-surfaces /mnt/lustre/users/jblogs/Stall_Sim/EnSight_ShroudPres in1:shroud_3_01 strut2:shroud_2_01 rot3:shroud_01 out4:shroud:1_01 () pressure () no "Export_ShroudPres" "time-step" 5
+</code>
+**Note:** If the files that are exported during multiple transient simulations are to be used as a set, all simulations must be executed on the same platform and with the same number of solver processes. This ensures that the resulting DVS files are structurally compatible and can be read together without partition mismatches.
 ===== Running Fluent on GPUs (experimental) =====
@@ Line 328: / Line 363: @@
+===== Running coupled fluid / structures models =====
+Alex Brocco of UP has done a tremendous job of not only devising how to run coupled models on the cluster, but has generously agreed to share his workflow in this document {{ :howto:systems_coupling_workflow.pdf |}}.
+Here is the example Python script {{ :howto:run_example_full.py.gz |}}. This is the example job script:
+<file bash CoupledJobScript.pbs>
+#!/bin/bash
+#PBS -l select=2:ncpus=24:mpiprocs=24
+#PBS -l cfd_base=1
+#PBS -l anshpc=44
+#PBS -q normal
+#PBS -P MECH1234
+#PBS -l walltime=0:20:00
+#PBS -o /mnt/lustre/users/jblogs/SystemCouplingTest/PBS_Out.out
+#PBS -e /mnt/lustre/users/jblogs/SystemCouplingTest/PBS_Err.err
+##### Running commands
+export LM_LICENSE_FILE=1055@login1
+export ANSYSLMD_LICENSE_FILE=1055@login1
+export FLUENT_ARCH=lnamd64
+### You may need the Intel compiler to be available
+module load chpc/parallel_studio_xe/18.0.2/2018.2.046
+### Mesa is needed to provide libGLU.so
+module load chpc/compmech/mesa/18.1.9
+export PBS_JOBDIR=/mnt/lustre/users/jblogs/SystemCouplingTest
+cd $PBS_JOBDIR
+nproc=`cat $PBS_NODEFILE | wc -l`
+AWP_ROOT232=/home/apps/chpc/compmech/ansys_inc/v232
+cat $PBS_NODEFILE > hosts.txt
+$AWP_ROOT232/SystemCoupling/bin/systemcoupling --connectiontimeout=200 --logLevel=2 --ic=infiniband --cnf=hosts.txt --sycnprocs=6 --nprocs=$nproc --runScript=run.py
+</file>

wiki.chpc.ac.za

User Tools

Site Tools

Differences

Page Tools