Centrifugal fan

Questions and remarks about code_saturne usage
Forum rules
Please read the forum usage recommendations before posting.
ZachJa

Re: Centrifugal fan

Post by ZachJa »

Hello, thank you!

yes, the box "auto" for inlet and outlet meshes is checked but there is no pressure or velocity output data when I open MED file with results for post-processing in ParaView, just Efforts and Yplus data.
Yvan Fournier
Posts: 4208
Joined: Mon Feb 20, 2012 3:25 pm

Re: Centrifugal fan

Post by Yvan Fournier »

Hello,

As I mentioned in the previous post, you also need to check cs_user_parameters.f90 to see how to activate postprocessing of a cell-defined variable on the boundary.

Actually, the best is to search for "Force postprocessing of projection of some variables at boundary"
(and check the example in the following lines)in SRC/EXAMPLES/cs_user_parameters-output.f90.

Regards,

Yvan
ZachJa

Re: Centrifugal fan

Post by ZachJa »

Hello, thank you.
I am not really sure how to use cs_user_parameters.f90 cause I am using GUI and as I know Fortran files have precedence over the GUI xml file, isn`t it?
So, if it is correct then I have to add some commands to get output files at specific patches (inlet/outlet).

1st - I tried the following:
<mesh id="-3" label="inlet" type="boundary_faces">
<all_variables status="on"/>
<location>inlet</location>
<writer id="-1"/>
</mesh>
but have got just Effort and Yplus values.

2nd - instead of "boundary_faces" I tried "cells" (and after "interior_faces")
but have got an error:
MED does not allow to export an empty mesh,
Mesh: "inlet" has no vertex.
Associated file: "postprocessing/results.med".


Not sure but maybe patch inlet should be defined not as mesh?
And how to get mean values (of pressure for example) ie just one number for whole patch - not a row of numbers over all nodes on patch?
Yvan Fournier
Posts: 4208
Joined: Mon Feb 20, 2012 3:25 pm

Re: Centrifugal fan

Post by Yvan Fournier »

Hello,

Yes, user subroutines take precedence over the GUI, but you need only specify specific things in the user subroutines.

For computation of average values over a whole patch, you also need user subroutines... We can try to make this sort of thing more automated in the future, but there is currently no alternative inside Code_Saturne.

A slightly less precise but simpler solution (if your geometry is not too "curved" for this) would be to use cut planes through the mesh volume in ParaView, just inside the mesh, so you can access the volume variables such as pressure and velocity.

Regards,

Yvan
Post Reply