Coupling with Code_Aster
Forum rules
Please read the forum usage recommendations before posting.
Please read the forum usage recommendations before posting.
Coupling with Code_Aster
Hello,
I would like to couple Code_Saturne to Code_Aster for FSI calculations. I found that Salome's YACS module is able to do that. I am having hard time in finding my way to practically to do this. Does anyone have any template or sample of doing that?
I appreciate any comments or hints to get it to work.
Thanks
Nima
I would like to couple Code_Saturne to Code_Aster for FSI calculations. I found that Salome's YACS module is able to do that. I am having hard time in finding my way to practically to do this. Does anyone have any template or sample of doing that?
I appreciate any comments or hints to get it to work.
Thanks
Nima
Re: Coupling with Code_Aster
Hello Nima,
YACS module can indeed be used for code/code coupling, though it may also be seen as a "code supervisor". However, this is not a simple task... even if a prototype is under validation in our labs (based on SALOME 5.1.3, Code_Saturne 2.0-rc1 and a development version of Code_Aster). The setup is still quite complex, so I don't expect an official release soon, nor an informal one :-/
Actually, do you really need coupling for FSI? Maybe a "simple" toolchain between Code_Saturne and Code_Aster would be enough for your purpose?
In this case, the solution is to create a specific mesh post-processing with only the pressure field as variable output (thanks to the usdpst.f90 and usvpst.f90 subroutines), and start a Code_Aster simulation with these fields as boundary conditions. An iteration process can be setup if needed (even through the YACS module if you wish so!).
Could you tell us more about your test case?
Regards,
David
YACS module can indeed be used for code/code coupling, though it may also be seen as a "code supervisor". However, this is not a simple task... even if a prototype is under validation in our labs (based on SALOME 5.1.3, Code_Saturne 2.0-rc1 and a development version of Code_Aster). The setup is still quite complex, so I don't expect an official release soon, nor an informal one :-/
Actually, do you really need coupling for FSI? Maybe a "simple" toolchain between Code_Saturne and Code_Aster would be enough for your purpose?
In this case, the solution is to create a specific mesh post-processing with only the pressure field as variable output (thanks to the usdpst.f90 and usvpst.f90 subroutines), and start a Code_Aster simulation with these fields as boundary conditions. An iteration process can be setup if needed (even through the YACS module if you wish so!).
Could you tell us more about your test case?
Regards,
David
Re: Coupling with Code_Aster
Thanks David for your reply. So setting up a YACS supervisor for FSI is really complex as looked to my eyes:).
The case is an internal pulsatile flow with turbulence which causes the nonlinear elastic wall to deform and this deformation has effect on the flow and so forth. This happens in arteries. I think pressure is not enough. We need shear on the wall from the flow domain and new wall configuration + its velocity(normal & tangent) from the solid domain as well.
By any chance, isn't there any way for replacing writing information as files (like MED) by using shared memory for variables between code_aster and code_saturne? I am asking this because writing and reading to/from hard for each fluid/solid iteration extremely slows down the solution?
Regards,
Nima
The case is an internal pulsatile flow with turbulence which causes the nonlinear elastic wall to deform and this deformation has effect on the flow and so forth. This happens in arteries. I think pressure is not enough. We need shear on the wall from the flow domain and new wall configuration + its velocity(normal & tangent) from the solid domain as well.
By any chance, isn't there any way for replacing writing information as files (like MED) by using shared memory for variables between code_aster and code_saturne? I am asking this because writing and reading to/from hard for each fluid/solid iteration extremely slows down the solution?
Regards,
Nima
Re: Coupling with Code_Aster
I am looking for such solutions for the same scope of applications ( see here ) :)
Re: Coupling with Code_Aster
I don't know if it can fit your requirements but I've seen some exemple of fsi in arteries using elmer :
http://www.csc.fi/english/pages/elmer/examples/Coupled_problems/hemodyn
For code_saturne / code_aster coupling I am also interested concerning marine applications. We have planed to have a student working on this topic (at least code chaining if real coupling is not possible) for 6 month.
We will see what is possible to do within salome environement, I know that is has already been done.
http://www.csc.fi/english/pages/elmer/examples/Coupled_problems/hemodyn
For code_saturne / code_aster coupling I am also interested concerning marine applications. We have planed to have a student working on this topic (at least code chaining if real coupling is not possible) for 6 month.
We will see what is possible to do within salome environement, I know that is has already been done.
Re: Coupling with Code_Aster
Regarding Elmer; I had already seen that. As far as I know, Elmer cannot handle hyperelastic material and its turbulence capabilities in FSI is very limited.
Re: Coupling with Code_Aster
Hi Nima,
I'm not sure I can be of much help for now.
What I can do is provide you with the development files and some sample when we think Code_Saturne / Code_Aster coupling is in a good shape. However, I cannot give a precise date, as we don't want to release something that doesn't work :-/
If you think the flow is steady, you can try to have chained calculation: Code_Saturne => Code_Aster => Code_Saturne => Code_Aster ... with enough iteration to have the FSI converged. This is already possible by having the pressure field at the walls transfered from Code_Saturne to Code_Aster (via a MED file specified in the usdpst.f90 subroutine).
This has already been done in some calculation.
David
I'm not sure I can be of much help for now.
What I can do is provide you with the development files and some sample when we think Code_Saturne / Code_Aster coupling is in a good shape. However, I cannot give a precise date, as we don't want to release something that doesn't work :-/
If you think the flow is steady, you can try to have chained calculation: Code_Saturne => Code_Aster => Code_Saturne => Code_Aster ... with enough iteration to have the FSI converged. This is already possible by having the pressure field at the walls transfered from Code_Saturne to Code_Aster (via a MED file specified in the usdpst.f90 subroutine).
This has already been done in some calculation.
David
Re: Coupling with Code_Aster
Guideline on how to chain Aster and Saturne can be found here:
http://www.advancedmcode.org/open-source-fluid-structure-interaction-chaining-code_aster-and-code_saturne.html
http://www.advancedmcode.org/open-source-fluid-structure-interaction-chaining-code_aster-and-code_saturne.html
Re: Coupling with Code_Aster
The link does not work.Can you please direct me to a working link?Would highly appreciate it.Thank you.I have the same kind of need in running an FSI simulation for flexible walled artery.Luigi Giaccari wrote: ↑Tue Nov 23, 2010 9:43 pm Guideline on how to chain Aster and Saturne can be found here:
http://www.advancedmcode.org/open-sourc ... turne.html