Differences

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

--- howto:ansys [2026/07/20 16:18]
ccrosby Added section by Alex Brocco on exporting images.
+++ howto:ansys [2026/07/21 09:03] (current)
ccrosby [Exporting graphics during a run]
@@ Line 179: / Line 179: @@
 The CHPC gratefully acknowledges Alex Brocco for the following contribution.
-For large parallel simulations, rendering and saving scenes natively within Fluent consistently fails, regardless of the graphics driver used or whether the display window is reset. Since the failure occurs regularly, it is highly likely that the visualizations are exceeding available single-node memory limits due to memory build-up.
+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, set up Ansys EnSight DVS (Direct Visualization Server) export files using the following TUI command:
+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 significantly more memory and CPU efficient compared to forcing the solver to render and save image files. It simply writes the designated surface data to disk, which can then be loaded into Ansys EnSight for post-processing and animation creation once the simulation completes.
+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 command:
+Alternatively, if full flow-field data is required, one can use the following TUI command:
 <code>
@@ Line 193: / Line 193: @@
 </code>
-However, this is less efficient in terms of storage and I/O performance since the entire 3D volume is exported.
+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.

wiki.chpc.ac.za

User Tools

Site Tools

Differences

Page Tools