Ansys: Difference between revisions

Ansys (view source)

Revision as of 20:25, 22 March 2024

566 bytes added , 7 months ago

m

no edit summary

Roberpj

cc_staff

1,857

edits

@@ Line 1,144: / Line 1,144: @@
 === Fluids === <!--T:1675-->
-::: <code>module load CcEnv StdEnv/2020 ansys/2021R1</code> (or newer)
+::: <code>module load CcEnv StdEnv/2020</code>
+::: <code>module load ansys/2021R1</code> (or newer versions)
 ::: <code>unset SESSION_MANAGER</code>
 ::: <code>fluent | cfx5 | icemcfd</code>
@@ Line 1,156: / Line 1,157: @@
 === Mapdl === <!--T:1681-->
-::: <code>module load StdEnv/2020</code>
+::: <code>module load CcEnv StdEnv/2020</code>
-::: <code>module load ansys/2021R2</code> (or newer versions)
+::: <code>module load ansys/2021R1</code> (or newer versions)
 ::: <code>mapdl -g</code>, or via launcher,
 ::: <code>unset SESSION_MANAGER; launcher</code> --> click RUN button
 === Workbench === <!--T:1676-->
-::: <code>module load CcEnv StdEnv/2020 ansys/2021R2</code> (or newer)
+::: <code>module load SnEnv</code>
+::: <code>module load ansys/2020R2</code> (or newer versions)
 ::: <code>export HOOPS_PICTURE=opengl</code>
 ::: <code>runwb2</code>
-::: o The export line prevents the following abbreviated tui Warning from appearing when fluent starts:
+::: o The export line avoids the following tui Warning from appearing when fluent starts:
-::: [<span style="Color:#ff7f50">Software rasterizer found, hardware acceleration will be disabled.</span>]
+:::: [<span style="Color:#ff7f50">Software rasterizer found, hardware acceleration will be disabled.</span>]
-::: Alternatively HOOPS_PICTURE can be set after workbench has started by doing the following:
+::: Alternatively the HOOPS_PICTURE environment variable can be set inside workbench by doing:
-::: Fluent Launcher --> Environment Tab --> HOOPS_PICTURE=opengl (without the export)
+:::: Fluent Launcher --> Environment Tab --> HOOPS_PICTURE=opengl (without the export)
-::: ------------------------------------------------------------------------------------
-::: <code>module load SnEnv ansys/2021R1</code>, or
-::: <code>module load SnEnv ansys/2020R2</code>
-::: <code>runwb2</code>
-::: <br>
-<!--T:2844-->
+::: NOTE1: When running Mechanical in Workbench on gra-vdi be sure to <b>tic</b> <i>Distributed</I> in the upper ribbon Solver panel and specify a maximum value of <b>24</b> cores.  When running Fluent on gra-vdi instead <b>untic</b> <i>Distributed</I> and specify a maximum value of <b>12</b> cores.  Do not attempt to use more than 128GB memory otherwise Ansys will hit the hard limit and be killed. If you need more cores or memory then please use a cluster compute node to run your graphical session on (as described in the previous Compute nodes section above).  When doing old pre-processing or post-processing work with Ansys on gra-vdi and not running calculation, please only use <b>4</b> cores otherwise hpc licenses will be checked out unnecessarily.
-::: NOTES: To run an Analysis Program in parallel within Workbench on gra-vdi such as Mechanical or Fluent, untick <i>Distributed</i> and specify a value of cores <b>no greater than 12</b>.  To run with more cores than 12 please use a compute node instead.  If an Ansys program refuses to start following a previous run there maybe hung processes if the program was not shutdown cleanly or possibly the program was minimized instead. To clear out any old processes run <code>pkill -9 -e -u $USER -f "ansys|fluent|mwrpcss|mwfwrapper|ENGINE|mono"</code> and then try starting the program again.
+::: NOTE2: On very rare occasions the Ansys workbench gui will freeze or become unresponsive in some way.  If this happens open a new terminal window and run  <code>pkill -9 -e -u $USER -f "ansys|fluent|mwrpcss|mwfwrapper|ENGINE|mono"</code> to fully kill off Ansys.  Likewise if Ansys crashes or vncviewer disconnect before Ansys could be shutdown cleanly then try running the pkill command if Ansys does not run normally afterwards.   In general, if Ansys is not behaving properly and you suspect one of the aforementioned causes try pkill before opening a problem ticket.
 === Ansys EDT === <!--T:1677-->
 ::: Open a terminal window and load the module:
-:::: <code>module load SnEnv ansysedt/2023R2</code>, or
+:::: <code>module load SnEnv ansysedt/2023R2</code>  or
 :::: <code>module load SnEnv ansysedt/2021R2</code>
 ::: Type <code>ansysedt</code> in the terminal and wait for the gui to start