code_saturne User's Forum

Hi, everyone

How to set the "Periodic Boundary Conditions" for 2.0?

Thank you very much!

Yuan huang

Hi Yuan,

There is an example of how to do it with the GUI at the tutorial here - http://cfd.mace.manchester.ac.uk/twiki/ ... leTutorial

Hope that helps!

James

Hi, James
Thanks very much, but how to do this without GUI?

Yuan Huang

Hello,

Defining periodicity without the GUI in version 2.0 is described in the user manual. Just search the pdf for "periodicity".

Regards,

Yvan

Hi, Yvan

I preprocess the mesh by command "cs_preprocess -m meshname --rota --angle --dir dx dy dz ----invpt x y z --group groupname", and then set "COMMAND PERIO=1", "EXEC PREPROCESS=no" in the runcase.
Is that correct?

Thanks very much!

Yuan Huang

Hello,

No, you need to set EXEC_PREPROCESS=yes if you want preprocessing.

But you don't need to edit the runcase for this: the GUI will do it for you.

Regards,

Yvan

hi,

I am really confused. If set EXEC_PREPROCESS=yes, how to use the preprocess get by the command "cs_preprocess -m meshname --rota --angle --dir dx dy dz ----invpt x y z --group groupname"?

And you said the GUI will do it, but the question is I don't use the GUI?

Can you tell the details?


Thanks very much!

Yuan Huang

Hello,

I did not realize that you ran the preprocessor first, then used the preprocessor_output file in the script. In that case, setting EXEC_PREPROCESS=no is okay.

When you run the preprocessor, it can output postprocessing files (viewable with ParaView, EnSight, or SALOME for example) to show you what periodicity was built and where the remaining boundaries are.

All the details are in the user documentation (search the pdf for "periodicity").

And why don't you use the GUI ?

Regards,

Yvan

Hi,

Because the case I simulated is about combustion, and I GUI don't support it.

Regards,

Yuan Huang

Hello,

The GUI does not support combustion setup in V2.0, but it still supports preprocessing, and you can mix the GUI and user subroutines: user subroutines have priority.

If this causes issues, at least, prepare all preprocessing with the GUI, and just set PARAM= in the runcase.

Regards,

Yvan