[Met_help] [rt.rap.ucar.edu #88706] History for Help on Total Cloud % grid_stat verification
John Halley Gotway via RT
met_help at ucar.edu
Wed Feb 13 11:34:06 MST 2019
----------------------------------------------------------------
Initial Request
----------------------------------------------------------------
Hi,
I need to verify the Total Cloud % in the global ensemble predication files for GFS, CMC, and NAVGEM model against WWMCA data.
However GFS has the grib2 record for Total cloud as a 6-12 hour average, while other models such as NAVGEM
has Total Cloud % as 12 hour forecast.
When I pair a GFS global ensemble member file, say gep01.t00Z.pgrb2af12 for the day 20181205 and forecast hr
012 with the WWMCA file "wwmca_0p5deg_2018120512.nc, for METv6.1 grid_stat() function it uses
20181205_060000 as valid_time. The output files reflect that too. Is there a way to force it to take 0012 as the valid time?
Thank you
suseela
----------------------------------------------------------------
Complete Ticket History
----------------------------------------------------------------
Subject: Help on Total Cloud % grid_stat verification
From: John Halley Gotway
Time: Mon Feb 11 13:44:12 2019
Suseela,
Just wanted to check in on this issue. Are you still experiencing
troubles
with timestamps when verifying total cloud amount in Grid-Stat?
Matt Sittel did hand me some sample data when he visited NCAR last
week
describing a problem with timestamps being off by 6 hours. I haven't
been
able to dig into those details yet, but this sounds very similar to
the
behavior he's describing.
Thanks,
John
On Wed, Jan 30, 2019 at 10:41 AM SARASAMMA, SUSEELA T CTR USAF AFMC
AFLCMC/HBAW-OL via RT <met_help at ucar.edu> wrote:
>
> Wed Jan 30 10:41:40 2019: Request 88706 was acted upon.
> Transaction: Ticket created by suseela.sarasamma.ctr at us.af.mil
> Queue: met_help
> Subject: Help on Total Cloud % grid_stat verification
> Owner: Nobody
> Requestors: suseela.sarasamma.ctr at us.af.mil
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=88706 >
>
>
> Hi,
>
> I need to verify the Total Cloud % in the global ensemble
predication
> files for GFS, CMC, and NAVGEM model against WWMCA data.
> However GFS has the grib2 record for Total cloud as a 6-12 hour
average,
> while other models such as NAVGEM
> has Total Cloud % as 12 hour forecast.
>
> When I pair a GFS global ensemble member file, say
gep01.t00Z.pgrb2af12
> for the day 20181205 and forecast hr
> 012 with the WWMCA file "wwmca_0p5deg_2018120512.nc, for METv6.1
> grid_stat() function it uses
> 20181205_060000 as valid_time. The output files reflect that too. Is
there
> a way to force it to take 0012 as the valid time?
>
> Thank you
> suseela
>
>
>
>
------------------------------------------------
Subject: RE: [Non-DoD Source] Re: [rt.rap.ucar.edu #88706] Help on Total Cloud % grid_stat verification
From: SARASAMMA, SUSEELA T CTR USAF AFMC AFLCMC/HBAW-OL
Time: Tue Feb 12 08:47:45 2019
John,
Yes, that is true for GFS model's ensemble files for Total Cloud.
Total cloud is available in the GFS as the 6 to 12 hr average not as
12 hr forecast as in
CMC and NAVGEM models. Then when MET grid_stat is run on Total cloud %
with GFS ensemble member
as forecast and WWMCA netcdf file as truth, the output file shows the
beginning time of the 6-12 hr
in its name and relevant fields instead of the 12 hr ending time.
suseela
-----Original Message-----
From: John Halley Gotway via RT <met_help at ucar.edu>
Sent: Monday, February 11, 2019 2:44 PM
To: SARASAMMA, SUSEELA T CTR USAF AFMC AFLCMC/HBAW-OL
<suseela.sarasamma.ctr at us.af.mil>
Subject: [Non-DoD Source] Re: [rt.rap.ucar.edu #88706] Help on Total
Cloud % grid_stat verification
Suseela,
Just wanted to check in on this issue. Are you still experiencing
troubles with timestamps when verifying total cloud amount in Grid-
Stat?
Matt Sittel did hand me some sample data when he visited NCAR last
week describing a problem with timestamps being off by 6 hours. I
haven't been able to dig into those details yet, but this sounds very
similar to the behavior he's describing.
Thanks,
John
On Wed, Jan 30, 2019 at 10:41 AM SARASAMMA, SUSEELA T CTR USAF AFMC
AFLCMC/HBAW-OL via RT <met_help at ucar.edu> wrote:
>
> Wed Jan 30 10:41:40 2019: Request 88706 was acted upon.
> Transaction: Ticket created by suseela.sarasamma.ctr at us.af.mil
> Queue: met_help
> Subject: Help on Total Cloud % grid_stat verification
> Owner: Nobody
> Requestors: suseela.sarasamma.ctr at us.af.mil
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=88706
> >
>
>
> Hi,
>
> I need to verify the Total Cloud % in the global ensemble
predication
> files for GFS, CMC, and NAVGEM model against WWMCA data.
> However GFS has the grib2 record for Total cloud as a 6-12 hour
> average, while other models such as NAVGEM has Total Cloud % as 12
> hour forecast.
>
> When I pair a GFS global ensemble member file, say
> gep01.t00Z.pgrb2af12 for the day 20181205 and forecast hr
> 012 with the WWMCA file "wwmca_0p5deg_2018120512.nc, for METv6.1
> grid_stat() function it uses
> 20181205_060000 as valid_time. The output files reflect that too. Is
> there a way to force it to take 0012 as the valid time?
>
> Thank you
> suseela
>
>
>
>
------------------------------------------------
Subject: Help on Total Cloud % grid_stat verification
From: John Halley Gotway
Time: Tue Feb 12 15:22:43 2019
Suseela,
OK, I'm able to replicate the behavior you describe. Thanks for
pointing
it out!
What's a bit odd is that MET does not have a problem with the global
GFS
data found in:
*
https://nomads.ncep.noaa.gov/pub/data/nccf/com/gens/prod/gefs.20190212/00/pgrb2a/geavg.t00z.pgrb2af12
<https://nomads.ncep.noaa.gov/pub/data/nccf/com/gens/prod/gefs.20190212/00/pgrb2a/geavg.t00z.pgrb2af12>*
But this issue does show up when processing individual ensemble
members:
*https://nomads.ncep.noaa.gov/pub/data/nccf/com/gens/prod/gefs.20190212/00/pgrb2/gep01.t00z.pgrb2f12
<https://nomads.ncep.noaa.gov/pub/data/nccf/com/gens/prod/gefs.20190212/00/pgrb2/gep01.t00z.pgrb2f12>*
I'm preparing the first beta release of met-8.1 for you folks to test
out.
Let me get this issue solved and then I'll get the met-8.1_beta1
release to
you as soon as possible (hopefully tomorrow).
Thanks,
John
On Tue, Feb 12, 2019 at 8:47 AM SARASAMMA, SUSEELA T CTR USAF AFMC
AFLCMC/HBAW-OL via RT <met_help at ucar.edu> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=88706 >
>
> John,
>
> Yes, that is true for GFS model's ensemble files for Total Cloud.
> Total cloud is available in the GFS as the 6 to 12 hr average not
as 12
> hr forecast as in
> CMC and NAVGEM models. Then when MET grid_stat is run on Total cloud
%
> with GFS ensemble member
> as forecast and WWMCA netcdf file as truth, the output file shows
the
> beginning time of the 6-12 hr
> in its name and relevant fields instead of the 12 hr ending time.
>
> suseela
>
> -----Original Message-----
> From: John Halley Gotway via RT <met_help at ucar.edu>
> Sent: Monday, February 11, 2019 2:44 PM
> To: SARASAMMA, SUSEELA T CTR USAF AFMC AFLCMC/HBAW-OL <
> suseela.sarasamma.ctr at us.af.mil>
> Subject: [Non-DoD Source] Re: [rt.rap.ucar.edu #88706] Help on Total
> Cloud % grid_stat verification
>
> Suseela,
>
> Just wanted to check in on this issue. Are you still experiencing
> troubles with timestamps when verifying total cloud amount in Grid-
Stat?
>
> Matt Sittel did hand me some sample data when he visited NCAR last
week
> describing a problem with timestamps being off by 6 hours. I
haven't been
> able to dig into those details yet, but this sounds very similar to
the
> behavior he's describing.
>
> Thanks,
> John
>
> On Wed, Jan 30, 2019 at 10:41 AM SARASAMMA, SUSEELA T CTR USAF AFMC
> AFLCMC/HBAW-OL via RT <met_help at ucar.edu> wrote:
>
> >
> > Wed Jan 30 10:41:40 2019: Request 88706 was acted upon.
> > Transaction: Ticket created by suseela.sarasamma.ctr at us.af.mil
> > Queue: met_help
> > Subject: Help on Total Cloud % grid_stat verification
> > Owner: Nobody
> > Requestors: suseela.sarasamma.ctr at us.af.mil
> > Status: new
> > Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=88706
> > >
> >
> >
> > Hi,
> >
> > I need to verify the Total Cloud % in the global ensemble
predication
> > files for GFS, CMC, and NAVGEM model against WWMCA data.
> > However GFS has the grib2 record for Total cloud as a 6-12 hour
> > average, while other models such as NAVGEM has Total Cloud % as 12
> > hour forecast.
> >
> > When I pair a GFS global ensemble member file, say
> > gep01.t00Z.pgrb2af12 for the day 20181205 and forecast hr
> > 012 with the WWMCA file "wwmca_0p5deg_2018120512.nc, for METv6.1
> > grid_stat() function it uses
> > 20181205_060000 as valid_time. The output files reflect that too.
Is
> > there a way to force it to take 0012 as the valid time?
> >
> > Thank you
> > suseela
> >
> >
> >
> >
>
>
>
>
------------------------------------------------
Subject: Help on Total Cloud % grid_stat verification
From: John Halley Gotway
Time: Tue Feb 12 16:48:16 2019
Suseela (Bob and Matt),
Good news. I was able to run the GFS ensemble member and mean files
side-by-side through a debugger with MET and identify the lines in
MET's
GRIB2 library code that were causing the discrepancy in the
timestamps.
The ensemble member uses product definition template number 11 while
the
mean uses template number 12. MET was handling 12 fine, but not 11:
https://www.nco.ncep.noaa.gov/pmb/docs/grib2/grib2_doc/grib2_temp4-
11.shtml
https://www.nco.ncep.noaa.gov/pmb/docs/grib2/grib2_doc/grib2_temp4-
12.shtml
So I patched that up and rebuilt the met-8.1_beta1 release to include
this
change.
Now I just need to deliver the met-8.1_beta1 release tarball to you.
Thanks,
John
On Tue, Feb 12, 2019 at 3:22 PM John Halley Gotway <johnhg at ucar.edu>
wrote:
> Suseela,
>
> OK, I'm able to replicate the behavior you describe. Thanks for
pointing
> it out!
>
> What's a bit odd is that MET does not have a problem with the global
GFS
> data found in:
> *
>
https://nomads.ncep.noaa.gov/pub/data/nccf/com/gens/prod/gefs.20190212/00/pgrb2a/geavg.t00z.pgrb2af12
>
<https://nomads.ncep.noaa.gov/pub/data/nccf/com/gens/prod/gefs.20190212/00/pgrb2a/geavg.t00z.pgrb2af12>*
>
> But this issue does show up when processing individual ensemble
members:
>
*https://nomads.ncep.noaa.gov/pub/data/nccf/com/gens/prod/gefs.20190212/00/pgrb2/gep01.t00z.pgrb2f12
>
<https://nomads.ncep.noaa.gov/pub/data/nccf/com/gens/prod/gefs.20190212/00/pgrb2/gep01.t00z.pgrb2f12>*
>
> I'm preparing the first beta release of met-8.1 for you folks to
test
> out. Let me get this issue solved and then I'll get the met-
8.1_beta1
> release to you as soon as possible (hopefully tomorrow).
>
> Thanks,
> John
>
> On Tue, Feb 12, 2019 at 8:47 AM SARASAMMA, SUSEELA T CTR USAF AFMC
> AFLCMC/HBAW-OL via RT <met_help at ucar.edu> wrote:
>
>>
>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=88706 >
>>
>> John,
>>
>> Yes, that is true for GFS model's ensemble files for Total Cloud.
>> Total cloud is available in the GFS as the 6 to 12 hr average not
as 12
>> hr forecast as in
>> CMC and NAVGEM models. Then when MET grid_stat is run on Total
cloud %
>> with GFS ensemble member
>> as forecast and WWMCA netcdf file as truth, the output file shows
the
>> beginning time of the 6-12 hr
>> in its name and relevant fields instead of the 12 hr ending time.
>>
>> suseela
>>
>> -----Original Message-----
>> From: John Halley Gotway via RT <met_help at ucar.edu>
>> Sent: Monday, February 11, 2019 2:44 PM
>> To: SARASAMMA, SUSEELA T CTR USAF AFMC AFLCMC/HBAW-OL <
>> suseela.sarasamma.ctr at us.af.mil>
>> Subject: [Non-DoD Source] Re: [rt.rap.ucar.edu #88706] Help on
Total
>> Cloud % grid_stat verification
>>
>> Suseela,
>>
>> Just wanted to check in on this issue. Are you still experiencing
>> troubles with timestamps when verifying total cloud amount in Grid-
Stat?
>>
>> Matt Sittel did hand me some sample data when he visited NCAR last
week
>> describing a problem with timestamps being off by 6 hours. I
haven't been
>> able to dig into those details yet, but this sounds very similar to
the
>> behavior he's describing.
>>
>> Thanks,
>> John
>>
>> On Wed, Jan 30, 2019 at 10:41 AM SARASAMMA, SUSEELA T CTR USAF AFMC
>> AFLCMC/HBAW-OL via RT <met_help at ucar.edu> wrote:
>>
>> >
>> > Wed Jan 30 10:41:40 2019: Request 88706 was acted upon.
>> > Transaction: Ticket created by suseela.sarasamma.ctr at us.af.mil
>> > Queue: met_help
>> > Subject: Help on Total Cloud % grid_stat verification
>> > Owner: Nobody
>> > Requestors: suseela.sarasamma.ctr at us.af.mil
>> > Status: new
>> > Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=88706
>> > >
>> >
>> >
>> > Hi,
>> >
>> > I need to verify the Total Cloud % in the global ensemble
predication
>> > files for GFS, CMC, and NAVGEM model against WWMCA data.
>> > However GFS has the grib2 record for Total cloud as a 6-12 hour
>> > average, while other models such as NAVGEM has Total Cloud % as
12
>> > hour forecast.
>> >
>> > When I pair a GFS global ensemble member file, say
>> > gep01.t00Z.pgrb2af12 for the day 20181205 and forecast hr
>> > 012 with the WWMCA file "wwmca_0p5deg_2018120512.nc, for METv6.1
>> > grid_stat() function it uses
>> > 20181205_060000 as valid_time. The output files reflect that too.
Is
>> > there a way to force it to take 0012 as the valid time?
>> >
>> > Thank you
>> > suseela
>> >
>> >
>> >
>> >
>>
>>
>>
>>
------------------------------------------------
Subject: RE: [Non-DoD Source] Re: [rt.rap.ucar.edu #88706] Help on Total Cloud % grid_stat verification
From: SARASAMMA, SUSEELA T CTR USAF AFMC AFLCMC/HBAW-OL
Time: Wed Feb 13 10:56:11 2019
John,
Thanks for the helpful info.
suseela
-----Original Message-----
From: John Halley Gotway via RT <met_help at ucar.edu>
Sent: Tuesday, February 12, 2019 5:48 PM
To: SARASAMMA, SUSEELA T CTR USAF AFMC AFLCMC/HBAW-OL
<suseela.sarasamma.ctr at us.af.mil>
Subject: Re: [Non-DoD Source] Re: [rt.rap.ucar.edu #88706] Help on
Total Cloud % grid_stat verification
Suseela (Bob and Matt),
Good news. I was able to run the GFS ensemble member and mean files
side-by-side through a debugger with MET and identify the lines in
MET's
GRIB2 library code that were causing the discrepancy in the
timestamps.
The ensemble member uses product definition template number 11 while
the mean uses template number 12. MET was handling 12 fine, but not
11:
https://www.nco.ncep.noaa.gov/pmb/docs/grib2/grib2_doc/grib2_temp4-
11.shtml
https://www.nco.ncep.noaa.gov/pmb/docs/grib2/grib2_doc/grib2_temp4-
12.shtml
So I patched that up and rebuilt the met-8.1_beta1 release to include
this change.
Now I just need to deliver the met-8.1_beta1 release tarball to you.
Thanks,
John
On Tue, Feb 12, 2019 at 3:22 PM John Halley Gotway <johnhg at ucar.edu>
wrote:
> Suseela,
>
> OK, I'm able to replicate the behavior you describe. Thanks for
> pointing it out!
>
> What's a bit odd is that MET does not have a problem with the global
> GFS data found in:
> *
>
>
https://nomads.ncep.noaa.gov/pub/data/nccf/com/gens/prod/gefs.20190212
> /00/pgrb2a/geavg.t00z.pgrb2af12
>
<https://nomads.ncep.noaa.gov/pub/data/nccf/com/gens/prod/gefs.2019021
> 2/00/pgrb2a/geavg.t00z.pgrb2af12>*
>
> But this issue does show up when processing individual ensemble
members:
>
>
*https://nomads.ncep.noaa.gov/pub/data/nccf/com/gens/prod/gefs.2019021
> 2/00/pgrb2/gep01.t00z.pgrb2f12
>
<https://nomads.ncep.noaa.gov/pub/data/nccf/com/gens/prod/gefs.2019021
> 2/00/pgrb2/gep01.t00z.pgrb2f12>*
>
> I'm preparing the first beta release of met-8.1 for you folks to
test
> out. Let me get this issue solved and then I'll get the met-
8.1_beta1
> release to you as soon as possible (hopefully tomorrow).
>
> Thanks,
> John
>
> On Tue, Feb 12, 2019 at 8:47 AM SARASAMMA, SUSEELA T CTR USAF AFMC
> AFLCMC/HBAW-OL via RT <met_help at ucar.edu> wrote:
>
>>
>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=88706 >
>>
>> John,
>>
>> Yes, that is true for GFS model's ensemble files for Total Cloud.
>> Total cloud is available in the GFS as the 6 to 12 hr average not
as
>> 12 hr forecast as in CMC and NAVGEM models. Then when MET grid_stat
>> is run on Total cloud % with GFS ensemble member as forecast and
>> WWMCA netcdf file as truth, the output file shows the beginning
time
>> of the 6-12 hr in its name and relevant fields instead of the 12 hr
>> ending time.
>>
>> suseela
>>
>> -----Original Message-----
>> From: John Halley Gotway via RT <met_help at ucar.edu>
>> Sent: Monday, February 11, 2019 2:44 PM
>> To: SARASAMMA, SUSEELA T CTR USAF AFMC AFLCMC/HBAW-OL <
>> suseela.sarasamma.ctr at us.af.mil>
>> Subject: [Non-DoD Source] Re: [rt.rap.ucar.edu #88706] Help on
Total
>> Cloud % grid_stat verification
>>
>> Suseela,
>>
>> Just wanted to check in on this issue. Are you still experiencing
>> troubles with timestamps when verifying total cloud amount in Grid-
Stat?
>>
>> Matt Sittel did hand me some sample data when he visited NCAR last
>> week describing a problem with timestamps being off by 6 hours. I
>> haven't been able to dig into those details yet, but this sounds
very
>> similar to the behavior he's describing.
>>
>> Thanks,
>> John
>>
>> On Wed, Jan 30, 2019 at 10:41 AM SARASAMMA, SUSEELA T CTR USAF AFMC
>> AFLCMC/HBAW-OL via RT <met_help at ucar.edu> wrote:
>>
>> >
>> > Wed Jan 30 10:41:40 2019: Request 88706 was acted upon.
>> > Transaction: Ticket created by suseela.sarasamma.ctr at us.af.mil
>> > Queue: met_help
>> > Subject: Help on Total Cloud % grid_stat verification
>> > Owner: Nobody
>> > Requestors: suseela.sarasamma.ctr at us.af.mil
>> > Status: new
>> > Ticket <URL:
>> > https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=88706
>> > >
>> >
>> >
>> > Hi,
>> >
>> > I need to verify the Total Cloud % in the global ensemble
>> > predication files for GFS, CMC, and NAVGEM model against WWMCA
data.
>> > However GFS has the grib2 record for Total cloud as a 6-12 hour
>> > average, while other models such as NAVGEM has Total Cloud % as
12
>> > hour forecast.
>> >
>> > When I pair a GFS global ensemble member file, say
>> > gep01.t00Z.pgrb2af12 for the day 20181205 and forecast hr
>> > 012 with the WWMCA file "wwmca_0p5deg_2018120512.nc, for METv6.1
>> > grid_stat() function it uses
>> > 20181205_060000 as valid_time. The output files reflect that too.
>> > Is there a way to force it to take 0012 as the valid time?
>> >
>> > Thank you
>> > suseela
>> >
>> >
>> >
>> >
>>
>>
>>
>>
------------------------------------------------
More information about the Met_help
mailing list