code_saturne User's Forum

Hello,

As far as I know, in the case of smooth walls, the y+ 20-30 rule applies to high-Reynolds wall laws. For low-Reynolds or "all-y+" wall laws, smaller y+ values are allowed.

I am not too sure about rough wall laws and would need to check with a colleague, but since they also include some ...

Hello,

This is probably computed in src/base/clptrg.f90. So it may be interesting to check/log/print the intermediate values used in its computation.

I'm not sure about the theory part, as there is both a legacy rough wall model, and a new one (continuous "smooth/rough" model). The newer model ...

Hello,

1) The quantities should only be on boundary faces. Do you have separate writers for volume and boundary faces ? If not, using "extract block" under ParaView might help separate them.

2) Yes, this sign is chosen from a "finite volume" rather than user perspective. A negative flux means heat ...

Hello,

It may be interesting on the code_saturne side to activate the visualization output of the thermal fluxes at walls (and wall temperature), to see what amount of heat exchange you have at the interface.

Depending on the mesh and turbulence model, the heat exchange might be underestimated ...

Hello,

The logging of the space dimension seems to be a bug, but I suspect your issue is that you have a 2D domain in Syrthes, and a 3D one in code_saturne. In the 3D disks example (whose reference setup should be updated), the "2D projection" option in the conjugate heat transfer section is set ...

Hello,

I meant that the choice of the roughness value can in itself be based on some user modeling choices. I was thinking mostly of the atmospheric cases where roughness can represent vegetation, which is accounted for in a simplified (i.e. modeled) way as a form of roughness.

Best regards,

Yvan

Hello,

I mean that Syrthes can compile its own OpenMPI library as an external dependency, but this does not seem to be the casde here.

But you may be missing a setting in the syrthes-install/setup.ini file : you should have:


ple_use=yes
syrthescfd INSTALL=yes


Otherwise, you will be missing ...

Hello,

Are you sure your code_saturne and Syrthes builds use the same MPI installation ? Mismatched MPI libraries could explain the observed behavior. Since the Syrthes install script builds its own MPI library by default, this could happen if you are not extra careful.

Best regards,

Yvan

Hello,

Not by default, but if you use the cs_restart_set_n_max_checkpoints function in.your settings (in cs_user_parameters) you should be able to do this (with an additional subdirectory per checkpoint time).

Best regards,

Yvan

Hello,

You can use iso_c_bindings to provide a C API to your Fotran code, and call that from the standard C user function.

If your Fortran code does not depend on too many internal code_saturne structures, or those can be passed as arguments, this should even continue to wrk after v9.0. If you use ...