different time stamp for mosart output file

TCNasa

Tom Caldwell
Member
I am trying a restart run. However, my run fails because it says it can't find

July13-base.mosart.r.2010-01-01-14400.nc

Looking at my restart path, I see that the mosart file has a different timestamp than the others in my startup run:

../../July13-base/run/finidat_interp_dest.nc
../../July13-base/run/July13-base.cam.r.2010-01-01-14400.nc
../../July13-base/run/July13-base.cam.rh0.2010-01-01-14400.nc
../../July13-base/run/July13-base.cam.rs.2010-01-01-14400.nc
../../July13-base/run/July13-base.cice.r.2010-01-01-14400.nc
../../July13-base/run/July13-base.clm2.r.2010-01-01-14400.nc
../../July13-base/run/July13-base.clm2.rh0.2010-01-01-14400.nc
../../July13-base/run/July13-base.cpl.r.2010-01-01-14400.nc
../../July13-base/run/July13-base.mosart.r.2010-01-01-21600.nc
../../July13-base/run/July13-base.mosart.rh0.2010-01-01-21600.nc


How do I get the file to have the correct timestamp?

Tom
 

erik

Erik Kluzek
CSEG and Liaisons
Staff member
The problem is that MOSART is normally coupled on a 3-hourly frequency, so can't write a restart at 4 hours into the day. So you need to make sure you save the restarts somewhere on that 3-hourly frequency.

So I would start the run over and make sure REST_N and REST_OPTION produces restart files that will work for MOSART. And then you should be good going forward.
 

TCNasa

Tom Caldwell
Member
Ok thanks. I'm going to run a full day. Then the mosart restart file should be on hour 0 of next day with the rest of the files.
I will let you know if it works.
 
Back
Top