code_saturne User's Forum

Hello, Regarding Rij, yes, the equation parameters are now common to all components, so you settings should work. Also, we just released v8.3.0 this afternoon (the tarballs are not updated yet to this website, but the GitHub repo has been synced), and we now have an option to disable flux reconstruc...

Hello, The change is due to the fact that in v8.0, the RSM model's "irijco" option's behavior was modified, and not a compiler issue. - In v7.0, with a coupled Rj model, you have a symmetric tensor field "rij", while with uncoupled model, you have separate "r11, r12, ...&quo...

Hello,

You should rather check the cs_post_stress_tangential function in src/base/cs_post_util.cpp, and use that as an example, keeping the normal rather than tangential component in your case.

Regards,

Yvan

Hello, stress_normal is not actually stored as a field, but evaluated locally using a cs_function_t mechanism. The field which is stored is named "boundary_stress" or something similar. Be careful, it is currently extensive and not intensive, so you need to divide values by the surface. Be...

Hello, Actually, using: git fetch origin master git cherry-pick fa6d25e5a3ff43a8e53da8e073d37dcb15e0bb75 From the v8.2 branch "almost" works. The C to C++ conversion is not the issue, You can run the command and edit cs_turbulence_rij do see the merge conflicts (between "<<<<<", ...

Hello,

I just fixed the issue in master, v8.2, and v8.0 branches, and synced the GitHub repo.

Best regards,

Yvan

Hello, Are you using v8.0, v8.2, or the master branch ? The time-stepping priority you describe does sound like a bug, unreported/noticed so far, so we'll need to check that. Regarding the clippings, Jean-François just pushed a change allowing separate deactivation of clippings for Rij and epsilon, ...

Hello,

I am not sure about details, but talked about it a bit with my colleague, and he expects to push a fix within a few days. I am not sure how much influence this can have on the computation.

Best regards,

Yvan

Hello,

I reproduce the issue also on my side. We'll try to fix this soon.

Best regards,

Yvan

Hello,

I think some colleagues are working on trying to solve this sort of issue (so they have observed it too), but I don't know how much progress they have made. I'll remind them to check the forum if they find a bit of spare time...

Best regards,

Yvan