gng@usgs_gov
New Member
I am creating my own meteorological data sets as input to CLM, and I am using hourly data (unlike the default 3- and 6-Hrly in the Qian set). I have set the appropriate strdata namelist parameters by adjusting the datm.cpl7.template and atm.template.streams.xml files in models/datm/bld to match how I set up my input files. I am using tIntAlgo = 'nearest' for the precip. The CLM simulations run fine, but for some reason, the precip data is not always read in exactly right.
During certain times of non-0 precip, a value slightly lower than the actual value in the input .nc file is used (I checked this by comparing the RAIN history file variable with the original input file variable). Overall, the values are usually correct or at least very close. However, some time steps can have rainfall values up to ~40% off. Furthermore, during those incorrect times, rainfall used at consecutive half-hourly time steps are not identical, as they should be for 'nearest' time interpolation and hourly meteorological inputs.
There does not to seem to be a problem if I use coarser time resolution for the met inputs, e.g. daily.
Has anyone else encountered this problem? If so, how can I get around it?
Thanks,
Crystal
During certain times of non-0 precip, a value slightly lower than the actual value in the input .nc file is used (I checked this by comparing the RAIN history file variable with the original input file variable). Overall, the values are usually correct or at least very close. However, some time steps can have rainfall values up to ~40% off. Furthermore, during those incorrect times, rainfall used at consecutive half-hourly time steps are not identical, as they should be for 'nearest' time interpolation and hourly meteorological inputs.
There does not to seem to be a problem if I use coarser time resolution for the met inputs, e.g. daily.
Has anyone else encountered this problem? If so, how can I get around it?
Thanks,
Crystal