search

ESCOMP / CTSM

Community Terrestrial Systems Model (includes the Community Land Model of CESM)
http://www.cesm.ucar.edu/models/cesm2.0/land/
Other
309 stars 313 forks source link

Add forcing height variable to GSWP3 forcing files #1760

Open olyson opened 2 years ago

olyson commented 2 years ago

We want to add a forcing height variable to the GSWP3 forcing files and stream text file (and probably eventually to other forcing datasets as well) so that it is read in from the forcing files instead of being hardcoded in the datm code (currently set to 30m). This variable would still be time- and space-invariant. The main reason is to make this variable more visible to users. This would also be consistent with our flux tower forcing files where forcing height is encoded as ZBOT in the datm forcing files.

ekluzek commented 2 years ago

This work will need to be done in CDEPS. The CTSM part of this will be to update to the CDEPS tag where this is done. I think the way to do this will be to add an additional file for ZBOT, that will be handled as an additional stream file. The file will only have a single time-sample and one latitude and longitude, but it would be a separate stream.

ekluzek commented 2 years ago

I have a branch and PR in CDEPS that fixes the read for ZBOT

https://github.com/ESCOMP/CDEPS/pull/169

wwieder commented 2 years ago

Just clarifying, this will also fix the bug with reading in ZBOT from DATM files for single point runs (adding next so we can discuss).

ekluzek commented 2 years ago

@wwieder the CDEPS PR above fixes the bug for reading ZBOT for single point runs. Using that branch will fix that for you. I've just pinged Jim to approve the PR so we'll have a CDEPS tag for it.