code_saturne User's Forum

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

Hello, Thanks for the feedback. Regarding coupling between code_saturne and code_aster, the old coupling based on Salome's YACS module has been broken since 2019 I believe (I last tested it with salome_meca 2017), and its architecture was a dead end (defined more for project constraints which are no...

Hello, I see you have used different BC types (Dirichlet or Neumann) for different velocity components, and I doubt this will work. I am not sure which BC type will be used, but the processing of the user-defined BC conditions into the coefa/coefb values described in the theoretical documentation in...

Hello, You also need to tell the probe set which field values to plot : - Either using cs_user_postprocess_values, as per the example. - Or calling cs_probe_set_auto_var(pset, true); after the probe set creation to simply output all fields output with regular probes (i.e. as set in the GUI). You can...