Fluid listed as surface

  • Last Post 20 March 2019
  • Topic Is Solved
FrankR posted this 18 March 2019

Dear Community,

for some obscure and unknown reason the fluid itself is listed under surfaces in my simulation. This phenomenon is not persist, the command
sometimes does contain the fluid , sometimes it does not.

If it does, my script adressing the true surfaces from which I want to extract data gets messed up because the index of these surfaces is modified. Also, export commands do not adress the surface for which they were intended.

Renaming the fluid so that it appears as the last entry in the list of surfaces does not help, it pops up again where is was before.

What is the cause why fluid is listed under surfaces, and how can this be prevented ?

I use the FLUENT "Academic Student Release" 19.2 on a Windows-PC in stand-alone mode (not using Workbench).

Thank you for your advice,


Order By: Standard | Newest | Votes
kkanade posted this 19 March 2019

2d or 3d?

can you give named selection in meshing before going to fluent?

  • Liked by
  • FrankR
FrankR posted this 19 March 2019

Dear kkanade

what would this forum be without you and rwoolhou ?

My simulation is 3d. I searched the user's guide for the term "named selection", but it did not come up with anything useful for me. My mesh was imported from the GAMBIT preprocessor. The problem I had stated yesterday was not observed till yesterday.

I found a workaround. My script is a mixture of GUI and TUI commands.

1) In the GUI commands I can state the name of the surface instead of an index, like
(cx-gui-do cx-set-list-selections "Contours*Table1*Frame3*Frame2*List2(Surfaces)" '( x=center))

2) I use TUI-commands in loops. For all surfaces I define an id at the beginning of the script 
(define idxc 11)
which can be modified, if need be, after a test run. And within the loop:
(ti-menu-load-string (format #f "display set contours surfaces ~a" (display idxc)));

I tried 1) out of dispair, and was unaware of this option till today. With 2) above I have to modify at most one index per surface after a test run. Thus, the work to be invested for modifications is halved.





rwoolhou posted this 20 March 2019

It'd be quiet without us... Don't forget abenhadj! 

You can set labels in GAMBIT as you build the models however I'd suggest looking at the CAD & Fluent Meshing Workflows in 2019Rx once the student version comes out. The GAMBIT DOC is embedded in the install somewhere (or should be) and has some notes on surface IDs etc. which should simplify the Fluent work. 



  • Liked by
  • Raef.Kobeissi
  • FrankR