Submitting to TotalCAE with Fluent
How to submit Fluent to TotalCAE Managed HPC clusters and Bring Your Own Clouds running TotalCAE platform
-
1
-
Welcome to Running Ansys Fluent on TotalCAE
-
Four ways to run Fluent on TotalCAE
-
Logging in and finding your way around
-
Getting your model onto the cluster
-
2
-
Your first Fluent job, start to finish
-
A tour of the Fluent job form
-
The fields you fill in
-
Where it runs, time limit and cost
-
Batch flags, Extra Arguments and Additional Files
-
Email alerts and comments
-
Copy the tsubmit command instead of submitting
-
3
-
What a journal file is
-
Walking through oil.jou
-
Recording a journal instead of typing one
-
Journal habits that keep batch runs smooth
-
Saving pictures from a batch run
-
4
-
The List Jobs page
-
Why is my job not running yet?
-
Peek Output: watching the Fluent transcript
-
The right-click menu
-
Saving and stopping: Check Fluent, Exit Fluent and Cancel
-
Job emails and TotalCAE Watchdog
-
5
-
What a Fluent job writes
-
Reading the transcript and logs
-
Downloading results
-
Viewing and post-processing results
-
6
-
Before you start: enable tsubmit
-
Reading tsubmit fluent --help
-
Submitting oil_rig_7m with tsubmit
-
Watching and controlling jobs from the CLI
-
7
-
Fluent licenses in plain terms
-
Using ANSHPC licenses
-
Checking license use
-
Running Fluent Meshing
-
Continuing a run from saved data
-
User-defined functions
-
Jobs that wait for other jobs
-
8
-
When to use Fluent interactively
-
Allocating nodes with salloc and making a hosts file
-
Starting Fluent Launcher and the Home tab
-
Parallel Settings and starting Fluent
-
9
-
How Workbench submits to TotalCAE
-
Opening Workbench 2026 R1 from the Desktop tab
-
Solution properties for RSM
-
Update, follow the job, and get results back
-
10
-
The PyFluent script you will submit
-
Submit the script with tsubmit
-
11
-
What the native GPU solver is
-
What the GPU solver supports
-
GPU queues and GPU memory
-
Licensing the GPU solver
-
Submitting a GPU job
-
12
-
Sizing guidance: cells per core and per GPU
-
Keeping an eye on cost and utilization when ru
-
Where to look and getting help
-
Keep Learning