[Go-essp-tech] time gaps in GFDL data sets
Ron Stouffer
ronald.stouffer at noaa.gov
Wed Apr 4 12:31:24 MDT 2012
HI all,
The time gaps in GFDL's data have been resolved/fixed...as far as we
know....for both the ESM and CM3 data sets. The server data1
(http://data1.gfdl.noaa.gov/) has the most up-to-date versions of our
public data. The data on ESG can be a few weeks behind...for reasons I
do not understand. The reasons for the data gaps were related to
problems moving data around both with our in-house software and
ESG/network software.
Hope this is helpful.
-Ron
Curt wrote:
Ron,
Thanks for the clarification. Sounds like you followed the CMIP5
protocol correctly. But meanwhile another user has found
data gaps in the contributions from GFDL (and from other groups). Can
you look over this user's comments, respond
for GFDL-ESM2M, and also forward the comments to whoever should respond
for GFDL-CM3?
Keep healthy,
Curt
On 3/22/12 7:23 AM, "Ron Stouffer" <ronald.stouffer at noaa.gov> wrote:
HI David and Sebastien,
We (GFDL ESM group) have made two 1% CO2 increase runs with both ESM2M
and ESM2G. The first run uses 1% increase to doubling (2X) and is found
in r1i1p1. The second run uses 1% increase to 4X and is found in r1i1p2.
This second run is what you are looking to use. Both of these runs are
found under the 1pctCO2 experiment on either the GFDL server or via ESG.
Thanks for your question. Let me know if there are still problems.
-Ron Stouffer
From: "Painter, Jeff" <painter1 at llnl.gov>
Date: Tue, 20 Mar 2012 16:13:58 -0700
To: "Taylor, Karl Taylor" <taylor13 at llnl.gov>
Cc: covey1 Covey <covey1 at llnl.gov>, Jennifer Adams <jma at cola.iges.org>,
"go-essp-tech at ucar.edu" <go-essp-tech at ucar.edu>
Subject: Re: Fwd: [Go-essp-tech] Data file gaps
I can shed some light on one of the gaps: the GISS-E2-R piControl files
actually contain TWO control runs! One side of the
gap is one control run, and the other side of the gap is the other
control run. I cut-and-pasted a message from Ken Lo
about this, at the bottom of this message.
- Jeff
On 3/20/12 11:55 AM, Karl Taylor wrote:
database problem??
-------- Original Message --------
Subject:
[Go-essp-tech] Data file gaps
Date:
Tue, 20 Mar 2012 11:50:07 -0700
From:
Jennifer Adams <jma at cola.iges.org>
To:
go-essp-tech at ucar.edu <go-essp-tech at ucar.edu>
Dear All,
I have a GrADS script that creates descriptor files for CMIP5 data, and
it has uncovered some gaps in the date
strings of files that belong to an atomic data set. I have checked the
ESGF gateways for all the datasets listed
below and I can confirm that these files are missing for some variables.
I haven't given the variable names, because
I have only checked the subset of variables that are of interest to me
and that may not be a complete list. If the
specific var names that I checked would be useful, I can provide them.
While checking on these gaps, I noticed that
not all variables in an atomic dataset span the same time range ? an
inconsistency that doesn't quite make sense to me.
I also noticed that in some cases, data files that I had grabbed are no
longer listed on the gateway, even though the
version number is the same. An example is
cmip5.output1.NCC.NorESM1-M.piControl.day.land.day.r1i1p1.v20110901, mrsos,
date range 11000101-12001231. What does that mean?
The gaps put these data into the "not quite usable" category. I wasn't
sure whether to send this to the helpdesk or
the forum or both; in the end I am just posting here.
--Jennifer
11880 times missing in
cmip5.output1.NASA-GISS.GISS-E2-H.piControl.mon.atmos.Amon.r1i1p1
between 141912 and 241001
11880 times missing in
cmip5.output1.NASA-GISS.GISS-E2-H.piControl.mon.land.Lmon.r1i1p1
between 141912 and 241001
4200 times missing in
cmip5.output1.NASA-GISS.GISS-E2-R.piControl.mon.land.Lmon.r1i1p1
between 363012 and 398101
11880 times missing in
cmip5.output1.NASA-GISS.GISS-E2-H.piControl.mon.ocean.Omon.r1i1p1
between 141912 and 241001
4200 times missing in
cmip5.output1.NASA-GISS.GISS-E2-R.piControl.mon.ocean.Omon.r1i1p1
between 363012 and 398101
1 times missing in
cmip5.output1.MOHC.HadGEM2-CC.historical.mon.ocean.Omon.r3i1p1
between 200110 and 200112
60 times missing in
cmip5.output1.NOAA-GFDL.GFDL-ESM2M.piControl.mon.land.Lmon.r1i1p1
between 017012 and 017601
60 times missing in
cmip5.output1.NOAA-GFDL.GFDL-ESM2M.piControl.mon.land.Lmon.r1i1p1
between 003012 and 003601
3650 times missing in
cmip5.output1.NOAA-GFDL.GFDL-CM3.piControl.day.atmos.day.r1i1p1
between 00101231 and
00210101
1825 times missing in
cmip5.output1.NOAA-GFDL.GFDL-CM3.piControl.day.atmos.day.r1i1p1
between 00401231 and
00460101
7300 times missing in
cmip5.output1.NOAA-GFDL.GFDL-CM3.piControl.day.atmos.day.r1i1p1
between 00751231 and
00960101
142350 times missing in
cmip5.output1.NOAA-GFDL.GFDL-CM3.piControl.day.atmos.day.r1i1p1
between 01001231 and
04910101
73000 times missing in
cmip5.output1.NCC.NorESM1-M.piControl.day.land.day.r1i1p1
between 08991231 and
11000101
29220 times missing in
cmip5.output1.MPI-M.MPI-ESM-LR.rcp85.day.atmos.day.r1i1p1
between 22001231 and
22810101
--
Jennifer M. Adams
IGES/COLA
4041 Powder Mill Road, Suite 302
Calverton, MD 20705
jma at cola.iges.org
On 11/4/11 6:07 AM, Ken Lo wrote:
Dear Jeff Painter,
Years 3331 to 3630 of the control run are meant to be compared with
historicalMisc (p1), while years 3981 to 4530 are meant to be compared
with historical, historicalMisc (p109), historicalGHG, historicalNat
and rcp runs (all p1 except indicated otherwise). The appropriate years
for comparison are written in the branch time of the metadata of each
file.
More information about the GO-ESSP-TECH
mailing list