wiki.chpc.ac.za

User Tools

Site Tools

You are here: start » howto » ansys
Trace:
howto:ansys

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
howto:ansys [2024/08/26 13:23]
ccrosby [Command line change required from v241] 		howto:ansys [2026/07/21 09:03] (current)
ccrosby [Exporting graphics during a run]
Line 1: Line 1:
 ====== ANSYS/Fluent ====== ====== 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 ===== ===== Command line change required from v241 =====
Line 171: Line 174:
  
 </file> </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) ===== ===== Running Fluent on GPUs (experimental) =====
/app/dokuwiki/data/attic/howto/ansys.1724671439.txt.gz · Last modified: 2024/08/26 13:23 by ccrosby

Page Tools

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial-Share Alike 3.0 Unported
CC Attribution-Noncommercial-Share Alike 3.0 Unported Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki