[alaspina]

Hello.

I have several C mesh boundary with airfoil wall case files that I would like to set up via Fluent to set up the inlet properties (velocity) and the type of viscous model that I would like to use. I have a general reference for what the journal file should look like to send it to a cluster (i believe running on linux):

/file/read-case file.cas
/solve/initialize/set-defaults/y-velocity 0
/solve/initialize/set-defaults/x-velocity 0
/solve/initialize/set-defaults/z-velocity 0
/solve/initialize/set-defaults/pressure 0
/define/boundary-conditions/velocity-inlet inlet no no yes yes no 25 no 0 no 300 yes
/solve/initialize/initialize-flow
/parallel/partition/print-active-partitions
/define/boundary-conditions/list-zones
/solve/set/max-iterations-per-time-step 40
/solve/monitors/residual/convergence-criteria 0.005 0.0001 0.0001 0.0001 0.00001
/solve/set/time-step 0.00020
/solve/set/number-of-time-steps 500000
/solve/set/p-v-coupling 20
/file/auto-save/data-frequency 0
/solve/iterate 50
/solve/update-physical-time
/file/auto-save/data-frequency 500
(Do ((x 1 (+ x 1))) ((> x 500))
(Ti-menu-load-string (format #f "/solve/iterate 20"))
(Ti-menu-load-string (format #f "/solve/update-physical-time"))
)
;(Do ((x 1 (+ x 1))) ((> x 6000))
; (Ti-menu-load-string (format #f "/solve/iterate 20"))
; (Ti-menu-load-string (format #f "/solve/update-physical-time"))
; )
close-fluent

I tried to repeat this by going through the GUI first and setting everything up and writing a journal file, but the syntax and format of the file looks completely different:

(cx-gui-do cx-activate-item "MenuBar*ImportSubMenu*Mesh...")
(cx-gui-do cx-activate-item "Question*Cancel")
(cx-gui-do cx-activate-item "MenuBar*ImportSubMenu*Mesh...")
(cx-gui-do cx-activate-item "Question*OK")
(cx-gui-do cx-set-file-dialog-entries "Select File" '( "/home/directory/meshNACA0012.msh") "Mesh Files (*.msh* *.MSH* )")
(cx-gui-do cx-set-list-tree-selections "NavigationPane*List_Tree1" (list "Setup|General"))
(cx-gui-do cx-set-list-tree-selections "NavigationPane*List_Tree1" (list "Setup|Models"))
(cx-gui-do cx-set-list-selections "Models*Table1*List1(Models)" '( 2))
(cx-gui-do cx-activate-item "Models*Table1*List1(Models)")
(cx-gui-do cx-activate-item "Models*Table1*PushButton2(Edit)")
(cx-gui-do cx-set-toggle-button2 "Viscous Model*Table1*ToggleBox1(Model)*Transition k-kl-omega (3 eqn)" #t)
(cx-gui-do cx-activate-item "Viscous Model*Table1*ToggleBox1(Model)*Transition k-kl-omega (3 eqn)")
(cx-gui-do cx-activate-item "Viscous Model*PanelButtons*PushButton1(OK)")
(cx-gui-do cx-set-list-tree-selections "NavigationPane*List_Tree1" (list "Setup|Materials"))
(cx-gui-do cx-set-list-selections "Materials*Table1*List1(Materials)" '( 1))
(cx-gui-do cx-activate-item "Materials*Table1*List1(Materials)")
(cx-gui-do cx-activate-item "Materials*Table1*ButtonBox2*PushButton1(Creat e/Edit)")
(cx-gui-do cx-activate-item "Create/Edit Materials*PanelButtons*PushButton1(Close)")
(cx-gui-do cx-set-list-tree-selections "NavigationPane*List_Tree1" (list "Setup|Cell Zone Conditions"))
(cx-gui-do cx-set-list-tree-selections "NavigationPane*List_Tree1" (list "Setup|Boundary Conditions"))
(cx-gui-do cx-set-list-selections "Boundary Conditions*Table1*List2(Zone)" '( 1))
(cx-gui-do cx-activate-item "Boundary Conditions*Table1*List2(Zone)")
(cx-gui-do cx-activate-item "Boundary Conditions*Table1*Table3*Table4*ButtonBox1*PushBut ton1(Edit)")
(cx-gui-do cx-set-list-selections "Velocity Inlet*Frame3*Frame1(Momentum)*Table1*DropDownList6 (Velocity Specification Method)" '( 1))
(cx-gui-do cx-activate-item "Velocity Inlet*Frame3*Frame1(Momentum)*Table1*DropDownList6 (Velocity Specification Method)")
(cx-gui-do cx-set-real-entry-list "Velocity Inlet*Frame3*Frame1(Momentum)*Table1*Table16*RealE ntry2(X-Velocity)" '( 1))
(cx-gui-do cx-activate-item "Velocity Inlet*PanelButtons*PushButton1(OK)")


And it goes on and on....

I ran the latter and I got an exitcode of 2 from my cluster. Looking online it seems that this is indeed an issue with the shell builtins, which I identify as the format not being correct. This is obvious, as the journal file seems to have been written for a GUI rather than a command prompt. Any help is appreciated. I am using Fluent 17.0 up to 17.2.

Essentially I want to find a list of the commands for the linux machine on the cluster. Also, I don't understand what the case file can and cannot cover. On the case file I had the solution initialization as well as the BC ready and all, but from the example I have it seems like everything needs to be done on the command prompt. Any help is appreciated.

[Kushal Puri]

Originally Posted by alaspina

Hello.

I have several C mesh boundary with airfoil wall case files that I would like to set up via Fluent to set up the inlet properties (velocity) and the type of viscous model that I would like to use. I have a general reference for what the journal file should look like to send it to a cluster (i believe running on linux):

/file/read-case file.cas
/solve/initialize/set-defaults/y-velocity 0
/solve/initialize/set-defaults/x-velocity 0
/solve/initialize/set-defaults/z-velocity 0
/solve/initialize/set-defaults/pressure 0
/define/boundary-conditions/velocity-inlet inlet no no yes yes no 25 no 0 no 300 yes
/solve/initialize/initialize-flow
/parallel/partition/print-active-partitions
/define/boundary-conditions/list-zones
/solve/set/max-iterations-per-time-step 40
/solve/monitors/residual/convergence-criteria 0.005 0.0001 0.0001 0.0001 0.00001
/solve/set/time-step 0.00020
/solve/set/number-of-time-steps 500000
/solve/set/p-v-coupling 20
/file/auto-save/data-frequency 0
/solve/iterate 50
/solve/update-physical-time
/file/auto-save/data-frequency 500
(Do ((x 1 (+ x 1))) ((> x 500))
(Ti-menu-load-string (format #f "/solve/iterate 20"))
(Ti-menu-load-string (format #f "/solve/update-physical-time"))
)
;(Do ((x 1 (+ x 1))) ((> x 6000))
; (Ti-menu-load-string (format #f "/solve/iterate 20"))
; (Ti-menu-load-string (format #f "/solve/update-physical-time"))
; )
close-fluent

I tried to repeat this by going through the GUI first and setting everything up and writing a journal file, but the syntax and format of the file looks completely different:

(cx-gui-do cx-activate-item "MenuBar*ImportSubMenu*Mesh...")
(cx-gui-do cx-activate-item "Question*Cancel")
(cx-gui-do cx-activate-item "MenuBar*ImportSubMenu*Mesh...")
(cx-gui-do cx-activate-item "Question*OK")
(cx-gui-do cx-set-file-dialog-entries "Select File" '( "/home/directory/meshNACA0012.msh") "Mesh Files (*.msh* *.MSH* )")
(cx-gui-do cx-set-list-tree-selections "NavigationPane*List_Tree1" (list "Setup|General"))
(cx-gui-do cx-set-list-tree-selections "NavigationPane*List_Tree1" (list "Setup|Models"))
(cx-gui-do cx-set-list-selections "Models*Table1*List1(Models)" '( 2))
(cx-gui-do cx-activate-item "Models*Table1*List1(Models)")
(cx-gui-do cx-activate-item "Models*Table1*PushButton2(Edit)")
(cx-gui-do cx-set-toggle-button2 "Viscous Model*Table1*ToggleBox1(Model)*Transition k-kl-omega (3 eqn)" #t)
(cx-gui-do cx-activate-item "Viscous Model*Table1*ToggleBox1(Model)*Transition k-kl-omega (3 eqn)")
(cx-gui-do cx-activate-item "Viscous Model*PanelButtons*PushButton1(OK)")
(cx-gui-do cx-set-list-tree-selections "NavigationPane*List_Tree1" (list "Setup|Materials"))
(cx-gui-do cx-set-list-selections "Materials*Table1*List1(Materials)" '( 1))
(cx-gui-do cx-activate-item "Materials*Table1*List1(Materials)")
(cx-gui-do cx-activate-item "Materials*Table1*ButtonBox2*PushButton1(Creat e/Edit)")
(cx-gui-do cx-activate-item "Create/Edit Materials*PanelButtons*PushButton1(Close)")
(cx-gui-do cx-set-list-tree-selections "NavigationPane*List_Tree1" (list "Setup|Cell Zone Conditions"))
(cx-gui-do cx-set-list-tree-selections "NavigationPane*List_Tree1" (list "Setup|Boundary Conditions"))
(cx-gui-do cx-set-list-selections "Boundary Conditions*Table1*List2(Zone)" '( 1))
(cx-gui-do cx-activate-item "Boundary Conditions*Table1*List2(Zone)")
(cx-gui-do cx-activate-item "Boundary Conditions*Table1*Table3*Table4*ButtonBox1*PushBut ton1(Edit)")
(cx-gui-do cx-set-list-selections "Velocity Inlet*Frame3*Frame1(Momentum)*Table1*DropDownList6 (Velocity Specification Method)" '( 1))
(cx-gui-do cx-activate-item "Velocity Inlet*Frame3*Frame1(Momentum)*Table1*DropDownList6 (Velocity Specification Method)")
(cx-gui-do cx-set-real-entry-list "Velocity Inlet*Frame3*Frame1(Momentum)*Table1*Table16*RealE ntry2(X-Velocity)" '( 1))
(cx-gui-do cx-activate-item "Velocity Inlet*PanelButtons*PushButton1(OK)")


And it goes on and on....

I ran the latter and I got an exitcode of 2 from my cluster. Looking online it seems that this is indeed an issue with the shell builtins, which I identify as the format not being correct. This is obvious, as the journal file seems to have been written for a GUI rather than a command prompt. Any help is appreciated. I am using Fluent 17.0 up to 17.2. Any help is appreciated.

Writing a journal file from the fluent actually capturing all the movement of the mouse (eg, where u are clicking and what u are selecting etc).

But using a command iis the direct way to access the panel.

[alaspina]

Originally Posted by Kushal Puri

Writing a journal file from the fluent actually capturing all the movement of the mouse (eg, where u are clicking and what u are selecting etc).

But using a command is the direct way to access the panel.

Right, so where can I find the command line commands?