In this group several parameters can be set which control the start of the time counting during a simulation and the total length of a job. If either one of the halt conditions below is met, CO5BOLD finishes the current step, writes a final model (plus some final information to other files), and stops execution.
For example on a CRAY one typically wants to use most of the CPU time
given for an individual batch job. In this case one can set e.g.
and the values for the other halt conditions to
real starttime f=E15.8 b=4 n='Start time' u=s 0.0Allowed values are
0.0: Set the initial time of the simulation to this value and override value from start model.
0.0: (default) Take the initial time from start model.
integer starttimestep f=I11 b=4 n='Start time step number' u=1 0Allowed values are
0: Set the initial time step of the simulation to this value and override value from start model.
0: (default) Take the initial time step count from start model.
rhd_mac_cray_module.f90). On other machines it is possible to specify the allowed total time for the job e.g. with
real cputime f=E15.8 b=4 n='CPU time' u=s 1000000.0During the run of CO5BOLD the leftover CPU time is computed by subtracting the used CPU time (which is given by
rhd_mac_sun_module.f90) from the specified total CPU time for the job.
real cputime_remainlimit f=E15.8 b=4 n='maximum remaining CPU time' u=s 2000.0Its value depends on the size of the model and the speed of the machine (more precisely the maximum CPU time per time step).
real endtime f=E15.8 b=4 n='total simulation time limit' u=s 10000.0A value
0.0deactivates this halt condition: it is not checked at all. If this parameter is set to a non-negative value a follow-up simulation should not use the same parameter file: it would stop immediately.
real plustime f=E15.8 b=4 n='simulation advance time' u=s 5.0E+07A value
0.0cancels this halt condition: it is not checked at all. This condition assures (if it is the only one) that all individual simulation runs cover (approximately) the same stellar time.
integer endtimestep f=I11 b=4 n='total simulation time step number' u=1 1234This might be useful to advance the simulation up to a point shortly before a previous simulation crashed. A value
0cancels this halt condition: it is not checked at all.
integer plustimestep f=I11 b=4 n='simulation advance time step number' u=1 2000A value
0deactivates this halt condition: it is not checked at all.