Inconsistency in Initial Condition Key ID (ics_phys) !

While performing a restart run, the initial condition is not correctly applied if the hardcoded index "1" is used instead of the parameterized key ics_phys. As a result, the simulation incorrectly starts from zero value (0.00) rather than using the final condition value (restart file) from the previous run.

This issue was identified in a one-day restart simulation, where the expected initial value for the surface elevation, zeta, was 0.4837, but the model initialised from zero when using the keyID index value 1. However, replacing 1 with ics_phys allowed the model to retrieve and apply the restart condition correctly.

The case where the Key ID index value (=1) is used ;

modfiles(io_inicon,1,1)%status   = 'R'
modfiles(io_inicon,1,1)%form     = 'N'
modfiles(io_inicon,1,1)%filename = 'DATA/CoSAM/restart/init_CoSAM_20190101_physics.nc' 

results ;

(Remember, what you see in the plot is the result of a one-day model run test.) The restart files are generated from a one-year spin-up simulation.

 

(you can see the value of 0.4837, which is the value for zeta at a selected location at 2019/01/01;00:00:000, but in the model simulation starts from 0)

The case the index value is replaced with Key ID, ics_phys;

!---initial condition
modfiles(io_inicon,ics_phys,1)%status   = 'R'
modfiles(io_inicon,ics_phys,1)%form     = 'N'
modfiles(io_inicon,ics_phys,1)%filename = 'DATA/CoSAM/restart/init_CoSAM_20190101_physics.nc'

(Here you can see the model starts from 0.4837)

And in the case of spin-up simulations (that is when we initialise the model with CMEMS files), giving the key-ID index value (=1) works perfectly. So this issue is present only for the restart files generated by COHERENS—this has also been tested!