Closed paspro closed 1 year ago
I do not reproduce this behavior on my side. Do you have any other elements which my help reproduce this ? Can you run the code under Valgrind or AddressSanitizer to see if we have an upstream issue ?
What I found out is that the specified maximum allowed time to run a case (unsteady run) influences the creation or not of checkpoints. For some values it does not create checkpoints and for others it does. For example this set of options does not create checkpoints:
<time_parameters>
<max_courant_num>4</max_courant_num>
<max_fourier_num>12</max_fourier_num>
<maximum_time>7200</maximum_time>
<property name="courant_number" label="CourantNb"/>
<property name="fourier_number" label="FourierNb"/>
<property name="local_time_step" label="LocalTime">
<postprocessing_recording status="off"/>
<probes choice="0"/>
</property>
<thermal_time_step status="on"/>
<time_passing>1</time_passing>
<time_step_max_factor>15</time_step_max_factor>
<time_step_min_factor>0.01</time_step_min_factor>
<time_step_ref>0.1</time_step_ref>
<time_step_var>0.2</time_step_var>
</time_parameters>
But if I change maximum_time to 72 then it does create checkpoints. Also, if maximum_time is 100 it does not create checkpoints but if I change it to 101 then it does create checkpoints!
Any progress on this issue?
Fixed.
I have a problem with code_saturne 8-beta and master when running an unsteady flow case in the sense that the code does not create any checkpoint files in the checkpoint directory and therefore a restart is not possible. For the same case, code_saturne 7.3 works properly and it creates checkpoint files.
The relevant setting in the setup.xml file is the following: