Using output from a previous run in datm when coupler history is not available

[eisenman@ucsd_edu]

I posted this as part of a question yesterday on the "CESM - General" Forum (no responses yet), but I realized this may be a more appropriate Forum for the question.

We're using CESM1.1.2 on Yellowstone and trying to do a run that uses datm with COREv2 data replaced by the output from the preindustrial control run, "b40.1850.track1.1deg.006". We found instructions for setting datm to use coupler history forcing from a previous simulation at http://www.cesm.ucar.edu/models/cesm1.1/clm/models/lnd/clm/doc/UsersGuide/x9068.html . But it looks like most simulation output on hsi at /CCSM/csm, including /CCSM/csm/b40.1850.track1.1deg.006, doesn't include the history files from the coupler. Is there another place this is stored for most runs, or if not, is there a way to use forcing from the atm history output of a previous run?

Thanks,
Ian

 

[eisenman@ucsd_edu]

I found the answer to this question (thanks Nan Rosenbloom!) and wanted to post it here in case others have similar issues (note that any misconceptions here are surely my own and not Nan's).datm wants very high frequency atmospheric forcing data, which is not typically saved in most runs - most runs don't save coupler history files. So you need to simulate another ~30 years from the end of the control run with the model specified to output 3hr coupler history fields. For some runs, including b40.1850, this has already been done (it's often called a MOAR run). For b40.1850, it's at /CCSM/csm/b40.1850.track1.1deg.006a/.

 

[eisenman@ucsd_edu]

I found the answer to this question (thanks Nan Rosenbloom!) and wanted to post it here in case others have similar issues (note that any misconceptions here are surely my own and not Nan's).datm wants very high frequency atmospheric forcing data, which is not typically saved in most runs - most runs don't save coupler history files. So you need to simulate another ~30 years from the end of the control run with the model specified to output 3hr coupler history fields. For some runs, including b40.1850, this has already been done (it's often called a MOAR run). For b40.1850, it's at /CCSM/csm/b40.1850.track1.1deg.006a/.