Perfect restart problem

[allencapa]

Hi all,

Recently I've been working on restart issues of ROMS, actually I'm trying to modify the restart files. But I have a stupid question about the dimensions in restart files. For instance, the zeta in restart file is like

Code: Select all

        double zeta(ocean_time, three, eta_rho, xi_rho) ;
                zeta:long_name = "free-surface" ;
                zeta:units = "meter" ;
                zeta:time = "ocean_time" ;
                zeta:coordinates = "lon_rho lat_rho ocean_time" ;
                zeta:field = "free-surface, scalar, series" ;
                zeta:_FillValue = 1.e+37 ;

while that in history file is

Code: Select all

        float zeta(ocean_time, eta_rho, xi_rho) ;
                zeta:long_name = "free-surface" ;
                zeta:units = "meter" ;
                zeta:time = "ocean_time" ;
                zeta:coordinates = "lon_rho lat_rho ocean_time" ;
                zeta:field = "free-surface, scalar, series" ;
                zeta:_FillValue = 1.e+37f ;

So my question is what the dimension 'three' means and how it affects the restart process.

Thank you in advance.
Yi

[kate]

You can read up on the ROMS timestepping on the ROMS wiki or in Sasha Shchepetkin's papers. Some schemes depend on having three time levels of some field available, while others just need two. That's what the three means. For PERFECT_RESTART, you need to save all the time levels while an imperfect restart would just save the one (as does the history file).

[allencapa]

You can read up on the ROMS timestepping on the ROMS wiki or in Sasha Shchepetkin's papers. Some schemes depend on having three time levels of some field available, while others just need two. That's what the three means. For PERFECT_RESTART, you need to save all the time levels while an imperfect restart would just save the one (as does the history file).

Hi Kate,

Thanks for your reply, that's what I'm looking for.
Best wishes