Defining Interface

Questions and remarks about code_saturne usage
Forum rules
Please read the forum usage recommendations before posting.
Post Reply
sofenkumarjena
Posts: 35
Joined: Thu May 19, 2022 4:37 pm

Defining Interface

Post by sofenkumarjena »

I have non-conformal meshing at the interface of two zones. The mesh is exported in .cgns format. When the mesh is imported to code saturne and boundary conditions are imported using pre-proceoor log file, then the interface is imported as wall boundary. There is now option available in gui to define it as interface. How to deal with this issues for non conformal meshes.

With Regards

Sofen
Yvan Fournier
Posts: 4070
Joined: Mon Feb 20, 2012 3:25 pm

Re: Defining Interface

Post by Yvan Fournier »

Hello,

In code_saturne, non-conforming interfaces are not handled as boundary conditions but as a mesh preprocessing (joining) step.

So look there in the GUI and documentation.

Regards,

Yvan
sofenkumarjena
Posts: 35
Joined: Thu May 19, 2022 4:37 pm

Re: Defining Interface

Post by sofenkumarjena »

Hi Yvan,
During the mesh preprocessing stage, in the face joining option declared all the selected interface. But unfortunately during loading of the preprocessor log file, the same is appeared as wall. Please find the attached screen shots and the log files.
Regards

Sofen
Attachments
preprocessor.log
(23.13 KiB) Downloaded 58 times
Screenshot from 2022-06-30 14-40-38.png
Screenshot from 2022-06-30 14-39-58.png
Yvan Fournier
Posts: 4070
Joined: Mon Feb 20, 2012 3:25 pm

Re: Defining Interface

Post by Yvan Fournier »

Hello,

Joining is actually applied during the preprocessing stage of the main solver, so it is normal that they apper this way in the preprocessor.log. You should check how this is transformed in the run_solver.log file (and you can even postprocess/visualize the joining to make sure everything is ok).

Regards,

Yvan
Post Reply