code_saturne User's Forum

In the v7 GUI, there is a setting for "Algorithm to take into account the density variation in time" with options for "automatic", "Boussinesq...", "dilatiable steady...", and "dilatable unsteady..." What is "automatic" in this case? The v7...

In v7, there is an option for using a "code_saturne mesh *.csm", but there doesn't appear to be any definition of what this format is in the User or Theory guide pdfs, or the website feature list <https://www.code-saturne.org/cms/features/mesh> ... is there a definition of this somewhere? ...

Having just seen that another Code_Saturne meeting took place (not having seen any announcements about it)... I was wondering, given that it was broadcast remotely, were any of the talks recorded in a way that we can still see online?

Thanks,
Jeff

Ok, thanks for the response. If it's still a question at some point in January, I'll come back for more info. That said, given that wall functions are not visible from the GUI, and the GUI has been promoted for some years now, it seems like a reasonable assumption that the options available by defau...

To try again on this...  For something simple... I assume that the C_log that appears in Eq. I.5.25 should be removed and was a typo? For default k-epsilon, for example, looking through the code, the friction velocity is called uk, and is determined from the value of k, using the theoretical log-lay...

The problem was noticed with VOF enabled in v6.0. I am able to replicate it with v6.2.0. In some sense, perhaps it is logical to always save the fluid properties for VOF. But in this case, it is strange from a user interface point of view if the checkbox in the volume solution control panel does not...

When looking at the output files, is it normal that one cannot turn off the density and molecular_viscosity fields from the default writer? For some test cases, in order to save space, I un-check the fluid properties from the "post-processing" list in the volume solution control, but the f...

It appears to be defined in the first line of the create() function of class Study of bin/cs_create.py

I presume that it is to assume that the user just wants to create a new case in an existing study, but in my case, the assumption was wrong

It seems that one cannot explicitly create a new study if the study name is identical to the name of the current folder. Are there any plans for this to change, or is this behavior documented somewhere? (Or could at least a warning be printed? -- it does not seem ideal from the user experience side ...

...?