Use it to handle parameters from restart snapshots. Also separate
printing I/O parameters from I/O module initialization.
Signed-off-by: Grzegorz Kowal <grzegorz@amuncode.org>
Parameters such block dimensions, the base level dimensions, or the
domain extrema cannot be modified when the job is restarted, so read
them from the restart snapshots.
Also add new subroutine to IO read integer vector attribute from the
HDF5 snapshots.
Signed-off-by: Grzegorz Kowal <grzegorz@amuncode.org>
If the job was restart with different maxlev, then
initialize_coordinates() has to know about it, so it generate
appropriate coordinates.
Read maxlev from the restart snapshot, if the job was restarted, and set
toplev as the maximum value between the previous and current maxlev.
Signed-off-by: Grzegorz Kowal <grzegorz@amuncode.org>
If we run a job from a restart snapshot and modify some of the
parameters in the parameter file, this could lead to problems. Some
parameters, like the set of equations, equation of state, or block
dimensions, simply cannot be modified. Therefore, any such parameter,
modifies in the parameter file, should be overwritten with the value
from the restart snapshot. The purpose of these subroutines is to read
these parameters from restart snapshots.
Signed-off-by: Grzegorz Kowal <grzegorz@amuncode.org>
