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 can I get daily output data ?

scs_wy@yahoo_cn

New Member
Thank you for your reply,suvarchal.
I kown that I can get OCN daily data by modifying the namelist "tavg_nml".But I don't kown how to get ATM daily data.All the ATM output data are monthly.
refer to ccsm user documentation ...page 22
Do you mean to modify the namelist "HIST_OPTION".But it does not apply to other component history files.
 
you can modify atm namelist(guess atm.stdin in ccsm) use variables such as
fincl2,nhtfrq(2) .. for more details refer to cam3 userguide
http://www.ccsm.ucar.edu/models/atm-cam/docs/usersguide/

scs_wy said:
Thank you for your reply,suvarchal.
I kown that I can get OCN daily data by modifying the namelist "tavg_nml".But I don't kown how to get ATM daily data.All the ATM output data are monthly.

Do you mean to modify the namelist "HIST_OPTION".But it does not apply to other component history files.
 

scs_wy@yahoo_cn

New Member
I add the namelist "nhtfrq= -24" in the file cam.buildnml_prestage.csh($CASE/Buildnml_prestage) and run the model.
But there is no daily Atm data but a file called "case.cam2.h0.0001-01-01-00000.nc"(/EXE/CASE/atm/)
Can somebody give more information about "nhtfrq"?
thanks..
 
i guess you missed out nhtfrq(?)

scs_wy said:
I add the namelist "nhtfrq= -24" in the file cam.buildnml_prestage.csh($CASE/Buildnml_prestage) and run the model.
But there is no daily Atm data but a file called "case.cam2.h0.0001-01-01-00000.nc"(/EXE/CASE/atm/)
Can somebody give more information about "nhtfrq"?
thanks..
 

hannay

Cecile Hannay
AMWG Liaison
Staff member
The variable NHTFRQ allows to write different frequency for each history files.
NHTFRQ(1) sets the frequency in the history file "*.h0.*.nc"
NHTFRQ(2) sets the frequency in the history file "*.h1.*.nc"
and so on...

If you output several history files you willl need to define the fields you want to include in the history files other than "*.h0.*.nc". (The default history fileds are only set for "*.h0.*.nc")
For this purpose, you should use the namelist variables FINCL
FINCL1 adds fields in the history file "*.h0.*.nc"
FINCL2 adds fields in the history file "*.h1.*.nc"
and so on...

If you save daily output, you may want to save the output in the "*.h1.*.nc" and not "*.h0.*.nc"
Then, you can do a careful selection of the fields you want to save daily and this way you can avoid to have too many big files.

Notice that the variable MFILT allows you to define the number of timesteps to write in each history files.

Here is an example:
fincl2 = 'U', 'V', 'T', 'Q', 'CLOUD'
nhtfrq = 0, -24
mfilt = 1, 10

In this example, you save monthly means in the file "*.h0.*.nc" all the default history variables.
You save daily means in the file "*.h1.*.nc" for the variables 'U', 'V', 'T', 'Q', 'CLOUD'.
 
Top