I have trouble with the compressible module in Code Saturne v6.3.0.
I am trying a testcase which runs well on v5.0.4, but fails on v6.3.0 As far as I can see from the listing/run_solver.log (attached) something is going wrong in the application of boundary conditions.
System is Linux Mint 18.3 Sylvia 64-bit (Ubuntu 16.04.7 LTS based), installation/compliations of Code Saturne went fine and calculation as incompressible works, but fails when incompressible.
Any help in solving this will be appreciated.
Boundary conditions for Compressible analysis v5.3.2, v6.0.6 v6.3.0 [Solved]
Forum rules
Please read the forum usage recommendations before posting.
Please read the forum usage recommendations before posting.
Boundary conditions for Compressible analysis v5.3.2, v6.0.6 v6.3.0 [Solved]
- Attachments
-
- run_solver.log
- (25.67 KiB) Downloaded 124 times
-
- setup.xml
- (9.81 KiB) Downloaded 133 times
Last edited by tpa on Sat Mar 20, 2021 6:02 pm, edited 2 times in total.
Re: Compressible analysis in v6.3.0 [Closed]
Might be caused by compilation environment issues. I close the topic for now.
Re: Boundary conditions for Compressible analysis v5.3.2, v6.0.6 v6.3.0 [Reopened]
Hi again.
This behaviour seems to persist on all versions I have tested after v5.0.4. In an effort to locate the cause and rule out the possibilities of a defect build environment, I most recently made the following:
I made a fresh install of Debian 10 (Debian seems to be the mother of several mainstream distros like Ubuntu and Mint, and seems to be the preferred distro by EDF). On that I installed from the repositories Code Saturne 5.3.2 and I tried to reproduce the analysis of a de Laval nozzle, which I recently uploaded in the "Flow Modeling Examples" section.
It is quite clear from the listing that some information is lost between the definition of boundary zones and the application of boundary conditions. The number of affected boundary faces 945 (i.e. non-affected, actually ) corresponds to the total number of faces in the boundary regions so this is not depending on the type of boundary condition.
I have not tried to apply boundary conditions manually with user FORTRAN to see if that helps. Mostly because I feel not really confident of how to do so.
Another peculiarity is that in v5.0.4 (built locally) for this kind of analysis I have the option in Time settings to select timestep Variable (actually adaptive on Courant number). This option is not selectable in the GUI of 5.3.2 when I setup this analysis.
So at this stage I am pretty sure that there is a bug somewhere.
I highly appreciate the work you put in to Code Saturne and hope that this can be addressed at some stage of development. For now I live happy with my v5.0.4 but I see there are other users who have challenges.
Best regards.
This behaviour seems to persist on all versions I have tested after v5.0.4. In an effort to locate the cause and rule out the possibilities of a defect build environment, I most recently made the following:
I made a fresh install of Debian 10 (Debian seems to be the mother of several mainstream distros like Ubuntu and Mint, and seems to be the preferred distro by EDF). On that I installed from the repositories Code Saturne 5.3.2 and I tried to reproduce the analysis of a de Laval nozzle, which I recently uploaded in the "Flow Modeling Examples" section.
It is quite clear from the listing that some information is lost between the definition of boundary zones and the application of boundary conditions. The number of affected boundary faces 945 (i.e. non-affected, actually ) corresponds to the total number of faces in the boundary regions so this is not depending on the type of boundary condition.
I have not tried to apply boundary conditions manually with user FORTRAN to see if that helps. Mostly because I feel not really confident of how to do so.
Another peculiarity is that in v5.0.4 (built locally) for this kind of analysis I have the option in Time settings to select timestep Variable (actually adaptive on Courant number). This option is not selectable in the GUI of 5.3.2 when I setup this analysis.
So at this stage I am pretty sure that there is a bug somewhere.
I highly appreciate the work you put in to Code Saturne and hope that this can be addressed at some stage of development. For now I live happy with my v5.0.4 but I see there are other users who have challenges.
Best regards.
Code: Select all
===============================================================
MAIN CALCULATION
================
===============================================================
===============================================================
INSTANT 0.200000000E-05 TIME STEP NUMBER 1
=============================================================
-----------------------------------------
Property Min. value Max. value
-----------------------------------------
density 0.1204E+01 0.1204E+01
molecular_viscos 0.1830E-04 0.1830E-04
turbulent_viscos 0.1765E-02 0.1765E-02
-----------------------------------------
--- Diffusivity:
-----------------------------------------------
Scalar Number Min. value Max. value
-----------------------------------------------
TotEner 1 0.3417E-04 0.3417E-04
temperature 2 0.2495E-01 0.2495E-01
-----------------------------------------------
** INFORMATION ON BOUNDARY FACES TYPE
----------------------------------
-------------------------------------------------------------------------
Boundary type Code Nb faces
-------------------------------------------------------------------------
Sub. enth. inlet 11 0
Ptot, Htot 10 521
Imp inlet/outlet 7 187
Subsonic outlet 9 237
Supersonic outlet 8 0
Smooth wall 5 6031
Rough wall 6 0
Symmetry 4 0
Undefined 1 0
-------------------------------------------------------------------------
** BOUNDARY MASS FLOW INFORMATION
------------------------------
---------------------------------------------------------------
Boundary type Code Nb faces Mass flow
---------------------------------------------------------------
Sub. enth. inlet 11 0 0.000000000E+00
Ptot, Htot 10 521 0.000000000E+00
Imp inlet/outlet 7 187 0.000000000E+00
Subsonic outlet 9 237 0.000000000E+00
Supersonic outlet 8 0 0.000000000E+00
Wall 5 6031 0.000000000E+00
Symmetry 4 0 0.000000000E+00
Undefined 1 0 0.000000000E+00
---------------------------------------------------------------
@
@ UNINITIALIZED BOUNDARY CONDITIONS
@ Number of boundary faces 945; variable Wall distance
@ icodcl variable last face 5564
@
@
@
@
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@
@ @@ WARNING: ABORT DURING THE BOUNDARY CONDITIONS CHECK
@ ========
@
@ Uninitialized boundary conditions : 945
@ Unexpected boundary conditions:
@ on the scalars : 0
@ on the scalars representing
@ a variance : 0
@ Incoherencies:
@ between velocity and scalars : 0
@
@ The calculation will not be run.
@
@ Verify the parameters given via the interface or
@ cs_user_boundary_conditions.
@
First face with boundary condition definition error
(out of 945)
has boundary condition type 10, center (-0.01, 0.0226651, -0.00711121)
cs_boundary_conditions.c:363: Fatal error.
Some boundary condition definitions are incomplete or incorrect.
For details, read the end of the calculation log,
or visualize the error postprocessing output.
- Attachments
-
- 20210307-1100.zip
- (2.48 MiB) Downloaded 131 times
-
- Posts: 4085
- Joined: Mon Feb 20, 2012 3:25 pm
Re: Boundary conditions for Compressible analysis v5.3.2, v6.0.6 v6.3.0 [Reopened]
Hello,
Looking at your error message, it seems similar to the issue described in the following thread in which you also answered : viewtopic.php?f=2&t=2788&start=10 .
I also attach the Laval Nozzle setup from our test suite. This setup isvalid for v6.; I also have an update for v7, which I can send separately. This case uses user-defined functions, so is not impacted by the GUI bug.
Note also that the compressible version is not the most used and tested part of code_saturne, and only a few people have worked on it and used it (explaining more potentially undetected issues), though we certainly appreciate feedback and participation around that version.
Regarding the GUI bug, it is fixed for future v7.0 and v6.0 releases.
Best regards,
Yvan
PS: i will probably move this thread to the general usage rather than install section of the forum in the near future, as it seems to be less and less of an install issue (so if you do not find it in this section anymore, check in the general usage section).
Looking at your error message, it seems similar to the issue described in the following thread in which you also answered : viewtopic.php?f=2&t=2788&start=10 .
I also attach the Laval Nozzle setup from our test suite. This setup isvalid for v6.; I also have an update for v7, which I can send separately. This case uses user-defined functions, so is not impacted by the GUI bug.
Note also that the compressible version is not the most used and tested part of code_saturne, and only a few people have worked on it and used it (explaining more potentially undetected issues), though we certainly appreciate feedback and participation around that version.
Regarding the GUI bug, it is fixed for future v7.0 and v6.0 releases.
Best regards,
Yvan
PS: i will probably move this thread to the general usage rather than install section of the forum in the near future, as it seems to be less and less of an install issue (so if you do not find it in this section anymore, check in the general usage section).
- Attachments
-
- 30_LAVAL_NOZZLE.tar.gz
- (320.94 KiB) Downloaded 137 times
Re: Boundary conditions for Compressible analysis v5.3.2, v6.0.6 v6.3.0 [Reopened]
Hi Yvan.
Thank you very much. This is highly appreciated. I have recently had my computer occupied by parametric investigations on air-air ejectors so I have had good use of the compressible module.
Best regards and thank you to all the good people and EDF who made this possible.
Thank you very much. This is highly appreciated. I have recently had my computer occupied by parametric investigations on air-air ejectors so I have had good use of the compressible module.
Best regards and thank you to all the good people and EDF who made this possible.
-
- Posts: 4085
- Joined: Mon Feb 20, 2012 3:25 pm
Re: Boundary conditions for Compressible analysis v5.3.2, v6.0.6 v6.3.0 [Reopened]
Hello,
I am able to run the case with the smaller time step on all releases of v5.0, up to v5.0.13, but this is broken by my patch for incorrect BC handling by the GUI. I will need to investigate further, but I guess that using the full BC's leads to steeper boundary conditions, because that patch should be used to get consistent BC's (at least, BC's as expected).
I'll keep you informed.
Best regards,
Yvan
I am able to run the case with the smaller time step on all releases of v5.0, up to v5.0.13, but this is broken by my patch for incorrect BC handling by the GUI. I will need to investigate further, but I guess that using the full BC's leads to steeper boundary conditions, because that patch should be used to get consistent BC's (at least, BC's as expected).
I'll keep you informed.
Best regards,
Yvan
Re: Boundary conditions for Compressible analysis v5.3.2, v6.0.6 v6.3.0 [Reopened]
And thank you here in this thread as well. It is very kind of you to take this topic up for further investigations. If I can assist, somehow, please let me know. here or at github where I have posted as well. I now have a fresh Debian Buster ready for testing where I can use the libraries of Salome-MECA 2020 (Salome 9 based) for the build.
Re: Boundary conditions for Compressible analysis v5.3.2, v6.0.6 v6.3.0 [Solved]
To the best of my knowledge the issues seem to be solved. I have not tested all mentioned versions, though. My thanks and kudos to the organisation and crew behind Code_Saturne.