code_saturne User's Forum

Hello Matthieu, As Yvan said, a direct solver has a memory consumption which is much higher than an iterative solver. The reading of your log files is clear : Elapsed time for the full computation = 29791s and elapsed time in solving the NavSto system = 29679s Moreover, there are some differences in...

Hello Matthieu, I think there are two problems: 1. Your boundaries are defined twice. Since CDO schemes are not fully available from the GUI, some steps should be done only with user source files. This is not a satisfactory situation... 2. MUMPS as a solver for the full system is not robust since th...

Thank you for the additional information. Regarding MUMPS, you have to add "--with-mumps=/path/to/your/mumps/install" at the "configure" step. If the usage of the "--with-mumps" tag gives the same result, you have to check your config.log file to figure out what is wron...

Hello Matthieu, This is weird. It looks like a non-convergence of the solver. The system to solve is a velocity/pressure coupled system (a saddle-point problem) which is difficult to solve in general. That's why, we usually rely on the MUMPS solver for this kind of system. In the current case, this ...