[dingyangyao1995]

Hi Everyone,

Whenever I update a boundary condition using TUI, for example,

define bc mass-flow-inlet

Fluent will print out all existing mass flow inlet surface, which I have hundreds in my model.

Is there a way to turn off the auto printout?

Thank you!

[gfoam]

Hi:
you could make a journal to set all the parameters of mass-flow-inlet in your model, ie:
define bc mfi inlet1 parm1 param2 ...
or do this in the TUI, but you need to know all the zone names you have to set in your model. Regards

[dingyangyao1995]

Hi, thank you for your reply.
What i meant is that, even if I do the entire TUI command to set new condition in one line, fluent still print out all the existing bc names in a square bracket, which is very annoying. Is there a way to turn off that prompt?

[gfoam]

Mmmm, dont think so. Because Fluent is listing the zone names with mass flow inlet BC's specified on it so you can choose one of them. Are you trying to specify the same mass flow on alll of them? Or, are there groups with the same mass flow? If so, then you can specify the mass flow on one o some of them and then use the Copy BC command to copy the settings on all BCs. Regards

[LuckyTran]

The define bc mass-flow-inlet command is designed to work this way.

To avoid the listing, you should use the more primitive command:

define/boundary-conditions/set mass-flow-inlet "ID" blah blah blah

[dingyangyao1995]

Originally Posted by LuckyTran

The define bc mass-flow-inlet command is designed to work this way.

To avoid the listing, you should use the more primitive command:

define/boundary-conditions/set mass-flow-inlet "ID" blah blah blah

This is exactly what I am looking for!
I wonder, where did you get these sort of information? From years of using fluent or is it from the fluent documentation?

[LuckyTran]

Originally Posted by dingyangyao1995

This is exactly what I am looking for!
I wonder, where did you get these sort of information? From years of using fluent or is it from the fluent documentation?

It was from a few minutes of just typing commands into the TUI to find the right command. It was based on a hunch that surely the people/developers at Fluent were not dumb enough to print the entire list of surfaces when there is no need to, especially since Fluent is designed to run in batch mode. The rest was elbow grease and willing to get your hands dirty to fix the problem.