OPM
Use min timestep from TUNING also when updating (not only initially)
(+ using the right value, TSMINZ, initially). Together with https://github.com/OPM/opm-common/pull/3740, should eliminate side effects of --enable-tuning=true when there is no TUNING record or non-default TUNING record items.
Test failures apparently due to changing the default value of minimum time step to coincide with the Flow default (i.e., without --enable-tuning=true). [Value is written to DOUBHEAD in the .INIT file.]
@vkip Should this still be reviewed and merged or is this resolved in another way already?
@vkip Should this still be reviewed and merged or is this resolved in another way already?
To my knowledge this is not yet resolved.
Or actually, using the min timestep you maybe fixed when working on NEXTSTEP? If so the only relevant thing here might be the changed message (getting the correct value in days).