yh3019@columbia_edu
Member
Hi all,
I am wondering if the restart file would include the accumulating history files in the middle of an accumulation period in CESM2?
My experiments are very expensive so I got my restart file to be written every 10 days to avoid some abrupt stop due to memory problems or run-time limits. However, I later realized that the monthly history output may not be really monthly-mean values if my model stops before the end of one month and gets restarted from that time later. For example, if my experiment stops on Jan-20 and I restart from Jan-20, would my h0 files be the mean of whole Jan or be the mean of Jan20-Jan31 only?
I only found some information about CESM1:
Many models are also able to restart accumulating history exactly files in the middle of an accumulation period, but this is not a current requirement in CESM1. In production, the model is usually started and stopped on monthly boundaries so monthly average history files are produced cleanly. The run length of a CESM1 production run is usually specified using the nmonths or nyears option and restart files are normally written only at the end of the run.
Thanks a lot!
Yu
I am wondering if the restart file would include the accumulating history files in the middle of an accumulation period in CESM2?
My experiments are very expensive so I got my restart file to be written every 10 days to avoid some abrupt stop due to memory problems or run-time limits. However, I later realized that the monthly history output may not be really monthly-mean values if my model stops before the end of one month and gets restarted from that time later. For example, if my experiment stops on Jan-20 and I restart from Jan-20, would my h0 files be the mean of whole Jan or be the mean of Jan20-Jan31 only?
I only found some information about CESM1:
Many models are also able to restart accumulating history exactly files in the middle of an accumulation period, but this is not a current requirement in CESM1. In production, the model is usually started and stopped on monthly boundaries so monthly average history files are produced cleanly. The run length of a CESM1 production run is usually specified using the nmonths or nyears option and restart files are normally written only at the end of the run.
Thanks a lot!
Yu