code_saturne User's Forum

Hello, and sorry for the delay, as Yvan said, the Lagrangian module theoretical part (physical modeling and trajectography step) is currently described in internal reports, which will be in the future translated and integrated in the general theoretical manual of Code_Saturne. For a description of t...

Hi,

the following link should work
http://publications.onera.fr/exl-php/vu ... /DOC376449

just click on the PDF icon to get the manuscript

Best regards,
Mathieu

Dear Chayawat, To my knowledge, it is not planned in a near future to implement dedicated models to simulate the trajectories of elongated, fiber-like objects (for instance) in a turbulent flows with the particle-tracking module of Code_Saturne, if this was what you had in mind. Additional equations...

Hi Yasmine, I fear that there is no evaporation model implemented in Code_Saturne; the fact that there is a grayed-out option in the GUI is most probably a mistake and should be corrected. If you are interested, I suggest to start by modifying the lagidp subroutine to implement the variation of the ...

Hi, starting from 3.1, Displacement.CASE is replaced by Particles.CASE with the same purpose, i.e. visualizing the time evolution of the particle position (= making animated movies with EnSight of Paraview) and additional attached variables. The setting of the particles output in the GUI has been mo...

Hi, cs_lagr_tracking.c contains currently (almost) only functions dedicated to locate the particles in the domain at the end of the time step, and to manage the interactions between particles and boundaries (see _bdy_treatment). The physical modeling is mostly in FORTRAN subroutines; for instance, l...

Hi, in the Lagrangian boundary condition, you must prescribe a number a classes other than 0 to inject particles through your inlet. (Note that due to a display bug, after setting for instance "1" class, you will have to click again on the "1" to have access to the definition of ...

Hi, from what I read, once the correction done, the pieces of codes should be equivalent. "particle.mass" is indeed the mass of one particle, so if you run a monodisperse calculation it should give basically the same value as any "ettp(ip,jmp)" (do not hesitate to perform some pr...

Hi, Maybe I am wrong, but I think you are dividing one time too many by face_area your variable vi in the CS 3.0 version of youir code. Perhaps the confusion stems from the fact that "surfbo({1,2,3}, kface)" in CS 2.0 is not a unit vector, but a vector whose norm is 'surfbn(kface)' . Howev...

Hi,

if properly activated, particle boundary statistics should then appear as variables in the postprocessing/RESULT.case file (which can be read by Paraview or Ensight for instance)

Best regards,
Mathieu