CFX update
This commit is contained in:
@ -75,10 +75,13 @@ An example for running CFX using a Slurm batch script is the following:
|
|||||||
module use unstable
|
module use unstable
|
||||||
module load ANSYS/2020R1-1
|
module load ANSYS/2020R1-1
|
||||||
|
|
||||||
|
export HOSTLIST=$(scontrol show hostname | tr '\n' ',' | sed 's/,$//g')
|
||||||
|
|
||||||
JOURNAL_FILE=/data/user/caubet_m/CFX/myjournal.in
|
JOURNAL_FILE=/data/user/caubet_m/CFX/myjournal.in
|
||||||
cfx5solve -batch -def "$JOURNAL_FILE" -part $SLURM_NTASKS
|
cfx5solve -batch -def "$JOURNAL_FILE" -par-dist "$HOSTLIST" -part $SLURM_NTASKS -start-method 'IBM MPI Distributed Parallel'
|
||||||
```
|
```
|
||||||
|
|
||||||
In the above example, one can increase the number of *nodes* and/or *ntasks* if needed and combine it
|
In the above example, one can increase the number of *nodes* and/or *ntasks* if needed and combine it
|
||||||
with `--exclusive` whenever needed. In general, **no hypertheading** is recommended for MPI based jobs.
|
with `--exclusive` whenever needed. In general, **no hypertheading** is recommended for MPI based jobs.
|
||||||
Also, one can combine it with `--exclusive` when necessary.
|
Also, one can combine it with `--exclusive` when necessary. Finally, one can change the MPI technology in `-start-method`
|
||||||
|
(check CFX documentation for possible values).
|
||||||
|
Reference in New Issue
Block a user