code_saturne User's Forum

Hello, In the 2nd image, I do not see the 1st 3 lines, containing the install paths, but I see the build dates are not exactly the same (3 minutes difference) in the 2 cases, so I suspect that either : - You have 2 different installs, one with MED support, the other without. - You overwrote the fixe...

Hello, Looking at the code, it seems that it is only possible to define multiple temperatures for premixed flames (Libby-Williams and EBU). For 3-point chemistry, the hinfue value is global to the model (which seems to be an unnecessary limitation, probably due to the initial coding rather that a re...

Hello, In this case, I would recommend either of 2 options : - Apply a revert of that patch on the sources for your build - Or use the gfortran Fortran compiler instead of the Intel compiler (that should be compatible with the Intel C/C++ compilers). Since very little Fortran code is left, performan...

Hello, No, to my knowledge, we have not observed this on our machines. Which version of the Intel compilers do you use (on our side, We mainly use the 2022.2 LLVM-based compilers on one cluster, and the (much) older 18.1 on another machine. I also tested with 24.1 on my local workstation. The PBS as...

Hello,

I think a colleague had plans for "summation by zone" of selected variables, which would fit here, so yes, there are plans for this in the GUI, though I have no idea on where this sits on the priority list.

Best regards,

Yvan

Hello, Yes, when you use the GUI, you only need to specify the "alpha" term, which is multipled by 0.5*|U| in the cs_gui_head_losses function, to build the ckupdc term which is itself multiplied by rho*U in the function and line you mention. When using the cs_user_head_losses term, the use...

Hello, Did you try visualizing the boundary stresses ? to check for the sensitivity when you increase the velocity ? This may help you determine if/where there is a bug (i.e. bug in you code, bug in upstream code_saturne, or no obvious bug but forces in given zone not too sensitive to velocity) ? Be...

Hello, It seems your source terms leads to temperature increasing very rapidly, and then velocity increasing very fast probably as a consequence. You might try adding the source term progresively, so as to avoid a high energy input that is not convected. I also recommend visualizing the source term ...

Hello, Temperature is computed based on enthalpy, so if you change one without changing the other, I am not too Also, the computation of rho requires specific precautions in combustion cases, and there is a relaxation parameter (check for srrom) in this regards. I would not expect a computation in w...

Hello, Which fields are you trying to turn off ? Whatever you do in d3pint, pppdfr, and d3pphy, some physical properties are updated elsewhere, and all solved combustion fields are still solved in the loop on scalars (which used to be scalai.f90 in older versions, and is now in cs_solve_transported_...