Page 1 of 1

Code_Saturne/Code_Saturne coupling

Posted: Mon Oct 20, 2014 9:08 am
by a.dalmon
Hello,

I would like to know if it is possible to separate a mesh in two different parts in which a Code_Saturne solver will solve NS equations. My problem is that the borders between the two parts can move during the simulation.
Are there tutorials on that subject ?

I would have permanent boundary conditions on the borders of the global mesh and specifics boundary conditions on the interface between the two instances of Saturne. How can I exchange information as pressure or speed from one part of the mesh to the other ?

Thanks

Alexis

Re: Code_Saturne/Code_Saturne coupling

Posted: Tue Oct 21, 2014 6:16 pm
by Yvan Fournier
Hello,

This seems similar to the Code_Saturne/Code_Saturne coupling that is used for RANS/LES coupling (often using volume-based exchanges) and rotor/stator coupling (using boundary exchanges, and the algorithm predating the new mesh-joining-based method).

Another user just asked for an example in another thread (http://code-saturne.org/forum/viewtopic.php?f=2&t=1586), so I need to provide such a case soon (there might be an older setup somewhere on this forum, if we check far back enough).

Regards,

Yvan

Re: Code_Saturne/Code_Saturne coupling

Posted: Fri Oct 24, 2014 9:12 am
by BLM
Hello,

The post http://code-saturne.org/forum/viewtopic.php?f=2&t=67 contains a few informations about Code_Saturne/Code_Saturne coupling.

Note that if you don't have any overlapping region between the two separated meshes, you can activated the coupling scheme dedicated to interfacial coupling by
ifaccp = 1
in cs_user_parameters.f90 (subroutine usipsu for instance). It is more robust in principle.

When (omegax, omegay, omegaz) rotation vector is zero for one instance of the code and non-zero for another one (turbomachinery kind simulation) the code automatically switch to ifaccp = 1.

Regards.