BLOM date missmatch for hybrid run with OCN_NCPL=1

[TomasTorsvik]

With OCN_NCPL=1 it is daily ocean coupling. Probably, the time management change associated with the major code restructuring (commit e2a4230) has not been properly tested with daily coupling (most CMIP6 simulations uses sub-diurnal coupling frequency). This should of course be corrected and is likely unrelated to the restart filename generation of this PR.

Originally posted by @matsbn in #124 (comment)

[TomasTorsvik]

Has hybrid restart of stand-alone BLOM/iHAMOCC been supported earlier? Is this a functionality we want/need to support?

[JorgSchwinger]

Is this a stand-alone issue? If it is a coupling frequency issue, as Mats suspected, then it would also be there in coupled mode if you would go back to daily coupling frequency.

[TomasTorsvik]

Looks like the problem is specific for hybrid runs. I was able to restart a branch run with noresm2.0.5 NOINYOC restart files.

[jmaerz]

This issue, first mentioned in #124 (comment) , still persists. I was/am having the same issue, when trying the hybrid run setup in stand alone mode, while, as @TomasTorsvik pointed out, a branch run is possible.