Code_Saturne and Code_Aster coupling workflow
Forum rules
Please read the forum usage recommendations before posting.
Please read the forum usage recommendations before posting.
-
saintlyknighted
- Posts: 20
- Joined: Sun Aug 06, 2023 3:40 am
Code_Saturne and Code_Aster coupling workflow
Hi, I am trying to take the thermal loads from my Code_Saturne T_Junction and using that to get thermal stresses on the T-Junction pipe in Code_Aster. I have two med results files from Code_Saturne, which are results_Boundary.med and results_Fluid_domain.med. What is the full workflow to go about inputting this to Code_Aster and using this as a b.c. to get thermal stresses and displacements? Given the software is mostly in French I am a bit lost.
-
Yvan Fournier
- Posts: 4274
- Joined: Mon Feb 20, 2012 3:25 pm
Re: Code_Saturne and Code_Aster coupling workflow
Hello,
Since the fluid and solid domains do not overlay, the boundary mesh data should be sufficient.
I do not know how you can define code_aster boundary conditions based on data in the MED file. I am not sure whether code_aster can read both face or vertex data (here we have face data), or whether it can do the interpolation, but use MEDCoupling, this should be possible upstream if code_aster does not do this.
In any case, if the code_saturne computation is not and ALE computation, you may have stresses but not displacments in the file. Also, you will have the boundary temperature and/or heat flux only if you activated them in the boundary postprocessing section. Also, since this is not real coupling, the boundary conditions used in code_saturne might not be completely equivalent to those you would have with real coupling, but that may be sufficient.
Note that true code_saturne/code_aster coupling is not operational yet (it has been delayed because of bugs or incomplete features in MEDCoupling), and should first handle mesh deformation, but not the thermal aspects to my knowledge.
Best regards,
Yvan
Since the fluid and solid domains do not overlay, the boundary mesh data should be sufficient.
I do not know how you can define code_aster boundary conditions based on data in the MED file. I am not sure whether code_aster can read both face or vertex data (here we have face data), or whether it can do the interpolation, but use MEDCoupling, this should be possible upstream if code_aster does not do this.
In any case, if the code_saturne computation is not and ALE computation, you may have stresses but not displacments in the file. Also, you will have the boundary temperature and/or heat flux only if you activated them in the boundary postprocessing section. Also, since this is not real coupling, the boundary conditions used in code_saturne might not be completely equivalent to those you would have with real coupling, but that may be sufficient.
Note that true code_saturne/code_aster coupling is not operational yet (it has been delayed because of bugs or incomplete features in MEDCoupling), and should first handle mesh deformation, but not the thermal aspects to my knowledge.
Best regards,
Yvan