Learning Forum

[zhongsheng]

Hi there,

I'm simulating a transient 3D flow around a cylinder case using Fluent on a HPC cluster.

In my point of view, running Fluent using TUI on HPC is quite different from running on local machines.

To work with HPC, I need to have, for example, a journal.jou file, which contains few lines of commands of instructions for the HPC to read in so that the HPC can setup the fluent.(see in the attached example)

I think I may need to specify the output interval in the journal.jou file, but I don't know the commands for doing this.

Can anyone familar or know how-to tell me what are the commands?

(P.s I am not talking about the export journal file in the Fluent.)

 

Thanks in advance!!!

ZS

[Karthik R]

What are you writing as output? Are you trying to save the files at a certain frequency? Please clarify what your exact need elaborately.

Thank you.

Karthik

 

[zhongsheng]

Hi Kremella,

Thanks for replying.

What I have now are the final state case file and dat file. And yes, I want my output files to be generated at a fixed frequency.

I need these so that I can visualize, for example,to plot the pressure changes with time.

 

Regards

Zhongsheng

[Rob]

You mean you want to save case & data at intervals or images? 

[zhongsheng]

Hi rwoolhou,

I want to save case and data files at each time steps, so that I can postprocess them in, for example, tecplot or paraview

ZS

[pawar002]

you can use below mentioned TUI command, (in below TUI, 3600 is a flow time/ frequency)

file/auto-save data-frequency 3600

[zhongsheng]

Do you mean something like this? 

**********************************************************************************

;Outputting solver performance data upon completion of the simulation

parallel timer usage

;

file/auto-save data-frequency 3600

;

;Writing the final case file (overwriting if required)

wc bladefluidout.cas.gz

yes

;

;Writing the final data file (overwriting if required)

wd bladefluidout.dat.gz

yes

;Exiting Fluent

exit

yes

**********************************************************************************

[Rob]

Assuming you can set up the model before switching to the cluster set the autosave and surface monitors via the GUI first and then transfer to the cluster. This reduces the complexity of the journal and avoids you overwriting files by accident. 

In the above if you're in the wrong level of the TUI it'll fail:

/file/write-case bladefluidout.cas.gz

is the full command, I'd advise using full commands to make the files easier to read. 

/file/write-data bladefluidout_%i.dat.gz

Will add the iteration number to the final data file which will stop it overwriting the first data file.