code_saturne User's Forum

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

Hello,

I think you forgot to post the files.

Regards,

Yvan

Hello,

The code complains it is missing some spack file. Coul you post species.spack.dat ?

Regards,

Yvan

Hello,

I checked very briefly with Martin, and it seems using a local tile step for the tracking and SDE integration should be possible (though a bit of extra validation when we do enable that would be strongly recommended).

So we'll keep that in mind, but i can't give you an exact timeline for ...

Hello,

Which version are you using ? I tried on a different case in v9.0 and it works fine.

Though beware, in the Lagrangien model, the space-varying time step only seems to apply to the carrier flow and statistics, but the Lagrangien tracking and integration of SDE's use the reference time step ...

Hello,

I am not aware of any voluntary change in the settings. So this may be a bug. Could you post a setup.xml file so we can compare the behavior between versions here an check this ?

Best regards,

Yvan