Scheduled Downtime
On Tuesday 24 October 2023 @ 5pm MT the forums will be in read only mode in preparation for the downtime. On Wednesday 25 October 2023 @ 5am MT, this website will be down for maintenance and expected to return online later in the morning.
Normal Operations
The forums are back online with normal operations. If you notice any issues or errors related to the forums, please reach out to help@ucar.edu

How do I change history file output frequency for CPL?

I want to change the output frequency of output for CPL. For example, I want "x2oacc_ox_Foxx_tauy" every calculation step, however cpl only output history file at the end of the run.(The data locates in restart, names like '${CASENAME}.cpl.r.0006-01-01-00000.nc')So, I'd like to know if there is way to increase the frequency. Appreciate if you have suggestions how to go about it. 
 
Thanks a lot! I followd your advice and output cpl history file.I'd like to ask another question:  if there is a way that I can read these output variables such as 'x2oacc_Facc_taux' back in cpl, that is, I want to use these output variables to cover variables during a cesm run.Thanks again!
 

tcraig

Member
There is currently no method for having the coupler read in data to overwrite "active" coupling data.  There is a capability in some data models to read in coupler history files and have the data models pass that data to the coupler.  That's the typical approach to using coupler data for coupling.
 
I noticed that  cesm can automatilly output CPLHIST3Hr data like 'b40mh6ka1d002_3h.0899-01.nc', is there another way  to achieve this goal other than edit HIST_N&HIST_OPTION?
 

tcraig

Member
There are several driver/coupler namelist flags that write out particular data.  You can find the namelist variables in the coupler user guide on the CESM web page.  In particular, there are namelist like histaux_a2x3hr that turns on these extra history files.  These features exist to generate coupler data to drive models.  These namelists should work.  If you want to output different data from the coupler, you should be able to mimic the current implementation in the coupler to add whatever special coupler data writes you need.
 
Top