code_saturne User's Forum

Hello,

If you want to replace "cs_real_t prdtur = 1;", since it is a local definition, a user-defined file will not be enough.

You can try using the modified source code file as a user-defined file, but I am not sure whether this will work or lead to link-time issues. It did work in most cases ...

Hello,

The slope test does not need to be toggled, as it adjusts to the scheme.

It seems the setting is disabled whenever you are using an LES turbulence model, because in this case a sencond(order scheme is required. In practice though, we seomtimes recommend adding 2% upwind (perhaps even) to ...

Hello,

If you still avec access to the build directory, you could edit the source code to apply the patch, then got to the build directory and simply re-run "make install".

Otherwise you may try to include the fixed file with user-define files, but you may have link issues related to multiply ...

Hello,

This seems to be due to an incorrect handling of reducers, fixed in commit 5de8c9.

So updating the code should fix hte issue (v9.1 was released Dec 30, so this is a good option).

Best regards,

Yvan

Hello,

The iprofc array was removed in commit 8edbd699(2023-03-29), with the following message:

[Atmo] Chemistry, remove iprofc array.

It was use to specify that we want to use chemistry profile for inlets.
This can already be done by specifying another value in
cs_user_boundary_conditions ...

Hello,

Do you use a specific tool or setting to obtain backtraces in the SLURM output ? By default, code_saturne installs its own exception handler, which logs backtraces (with less details) to error* files, but some libraries (at least PT-Scotch and ParaView, possibly others) can force their own ...

@Antech I am not sure I understand your remark for the SST model being required for CHT.
CHT can be used with any turbulence model, as well as for laminar flows. Quality of heat exchange modeling will depend on the chosen model, and research is still ongoing to improve the state of th art in this ...

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 ...

Hello,

There may be several issues here. Looking at the mesh, it seems that only the fluid portion is extruded, not the solid portion. Is this desired ? In any case, the code separates the fluid and solid parts before extrusion, which explains why y have more auto:internal_coupling_0_fluid than ...

Hello,

The issue is due to a change in v9.0. In dimensions.f90, replacing

subroutine ssh_dimensions ( &
Ns, Nr, Nr_photolysis)

by:

subroutine ssh_dimensions(Ns, Nr, Nr_photolysis) &
bind(C, name='cs_f_ssh_dimensions')

Should fix the issue.

As this broke compatibility and consistency, the ...