[Met_help] [rt.rap.ucar.edu #90155] History for climatology file examples
John Halley Gotway via RT
met_help at ucar.edu
Thu May 16 16:04:05 MDT 2019
----------------------------------------------------------------
Initial Request
----------------------------------------------------------------
I am trying to understand the interpolation of the climatology data, and I
need some help. I think John Halley Gotway may be the best help since it looks
like he wrote the climatology software.
Ref:
src/libcode/vx_statistics/read_climo.cc
// Search the files for the requested records
for(i=0; i<climo_files.n_elements(); i++) {
read_climo_file(climo_files[i], ctype, &i_dict, vld_ut,
match_month, match_day, time_step,
vx_grid, regrid_info, dpa);
}
// Time interpolation for mean fields
dpa = climo_time_interp(dpa, vld_ut, time_interp);
I understand the climatology files must be grid input format (guessing GRIB2
best practice), however, I am stuck on the date range of your typical
climatology files. I am starting out with pre-existing ieee Monthly
climatology files, and these files are interpolated with previous and next
month, and computing continues to get the weighted value for anomaly
correlation.
In other words, what is the typical file naming, and date range of climatology
files that play well with MET ?
Thanks,
Glen
--
Mr. Glen CARL
NRL Monterey Contractor SAIC/0cog, Bldg 704 Rm 133, Code 7532
831.325.6269
glen.carl.ctr at nrlmry.navy.mil
----------------------------------------------------------------
Complete Ticket History
----------------------------------------------------------------
Subject: climatology file examples
From: Minna Win
Time: Thu May 09 15:20:37 2019
Hello Glen,
It looks like you have some questions regarding climatology files in
MET.
I'm assigning this issue to John Halley Gotway.
Regards,
Minna
---------------
Minna Win
NCAR
Research Applications Lab
Phone: 303-497-8423
Fax: 303-497-8401
On Thu, May 9, 2019 at 8:13 PM Carl, Mr. Glen, Contractor, Code 7532
via RT
<met_help at ucar.edu> wrote:
>
> Thu May 09 14:13:29 2019: Request 90155 was acted upon.
> Transaction: Ticket created by glen.carl.ctr at nrlmry.navy.mil
> Queue: met_help
> Subject: climatology file examples
> Owner: Nobody
> Requestors: glen.carl.ctr at nrlmry.navy.mil
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=90155 >
>
>
>
> I am trying to understand the interpolation of the climatology data,
and I
> need some help. I think John Halley Gotway may be the best help
since it
> looks
> like he wrote the climatology software.
>
> Ref:
> src/libcode/vx_statistics/read_climo.cc
>
> // Search the files for the requested records
> for(i=0; i<climo_files.n_elements(); i++) {
> read_climo_file(climo_files[i], ctype, &i_dict, vld_ut,
> match_month, match_day, time_step,
> vx_grid, regrid_info, dpa);
> }
>
> // Time interpolation for mean fields
> dpa = climo_time_interp(dpa, vld_ut, time_interp);
>
> I understand the climatology files must be grid input format
(guessing
> GRIB2
> best practice), however, I am stuck on the date range of your
typical
> climatology files. I am starting out with pre-existing ieee Monthly
> climatology files, and these files are interpolated with previous
and next
> month, and computing continues to get the weighted value for anomaly
> correlation.
>
> In other words, what is the typical file naming, and date range of
> climatology
> files that play well with MET ?
>
> Thanks,
> Glen
>
> --
> Mr. Glen CARL
> NRL Monterey Contractor SAIC/0cog, Bldg 704 Rm 133, Code 7532
> 831.325.6269
> glen.carl.ctr at nrlmry.navy.mil
>
>
>
>
------------------------------------------------
Subject: climatology file examples
From: John Halley Gotway
Time: Fri May 10 13:20:31 2019
Hi Glen,
I see you have a question about defining climatologies for use in MET.
This development was done and tested with 3 different flavors of
climatology data in mind:
(1) NOAA/EMC has a legacy global 2.5 degree climatology dataset. They
store this data in GRIB1 files with separate files for each month.
And for
each month, they have separate files for "mean" and "stdv":
*mean files* = pgba_mean.19590115, pgba_mean.19590215,
pgba_mean.19590315,
pgba_mean.19590415, pgba_mean.19590515, pgba_mean.19590615,
pgba_mean.19590715, pgba_mean.19590815, pgba_mean.19590915,
pgba_mean.19591015, pgba_mean.19591115, pgba_mean.19591215
*standard deviation files* = pgba_stdv.19590115, pgba_stdv.19590215,
pgba_stdv.19590315, pgba_stdv.19590415, pgba_stdv.19590515,
pgba_stdv.19590615, pgba_stdv.19590715, pgba_stdv.19590815,
pgba_stdv.19590915, pgba_stdv.19591015, pgba_stdv.19591115,
pgba_stdv.19591215
Each file contains data for the following variables at 00Z, 06Z, 12Z,
and
18Z. In total, it's 76 records, so 19 for each of 00, 06, 12, and 18:
HGT, PRMSL, TMAX, TMIN, TMP, UGRD, VGRD
(2) NOAA/EMC has an experimental global 1.0 degree climatology.
Instead of
have 12 files for 12 months, there are separate files for each day of
the
year. Like the 2.5 degree climo, there are separate output times 00,
06,
12, and 18. Each file contains 80 records, so 20 climo fields for
each
output time. These files follow this naming convention:
cmean_1d.1979MMDD and cstdv_1d.1979MMDD where MMDD indicate the
current day.
(3) The 3rd variant is an ERA interim analysis which is used by WMO.
These
data files are organized by variable name. Each GRIB file contains
732
records... 366 days of the year (with a leap year), every 12 hours.
Here's
a site for this one:
https://www.ecmwf.int/en/forecasts/datasets/reanalysis-datasets/era-
interim
I think the first or second option is preferable to the 3rd. Since
you run
the MET tools to evaluate a particular valid time, it's convenient to
have
all the climo data you'll be using for that valid time in the same
file.
The ERA interim data will work too, but it'll take the tools longer to
sift
through all those records to find the one which matches the current
valid
time.
Hope that helps.
Thanks,
John
On Thu, May 9, 2019 at 3:20 PM Minna Win via RT <met_help at ucar.edu>
wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=90155 >
>
> Hello Glen,
>
> It looks like you have some questions regarding climatology files in
MET.
> I'm assigning this issue to John Halley Gotway.
>
> Regards,
> Minna
> ---------------
> Minna Win
> NCAR
> Research Applications Lab
> Phone: 303-497-8423
> Fax: 303-497-8401
>
>
>
> On Thu, May 9, 2019 at 8:13 PM Carl, Mr. Glen, Contractor, Code 7532
via RT
> <met_help at ucar.edu> wrote:
>
> >
> > Thu May 09 14:13:29 2019: Request 90155 was acted upon.
> > Transaction: Ticket created by glen.carl.ctr at nrlmry.navy.mil
> > Queue: met_help
> > Subject: climatology file examples
> > Owner: Nobody
> > Requestors: glen.carl.ctr at nrlmry.navy.mil
> > Status: new
> > Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=90155 >
> >
> >
> >
> > I am trying to understand the interpolation of the climatology
data, and
> I
> > need some help. I think John Halley Gotway may be the best help
since it
> > looks
> > like he wrote the climatology software.
> >
> > Ref:
> > src/libcode/vx_statistics/read_climo.cc
> >
> > // Search the files for the requested records
> > for(i=0; i<climo_files.n_elements(); i++) {
> > read_climo_file(climo_files[i], ctype, &i_dict, vld_ut,
> > match_month, match_day, time_step,
> > vx_grid, regrid_info, dpa);
> > }
> >
> > // Time interpolation for mean fields
> > dpa = climo_time_interp(dpa, vld_ut, time_interp);
> >
> > I understand the climatology files must be grid input format
(guessing
> > GRIB2
> > best practice), however, I am stuck on the date range of your
typical
> > climatology files. I am starting out with pre-existing ieee
Monthly
> > climatology files, and these files are interpolated with previous
and
> next
> > month, and computing continues to get the weighted value for
anomaly
> > correlation.
> >
> > In other words, what is the typical file naming, and date range of
> > climatology
> > files that play well with MET ?
> >
> > Thanks,
> > Glen
> >
> > --
> > Mr. Glen CARL
> > NRL Monterey Contractor SAIC/0cog, Bldg 704 Rm 133, Code 7532
> > 831.325.6269
> > glen.carl.ctr at nrlmry.navy.mil
> >
> >
> >
> >
>
>
------------------------------------------------
Subject: climatology file examples
From: Carl, Mr. Glen, Contractor, Code 7532
Time: Fri May 10 13:39:09 2019
Hi John,
This information is very helpful. Based on this information, we are
going to
need to do some team thought on how to design climatology files that
will work
better with MET.
Also, is there a way for me to generate ANOM_COR without our
climatology
files. In the MET documentation, there looked like there was a
reference to
just use MET default climatology data. Sounded like a small data set,
however,
it would allow us to make sure we can generate ANOM_COR while waiting
for our
new climatology file design.
Thanks,
Glen
-----Original Message-----
From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
Sent: Friday, May 10, 2019 12:21 PM
To: Carl, Mr. Glen, Contractor, Code 7532
Subject: Re: [rt.rap.ucar.edu #90155] climatology file examples
Hi Glen,
I see you have a question about defining climatologies for use in MET.
This development was done and tested with 3 different flavors of
climatology data in mind:
(1) NOAA/EMC has a legacy global 2.5 degree climatology dataset. They
store this data in GRIB1 files with separate files for each month.
And for
each month, they have separate files for "mean" and "stdv":
*mean files* = pgba_mean.19590115, pgba_mean.19590215,
pgba_mean.19590315,
pgba_mean.19590415, pgba_mean.19590515, pgba_mean.19590615,
pgba_mean.19590715, pgba_mean.19590815, pgba_mean.19590915,
pgba_mean.19591015, pgba_mean.19591115, pgba_mean.19591215
*standard deviation files* = pgba_stdv.19590115, pgba_stdv.19590215,
pgba_stdv.19590315, pgba_stdv.19590415, pgba_stdv.19590515,
pgba_stdv.19590615, pgba_stdv.19590715, pgba_stdv.19590815,
pgba_stdv.19590915, pgba_stdv.19591015, pgba_stdv.19591115,
pgba_stdv.19591215
Each file contains data for the following variables at 00Z, 06Z, 12Z,
and
18Z. In total, it's 76 records, so 19 for each of 00, 06, 12, and 18:
HGT, PRMSL, TMAX, TMIN, TMP, UGRD, VGRD
(2) NOAA/EMC has an experimental global 1.0 degree climatology.
Instead of
have 12 files for 12 months, there are separate files for each day of
the
year. Like the 2.5 degree climo, there are separate output times 00,
06,
12, and 18. Each file contains 80 records, so 20 climo fields for
each
output time. These files follow this naming convention:
cmean_1d.1979MMDD and cstdv_1d.1979MMDD where MMDD indicate the
current day.
(3) The 3rd variant is an ERA interim analysis which is used by WMO.
These
data files are organized by variable name. Each GRIB file contains
732
records... 366 days of the year (with a leap year), every 12 hours.
Here's
a site for this one:
https://www.ecmwf.int/en/forecasts/datasets/reanalysis-datasets/era-
interim
I think the first or second option is preferable to the 3rd. Since
you run
the MET tools to evaluate a particular valid time, it's convenient to
have
all the climo data you'll be using for that valid time in the same
file.
The ERA interim data will work too, but it'll take the tools longer to
sift
through all those records to find the one which matches the current
valid
time.
Hope that helps.
Thanks,
John
On Thu, May 9, 2019 at 3:20 PM Minna Win via RT <met_help at ucar.edu>
wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=90155 >
>
> Hello Glen,
>
> It looks like you have some questions regarding climatology files in
MET.
> I'm assigning this issue to John Halley Gotway.
>
> Regards,
> Minna
> ---------------
> Minna Win
> NCAR
> Research Applications Lab
> Phone: 303-497-8423
> Fax: 303-497-8401
>
>
>
> On Thu, May 9, 2019 at 8:13 PM Carl, Mr. Glen, Contractor, Code 7532
via RT
> <met_help at ucar.edu> wrote:
>
> >
> > Thu May 09 14:13:29 2019: Request 90155 was acted upon.
> > Transaction: Ticket created by glen.carl.ctr at nrlmry.navy.mil
> > Queue: met_help
> > Subject: climatology file examples
> > Owner: Nobody
> > Requestors: glen.carl.ctr at nrlmry.navy.mil
> > Status: new
> > Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=90155 >
> >
> >
> >
> > I am trying to understand the interpolation of the climatology
data, and
> I
> > need some help. I think John Halley Gotway may be the best help
since it
> > looks
> > like he wrote the climatology software.
> >
> > Ref:
> > src/libcode/vx_statistics/read_climo.cc
> >
> > // Search the files for the requested records
> > for(i=0; i<climo_files.n_elements(); i++) {
> > read_climo_file(climo_files[i], ctype, &i_dict, vld_ut,
> > match_month, match_day, time_step,
> > vx_grid, regrid_info, dpa);
> > }
> >
> > // Time interpolation for mean fields
> > dpa = climo_time_interp(dpa, vld_ut, time_interp);
> >
> > I understand the climatology files must be grid input format
(guessing
> > GRIB2
> > best practice), however, I am stuck on the date range of your
typical
> > climatology files. I am starting out with pre-existing ieee
Monthly
> > climatology files, and these files are interpolated with previous
and
> next
> > month, and computing continues to get the weighted value for
anomaly
> > correlation.
> >
> > In other words, what is the typical file naming, and date range of
> > climatology
> > files that play well with MET ?
> >
> > Thanks,
> > Glen
> >
> > --
> > Mr. Glen CARL
> > NRL Monterey Contractor SAIC/0cog, Bldg 704 Rm 133, Code 7532
> > 831.325.6269
> > glen.carl.ctr at nrlmry.navy.mil
> >
> >
> >
> >
>
>
------------------------------------------------
Subject: climatology file examples
From: John Halley Gotway
Time: Fri May 10 13:51:07 2019
Glen,
We could ask folks at NOAA/EMC if we can share their 2.5 or 1.0 degree
climatology data. I presume that they wouldn't mind, but we'd need to
ask
first.
Alternatively, you can request access from ECMWF to the ERA-Interim
analysis dataset:
https://www.ecmwf.int/en/forecasts/datasets/reanalysis-datasets/era-
interim
Just let me know how you'd like to proceed.
Thanks,
John
On Fri, May 10, 2019 at 1:39 PM Carl, Mr. Glen, Contractor, Code 7532
via
RT <met_help at ucar.edu> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=90155 >
>
> Hi John,
> This information is very helpful. Based on this information, we are
going
> to
> need to do some team thought on how to design climatology files that
will
> work
> better with MET.
>
> Also, is there a way for me to generate ANOM_COR without our
climatology
> files. In the MET documentation, there looked like there was a
reference
> to
> just use MET default climatology data. Sounded like a small data
set,
> however,
> it would allow us to make sure we can generate ANOM_COR while
waiting for
> our
> new climatology file design.
>
> Thanks,
> Glen
>
> -----Original Message-----
> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> Sent: Friday, May 10, 2019 12:21 PM
> To: Carl, Mr. Glen, Contractor, Code 7532
> Subject: Re: [rt.rap.ucar.edu #90155] climatology file examples
>
> Hi Glen,
>
> I see you have a question about defining climatologies for use in
MET.
> This development was done and tested with 3 different flavors of
> climatology data in mind:
>
> (1) NOAA/EMC has a legacy global 2.5 degree climatology dataset.
They
> store this data in GRIB1 files with separate files for each month.
And for
> each month, they have separate files for "mean" and "stdv":
> *mean files* = pgba_mean.19590115, pgba_mean.19590215,
pgba_mean.19590315,
> pgba_mean.19590415, pgba_mean.19590515, pgba_mean.19590615,
> pgba_mean.19590715, pgba_mean.19590815, pgba_mean.19590915,
> pgba_mean.19591015, pgba_mean.19591115, pgba_mean.19591215
> *standard deviation files* = pgba_stdv.19590115, pgba_stdv.19590215,
> pgba_stdv.19590315, pgba_stdv.19590415, pgba_stdv.19590515,
> pgba_stdv.19590615, pgba_stdv.19590715, pgba_stdv.19590815,
> pgba_stdv.19590915, pgba_stdv.19591015, pgba_stdv.19591115,
> pgba_stdv.19591215
>
> Each file contains data for the following variables at 00Z, 06Z,
12Z, and
> 18Z. In total, it's 76 records, so 19 for each of 00, 06, 12, and
18:
> HGT, PRMSL, TMAX, TMIN, TMP, UGRD, VGRD
>
> (2) NOAA/EMC has an experimental global 1.0 degree climatology.
Instead of
> have 12 files for 12 months, there are separate files for each day
of the
> year. Like the 2.5 degree climo, there are separate output times
00, 06,
> 12, and 18. Each file contains 80 records, so 20 climo fields for
each
> output time. These files follow this naming convention:
> cmean_1d.1979MMDD and cstdv_1d.1979MMDD where MMDD indicate the
current
> day.
>
> (3) The 3rd variant is an ERA interim analysis which is used by WMO.
These
> data files are organized by variable name. Each GRIB file contains
732
> records... 366 days of the year (with a leap year), every 12 hours.
Here's
> a site for this one:
> https://www.ecmwf.int/en/forecasts/datasets/reanalysis-datasets/era-
interim
>
> I think the first or second option is preferable to the 3rd. Since
you run
> the MET tools to evaluate a particular valid time, it's convenient
to have
> all the climo data you'll be using for that valid time in the same
file.
> The ERA interim data will work too, but it'll take the tools longer
to sift
> through all those records to find the one which matches the current
valid
> time.
>
> Hope that helps.
>
> Thanks,
> John
>
>
>
>
> On Thu, May 9, 2019 at 3:20 PM Minna Win via RT <met_help at ucar.edu>
wrote:
>
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=90155 >
> >
> > Hello Glen,
> >
> > It looks like you have some questions regarding climatology files
in MET.
> > I'm assigning this issue to John Halley Gotway.
> >
> > Regards,
> > Minna
> > ---------------
> > Minna Win
> > NCAR
> > Research Applications Lab
> > Phone: 303-497-8423
> > Fax: 303-497-8401
> >
> >
> >
> > On Thu, May 9, 2019 at 8:13 PM Carl, Mr. Glen, Contractor, Code
7532 via
> RT
> > <met_help at ucar.edu> wrote:
> >
> > >
> > > Thu May 09 14:13:29 2019: Request 90155 was acted upon.
> > > Transaction: Ticket created by glen.carl.ctr at nrlmry.navy.mil
> > > Queue: met_help
> > > Subject: climatology file examples
> > > Owner: Nobody
> > > Requestors: glen.carl.ctr at nrlmry.navy.mil
> > > Status: new
> > > Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=90155
> >
> > >
> > >
> > >
> > > I am trying to understand the interpolation of the climatology
data,
> and
> > I
> > > need some help. I think John Halley Gotway may be the best help
since
> it
> > > looks
> > > like he wrote the climatology software.
> > >
> > > Ref:
> > > src/libcode/vx_statistics/read_climo.cc
> > >
> > > // Search the files for the requested records
> > > for(i=0; i<climo_files.n_elements(); i++) {
> > > read_climo_file(climo_files[i], ctype, &i_dict, vld_ut,
> > > match_month, match_day, time_step,
> > > vx_grid, regrid_info, dpa);
> > > }
> > >
> > > // Time interpolation for mean fields
> > > dpa = climo_time_interp(dpa, vld_ut, time_interp);
> > >
> > > I understand the climatology files must be grid input format
(guessing
> > > GRIB2
> > > best practice), however, I am stuck on the date range of your
typical
> > > climatology files. I am starting out with pre-existing ieee
Monthly
> > > climatology files, and these files are interpolated with
previous and
> > next
> > > month, and computing continues to get the weighted value for
anomaly
> > > correlation.
> > >
> > > In other words, what is the typical file naming, and date range
of
> > > climatology
> > > files that play well with MET ?
> > >
> > > Thanks,
> > > Glen
> > >
> > > --
> > > Mr. Glen CARL
> > > NRL Monterey Contractor SAIC/0cog, Bldg 704 Rm 133, Code 7532
> > > 831.325.6269
> > > glen.carl.ctr at nrlmry.navy.mil
> > >
> > >
> > >
> > >
> >
> >
>
>
>
------------------------------------------------
Subject: climatology file examples
From: Carl, Mr. Glen, Contractor, Code 7532
Time: Fri May 10 15:23:30 2019
We have a meeting in about 40 minutes from now and will discuss.
I noticed
ERA Interim is being phased out. Users are strongly advised to migrate
to
ERA5. The last date to be made available in ERA Interim will be 31
August
2019, which will be released at the end of October 2019.
https://apps.ecmwf.int/datasets/data/interim-full-daily/levtype=sfc/
We would want the 1.0 degree global if possible. I guess you are
saying that
there is not just a small sample set included with MET.
Thank you so much! Have fun weekend!
Glen
-----Original Message-----
From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
Sent: Friday, May 10, 2019 12:51 PM
To: Carl, Mr. Glen, Contractor, Code 7532
Subject: Re: [rt.rap.ucar.edu #90155] climatology file examples
Glen,
We could ask folks at NOAA/EMC if we can share their 2.5 or 1.0 degree
climatology data. I presume that they wouldn't mind, but we'd need to
ask
first.
Alternatively, you can request access from ECMWF to the ERA-Interim
analysis dataset:
https://www.ecmwf.int/en/forecasts/datasets/reanalysis-datasets/era-
interim
Just let me know how you'd like to proceed.
Thanks,
John
On Fri, May 10, 2019 at 1:39 PM Carl, Mr. Glen, Contractor, Code 7532
via
RT <met_help at ucar.edu> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=90155 >
>
> Hi John,
> This information is very helpful. Based on this information, we are
going
> to
> need to do some team thought on how to design climatology files that
will
> work
> better with MET.
>
> Also, is there a way for me to generate ANOM_COR without our
climatology
> files. In the MET documentation, there looked like there was a
reference
> to
> just use MET default climatology data. Sounded like a small data
set,
> however,
> it would allow us to make sure we can generate ANOM_COR while
waiting for
> our
> new climatology file design.
>
> Thanks,
> Glen
>
> -----Original Message-----
> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> Sent: Friday, May 10, 2019 12:21 PM
> To: Carl, Mr. Glen, Contractor, Code 7532
> Subject: Re: [rt.rap.ucar.edu #90155] climatology file examples
>
> Hi Glen,
>
> I see you have a question about defining climatologies for use in
MET.
> This development was done and tested with 3 different flavors of
> climatology data in mind:
>
> (1) NOAA/EMC has a legacy global 2.5 degree climatology dataset.
They
> store this data in GRIB1 files with separate files for each month.
And for
> each month, they have separate files for "mean" and "stdv":
> *mean files* = pgba_mean.19590115, pgba_mean.19590215,
pgba_mean.19590315,
> pgba_mean.19590415, pgba_mean.19590515, pgba_mean.19590615,
> pgba_mean.19590715, pgba_mean.19590815, pgba_mean.19590915,
> pgba_mean.19591015, pgba_mean.19591115, pgba_mean.19591215
> *standard deviation files* = pgba_stdv.19590115, pgba_stdv.19590215,
> pgba_stdv.19590315, pgba_stdv.19590415, pgba_stdv.19590515,
> pgba_stdv.19590615, pgba_stdv.19590715, pgba_stdv.19590815,
> pgba_stdv.19590915, pgba_stdv.19591015, pgba_stdv.19591115,
> pgba_stdv.19591215
>
> Each file contains data for the following variables at 00Z, 06Z,
12Z, and
> 18Z. In total, it's 76 records, so 19 for each of 00, 06, 12, and
18:
> HGT, PRMSL, TMAX, TMIN, TMP, UGRD, VGRD
>
> (2) NOAA/EMC has an experimental global 1.0 degree climatology.
Instead of
> have 12 files for 12 months, there are separate files for each day
of the
> year. Like the 2.5 degree climo, there are separate output times
00, 06,
> 12, and 18. Each file contains 80 records, so 20 climo fields for
each
> output time. These files follow this naming convention:
> cmean_1d.1979MMDD and cstdv_1d.1979MMDD where MMDD indicate the
current
> day.
>
> (3) The 3rd variant is an ERA interim analysis which is used by WMO.
These
> data files are organized by variable name. Each GRIB file contains
732
> records... 366 days of the year (with a leap year), every 12 hours.
Here's
> a site for this one:
> https://www.ecmwf.int/en/forecasts/datasets/reanalysis-datasets/era-
interim
>
> I think the first or second option is preferable to the 3rd. Since
you run
> the MET tools to evaluate a particular valid time, it's convenient
to have
> all the climo data you'll be using for that valid time in the same
file.
> The ERA interim data will work too, but it'll take the tools longer
to sift
> through all those records to find the one which matches the current
valid
> time.
>
> Hope that helps.
>
> Thanks,
> John
>
>
>
>
> On Thu, May 9, 2019 at 3:20 PM Minna Win via RT <met_help at ucar.edu>
wrote:
>
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=90155 >
> >
> > Hello Glen,
> >
> > It looks like you have some questions regarding climatology files
in MET.
> > I'm assigning this issue to John Halley Gotway.
> >
> > Regards,
> > Minna
> > ---------------
> > Minna Win
> > NCAR
> > Research Applications Lab
> > Phone: 303-497-8423
> > Fax: 303-497-8401
> >
> >
> >
> > On Thu, May 9, 2019 at 8:13 PM Carl, Mr. Glen, Contractor, Code
7532 via
> RT
> > <met_help at ucar.edu> wrote:
> >
> > >
> > > Thu May 09 14:13:29 2019: Request 90155 was acted upon.
> > > Transaction: Ticket created by glen.carl.ctr at nrlmry.navy.mil
> > > Queue: met_help
> > > Subject: climatology file examples
> > > Owner: Nobody
> > > Requestors: glen.carl.ctr at nrlmry.navy.mil
> > > Status: new
> > > Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=90155
> >
> > >
> > >
> > >
> > > I am trying to understand the interpolation of the climatology
data,
> and
> > I
> > > need some help. I think John Halley Gotway may be the best help
since
> it
> > > looks
> > > like he wrote the climatology software.
> > >
> > > Ref:
> > > src/libcode/vx_statistics/read_climo.cc
> > >
> > > // Search the files for the requested records
> > > for(i=0; i<climo_files.n_elements(); i++) {
> > > read_climo_file(climo_files[i], ctype, &i_dict, vld_ut,
> > > match_month, match_day, time_step,
> > > vx_grid, regrid_info, dpa);
> > > }
> > >
> > > // Time interpolation for mean fields
> > > dpa = climo_time_interp(dpa, vld_ut, time_interp);
> > >
> > > I understand the climatology files must be grid input format
(guessing
> > > GRIB2
> > > best practice), however, I am stuck on the date range of your
typical
> > > climatology files. I am starting out with pre-existing ieee
Monthly
> > > climatology files, and these files are interpolated with
previous and
> > next
> > > month, and computing continues to get the weighted value for
anomaly
> > > correlation.
> > >
> > > In other words, what is the typical file naming, and date range
of
> > > climatology
> > > files that play well with MET ?
> > >
> > > Thanks,
> > > Glen
> > >
> > > --
> > > Mr. Glen CARL
> > > NRL Monterey Contractor SAIC/0cog, Bldg 704 Rm 133, Code 7532
> > > 831.325.6269
> > > glen.carl.ctr at nrlmry.navy.mil
> > >
> > >
> > >
> > >
> >
> >
>
>
>
------------------------------------------------
Subject: climatology file examples
From: Carl, Mr. Glen, Contractor, Code 7532
Time: Thu May 16 11:53:43 2019
Hi John,
We would like to try the global 1.0 degree climatology data from
NOAA/EMC if
they are willing to share.
I cc'd Dr. Satterfield and Dr. McLay, since they are Civilians that
are fully
authorize the request if it is needed.
Thanks,
Glen
--
Mr. Glen CARL
NRL Monterey Contractor SAIC/0cog, Bldg 704 Rm 133, Code 7532
831.325.6269
glen.carl.ctr at nrlmry.navy.mil
-----Original Message-----
From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
Sent: Friday, May 10, 2019 12:51 PM
To: Carl, Mr. Glen, Contractor, Code 7532
Subject: Re: [rt.rap.ucar.edu #90155] climatology file examples
Glen,
We could ask folks at NOAA/EMC if we can share their 2.5 or 1.0 degree
climatology data. I presume that they wouldn't mind, but we'd need to
ask
first.
Alternatively, you can request access from ECMWF to the ERA-Interim
analysis dataset:
https://www.ecmwf.int/en/forecasts/datasets/reanalysis-datasets/era-
interim
Just let me know how you'd like to proceed.
Thanks,
John
On Fri, May 10, 2019 at 1:39 PM Carl, Mr. Glen, Contractor, Code 7532
via
RT <met_help at ucar.edu> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=90155 >
>
> Hi John,
> This information is very helpful. Based on this information, we are
going
> to
> need to do some team thought on how to design climatology files that
will
> work
> better with MET.
>
> Also, is there a way for me to generate ANOM_COR without our
climatology
> files. In the MET documentation, there looked like there was a
reference
> to
> just use MET default climatology data. Sounded like a small data
set,
> however,
> it would allow us to make sure we can generate ANOM_COR while
waiting for
> our
> new climatology file design.
>
> Thanks,
> Glen
>
> -----Original Message-----
> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> Sent: Friday, May 10, 2019 12:21 PM
> To: Carl, Mr. Glen, Contractor, Code 7532
> Subject: Re: [rt.rap.ucar.edu #90155] climatology file examples
>
> Hi Glen,
>
> I see you have a question about defining climatologies for use in
MET.
> This development was done and tested with 3 different flavors of
> climatology data in mind:
>
> (1) NOAA/EMC has a legacy global 2.5 degree climatology dataset.
They
> store this data in GRIB1 files with separate files for each month.
And for
> each month, they have separate files for "mean" and "stdv":
> *mean files* = pgba_mean.19590115, pgba_mean.19590215,
pgba_mean.19590315,
> pgba_mean.19590415, pgba_mean.19590515, pgba_mean.19590615,
> pgba_mean.19590715, pgba_mean.19590815, pgba_mean.19590915,
> pgba_mean.19591015, pgba_mean.19591115, pgba_mean.19591215
> *standard deviation files* = pgba_stdv.19590115, pgba_stdv.19590215,
> pgba_stdv.19590315, pgba_stdv.19590415, pgba_stdv.19590515,
> pgba_stdv.19590615, pgba_stdv.19590715, pgba_stdv.19590815,
> pgba_stdv.19590915, pgba_stdv.19591015, pgba_stdv.19591115,
> pgba_stdv.19591215
>
> Each file contains data for the following variables at 00Z, 06Z,
12Z, and
> 18Z. In total, it's 76 records, so 19 for each of 00, 06, 12, and
18:
> HGT, PRMSL, TMAX, TMIN, TMP, UGRD, VGRD
>
> (2) NOAA/EMC has an experimental global 1.0 degree climatology.
Instead of
> have 12 files for 12 months, there are separate files for each day
of the
> year. Like the 2.5 degree climo, there are separate output times
00, 06,
> 12, and 18. Each file contains 80 records, so 20 climo fields for
each
> output time. These files follow this naming convention:
> cmean_1d.1979MMDD and cstdv_1d.1979MMDD where MMDD indicate the
current
> day.
>
> (3) The 3rd variant is an ERA interim analysis which is used by WMO.
These
> data files are organized by variable name. Each GRIB file contains
732
> records... 366 days of the year (with a leap year), every 12 hours.
Here's
> a site for this one:
> https://www.ecmwf.int/en/forecasts/datasets/reanalysis-datasets/era-
interim
>
> I think the first or second option is preferable to the 3rd. Since
you run
> the MET tools to evaluate a particular valid time, it's convenient
to have
> all the climo data you'll be using for that valid time in the same
file.
> The ERA interim data will work too, but it'll take the tools longer
to sift
> through all those records to find the one which matches the current
valid
> time.
>
> Hope that helps.
>
> Thanks,
> John
>
>
>
>
> On Thu, May 9, 2019 at 3:20 PM Minna Win via RT <met_help at ucar.edu>
wrote:
>
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=90155 >
> >
> > Hello Glen,
> >
> > It looks like you have some questions regarding climatology files
in MET.
> > I'm assigning this issue to John Halley Gotway.
> >
> > Regards,
> > Minna
> > ---------------
> > Minna Win
> > NCAR
> > Research Applications Lab
> > Phone: 303-497-8423
> > Fax: 303-497-8401
> >
> >
> >
> > On Thu, May 9, 2019 at 8:13 PM Carl, Mr. Glen, Contractor, Code
7532 via
> RT
> > <met_help at ucar.edu> wrote:
> >
> > >
> > > Thu May 09 14:13:29 2019: Request 90155 was acted upon.
> > > Transaction: Ticket created by glen.carl.ctr at nrlmry.navy.mil
> > > Queue: met_help
> > > Subject: climatology file examples
> > > Owner: Nobody
> > > Requestors: glen.carl.ctr at nrlmry.navy.mil
> > > Status: new
> > > Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=90155
> >
> > >
> > >
> > >
> > > I am trying to understand the interpolation of the climatology
data,
> and
> > I
> > > need some help. I think John Halley Gotway may be the best help
since
> it
> > > looks
> > > like he wrote the climatology software.
> > >
> > > Ref:
> > > src/libcode/vx_statistics/read_climo.cc
> > >
> > > // Search the files for the requested records
> > > for(i=0; i<climo_files.n_elements(); i++) {
> > > read_climo_file(climo_files[i], ctype, &i_dict, vld_ut,
> > > match_month, match_day, time_step,
> > > vx_grid, regrid_info, dpa);
> > > }
> > >
> > > // Time interpolation for mean fields
> > > dpa = climo_time_interp(dpa, vld_ut, time_interp);
> > >
> > > I understand the climatology files must be grid input format
(guessing
> > > GRIB2
> > > best practice), however, I am stuck on the date range of your
typical
> > > climatology files. I am starting out with pre-existing ieee
Monthly
> > > climatology files, and these files are interpolated with
previous and
> > next
> > > month, and computing continues to get the weighted value for
anomaly
> > > correlation.
> > >
> > > In other words, what is the typical file naming, and date range
of
> > > climatology
> > > files that play well with MET ?
> > >
> > > Thanks,
> > > Glen
> > >
> > > --
> > > Mr. Glen CARL
> > > NRL Monterey Contractor SAIC/0cog, Bldg 704 Rm 133, Code 7532
> > > 831.325.6269
> > > glen.carl.ctr at nrlmry.navy.mil
> > >
> > >
> > >
> > >
> >
> >
>
>
>
------------------------------------------------
More information about the Met_help
mailing list