Is TRENDY v10 or CRUJRA v2.2 forcing available in FATES friendly format? #957
Replies: 2 comments 3 replies
-
Looks like some relevant discussion in ESCOMP/CTSM#1895? |
Beta Was this translation helpful? Give feedback.
-
I recently created a Globus guest collection for this. Try this link: https://app.globus.org/file-manager?origin_id=15ed38d8-58dd-44a8-9b87-cdf7b24f82dc&origin_path=%2F Since this dataset includes JRA-55 data, acknowledgment should include the following: "The dataset used for this study includes data from the Japanese 55-year Reanalysis (JRA-55) project carried out by the Japan Meteorological Agency (JMA)." Furthermore, note that "Individual users should provide JMA (jra@met.kishou.go.jp) with a copy of their scientific or technical papers, publications, press releases or other communications regarding these datasets." |
Beta Was this translation helpful? Give feedback.
-
For the demographic benchmarking model inter-comparison project we need to use TRENDY v10 forcing based on CRU-JRA 2.2 (1901-2020). Does anyone know if these versions are available somewhere in a format that FATES can read - one file per month for Solar, Precip and TPQWL?
Both compy and cori have CRUJRA but I'm not sure if it is the correct version. On cori CRUJRA forcing is here: /global/cfs/cdirs/e3sm/inputdata/atm/datm7/atm_forcing.CRUJRA/
Both compy and cori data have the following met data:
global attributes : CRUNCEP 6-Hourly Atmospheric Forcing: Incoming Solar. Missing values filled with 1948 Qian data interpolated by datm to CRUNCEP grid. See CRUNCEP_Landmask.nc in /glade/p/cesm/lmwg/atm_forcing.datm7.cruncep_qianFill.0.5d.V4.c130305 for valid (not filled) CRUNCEP data.
I don't see a version number. Anyone have any idea if that is v2.2?
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions