Dear CMS,
I have been trying to run u-dr496 with 1 month jobs starting 1/9/2010 and using a 360-day calendar. Model is vn13.8 using cylc 8. It was taken from a 13.8 UKESM1.1 AMIP workflow and has a much reduced diagnostic set – only producing one output stream of monthly mean data and running (in theory) for 17 months. 17 months gives me a 4 month spin up, 12 months for the data I am interested in and a final month to make the December 2011 pp data.
However, if I run in 1 month segement the model runs the September 2010 cycle. But when it runs the October 2010 cycle it starts again with 1/9/2010 and runs 2 months. Then for November cycle it starts again with 1/9/2010 and runs 3 months… For the December cycle, the model starts 1/12/2010 and runs a month. Next cycle it runs 2 months etc. Eventually the model fails in post-process with a complaint about 0 length header when it is expected 256 words… I am guessing this is because the post-process can’t find something because the model has started again and post-process runs fast enough to not find an expected file.
If I run in three month periods then everything (so far – april 2011) is OK. I suspect I am pushing the UM system too far but is there anything I can to make it run in 1 month segments? My goal is to get the Dec 2011 output converted to pp and archived without having to do a manual intervention and use the minimum computer time!
Simon