Hello,
I'm using Code_Saturne with Hypermesh (for meshing) and Paraview (for postprocessing), i'm using .cgns extension for the mesh to be recognized by CS. All my boundaries (3 Walls, 1 inlet, 1 outlet) are here in the boundary condition window, but when i'm loading the result (.case file) in paraview i have only 2 entities : fluid domain and boundary conditions (which correspond to the entities in CS --> Calculation control --> Mesh).
How can I do to have all my boundaries present for the postprocessing (for exemple if I need to integer over an inlet) ?
Thank you
How to have all the boundaries in the output file
Forum rules
Please read the forum usage recommendations before posting.
Please read the forum usage recommendations before posting.
-
- Posts: 4208
- Joined: Mon Feb 20, 2012 3:25 pm
Re: How to have all the boundaries in the output file
Hello,
The EnSight format is not well suited to this: to show separate boundary or volume regions, we need to output all boundaries as separate sub-meshes. This is done in in preprocessing/mesh quality verification mode, but not for general results (as this would also lead to artificial boundaries and degrade performance).
CGNS allows this be we do not yet output boundary conditions in postprocessing output (as CGNS is still missing some options such as partial writes for this, or was missing those last time I checked).
So for your needs, the MED format could be interesting, though this assumes postprocessing the the Paravis (ParaView + modules + MED format reader) tool for the SALOME platform.
But when defining postprocessing output in Code_Saturne, you can define additional sub-meshes, so you can for example create a postprocessing mesh only for the inlet or other selected sub-volumes or boundaries, and output values on those. Thiw will work whether you are using EnSight, CGNS, or MED output (but is less useful for MED unless you want to reduce file size, since the reader can also handle this 'on the fly" based on cell or face groups).
Regards,
Yvan
The EnSight format is not well suited to this: to show separate boundary or volume regions, we need to output all boundaries as separate sub-meshes. This is done in in preprocessing/mesh quality verification mode, but not for general results (as this would also lead to artificial boundaries and degrade performance).
CGNS allows this be we do not yet output boundary conditions in postprocessing output (as CGNS is still missing some options such as partial writes for this, or was missing those last time I checked).
So for your needs, the MED format could be interesting, though this assumes postprocessing the the Paravis (ParaView + modules + MED format reader) tool for the SALOME platform.
But when defining postprocessing output in Code_Saturne, you can define additional sub-meshes, so you can for example create a postprocessing mesh only for the inlet or other selected sub-volumes or boundaries, and output values on those. Thiw will work whether you are using EnSight, CGNS, or MED output (but is less useful for MED unless you want to reduce file size, since the reader can also handle this 'on the fly" based on cell or face groups).
Regards,
Yvan
Re: How to have all the boundaries in the output file
Thank you for your answer,
If I understand correctly, I have the choice between :
- put the output control as MED file
- create submeshes (and keep EnSight or CGNS as output format)
How do you do to create sub meshes and postprocess them ?
Regards
If I understand correctly, I have the choice between :
- put the output control as MED file
- create submeshes (and keep EnSight or CGNS as output format)
How do you do to create sub meshes and postprocess them ?
Regards
-
- Posts: 4208
- Joined: Mon Feb 20, 2012 3:25 pm
Re: How to have all the boundaries in the output file
Hello,
Yes this is correct. You can use the GUI to define additional postprocessing meshes (Calculation Control/Output Control/Mesh.
For user subroutines, you can also check examples in the Doxygen documentation.
Regards,
Yvan
Yes this is correct. You can use the GUI to define additional postprocessing meshes (Calculation Control/Output Control/Mesh.
For user subroutines, you can also check examples in the Doxygen documentation.
Regards,
Yvan