Opened 7 weeks ago

Last modified 7 weeks ago

#2923 new help

Timing of dump files

Reported by: mtodt Owned by: pmcguire
Component: JULES Keywords:
Cc: mcguirepatr@… Platform: JASMIN
UM Version:

Description

Hi Patrick

I'm a bit confused about how to restart a main run. My run got to 1996:
3384195283 May 30 11:24 WFDEI_NOirrig_NOtopmodel_05deg_SEAsia.6-hourly.1995.nc
2726827375 May 30 13:26 WFDEI_NOirrig_NOtopmodel_05deg_SEAsia.6-hourly.1996.nc
4885292 May 30 09:28 WFDEI_NOirrig_NOtopmodel_05deg_SEAsia.dump.19950101.0.nc
4885292 May 30 11:24 WFDEI_NOirrig_NOtopmodel_05deg_SEAsia.dump.19960101.0.nc

Considering timestamps, file names, and file sizes (the output file for 1996 apparently didn't get finished) am I correct that dump files correspond to the start of a particular year? So, simulation for 1996 starts from dump.19960101; dump.19960101 is not the file that gets created at the end of 1996? What about spin-up dump files? Does the first spin-up dump file correspond to the start of the spin-up?

Cheers
Markus

Change History (1)

comment:1 Changed 7 weeks ago by pmcguire

Hi Markus
Yes, the dump files correspond to the start. of the year. The date of the dump is given by 0101 here which is January 1st.
The spin-up dump files are the same way.

It is very good to look at the file dates and sizes like you did.

I don't use the rose restart option. I never trusted that it would restart things properly, especially if a restart is needed in the middle of spin-up, and I didn't do any comprehensive testing to begin to trust it. Instead, I just edit the app/jules/rose-app.conf file and the suite.rc file etc. by hand to tell JULES which dump file to restart from, and the new start date, and number of remaining spinups, new log file name, etc.

Does this help?
Patrick

Note: See TracTickets for help on using tickets.