Problems with text command interface of Fluent
 

Hello,

I want to use Fluent (6.2) in a parallel environment, starting the job with a script file containing all the necessary commands to set up the case. The problem I encounter is with the initialize-flow command: When I use it the first time, I get a segmentation violation fault, but Fluent continues to work. When I enter the same command again, the initialization takes place without the slightest complaint. If I used a single processor machine only I would not be bothered at all, but when using a parallel machine, this segmentation violation causes the jobs on the other processors to crash. The following is my script file:

---------------------------------

#!/bin/bash

/opt/fluent/6.2.16/Fluent.Inc/bin/fluent 3ddp -g -64 << EOFluentInput > test.log

file/confirm-overwrite n

file/read-case test.msh

grid/scale 0.001 0.001 0.001

surface/plane-slice y_0 0 1 0 0

define/models/solver segregated yes

define/models unsteady-1st-order yes

define/models/viscous ke-standard yes

define/models multiphase vof 2 geo-reconstruct 0.25 yes yes yes

;define/models multiphase vof 2 implicit yes

define/materials copy fluid water-liquid

define/phases/phase-domain phase-1 luft yes air

define/phases/phase-domain phase-2 wasser yes water-liquid

define/operating-conditions gravity yes 0 0 -9.81

define/operating-condition operating-pressure 101325

define/operating-condition reference-pressure-location 0.1 0 0.1

define/operating-condition operating-density yes 1.225

define/boundary-conditions pressure-inlet einlass_unten mixture yes no 0 no 0 no yes yes no 1 no 1

define/boundary-conditions pressure-inlet einlass_unten mixture yes 1 yes yes 0 -4.8 no 0.001 no yes no no no yes 10 6

define/boundary-conditions pressure-inlet einlass_oben mixture yes no 0 no 0 no yes yes no 1 no 1

define/boundary-conditions pressure-inlet einlass_oben mixture yes 1 yes yes 0 -4.8 no 0.001 no yes no no no yes 10 6

define/boundary-conditions pressure-outlet auslass_oben mixture yes no 0 no no yes yes no 1 no 1

define/boundary-conditions pressure-outlet auslass_unten mixture yes no 0 no no yes yes no 1 no 1

define/boundary-conditions pressure-outlet auslass_oben mixture yes 1 yes 0 -4.8 no no yes no no no yes 10 6

define/boundary-conditions pressure-outlet auslass_unten mixture yes 1 yes 0 -4.8 no no yes no no no yes 10 6

solve/set discretization-scheme pressure 13

solve/set discretization-scheme mom 0

solve/set discretization-scheme k 0

solve/set discretization-scheme epsilon 0

solve/set p-v-coupling 22

solve/set piso 1 1 yes

solve/set equations flow yes

solve/set equations ke yes

solve/set equations mp yes

solve/set under-relaxation body-force 1

solve/set under-relaxation density 1

solve/set under-relaxation epsilon 0.8

solve/set under-relaxation k 0.8

solve/set under-relaxation mom 0.7

solve/set under-relaxation pressure 0.3

solve/set under-relaxation turb-viscosity 1

solve/monitors/residual convergence-criteria 0.001 0.001 0.001 0.001 0.001 0.001

file/autosave data-frequency 1

file/autosave root-name test

file/autosave overwrite-existing-files yes

file/autosave max-files 2

solve/init/compute-defaults pressure-inlet einlass_oben mixture

solve/init initialize-flow

solve/init initialize-flow yes

adapt/mark-inout-hexahedron yes no 0 24 -4 4 -4.8 0 solve/patch wasser ( ) 0 ( ) mp 1

file/write-case test.cas

file/write-data test.dat

solve/set/time-step 0.001

solve/dual-time-iterate 100 500

file/binary-files y

file/confirm-overwrite n

exit

y

EOFluentInput

------------------------------------------------

I hope this is not too detailed though ;-)

Any ideas?

Thanks in advance for any advice!

P.A.

Re: Problems with text command interface of Fluent
 

Sorry, I have nothing useful to offer in re this problem. But I had to write because it appears you are a rare example of someone writing significant .jou file programs. I do almost all my CFD work this way and wonder what resources you used to get proficient at this, and what tips you have to share. Writing .jou files seems very difficult to me, because of all the experimenting necessary to discover the text prompt questions each line must answer, and especially because the questions are often state-dependant in ways one might not anticipate.

How have you managed? Do you have any resources you'd care to share, beyond the docs available from Fluent? Thanks - and sorry I wasn't any help!

Re: Problems with text command interface of Fluent
 

Unfortunately I do it exactly the same way you described. It took me lots of hacking through the TUI menu to find the entries I am used to see in the GUI. What seems most crucial to me is that many settings in the TUI can not be made at the same "menu" position like in the GUI, which is really confusing sometimes. The worst thing is, that there seems to be no appropriate documentation on this scripting stuff. I am sorry that I can be not really helpfull on this!

Cheers, Pascal Anschau.