[Met_help] [rt.rap.ucar.edu #85223] History for Point Stat Precip Issue
John Halley Gotway via RT
met_help at ucar.edu
Tue Jul 9 12:03:36 MDT 2019
----------------------------------------------------------------
Initial Request
----------------------------------------------------------------
John, I have been following your dialog with Matt but I seem to have a
different issue then you worked with him.
I am running MET 6.1 and verifying precip probabilities (> .1in (2.54 mm)).
I am able to read the precip grib file okay (checked it with
plot_data_plane). The ob file is net cdf file in millimeters, attached .
The config file is also attached. When I run I get the following error:
DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized GRIB2
field indexes - disc: 0, master table: 10, center: 57, local table: 1,
parm_cat: 6, parm: 70
DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized GRIB2
field indexes - disc: 0, master table: 10, center: 57, local table: 1,
parm_cat: 6, parm: 70
DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized GRIB2
field indexes - disc: 0, master table: 10, center: 57, local table: 1,
parm_cat: 6, parm: 70
DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized GRIB2
field indexes - disc: 0, master table: 10, center: 57, local table: 1,
parm_cat: 6, parm: 70
DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized GRIB2
field indexes - disc: 0, master table: 10, center: 57, local table: 1,
parm_cat: 6, parm: 70
DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized GRIB2
field indexes - disc: 0, master table: 10, center: 57, local table: 1,
parm_cat: 6, parm: 70
DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized GRIB2
field indexes - disc: 0, master table: 10, center: 57, local table: 1,
parm_cat: 6, parm: 70
DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized GRIB2
field indexes - disc: 0, master table: 10, center: 57, local table: 1,
parm_cat: 6, parm: 70
DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized GRIB2
field indexes - disc: 0, master table: 10, center: 57, local table: 1,
parm_cat: 6, parm: 70
DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized GRIB2
field indexes - disc: 0, master table: 10, center: 57, local table: 1,
parm_cat: 6, parm: 70
DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized GRIB2
field indexes - disc: 0, master table: 10, center: 57, local table: 1,
parm_cat: 6, parm: 70
DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized GRIB2
field indexes - disc: 0, master table: 10, center: 57, local table: 1,
parm_cat: 19, parm: 223
DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized GRIB2
field indexes - disc: 0, master table: 10, center: 57, local table: 1,
parm_cat: 19, parm: 223
DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized GRIB2
field indexes - disc: 0, master table: 10, center: 57, local table: 1,
parm_cat: 19, parm: 223
DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized GRIB2
field indexes - disc: 0, master table: 10, center: 57, local table: 1,
parm_cat: 19, parm: 223
DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized GRIB2
field indexes - disc: 0, master table: 10, center: 57, local table: 1,
parm_cat: 19, parm: 223
ERROR :
ERROR : PointStatConfInfo::process_config() -> The number of verification
tasks in "obs.field" must be non-zero and match the number in "fcst.field".
ERROR :
The ob file contains a grib 1 kpds5 value of 61 which translates to APCP in
the grib 1 table (attached).
So what am I doing wrong? I sent the data files via AMRDEC
Thanks
Bob
----------------------------------------------------------------
Complete Ticket History
----------------------------------------------------------------
Subject: Point Stat Precip Issue
From: John Halley Gotway
Time: Fri May 18 11:02:37 2018
Bob,
Based on your description, it sounds like you're comparing gridded
model
output to a gridded analysis field. Since you're doing grid-to-grid
verification, you should be running the Grid-Stat tool. The Point-
Stat
tool is used to verify against point observations.
If you need me to take a closer look at the data you sent through
ARMDEC,
just let me know.
But please try running Grid-Stat to see if you have better success.
Thanks,
John
On Fri, May 18, 2018 at 10:53 AM, robert.craig.2 at us.af.mil via RT <
met_help at ucar.edu> wrote:
>
> Fri May 18 10:53:15 2018: Request 85223 was acted upon.
> Transaction: Ticket created by robert.craig.2 at us.af.mil
> Queue: met_help
> Subject: Point Stat Precip Issue
> Owner: Nobody
> Requestors: robert.craig.2 at us.af.mil
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=85223 >
>
>
> John, I have been following your dialog with Matt but I seem to have
a
> different issue then you worked with him.
>
> I am running MET 6.1 and verifying precip probabilities (> .1in
(2.54 mm)).
> I am able to read the precip grib file okay (checked it with
> plot_data_plane). The ob file is net cdf file in millimeters,
attached .
> The config file is also attached. When I run I get the following
error:
>
> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2
> field indexes - disc: 0, master table: 10, center: 57, local table:
1,
> parm_cat: 6, parm: 70
> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2
> field indexes - disc: 0, master table: 10, center: 57, local table:
1,
> parm_cat: 6, parm: 70
> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2
> field indexes - disc: 0, master table: 10, center: 57, local table:
1,
> parm_cat: 6, parm: 70
> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2
> field indexes - disc: 0, master table: 10, center: 57, local table:
1,
> parm_cat: 6, parm: 70
> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2
> field indexes - disc: 0, master table: 10, center: 57, local table:
1,
> parm_cat: 6, parm: 70
> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2
> field indexes - disc: 0, master table: 10, center: 57, local table:
1,
> parm_cat: 6, parm: 70
> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2
> field indexes - disc: 0, master table: 10, center: 57, local table:
1,
> parm_cat: 6, parm: 70
> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2
> field indexes - disc: 0, master table: 10, center: 57, local table:
1,
> parm_cat: 6, parm: 70
> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2
> field indexes - disc: 0, master table: 10, center: 57, local table:
1,
> parm_cat: 6, parm: 70
> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2
> field indexes - disc: 0, master table: 10, center: 57, local table:
1,
> parm_cat: 6, parm: 70
> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2
> field indexes - disc: 0, master table: 10, center: 57, local table:
1,
> parm_cat: 6, parm: 70
> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2
> field indexes - disc: 0, master table: 10, center: 57, local table:
1,
> parm_cat: 19, parm: 223
> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2
> field indexes - disc: 0, master table: 10, center: 57, local table:
1,
> parm_cat: 19, parm: 223
> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2
> field indexes - disc: 0, master table: 10, center: 57, local table:
1,
> parm_cat: 19, parm: 223
> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2
> field indexes - disc: 0, master table: 10, center: 57, local table:
1,
> parm_cat: 19, parm: 223
> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2
> field indexes - disc: 0, master table: 10, center: 57, local table:
1,
> parm_cat: 19, parm: 223
> ERROR :
> ERROR : PointStatConfInfo::process_config() -> The number of
verification
> tasks in "obs.field" must be non-zero and match the number in
"fcst.field".
> ERROR :
>
> The ob file contains a grib 1 kpds5 value of 61 which translates to
APCP in
> the grib 1 table (attached).
>
> So what am I doing wrong? I sent the data files via AMRDEC
>
> Thanks
> Bob
>
>
------------------------------------------------
Subject: Point Stat Precip Issue
From: John Halley Gotway
Time: Fri May 18 11:04:06 2018
Bob,
Ah never mind, I apologize. That sample NetCDF file really does
contain
point obs. I'll take a closer look now.
Thanks,
John
On Fri, May 18, 2018 at 11:02 AM, John Halley Gotway <johnhg at ucar.edu>
wrote:
> Bob,
>
> Based on your description, it sounds like you're comparing gridded
model
> output to a gridded analysis field. Since you're doing grid-to-grid
> verification, you should be running the Grid-Stat tool. The Point-
Stat
> tool is used to verify against point observations.
>
> If you need me to take a closer look at the data you sent through
ARMDEC,
> just let me know.
>
> But please try running Grid-Stat to see if you have better success.
>
> Thanks,
> John
>
> On Fri, May 18, 2018 at 10:53 AM, robert.craig.2 at us.af.mil via RT <
> met_help at ucar.edu> wrote:
>
>>
>> Fri May 18 10:53:15 2018: Request 85223 was acted upon.
>> Transaction: Ticket created by robert.craig.2 at us.af.mil
>> Queue: met_help
>> Subject: Point Stat Precip Issue
>> Owner: Nobody
>> Requestors: robert.craig.2 at us.af.mil
>> Status: new
>> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=85223 >
>>
>>
>> John, I have been following your dialog with Matt but I seem to
have a
>> different issue then you worked with him.
>>
>> I am running MET 6.1 and verifying precip probabilities (> .1in
(2.54
>> mm)).
>> I am able to read the precip grib file okay (checked it with
>> plot_data_plane). The ob file is net cdf file in millimeters,
attached .
>> The config file is also attached. When I run I get the following
error:
>>
>> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2
>> field indexes - disc: 0, master table: 10, center: 57, local table:
1,
>> parm_cat: 6, parm: 70
>> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2
>> field indexes - disc: 0, master table: 10, center: 57, local table:
1,
>> parm_cat: 6, parm: 70
>> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2
>> field indexes - disc: 0, master table: 10, center: 57, local table:
1,
>> parm_cat: 6, parm: 70
>> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2
>> field indexes - disc: 0, master table: 10, center: 57, local table:
1,
>> parm_cat: 6, parm: 70
>> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2
>> field indexes - disc: 0, master table: 10, center: 57, local table:
1,
>> parm_cat: 6, parm: 70
>> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2
>> field indexes - disc: 0, master table: 10, center: 57, local table:
1,
>> parm_cat: 6, parm: 70
>> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2
>> field indexes - disc: 0, master table: 10, center: 57, local table:
1,
>> parm_cat: 6, parm: 70
>> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2
>> field indexes - disc: 0, master table: 10, center: 57, local table:
1,
>> parm_cat: 6, parm: 70
>> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2
>> field indexes - disc: 0, master table: 10, center: 57, local table:
1,
>> parm_cat: 6, parm: 70
>> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2
>> field indexes - disc: 0, master table: 10, center: 57, local table:
1,
>> parm_cat: 6, parm: 70
>> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2
>> field indexes - disc: 0, master table: 10, center: 57, local table:
1,
>> parm_cat: 6, parm: 70
>> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2
>> field indexes - disc: 0, master table: 10, center: 57, local table:
1,
>> parm_cat: 19, parm: 223
>> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2
>> field indexes - disc: 0, master table: 10, center: 57, local table:
1,
>> parm_cat: 19, parm: 223
>> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2
>> field indexes - disc: 0, master table: 10, center: 57, local table:
1,
>> parm_cat: 19, parm: 223
>> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2
>> field indexes - disc: 0, master table: 10, center: 57, local table:
1,
>> parm_cat: 19, parm: 223
>> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2
>> field indexes - disc: 0, master table: 10, center: 57, local table:
1,
>> parm_cat: 19, parm: 223
>> ERROR :
>> ERROR : PointStatConfInfo::process_config() -> The number of
>> verification
>> tasks in "obs.field" must be non-zero and match the number in
>> "fcst.field".
>> ERROR :
>>
>> The ob file contains a grib 1 kpds5 value of 61 which translates to
APCP
>> in
>> the grib 1 table (attached).
>>
>> So what am I doing wrong? I sent the data files via AMRDEC
>>
>> Thanks
>> Bob
>>
>>
>
------------------------------------------------
Subject: RE: [Non-DoD Source] Re: [rt.rap.ucar.edu #85223] Point Stat Precip Issue
From: robert.craig.2 at us.af.mil
Time: Fri May 18 11:47:09 2018
John, the NETCDF file is point data, not gridded data, so point stat
is the program to use. Please check the data.
-----Original Message-----
From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
Sent: Friday, May 18, 2018 12:03 PM
To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
<robert.craig.2 at us.af.mil>
Subject: [Non-DoD Source] Re: [rt.rap.ucar.edu #85223] Point Stat
Precip Issue
Bob,
Based on your description, it sounds like you're comparing gridded
model output to a gridded analysis field. Since you're doing grid-to-
grid verification, you should be running the Grid-Stat tool. The
Point-Stat tool is used to verify against point observations.
If you need me to take a closer look at the data you sent through
ARMDEC, just let me know.
But please try running Grid-Stat to see if you have better success.
Thanks,
John
On Fri, May 18, 2018 at 10:53 AM, robert.craig.2 at us.af.mil via RT <
met_help at ucar.edu> wrote:
>
> Fri May 18 10:53:15 2018: Request 85223 was acted upon.
> Transaction: Ticket created by robert.craig.2 at us.af.mil
> Queue: met_help
> Subject: Point Stat Precip Issue
> Owner: Nobody
> Requestors: robert.craig.2 at us.af.mil
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=85223
> >
>
>
> John, I have been following your dialog with Matt but I seem to have
a
> different issue then you worked with him.
>
> I am running MET 6.1 and verifying precip probabilities (> .1in
(2.54 mm)).
> I am able to read the precip grib file okay (checked it with
> plot_data_plane). The ob file is net cdf file in millimeters,
attached .
> The config file is also attached. When I run I get the following
error:
>
> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> table: 1,
> parm_cat: 6, parm: 70
> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> table: 1,
> parm_cat: 6, parm: 70
> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> table: 1,
> parm_cat: 6, parm: 70
> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> table: 1,
> parm_cat: 6, parm: 70
> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> table: 1,
> parm_cat: 6, parm: 70
> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> table: 1,
> parm_cat: 6, parm: 70
> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> table: 1,
> parm_cat: 6, parm: 70
> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> table: 1,
> parm_cat: 6, parm: 70
> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> table: 1,
> parm_cat: 6, parm: 70
> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> table: 1,
> parm_cat: 6, parm: 70
> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> table: 1,
> parm_cat: 6, parm: 70
> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> table: 1,
> parm_cat: 19, parm: 223
> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> table: 1,
> parm_cat: 19, parm: 223
> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> table: 1,
> parm_cat: 19, parm: 223
> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> table: 1,
> parm_cat: 19, parm: 223
> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> table: 1,
> parm_cat: 19, parm: 223
> ERROR :
> ERROR : PointStatConfInfo::process_config() -> The number of
> verification tasks in "obs.field" must be non-zero and match the
number in "fcst.field".
> ERROR :
>
> The ob file contains a grib 1 kpds5 value of 61 which translates to
> APCP in the grib 1 table (attached).
>
> So what am I doing wrong? I sent the data files via AMRDEC
>
> Thanks
> Bob
>
>
------------------------------------------------
Subject: Point Stat Precip Issue
From: John Halley Gotway
Time: Fri May 18 11:48:51 2018
Bob,
Thanks for sending your sample data.
The first step is getting MET to understand what you mean by the
string
"QP010". I see that you attached the file named "grib1_af_131_57.txt"
but
"QP010" doesn't show up in that file... and this is GRIB2 anyway. I
hunted
through the GRIB2 tables for the current development version of MET
but
didn't find QP010 there either. Looking at your config file entries,
I'm
still unsure which GRIB2 record you're trying to verify.
Presumably, it's at the surface and is a 6 hour accumulation... which
narrows it down a bit:
wgrib2 grib2.2018040100.0012 | egrep -i surface | egrep "6-12 hour
acc"
247:9779539:d=2018040100:var discipline=0 master_table=10 parmcat=19
parm=173:surface:6-12 hour acc fcst:ENS=hi-res ctl
249:9850964:d=2018040100:var discipline=0 master_table=10 parmcat=19
parm=182:surface:6-12 hour acc fcst:ENS=hi-res ctl
251:9885811:d=2018040100:var discipline=0 master_table=10 parmcat=19
parm=175:surface:6-12 hour acc fcst:ENS=hi-res ctl
252:9936766:d=2018040100:var discipline=0 master_table=10 parmcat=19
parm=176:surface:6-12 hour acc fcst:ENS=hi-res ctl
253:9977412:d=2018040100:var discipline=0 master_table=10 parmcat=19
parm=177:surface:6-12 hour acc fcst:ENS=hi-res ctl
254:10003210:d=2018040100:var discipline=0 master_table=10 parmcat=19
parm=178:surface:6-12 hour acc fcst:ENS=hi-res ctl
255:10018565:d=2018040100:var discipline=0 master_table=10 parmcat=19
parm=179:surface:6-12 hour acc fcst:ENS=hi-res ctl
256:10028421:d=2018040100:var discipline=0 master_table=10 parmcat=19
parm=180:surface:6-12 hour acc fcst:ENS=hi-res ctl
326:11553685:d=2018040100:var discipline=0 master_table=10 parmcat=19
parm=184:surface:6-12 hour acc fcst:ENS=hi-res ctl
327:11563992:d=2018040100:var discipline=0 master_table=10 parmcat=19
parm=185:surface:6-12 hour acc fcst:ENS=hi-res ctl
328:11568924:d=2018040100:var discipline=0 master_table=10 parmcat=19
parm=186:surface:6-12 hour acc fcst:ENS=hi-res ctl
416:16784501:d=2018040100:SDWE:surface:6-12 hour acc fcst:ENS=hi-res
ctl
417:16812843:d=2018040100:var discipline=0 center=57 local_table=1
parmcat=1 parm=243:surface:6-12 hour acc fcst:ENS=hi-res ctl
421:16881856:d=2018040100:var discipline=0 master_table=10 parmcat=19
parm=169:surface:6-12 hour acc fcst:ENS=hi-res ctl
Ultimately, we should create a custom GRIB2 table that tells MET how
to
interpret this data. Following the example from Matt, I'll make a
very
simple one and *ASSUME* that parm=173 should be called "QP010". This
is
probably wrong... so you should update this table with the correct
settings:
cat grib2_af_qpf.txt (see attached)
+++++++++++++++++++++++++
GRIB2
0 10 0 255 57 0 19 173 "QP010" "Probability of precip" "%"
+++++++++++++++++++++++++
Next, I ran plot_data_plane to make sure MET was happy:
setenv MET_GRIB_TABLES grib2_af_qpf.txt
met-6.1/bin/plot_data_plane grib2.2018040100.0012 plot.ps
'name="QP010";
level="Z0";' -v 4
But I found an issue... at verbosity level 4, MET thinks the forecast
is
valid at 20180401_060000. But wgrib2 says that it's valid 6 hour
later:
247:9779539:d=2018040100:var discipline=0 master_table=10
parmcat=19
parm=173:surface:6-12 hour acc fcst:ENS=hi-res ctl
This leads to 0 matched pairs in Point-Stat because of this time
offset.
I'll need to figure out this discrepancy.
In the meantime, do you already have a GRIB2 table where QP010 is
defined?
Thanks,
John
On Fri, May 18, 2018 at 11:03 AM, John Halley Gotway <johnhg at ucar.edu>
wrote:
> Bob,
>
> Ah never mind, I apologize. That sample NetCDF file really does
contain
> point obs. I'll take a closer look now.
>
> Thanks,
> John
>
> On Fri, May 18, 2018 at 11:02 AM, John Halley Gotway
<johnhg at ucar.edu>
> wrote:
>
>> Bob,
>>
>> Based on your description, it sounds like you're comparing gridded
model
>> output to a gridded analysis field. Since you're doing grid-to-
grid
>> verification, you should be running the Grid-Stat tool. The Point-
Stat
>> tool is used to verify against point observations.
>>
>> If you need me to take a closer look at the data you sent through
ARMDEC,
>> just let me know.
>>
>> But please try running Grid-Stat to see if you have better success.
>>
>> Thanks,
>> John
>>
>> On Fri, May 18, 2018 at 10:53 AM, robert.craig.2 at us.af.mil via RT <
>> met_help at ucar.edu> wrote:
>>
>>>
>>> Fri May 18 10:53:15 2018: Request 85223 was acted upon.
>>> Transaction: Ticket created by robert.craig.2 at us.af.mil
>>> Queue: met_help
>>> Subject: Point Stat Precip Issue
>>> Owner: Nobody
>>> Requestors: robert.craig.2 at us.af.mil
>>> Status: new
>>> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=85223 >
>>>
>>>
>>> John, I have been following your dialog with Matt but I seem to
have a
>>> different issue then you worked with him.
>>>
>>> I am running MET 6.1 and verifying precip probabilities (> .1in
(2.54
>>> mm)).
>>> I am able to read the precip grib file okay (checked it with
>>> plot_data_plane). The ob file is net cdf file in millimeters,
attached .
>>> The config file is also attached. When I run I get the following
error:
>>>
>>> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2
>>> field indexes - disc: 0, master table: 10, center: 57, local
table: 1,
>>> parm_cat: 6, parm: 70
>>> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2
>>> field indexes - disc: 0, master table: 10, center: 57, local
table: 1,
>>> parm_cat: 6, parm: 70
>>> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2
>>> field indexes - disc: 0, master table: 10, center: 57, local
table: 1,
>>> parm_cat: 6, parm: 70
>>> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2
>>> field indexes - disc: 0, master table: 10, center: 57, local
table: 1,
>>> parm_cat: 6, parm: 70
>>> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2
>>> field indexes - disc: 0, master table: 10, center: 57, local
table: 1,
>>> parm_cat: 6, parm: 70
>>> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2
>>> field indexes - disc: 0, master table: 10, center: 57, local
table: 1,
>>> parm_cat: 6, parm: 70
>>> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2
>>> field indexes - disc: 0, master table: 10, center: 57, local
table: 1,
>>> parm_cat: 6, parm: 70
>>> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2
>>> field indexes - disc: 0, master table: 10, center: 57, local
table: 1,
>>> parm_cat: 6, parm: 70
>>> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2
>>> field indexes - disc: 0, master table: 10, center: 57, local
table: 1,
>>> parm_cat: 6, parm: 70
>>> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2
>>> field indexes - disc: 0, master table: 10, center: 57, local
table: 1,
>>> parm_cat: 6, parm: 70
>>> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2
>>> field indexes - disc: 0, master table: 10, center: 57, local
table: 1,
>>> parm_cat: 6, parm: 70
>>> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2
>>> field indexes - disc: 0, master table: 10, center: 57, local
table: 1,
>>> parm_cat: 19, parm: 223
>>> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2
>>> field indexes - disc: 0, master table: 10, center: 57, local
table: 1,
>>> parm_cat: 19, parm: 223
>>> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2
>>> field indexes - disc: 0, master table: 10, center: 57, local
table: 1,
>>> parm_cat: 19, parm: 223
>>> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2
>>> field indexes - disc: 0, master table: 10, center: 57, local
table: 1,
>>> parm_cat: 19, parm: 223
>>> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2
>>> field indexes - disc: 0, master table: 10, center: 57, local
table: 1,
>>> parm_cat: 19, parm: 223
>>> ERROR :
>>> ERROR : PointStatConfInfo::process_config() -> The number of
>>> verification
>>> tasks in "obs.field" must be non-zero and match the number in
>>> "fcst.field".
>>> ERROR :
>>>
>>> The ob file contains a grib 1 kpds5 value of 61 which translates
to APCP
>>> in
>>> the grib 1 table (attached).
>>>
>>> So what am I doing wrong? I sent the data files via AMRDEC
>>>
>>> Thanks
>>> Bob
>>>
>>>
>>
>
------------------------------------------------
Subject: Point Stat Precip Issue
From: John Halley Gotway
Time: Fri May 18 11:48:51 2018
GRIB2
0 10 0 255 57 0 19 173 "QP010" "Probability of precip" "%"
------------------------------------------------
Subject: Point Stat Precip Issue
From: robert.craig.2 at us.af.mil
Time: Fri May 18 11:57:43 2018
John, I attached is my GRIB 2 table.
-----Original Message-----
From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
Sent: Friday, May 18, 2018 12:04 PM
To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
<robert.craig.2 at us.af.mil>
Subject: [Non-DoD Source] Re: [rt.rap.ucar.edu #85223] Point Stat
Precip Issue
Bob,
Ah never mind, I apologize. That sample NetCDF file really does
contain point
obs. I'll take a closer look now.
Thanks,
John
On Fri, May 18, 2018 at 11:02 AM, John Halley Gotway <johnhg at ucar.edu>
wrote:
> Bob,
>
> Based on your description, it sounds like you're comparing gridded
> model output to a gridded analysis field. Since you're doing
> grid-to-grid verification, you should be running the Grid-Stat tool.
> The Point-Stat tool is used to verify against point observations.
>
> If you need me to take a closer look at the data you sent through
> ARMDEC, just let me know.
>
> But please try running Grid-Stat to see if you have better success.
>
> Thanks,
> John
>
> On Fri, May 18, 2018 at 10:53 AM, robert.craig.2 at us.af.mil via RT <
> met_help at ucar.edu> wrote:
>
>>
>> Fri May 18 10:53:15 2018: Request 85223 was acted upon.
>> Transaction: Ticket created by robert.craig.2 at us.af.mil
>> Queue: met_help
>> Subject: Point Stat Precip Issue
>> Owner: Nobody
>> Requestors: robert.craig.2 at us.af.mil
>> Status: new
>> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=85223
>> >
>>
>>
>> John, I have been following your dialog with Matt but I seem to
have
>> a different issue then you worked with him.
>>
>> I am running MET 6.1 and verifying precip probabilities (> .1in
(2.54
>> mm)).
>> I am able to read the precip grib file okay (checked it with
>> plot_data_plane). The ob file is net cdf file in millimeters,
attached .
>> The config file is also attached. When I run I get the following
error:
>>
>> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
>> GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
>> table: 1,
>> parm_cat: 6, parm: 70
>> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
>> GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
>> table: 1,
>> parm_cat: 6, parm: 70
>> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
>> GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
>> table: 1,
>> parm_cat: 6, parm: 70
>> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
>> GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
>> table: 1,
>> parm_cat: 6, parm: 70
>> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
>> GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
>> table: 1,
>> parm_cat: 6, parm: 70
>> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
>> GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
>> table: 1,
>> parm_cat: 6, parm: 70
>> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
>> GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
>> table: 1,
>> parm_cat: 6, parm: 70
>> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
>> GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
>> table: 1,
>> parm_cat: 6, parm: 70
>> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
>> GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
>> table: 1,
>> parm_cat: 6, parm: 70
>> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
>> GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
>> table: 1,
>> parm_cat: 6, parm: 70
>> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
>> GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
>> table: 1,
>> parm_cat: 6, parm: 70
>> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
>> GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
>> table: 1,
>> parm_cat: 19, parm: 223
>> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
>> GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
>> table: 1,
>> parm_cat: 19, parm: 223
>> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
>> GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
>> table: 1,
>> parm_cat: 19, parm: 223
>> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
>> GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
>> table: 1,
>> parm_cat: 19, parm: 223
>> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
>> GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
>> table: 1,
>> parm_cat: 19, parm: 223
>> ERROR :
>> ERROR : PointStatConfInfo::process_config() -> The number of
>> verification tasks in "obs.field" must be non-zero and match the
>> number in "fcst.field".
>> ERROR :
>>
>> The ob file contains a grib 1 kpds5 value of 61 which translates to
>> APCP in the grib 1 table (attached).
>>
>> So what am I doing wrong? I sent the data files via AMRDEC
>>
>> Thanks
>> Bob
>>
>>
>
------------------------------------------------
Subject: Point Stat Precip Issue
From: robert.craig.2 at us.af.mil
Time: Fri May 18 11:57:43 2018
GRIB2
0 14 0 255 57 0 1 33 "CRAIN" "Categorical Rain" "-"
0 14 0 255 57 0 1 36 "CSNOW" "Categorical Snow" "-"
0 14 0 255 57 0 1 34 "CFRZR" "Categorical Freezing Rain" "-"
0 14 0 255 57 0 19 0 "VIS" "Visibility" "m"
0 10 0 255 57 1 19 161 "PWS15" "10 m above ground" "%"
0 10 0 255 57 1 19 163 "PWS25" "Probabilty of 10 m winds above
25kts" "%"
0 10 0 255 57 1 19 164 "PWS35" "Probabilty of 10 m winds above
35kts" "%"
0 10 0 255 57 1 19 165 "PWS50" "Probabilty of 10 m winds above
50kts" "%"
0 10 0 255 57 1 19 182 "PSN1" "Probability of snow accumulation > 1"
"%"
0 10 0 255 57 1 19 183 "PSN2" "Probability of snow accumulation > 2"
"%"
0 10 0 255 57 1 19 176 "APCP" "Probability of precip accumulation >
.10" "%"
0 1 0 255 57 1 1 8 "APCP" "Probability of precip accumulation > .25"
"%"
0 1 0 255 57 1 1 8 "APCP" "Probability of precip accumulation > .50"
"%"
0 1 0 255 57 1 1 8 "APCP" "Probability of precip accumulation > .75"
"%"
0 1 0 255 57 1 1 8 "APCP" "Probability of precip accumulation > 1.0"
"%"
0 1 0 255 57 1 1 8 "APCP" "Probability of precip accumulation > 5.0"
"%"
0 10 0 255 57 1 19 211 "DUST" "Dust visiblity" "m"
0 10 0 255 57 1 19 212 "PT273" "Probability of 2m temperature > 273"
"%"
0 10 0 255 57 1 19 213 "PT305" "Probability of 2m temperature > 305"
"%"
0 10 0 255 57 1 19 207 "PHT58" "Probability of 500mb HGT > 5800 m"
"%"
0 10 0 255 57 1 19 203 "PVIS1" "Probability of surface visiblity < 1
mi" "%"
0 10 0 255 57 1 19 202 "PVIS3" "Probability of surface visibility <
3 mi" "%"
0 10 0 255 57 1 19 201 "PVIS5" "Probability of surface visibility <
5 mi" "%"
0 10 0 255 57 1 19 224 "PC20" "Probabilty of Total Cloud < 20 %"
"%"
0 10 0 255 57 1 19 225 "PC80" "Probablity of Total Cloud > 80 %"
"%"
0 14 0 255 57 0 1 8 "APCP" "Total accumulated precipitation"
"kilogramsPerMeterSquared"
0 1 0 255 57 1 1 8 "APCP" "Probability of precip accumulation > .01"
"%"
0 1 0 255 57 1 1 8 "APCP" "Probability of precip accumulation > .02"
"%"
0 1 0 255 57 1 1 8 "APCP" "Probability of precip accumulation > .05"
"%"
0 10 0 255 57 1 19 176 "QP010" "Probability of precip accumulation >
.01" "%"
------------------------------------------------
Subject: Point Stat Precip Issue
From: John Halley Gotway
Time: Mon May 21 13:39:18 2018
Bob,
I was working on this last Friday. Unfortunately, I don't have a good
solution for you. MET is not parsing the timing information for this
data
correctly.
We need to update the GRIB library parsing logic to account for this.
setenv MET_GRIB_TABLES grib2_geps.txt
met-6.1/bin/plot_data_plane grib2.2018040100.0012
grib2.2018040100.0012.ps
'name="QP010"; level="Z0";' -v 4
DEBUG 4: valid time: 20180401_060000
DEBUG 4: lead time: 060000
DEBUG 4: init time: 20180401_000000
MET gets the initialization time correct, but it processes the data as
a 6
hour forecast, rather than recognizing it as a 6-12 hour accumulation.
Therefore the lead time and valid times are wrong. And that leads to
zero
matched pairs from Point-Stat. We need to patch MET to correctly
parse the
accumulation information from this file.
In the meantime, one band-aid would be adjusting the matching time
window
in Point-Stat to account for the 6 hour offset:
met-6.1/bin/point_stat grib2.2018040100.0012 nc_2018040112
PointStatConfig_geps_precip_updated-NEW -outdir out -v 3
DEBUG 2: Processing QP010/Z0 versus APCP/A0, for observation type
ADPSFC,
over region FULL, for interpolation method NEAREST(1), using 448
pairs.
DEBUG 3: Number of matched pairs = 448
DEBUG 3: Observations processed = 449
Since MET thinks the forecast is valid 6 hours earlier than it really
is, I
set the matching time window to select obs 6 hours later:
obs_window = {
beg = 6*3600 - 600;
end = 6*3600 + 600;
}
See that attached config file.
Matt tells me that MET is "frozen" there. Are you able to recompile
with
patches for met-6.1? Or stuck with what you've got?
Thanks,
John
On Fri, May 18, 2018 at 11:57 AM, robert.craig.2 at us.af.mil via RT <
met_help at ucar.edu> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=85223 >
>
> John, I attached is my GRIB 2 table.
>
> -----Original Message-----
> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> Sent: Friday, May 18, 2018 12:04 PM
> To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
<robert.craig.2 at us.af.mil>
> Subject: [Non-DoD Source] Re: [rt.rap.ucar.edu #85223] Point Stat
Precip
> Issue
>
> Bob,
>
> Ah never mind, I apologize. That sample NetCDF file really does
contain
> point
> obs. I'll take a closer look now.
>
> Thanks,
> John
>
> On Fri, May 18, 2018 at 11:02 AM, John Halley Gotway
<johnhg at ucar.edu>
> wrote:
>
> > Bob,
> >
> > Based on your description, it sounds like you're comparing gridded
> > model output to a gridded analysis field. Since you're doing
> > grid-to-grid verification, you should be running the Grid-Stat
tool.
> > The Point-Stat tool is used to verify against point observations.
> >
> > If you need me to take a closer look at the data you sent through
> > ARMDEC, just let me know.
> >
> > But please try running Grid-Stat to see if you have better
success.
> >
> > Thanks,
> > John
> >
> > On Fri, May 18, 2018 at 10:53 AM, robert.craig.2 at us.af.mil via RT
<
> > met_help at ucar.edu> wrote:
> >
> >>
> >> Fri May 18 10:53:15 2018: Request 85223 was acted upon.
> >> Transaction: Ticket created by robert.craig.2 at us.af.mil
> >> Queue: met_help
> >> Subject: Point Stat Precip Issue
> >> Owner: Nobody
> >> Requestors: robert.craig.2 at us.af.mil
> >> Status: new
> >> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=85223
> >> >
> >>
> >>
> >> John, I have been following your dialog with Matt but I seem to
have
> >> a different issue then you worked with him.
> >>
> >> I am running MET 6.1 and verifying precip probabilities (> .1in
(2.54
> >> mm)).
> >> I am able to read the precip grib file okay (checked it with
> >> plot_data_plane). The ob file is net cdf file in millimeters,
attached
> .
> >> The config file is also attached. When I run I get the following
error:
> >>
> >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> >> GRIB2 field indexes - disc: 0, master table: 10, center: 57,
local
> >> table: 1,
> >> parm_cat: 6, parm: 70
> >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> >> GRIB2 field indexes - disc: 0, master table: 10, center: 57,
local
> >> table: 1,
> >> parm_cat: 6, parm: 70
> >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> >> GRIB2 field indexes - disc: 0, master table: 10, center: 57,
local
> >> table: 1,
> >> parm_cat: 6, parm: 70
> >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> >> GRIB2 field indexes - disc: 0, master table: 10, center: 57,
local
> >> table: 1,
> >> parm_cat: 6, parm: 70
> >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> >> GRIB2 field indexes - disc: 0, master table: 10, center: 57,
local
> >> table: 1,
> >> parm_cat: 6, parm: 70
> >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> >> GRIB2 field indexes - disc: 0, master table: 10, center: 57,
local
> >> table: 1,
> >> parm_cat: 6, parm: 70
> >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> >> GRIB2 field indexes - disc: 0, master table: 10, center: 57,
local
> >> table: 1,
> >> parm_cat: 6, parm: 70
> >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> >> GRIB2 field indexes - disc: 0, master table: 10, center: 57,
local
> >> table: 1,
> >> parm_cat: 6, parm: 70
> >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> >> GRIB2 field indexes - disc: 0, master table: 10, center: 57,
local
> >> table: 1,
> >> parm_cat: 6, parm: 70
> >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> >> GRIB2 field indexes - disc: 0, master table: 10, center: 57,
local
> >> table: 1,
> >> parm_cat: 6, parm: 70
> >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> >> GRIB2 field indexes - disc: 0, master table: 10, center: 57,
local
> >> table: 1,
> >> parm_cat: 6, parm: 70
> >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> >> GRIB2 field indexes - disc: 0, master table: 10, center: 57,
local
> >> table: 1,
> >> parm_cat: 19, parm: 223
> >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> >> GRIB2 field indexes - disc: 0, master table: 10, center: 57,
local
> >> table: 1,
> >> parm_cat: 19, parm: 223
> >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> >> GRIB2 field indexes - disc: 0, master table: 10, center: 57,
local
> >> table: 1,
> >> parm_cat: 19, parm: 223
> >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> >> GRIB2 field indexes - disc: 0, master table: 10, center: 57,
local
> >> table: 1,
> >> parm_cat: 19, parm: 223
> >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> >> GRIB2 field indexes - disc: 0, master table: 10, center: 57,
local
> >> table: 1,
> >> parm_cat: 19, parm: 223
> >> ERROR :
> >> ERROR : PointStatConfInfo::process_config() -> The number of
> >> verification tasks in "obs.field" must be non-zero and match the
> >> number in "fcst.field".
> >> ERROR :
> >>
> >> The ob file contains a grib 1 kpds5 value of 61 which translates
to
> >> APCP in the grib 1 table (attached).
> >>
> >> So what am I doing wrong? I sent the data files via AMRDEC
> >>
> >> Thanks
> >> Bob
> >>
> >>
> >
>
>
>
>
------------------------------------------------
Subject: RE: [Non-DoD Source] Re: [rt.rap.ucar.edu #85223] Point Stat Precip Issue
From: robert.craig.2 at us.af.mil
Time: Mon May 21 14:00:51 2018
John,
We are frozen until you deliver the version with the Fortify error
fixes. I was hoping to be running on MET entirely by now but the new
security rules are not allowing that.
Bob
-----Original Message-----
From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
Sent: Monday, May 21, 2018 2:39 PM
To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
<robert.craig.2 at us.af.mil>
Subject: Re: [Non-DoD Source] Re: [rt.rap.ucar.edu #85223] Point Stat
Precip Issue
Bob,
I was working on this last Friday. Unfortunately, I don't have a good
solution for you. MET is not parsing the timing information for this
data correctly.
We need to update the GRIB library parsing logic to account for this.
setenv MET_GRIB_TABLES grib2_geps.txt
met-6.1/bin/plot_data_plane grib2.2018040100.0012
grib2.2018040100.0012.ps 'name="QP010"; level="Z0";' -v 4
DEBUG 4: valid time: 20180401_060000
DEBUG 4: lead time: 060000
DEBUG 4: init time: 20180401_000000
MET gets the initialization time correct, but it processes the data as
a 6 hour forecast, rather than recognizing it as a 6-12 hour
accumulation.
Therefore the lead time and valid times are wrong. And that leads to
zero matched pairs from Point-Stat. We need to patch MET to correctly
parse the accumulation information from this file.
In the meantime, one band-aid would be adjusting the matching time
window in Point-Stat to account for the 6 hour offset:
met-6.1/bin/point_stat grib2.2018040100.0012 nc_2018040112
PointStatConfig_geps_precip_updated-NEW -outdir out -v 3
DEBUG 2: Processing QP010/Z0 versus APCP/A0, for observation type
ADPSFC, over region FULL, for interpolation method NEAREST(1), using
448 pairs.
DEBUG 3: Number of matched pairs = 448
DEBUG 3: Observations processed = 449
Since MET thinks the forecast is valid 6 hours earlier than it really
is, I set the matching time window to select obs 6 hours later:
obs_window = {
beg = 6*3600 - 600;
end = 6*3600 + 600;
}
See that attached config file.
Matt tells me that MET is "frozen" there. Are you able to recompile
with patches for met-6.1? Or stuck with what you've got?
Thanks,
John
On Fri, May 18, 2018 at 11:57 AM, robert.craig.2 at us.af.mil via RT <
met_help at ucar.edu> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=85223 >
>
> John, I attached is my GRIB 2 table.
>
> -----Original Message-----
> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> Sent: Friday, May 18, 2018 12:04 PM
> To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
> <robert.craig.2 at us.af.mil>
> Subject: [Non-DoD Source] Re: [rt.rap.ucar.edu #85223] Point Stat
> Precip Issue
>
> Bob,
>
> Ah never mind, I apologize. That sample NetCDF file really does
> contain point obs. I'll take a closer look now.
>
> Thanks,
> John
>
> On Fri, May 18, 2018 at 11:02 AM, John Halley Gotway
<johnhg at ucar.edu>
> wrote:
>
> > Bob,
> >
> > Based on your description, it sounds like you're comparing gridded
> > model output to a gridded analysis field. Since you're doing
> > grid-to-grid verification, you should be running the Grid-Stat
tool.
> > The Point-Stat tool is used to verify against point observations.
> >
> > If you need me to take a closer look at the data you sent through
> > ARMDEC, just let me know.
> >
> > But please try running Grid-Stat to see if you have better
success.
> >
> > Thanks,
> > John
> >
> > On Fri, May 18, 2018 at 10:53 AM, robert.craig.2 at us.af.mil via RT
<
> > met_help at ucar.edu> wrote:
> >
> >>
> >> Fri May 18 10:53:15 2018: Request 85223 was acted upon.
> >> Transaction: Ticket created by robert.craig.2 at us.af.mil
> >> Queue: met_help
> >> Subject: Point Stat Precip Issue
> >> Owner: Nobody
> >> Requestors: robert.craig.2 at us.af.mil
> >> Status: new
> >> Ticket <URL:
> >> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=85223
> >> >
> >>
> >>
> >> John, I have been following your dialog with Matt but I seem to
> >> have a different issue then you worked with him.
> >>
> >> I am running MET 6.1 and verifying precip probabilities (> .1in
> >> (2.54 mm)).
> >> I am able to read the precip grib file okay (checked it with
> >> plot_data_plane). The ob file is net cdf file in millimeters,
> >> attached
> .
> >> The config file is also attached. When I run I get the following
error:
> >>
> >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> >> GRIB2 field indexes - disc: 0, master table: 10, center: 57,
local
> >> table: 1,
> >> parm_cat: 6, parm: 70
> >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> >> GRIB2 field indexes - disc: 0, master table: 10, center: 57,
local
> >> table: 1,
> >> parm_cat: 6, parm: 70
> >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> >> GRIB2 field indexes - disc: 0, master table: 10, center: 57,
local
> >> table: 1,
> >> parm_cat: 6, parm: 70
> >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> >> GRIB2 field indexes - disc: 0, master table: 10, center: 57,
local
> >> table: 1,
> >> parm_cat: 6, parm: 70
> >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> >> GRIB2 field indexes - disc: 0, master table: 10, center: 57,
local
> >> table: 1,
> >> parm_cat: 6, parm: 70
> >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> >> GRIB2 field indexes - disc: 0, master table: 10, center: 57,
local
> >> table: 1,
> >> parm_cat: 6, parm: 70
> >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> >> GRIB2 field indexes - disc: 0, master table: 10, center: 57,
local
> >> table: 1,
> >> parm_cat: 6, parm: 70
> >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> >> GRIB2 field indexes - disc: 0, master table: 10, center: 57,
local
> >> table: 1,
> >> parm_cat: 6, parm: 70
> >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> >> GRIB2 field indexes - disc: 0, master table: 10, center: 57,
local
> >> table: 1,
> >> parm_cat: 6, parm: 70
> >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> >> GRIB2 field indexes - disc: 0, master table: 10, center: 57,
local
> >> table: 1,
> >> parm_cat: 6, parm: 70
> >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> >> GRIB2 field indexes - disc: 0, master table: 10, center: 57,
local
> >> table: 1,
> >> parm_cat: 6, parm: 70
> >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> >> GRIB2 field indexes - disc: 0, master table: 10, center: 57,
local
> >> table: 1,
> >> parm_cat: 19, parm: 223
> >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> >> GRIB2 field indexes - disc: 0, master table: 10, center: 57,
local
> >> table: 1,
> >> parm_cat: 19, parm: 223
> >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> >> GRIB2 field indexes - disc: 0, master table: 10, center: 57,
local
> >> table: 1,
> >> parm_cat: 19, parm: 223
> >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> >> GRIB2 field indexes - disc: 0, master table: 10, center: 57,
local
> >> table: 1,
> >> parm_cat: 19, parm: 223
> >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> >> GRIB2 field indexes - disc: 0, master table: 10, center: 57,
local
> >> table: 1,
> >> parm_cat: 19, parm: 223
> >> ERROR :
> >> ERROR : PointStatConfInfo::process_config() -> The number of
> >> verification tasks in "obs.field" must be non-zero and match the
> >> number in "fcst.field".
> >> ERROR :
> >>
> >> The ob file contains a grib 1 kpds5 value of 61 which translates
to
> >> APCP in the grib 1 table (attached).
> >>
> >> So what am I doing wrong? I sent the data files via AMRDEC
> >>
> >> Thanks
> >> Bob
> >>
> >>
> >
>
>
>
>
------------------------------------------------
Subject: Point Stat Precip Issue
From: John Halley Gotway
Time: Mon May 21 14:16:51 2018
OK, so does that band-aid make sense to you? Adjusting the time
window so
that Point-Stat can find matches.
John
On Mon, May 21, 2018 at 2:00 PM, robert.craig.2 at us.af.mil via RT <
met_help at ucar.edu> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=85223 >
>
> John,
>
> We are frozen until you deliver the version with the Fortify error
fixes.
> I was hoping to be running on MET entirely by now but the new
security
> rules are not allowing that.
>
> Bob
>
>
> -----Original Message-----
> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> Sent: Monday, May 21, 2018 2:39 PM
> To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
<robert.craig.2 at us.af.mil>
> Subject: Re: [Non-DoD Source] Re: [rt.rap.ucar.edu #85223] Point
Stat
> Precip Issue
>
> Bob,
>
> I was working on this last Friday. Unfortunately, I don't have a
good
> solution for you. MET is not parsing the timing information for
this data
> correctly.
>
> We need to update the GRIB library parsing logic to account for
this.
>
> setenv MET_GRIB_TABLES grib2_geps.txt
> met-6.1/bin/plot_data_plane grib2.2018040100.0012
grib2.2018040100.0012.ps
> 'name="QP010"; level="Z0";' -v 4
>
> DEBUG 4: valid time: 20180401_060000
> DEBUG 4: lead time: 060000
> DEBUG 4: init time: 20180401_000000
>
> MET gets the initialization time correct, but it processes the data
as a 6
> hour forecast, rather than recognizing it as a 6-12 hour
accumulation.
> Therefore the lead time and valid times are wrong. And that leads
to zero
> matched pairs from Point-Stat. We need to patch MET to correctly
parse the
> accumulation information from this file.
>
> In the meantime, one band-aid would be adjusting the matching time
window
> in Point-Stat to account for the 6 hour offset:
>
> met-6.1/bin/point_stat grib2.2018040100.0012 nc_2018040112
> PointStatConfig_geps_precip_updated-NEW -outdir out -v 3
>
> DEBUG 2: Processing QP010/Z0 versus APCP/A0, for observation type
ADPSFC,
> over region FULL, for interpolation method NEAREST(1), using 448
pairs.
> DEBUG 3: Number of matched pairs = 448
> DEBUG 3: Observations processed = 449
>
> Since MET thinks the forecast is valid 6 hours earlier than it
really is,
> I set the matching time window to select obs 6 hours later:
> obs_window = {
> beg = 6*3600 - 600;
> end = 6*3600 + 600;
> }
>
> See that attached config file.
>
> Matt tells me that MET is "frozen" there. Are you able to recompile
with
> patches for met-6.1? Or stuck with what you've got?
>
> Thanks,
> John
>
>
>
> On Fri, May 18, 2018 at 11:57 AM, robert.craig.2 at us.af.mil via RT <
> met_help at ucar.edu> wrote:
>
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=85223 >
> >
> > John, I attached is my GRIB 2 table.
> >
> > -----Original Message-----
> > From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> > Sent: Friday, May 18, 2018 12:04 PM
> > To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
> > <robert.craig.2 at us.af.mil>
> > Subject: [Non-DoD Source] Re: [rt.rap.ucar.edu #85223] Point Stat
> > Precip Issue
> >
> > Bob,
> >
> > Ah never mind, I apologize. That sample NetCDF file really does
> > contain point obs. I'll take a closer look now.
> >
> > Thanks,
> > John
> >
> > On Fri, May 18, 2018 at 11:02 AM, John Halley Gotway
<johnhg at ucar.edu>
> > wrote:
> >
> > > Bob,
> > >
> > > Based on your description, it sounds like you're comparing
gridded
> > > model output to a gridded analysis field. Since you're doing
> > > grid-to-grid verification, you should be running the Grid-Stat
tool.
> > > The Point-Stat tool is used to verify against point
observations.
> > >
> > > If you need me to take a closer look at the data you sent
through
> > > ARMDEC, just let me know.
> > >
> > > But please try running Grid-Stat to see if you have better
success.
> > >
> > > Thanks,
> > > John
> > >
> > > On Fri, May 18, 2018 at 10:53 AM, robert.craig.2 at us.af.mil via
RT <
> > > met_help at ucar.edu> wrote:
> > >
> > >>
> > >> Fri May 18 10:53:15 2018: Request 85223 was acted upon.
> > >> Transaction: Ticket created by robert.craig.2 at us.af.mil
> > >> Queue: met_help
> > >> Subject: Point Stat Precip Issue
> > >> Owner: Nobody
> > >> Requestors: robert.craig.2 at us.af.mil
> > >> Status: new
> > >> Ticket <URL:
> > >> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=85223
> > >> >
> > >>
> > >>
> > >> John, I have been following your dialog with Matt but I seem to
> > >> have a different issue then you worked with him.
> > >>
> > >> I am running MET 6.1 and verifying precip probabilities (> .1in
> > >> (2.54 mm)).
> > >> I am able to read the precip grib file okay (checked it with
> > >> plot_data_plane). The ob file is net cdf file in millimeters,
> > >> attached
> > .
> > >> The config file is also attached. When I run I get the
following
> error:
> > >>
> > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> > >> GRIB2 field indexes - disc: 0, master table: 10, center: 57,
local
> > >> table: 1,
> > >> parm_cat: 6, parm: 70
> > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> > >> GRIB2 field indexes - disc: 0, master table: 10, center: 57,
local
> > >> table: 1,
> > >> parm_cat: 6, parm: 70
> > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> > >> GRIB2 field indexes - disc: 0, master table: 10, center: 57,
local
> > >> table: 1,
> > >> parm_cat: 6, parm: 70
> > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> > >> GRIB2 field indexes - disc: 0, master table: 10, center: 57,
local
> > >> table: 1,
> > >> parm_cat: 6, parm: 70
> > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> > >> GRIB2 field indexes - disc: 0, master table: 10, center: 57,
local
> > >> table: 1,
> > >> parm_cat: 6, parm: 70
> > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> > >> GRIB2 field indexes - disc: 0, master table: 10, center: 57,
local
> > >> table: 1,
> > >> parm_cat: 6, parm: 70
> > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> > >> GRIB2 field indexes - disc: 0, master table: 10, center: 57,
local
> > >> table: 1,
> > >> parm_cat: 6, parm: 70
> > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> > >> GRIB2 field indexes - disc: 0, master table: 10, center: 57,
local
> > >> table: 1,
> > >> parm_cat: 6, parm: 70
> > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> > >> GRIB2 field indexes - disc: 0, master table: 10, center: 57,
local
> > >> table: 1,
> > >> parm_cat: 6, parm: 70
> > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> > >> GRIB2 field indexes - disc: 0, master table: 10, center: 57,
local
> > >> table: 1,
> > >> parm_cat: 6, parm: 70
> > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> > >> GRIB2 field indexes - disc: 0, master table: 10, center: 57,
local
> > >> table: 1,
> > >> parm_cat: 6, parm: 70
> > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> > >> GRIB2 field indexes - disc: 0, master table: 10, center: 57,
local
> > >> table: 1,
> > >> parm_cat: 19, parm: 223
> > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> > >> GRIB2 field indexes - disc: 0, master table: 10, center: 57,
local
> > >> table: 1,
> > >> parm_cat: 19, parm: 223
> > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> > >> GRIB2 field indexes - disc: 0, master table: 10, center: 57,
local
> > >> table: 1,
> > >> parm_cat: 19, parm: 223
> > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> > >> GRIB2 field indexes - disc: 0, master table: 10, center: 57,
local
> > >> table: 1,
> > >> parm_cat: 19, parm: 223
> > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> > >> GRIB2 field indexes - disc: 0, master table: 10, center: 57,
local
> > >> table: 1,
> > >> parm_cat: 19, parm: 223
> > >> ERROR :
> > >> ERROR : PointStatConfInfo::process_config() -> The number of
> > >> verification tasks in "obs.field" must be non-zero and match
the
> > >> number in "fcst.field".
> > >> ERROR :
> > >>
> > >> The ob file contains a grib 1 kpds5 value of 61 which
translates to
> > >> APCP in the grib 1 table (attached).
> > >>
> > >> So what am I doing wrong? I sent the data files via AMRDEC
> > >>
> > >> Thanks
> > >> Bob
> > >>
> > >>
> > >
> >
> >
> >
> >
>
>
>
>
------------------------------------------------
Subject: RE: [Non-DoD Source] Re: [rt.rap.ucar.edu #85223] Point Stat Precip Issue
From: robert.craig.2 at us.af.mil
Time: Mon May 21 14:43:50 2018
John, I tried the ob time window adjustment you provided but still get
the same error. See below.
DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
table: 1, parm_cat: 19, parm: 223
ERROR :
ERROR : PointStatConfInfo::process_config() -> The number of
verification tasks in "obs.field" must be non-zero and match the
number in "fcst.field".
ERROR :
I noticed that you had the obs set to just APCP and A0 even though is
a probability forecast. In the past I had to use the following:
field = [
{cat_thresh=[>.1];
name="PROB";level="A006";prob={name="APCP";thresh_lo=.1;}}
];
How does MET know what to threshold the observation data by?
Bob
-----Original Message-----
From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
Sent: Monday, May 21, 2018 3:17 PM
To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
<robert.craig.2 at us.af.mil>
Subject: Re: [Non-DoD Source] Re: [rt.rap.ucar.edu #85223] Point Stat
Precip Issue
OK, so does that band-aid make sense to you? Adjusting the time
window so that Point-Stat can find matches.
John
On Mon, May 21, 2018 at 2:00 PM, robert.craig.2 at us.af.mil via RT <
met_help at ucar.edu> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=85223 >
>
> John,
>
> We are frozen until you deliver the version with the Fortify error
fixes.
> I was hoping to be running on MET entirely by now but the new
> security rules are not allowing that.
>
> Bob
>
>
> -----Original Message-----
> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> Sent: Monday, May 21, 2018 2:39 PM
> To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
> <robert.craig.2 at us.af.mil>
> Subject: Re: [Non-DoD Source] Re: [rt.rap.ucar.edu #85223] Point
Stat
> Precip Issue
>
> Bob,
>
> I was working on this last Friday. Unfortunately, I don't have a
good
> solution for you. MET is not parsing the timing information for
this
> data correctly.
>
> We need to update the GRIB library parsing logic to account for
this.
>
> setenv MET_GRIB_TABLES grib2_geps.txt
> met-6.1/bin/plot_data_plane grib2.2018040100.0012
> grib2.2018040100.0012.ps 'name="QP010"; level="Z0";' -v 4
>
> DEBUG 4: valid time: 20180401_060000
> DEBUG 4: lead time: 060000
> DEBUG 4: init time: 20180401_000000
>
> MET gets the initialization time correct, but it processes the data
as
> a 6 hour forecast, rather than recognizing it as a 6-12 hour
accumulation.
> Therefore the lead time and valid times are wrong. And that leads
to
> zero matched pairs from Point-Stat. We need to patch MET to
correctly
> parse the accumulation information from this file.
>
> In the meantime, one band-aid would be adjusting the matching time
> window in Point-Stat to account for the 6 hour offset:
>
> met-6.1/bin/point_stat grib2.2018040100.0012 nc_2018040112
> PointStatConfig_geps_precip_updated-NEW -outdir out -v 3
>
> DEBUG 2: Processing QP010/Z0 versus APCP/A0, for observation type
> ADPSFC, over region FULL, for interpolation method NEAREST(1), using
448 pairs.
> DEBUG 3: Number of matched pairs = 448
> DEBUG 3: Observations processed = 449
>
> Since MET thinks the forecast is valid 6 hours earlier than it
really
> is, I set the matching time window to select obs 6 hours later:
> obs_window = {
> beg = 6*3600 - 600;
> end = 6*3600 + 600;
> }
>
> See that attached config file.
>
> Matt tells me that MET is "frozen" there. Are you able to recompile
> with patches for met-6.1? Or stuck with what you've got?
>
> Thanks,
> John
>
>
>
> On Fri, May 18, 2018 at 11:57 AM, robert.craig.2 at us.af.mil via RT <
> met_help at ucar.edu> wrote:
>
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=85223 >
> >
> > John, I attached is my GRIB 2 table.
> >
> > -----Original Message-----
> > From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> > Sent: Friday, May 18, 2018 12:04 PM
> > To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
> > <robert.craig.2 at us.af.mil>
> > Subject: [Non-DoD Source] Re: [rt.rap.ucar.edu #85223] Point Stat
> > Precip Issue
> >
> > Bob,
> >
> > Ah never mind, I apologize. That sample NetCDF file really does
> > contain point obs. I'll take a closer look now.
> >
> > Thanks,
> > John
> >
> > On Fri, May 18, 2018 at 11:02 AM, John Halley Gotway
> > <johnhg at ucar.edu>
> > wrote:
> >
> > > Bob,
> > >
> > > Based on your description, it sounds like you're comparing
gridded
> > > model output to a gridded analysis field. Since you're doing
> > > grid-to-grid verification, you should be running the Grid-Stat
tool.
> > > The Point-Stat tool is used to verify against point
observations.
> > >
> > > If you need me to take a closer look at the data you sent
through
> > > ARMDEC, just let me know.
> > >
> > > But please try running Grid-Stat to see if you have better
success.
> > >
> > > Thanks,
> > > John
> > >
> > > On Fri, May 18, 2018 at 10:53 AM, robert.craig.2 at us.af.mil via
RT
> > > < met_help at ucar.edu> wrote:
> > >
> > >>
> > >> Fri May 18 10:53:15 2018: Request 85223 was acted upon.
> > >> Transaction: Ticket created by robert.craig.2 at us.af.mil
> > >> Queue: met_help
> > >> Subject: Point Stat Precip Issue
> > >> Owner: Nobody
> > >> Requestors: robert.craig.2 at us.af.mil
> > >> Status: new
> > >> Ticket <URL:
> > >> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=85223
> > >> >
> > >>
> > >>
> > >> John, I have been following your dialog with Matt but I seem to
> > >> have a different issue then you worked with him.
> > >>
> > >> I am running MET 6.1 and verifying precip probabilities (> .1in
> > >> (2.54 mm)).
> > >> I am able to read the precip grib file okay (checked it with
> > >> plot_data_plane). The ob file is net cdf file in millimeters,
> > >> attached
> > .
> > >> The config file is also attached. When I run I get the
following
> error:
> > >>
> > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > >> unrecognized
> > >> GRIB2 field indexes - disc: 0, master table: 10, center: 57,
> > >> local
> > >> table: 1,
> > >> parm_cat: 6, parm: 70
> > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > >> unrecognized
> > >> GRIB2 field indexes - disc: 0, master table: 10, center: 57,
> > >> local
> > >> table: 1,
> > >> parm_cat: 6, parm: 70
> > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > >> unrecognized
> > >> GRIB2 field indexes - disc: 0, master table: 10, center: 57,
> > >> local
> > >> table: 1,
> > >> parm_cat: 6, parm: 70
> > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > >> unrecognized
> > >> GRIB2 field indexes - disc: 0, master table: 10, center: 57,
> > >> local
> > >> table: 1,
> > >> parm_cat: 6, parm: 70
> > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > >> unrecognized
> > >> GRIB2 field indexes - disc: 0, master table: 10, center: 57,
> > >> local
> > >> table: 1,
> > >> parm_cat: 6, parm: 70
> > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > >> unrecognized
> > >> GRIB2 field indexes - disc: 0, master table: 10, center: 57,
> > >> local
> > >> table: 1,
> > >> parm_cat: 6, parm: 70
> > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > >> unrecognized
> > >> GRIB2 field indexes - disc: 0, master table: 10, center: 57,
> > >> local
> > >> table: 1,
> > >> parm_cat: 6, parm: 70
> > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > >> unrecognized
> > >> GRIB2 field indexes - disc: 0, master table: 10, center: 57,
> > >> local
> > >> table: 1,
> > >> parm_cat: 6, parm: 70
> > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > >> unrecognized
> > >> GRIB2 field indexes - disc: 0, master table: 10, center: 57,
> > >> local
> > >> table: 1,
> > >> parm_cat: 6, parm: 70
> > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > >> unrecognized
> > >> GRIB2 field indexes - disc: 0, master table: 10, center: 57,
> > >> local
> > >> table: 1,
> > >> parm_cat: 6, parm: 70
> > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > >> unrecognized
> > >> GRIB2 field indexes - disc: 0, master table: 10, center: 57,
> > >> local
> > >> table: 1,
> > >> parm_cat: 6, parm: 70
> > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > >> unrecognized
> > >> GRIB2 field indexes - disc: 0, master table: 10, center: 57,
> > >> local
> > >> table: 1,
> > >> parm_cat: 19, parm: 223
> > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > >> unrecognized
> > >> GRIB2 field indexes - disc: 0, master table: 10, center: 57,
> > >> local
> > >> table: 1,
> > >> parm_cat: 19, parm: 223
> > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > >> unrecognized
> > >> GRIB2 field indexes - disc: 0, master table: 10, center: 57,
> > >> local
> > >> table: 1,
> > >> parm_cat: 19, parm: 223
> > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > >> unrecognized
> > >> GRIB2 field indexes - disc: 0, master table: 10, center: 57,
> > >> local
> > >> table: 1,
> > >> parm_cat: 19, parm: 223
> > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > >> unrecognized
> > >> GRIB2 field indexes - disc: 0, master table: 10, center: 57,
> > >> local
> > >> table: 1,
> > >> parm_cat: 19, parm: 223
> > >> ERROR :
> > >> ERROR : PointStatConfInfo::process_config() -> The number of
> > >> verification tasks in "obs.field" must be non-zero and match
the
> > >> number in "fcst.field".
> > >> ERROR :
> > >>
> > >> The ob file contains a grib 1 kpds5 value of 61 which
translates
> > >> to APCP in the grib 1 table (attached).
> > >>
> > >> So what am I doing wrong? I sent the data files via AMRDEC
> > >>
> > >> Thanks
> > >> Bob
> > >>
> > >>
> > >
> >
> >
> >
> >
>
>
>
>
------------------------------------------------
Subject: Point Stat Precip Issue
From: John Halley Gotway
Time: Mon May 21 15:30:21 2018
Bob,
I attached a point-stat config file to my message with a "-NEW" suffix
at
the end. That contained changes to get point-stat up and running.
Did that attachment come through? If not, I could just cut-and-paste
it
inline in an email.
John
On Mon, May 21, 2018 at 2:43 PM, robert.craig.2 at us.af.mil via RT <
met_help at ucar.edu> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=85223 >
>
> John, I tried the ob time window adjustment you provided but still
get the
> same error. See below.
>
> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2
> field indexes - disc: 0, master table: 10, center: 57, local table:
1,
> parm_cat: 19, parm: 223
> ERROR :
> ERROR : PointStatConfInfo::process_config() -> The number of
> verification tasks in "obs.field" must be non-zero and match the
number in
> "fcst.field".
> ERROR :
>
> I noticed that you had the obs set to just APCP and A0 even though
is a
> probability forecast. In the past I had to use the following:
>
> field = [
> {cat_thresh=[>.1];
> name="PROB";level="A006";prob={name="APCP";thresh_lo=.1;}}
> ];
>
> How does MET know what to threshold the observation data by?
>
> Bob
>
> -----Original Message-----
> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> Sent: Monday, May 21, 2018 3:17 PM
> To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
<robert.craig.2 at us.af.mil>
> Subject: Re: [Non-DoD Source] Re: [rt.rap.ucar.edu #85223] Point
Stat
> Precip Issue
>
> OK, so does that band-aid make sense to you? Adjusting the time
window so
> that Point-Stat can find matches.
>
> John
>
> On Mon, May 21, 2018 at 2:00 PM, robert.craig.2 at us.af.mil via RT <
> met_help at ucar.edu> wrote:
>
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=85223 >
> >
> > John,
> >
> > We are frozen until you deliver the version with the Fortify error
fixes.
> > I was hoping to be running on MET entirely by now but the new
> > security rules are not allowing that.
> >
> > Bob
> >
> >
> > -----Original Message-----
> > From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> > Sent: Monday, May 21, 2018 2:39 PM
> > To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
> > <robert.craig.2 at us.af.mil>
> > Subject: Re: [Non-DoD Source] Re: [rt.rap.ucar.edu #85223] Point
Stat
> > Precip Issue
> >
> > Bob,
> >
> > I was working on this last Friday. Unfortunately, I don't have a
good
> > solution for you. MET is not parsing the timing information for
this
> > data correctly.
> >
> > We need to update the GRIB library parsing logic to account for
this.
> >
> > setenv MET_GRIB_TABLES grib2_geps.txt
> > met-6.1/bin/plot_data_plane grib2.2018040100.0012
> > grib2.2018040100.0012.ps 'name="QP010"; level="Z0";' -v 4
> >
> > DEBUG 4: valid time: 20180401_060000
> > DEBUG 4: lead time: 060000
> > DEBUG 4: init time: 20180401_000000
> >
> > MET gets the initialization time correct, but it processes the
data as
> > a 6 hour forecast, rather than recognizing it as a 6-12 hour
> accumulation.
> > Therefore the lead time and valid times are wrong. And that leads
to
> > zero matched pairs from Point-Stat. We need to patch MET to
correctly
> > parse the accumulation information from this file.
> >
> > In the meantime, one band-aid would be adjusting the matching time
> > window in Point-Stat to account for the 6 hour offset:
> >
> > met-6.1/bin/point_stat grib2.2018040100.0012 nc_2018040112
> > PointStatConfig_geps_precip_updated-NEW -outdir out -v 3
> >
> > DEBUG 2: Processing QP010/Z0 versus APCP/A0, for observation type
> > ADPSFC, over region FULL, for interpolation method NEAREST(1),
using 448
> pairs.
> > DEBUG 3: Number of matched pairs = 448
> > DEBUG 3: Observations processed = 449
> >
> > Since MET thinks the forecast is valid 6 hours earlier than it
really
> > is, I set the matching time window to select obs 6 hours later:
> > obs_window = {
> > beg = 6*3600 - 600;
> > end = 6*3600 + 600;
> > }
> >
> > See that attached config file.
> >
> > Matt tells me that MET is "frozen" there. Are you able to
recompile
> > with patches for met-6.1? Or stuck with what you've got?
> >
> > Thanks,
> > John
> >
> >
> >
> > On Fri, May 18, 2018 at 11:57 AM, robert.craig.2 at us.af.mil via RT
<
> > met_help at ucar.edu> wrote:
> >
> > >
> > > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=85223 >
> > >
> > > John, I attached is my GRIB 2 table.
> > >
> > > -----Original Message-----
> > > From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> > > Sent: Friday, May 18, 2018 12:04 PM
> > > To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
> > > <robert.craig.2 at us.af.mil>
> > > Subject: [Non-DoD Source] Re: [rt.rap.ucar.edu #85223] Point
Stat
> > > Precip Issue
> > >
> > > Bob,
> > >
> > > Ah never mind, I apologize. That sample NetCDF file really does
> > > contain point obs. I'll take a closer look now.
> > >
> > > Thanks,
> > > John
> > >
> > > On Fri, May 18, 2018 at 11:02 AM, John Halley Gotway
> > > <johnhg at ucar.edu>
> > > wrote:
> > >
> > > > Bob,
> > > >
> > > > Based on your description, it sounds like you're comparing
gridded
> > > > model output to a gridded analysis field. Since you're doing
> > > > grid-to-grid verification, you should be running the Grid-Stat
tool.
> > > > The Point-Stat tool is used to verify against point
observations.
> > > >
> > > > If you need me to take a closer look at the data you sent
through
> > > > ARMDEC, just let me know.
> > > >
> > > > But please try running Grid-Stat to see if you have better
success.
> > > >
> > > > Thanks,
> > > > John
> > > >
> > > > On Fri, May 18, 2018 at 10:53 AM, robert.craig.2 at us.af.mil via
RT
> > > > < met_help at ucar.edu> wrote:
> > > >
> > > >>
> > > >> Fri May 18 10:53:15 2018: Request 85223 was acted upon.
> > > >> Transaction: Ticket created by robert.craig.2 at us.af.mil
> > > >> Queue: met_help
> > > >> Subject: Point Stat Precip Issue
> > > >> Owner: Nobody
> > > >> Requestors: robert.craig.2 at us.af.mil
> > > >> Status: new
> > > >> Ticket <URL:
> > > >> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=85223
> > > >> >
> > > >>
> > > >>
> > > >> John, I have been following your dialog with Matt but I seem
to
> > > >> have a different issue then you worked with him.
> > > >>
> > > >> I am running MET 6.1 and verifying precip probabilities (>
.1in
> > > >> (2.54 mm)).
> > > >> I am able to read the precip grib file okay (checked it with
> > > >> plot_data_plane). The ob file is net cdf file in
millimeters,
> > > >> attached
> > > .
> > > >> The config file is also attached. When I run I get the
following
> > error:
> > > >>
> > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > >> unrecognized
> > > >> GRIB2 field indexes - disc: 0, master table: 10, center: 57,
> > > >> local
> > > >> table: 1,
> > > >> parm_cat: 6, parm: 70
> > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > >> unrecognized
> > > >> GRIB2 field indexes - disc: 0, master table: 10, center: 57,
> > > >> local
> > > >> table: 1,
> > > >> parm_cat: 6, parm: 70
> > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > >> unrecognized
> > > >> GRIB2 field indexes - disc: 0, master table: 10, center: 57,
> > > >> local
> > > >> table: 1,
> > > >> parm_cat: 6, parm: 70
> > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > >> unrecognized
> > > >> GRIB2 field indexes - disc: 0, master table: 10, center: 57,
> > > >> local
> > > >> table: 1,
> > > >> parm_cat: 6, parm: 70
> > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > >> unrecognized
> > > >> GRIB2 field indexes - disc: 0, master table: 10, center: 57,
> > > >> local
> > > >> table: 1,
> > > >> parm_cat: 6, parm: 70
> > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > >> unrecognized
> > > >> GRIB2 field indexes - disc: 0, master table: 10, center: 57,
> > > >> local
> > > >> table: 1,
> > > >> parm_cat: 6, parm: 70
> > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > >> unrecognized
> > > >> GRIB2 field indexes - disc: 0, master table: 10, center: 57,
> > > >> local
> > > >> table: 1,
> > > >> parm_cat: 6, parm: 70
> > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > >> unrecognized
> > > >> GRIB2 field indexes - disc: 0, master table: 10, center: 57,
> > > >> local
> > > >> table: 1,
> > > >> parm_cat: 6, parm: 70
> > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > >> unrecognized
> > > >> GRIB2 field indexes - disc: 0, master table: 10, center: 57,
> > > >> local
> > > >> table: 1,
> > > >> parm_cat: 6, parm: 70
> > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > >> unrecognized
> > > >> GRIB2 field indexes - disc: 0, master table: 10, center: 57,
> > > >> local
> > > >> table: 1,
> > > >> parm_cat: 6, parm: 70
> > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > >> unrecognized
> > > >> GRIB2 field indexes - disc: 0, master table: 10, center: 57,
> > > >> local
> > > >> table: 1,
> > > >> parm_cat: 6, parm: 70
> > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > >> unrecognized
> > > >> GRIB2 field indexes - disc: 0, master table: 10, center: 57,
> > > >> local
> > > >> table: 1,
> > > >> parm_cat: 19, parm: 223
> > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > >> unrecognized
> > > >> GRIB2 field indexes - disc: 0, master table: 10, center: 57,
> > > >> local
> > > >> table: 1,
> > > >> parm_cat: 19, parm: 223
> > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > >> unrecognized
> > > >> GRIB2 field indexes - disc: 0, master table: 10, center: 57,
> > > >> local
> > > >> table: 1,
> > > >> parm_cat: 19, parm: 223
> > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > >> unrecognized
> > > >> GRIB2 field indexes - disc: 0, master table: 10, center: 57,
> > > >> local
> > > >> table: 1,
> > > >> parm_cat: 19, parm: 223
> > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > >> unrecognized
> > > >> GRIB2 field indexes - disc: 0, master table: 10, center: 57,
> > > >> local
> > > >> table: 1,
> > > >> parm_cat: 19, parm: 223
> > > >> ERROR :
> > > >> ERROR : PointStatConfInfo::process_config() -> The number of
> > > >> verification tasks in "obs.field" must be non-zero and match
the
> > > >> number in "fcst.field".
> > > >> ERROR :
> > > >>
> > > >> The ob file contains a grib 1 kpds5 value of 61 which
translates
> > > >> to APCP in the grib 1 table (attached).
> > > >>
> > > >> So what am I doing wrong? I sent the data files via AMRDEC
> > > >>
> > > >> Thanks
> > > >> Bob
> > > >>
> > > >>
> > > >
> > >
> > >
> > >
> > >
> >
> >
> >
> >
>
>
>
>
>
------------------------------------------------
Subject: RE: [Non-DoD Source] Re: [rt.rap.ucar.edu #85223] Point Stat Precip Issue
From: robert.craig.2 at us.af.mil
Time: Mon May 21 15:45:20 2018
John, I only had used the adjustment to the ob window before and ob
field definition, but when I used the entire config file it worked.
When I look in the stat file I see the ob column has precip values
instead of the 0 or 1 based on my threshold. What is the proper
syntax to threshold the ob data to 2.54 mm/.1 "?
Thanks
Bob
-----Original Message-----
From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
Sent: Monday, May 21, 2018 4:30 PM
To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
<robert.craig.2 at us.af.mil>
Subject: Re: [Non-DoD Source] Re: [rt.rap.ucar.edu #85223] Point Stat
Precip Issue
Bob,
I attached a point-stat config file to my message with a "-NEW" suffix
at the end. That contained changes to get point-stat up and running.
Did that attachment come through? If not, I could just cut-and-paste
it inline in an email.
John
On Mon, May 21, 2018 at 2:43 PM, robert.craig.2 at us.af.mil via RT <
met_help at ucar.edu> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=85223 >
>
> John, I tried the ob time window adjustment you provided but still
get the
> same error. See below.
>
> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> table: 1,
> parm_cat: 19, parm: 223
> ERROR :
> ERROR : PointStatConfInfo::process_config() -> The number of
> verification tasks in "obs.field" must be non-zero and match the
> number in "fcst.field".
> ERROR :
>
> I noticed that you had the obs set to just APCP and A0 even though
is a
> probability forecast. In the past I had to use the following:
>
> field = [
> {cat_thresh=[>.1];
> name="PROB";level="A006";prob={name="APCP";thresh_lo=.1;}}
> ];
>
> How does MET know what to threshold the observation data by?
>
> Bob
>
> -----Original Message-----
> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> Sent: Monday, May 21, 2018 3:17 PM
> To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
> <robert.craig.2 at us.af.mil>
> Subject: Re: [Non-DoD Source] Re: [rt.rap.ucar.edu #85223] Point
Stat
> Precip Issue
>
> OK, so does that band-aid make sense to you? Adjusting the time
> window so that Point-Stat can find matches.
>
> John
>
> On Mon, May 21, 2018 at 2:00 PM, robert.craig.2 at us.af.mil via RT <
> met_help at ucar.edu> wrote:
>
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=85223 >
> >
> > John,
> >
> > We are frozen until you deliver the version with the Fortify error
fixes.
> > I was hoping to be running on MET entirely by now but the new
> > security rules are not allowing that.
> >
> > Bob
> >
> >
> > -----Original Message-----
> > From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> > Sent: Monday, May 21, 2018 2:39 PM
> > To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
> > <robert.craig.2 at us.af.mil>
> > Subject: Re: [Non-DoD Source] Re: [rt.rap.ucar.edu #85223] Point
> > Stat Precip Issue
> >
> > Bob,
> >
> > I was working on this last Friday. Unfortunately, I don't have a
> > good solution for you. MET is not parsing the timing information
> > for this data correctly.
> >
> > We need to update the GRIB library parsing logic to account for
this.
> >
> > setenv MET_GRIB_TABLES grib2_geps.txt met-6.1/bin/plot_data_plane
> > grib2.2018040100.0012 grib2.2018040100.0012.ps 'name="QP010";
> > level="Z0";' -v 4
> >
> > DEBUG 4: valid time: 20180401_060000
> > DEBUG 4: lead time: 060000
> > DEBUG 4: init time: 20180401_000000
> >
> > MET gets the initialization time correct, but it processes the
data
> > as a 6 hour forecast, rather than recognizing it as a 6-12 hour
> accumulation.
> > Therefore the lead time and valid times are wrong. And that leads
> > to zero matched pairs from Point-Stat. We need to patch MET to
> > correctly parse the accumulation information from this file.
> >
> > In the meantime, one band-aid would be adjusting the matching time
> > window in Point-Stat to account for the 6 hour offset:
> >
> > met-6.1/bin/point_stat grib2.2018040100.0012 nc_2018040112
> > PointStatConfig_geps_precip_updated-NEW -outdir out -v 3
> >
> > DEBUG 2: Processing QP010/Z0 versus APCP/A0, for observation type
> > ADPSFC, over region FULL, for interpolation method NEAREST(1),
using
> > 448
> pairs.
> > DEBUG 3: Number of matched pairs = 448
> > DEBUG 3: Observations processed = 449
> >
> > Since MET thinks the forecast is valid 6 hours earlier than it
> > really is, I set the matching time window to select obs 6 hours
later:
> > obs_window = {
> > beg = 6*3600 - 600;
> > end = 6*3600 + 600;
> > }
> >
> > See that attached config file.
> >
> > Matt tells me that MET is "frozen" there. Are you able to
recompile
> > with patches for met-6.1? Or stuck with what you've got?
> >
> > Thanks,
> > John
> >
> >
> >
> > On Fri, May 18, 2018 at 11:57 AM, robert.craig.2 at us.af.mil via RT
<
> > met_help at ucar.edu> wrote:
> >
> > >
> > > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=85223 >
> > >
> > > John, I attached is my GRIB 2 table.
> > >
> > > -----Original Message-----
> > > From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> > > Sent: Friday, May 18, 2018 12:04 PM
> > > To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
> > > <robert.craig.2 at us.af.mil>
> > > Subject: [Non-DoD Source] Re: [rt.rap.ucar.edu #85223] Point
Stat
> > > Precip Issue
> > >
> > > Bob,
> > >
> > > Ah never mind, I apologize. That sample NetCDF file really does
> > > contain point obs. I'll take a closer look now.
> > >
> > > Thanks,
> > > John
> > >
> > > On Fri, May 18, 2018 at 11:02 AM, John Halley Gotway
> > > <johnhg at ucar.edu>
> > > wrote:
> > >
> > > > Bob,
> > > >
> > > > Based on your description, it sounds like you're comparing
> > > > gridded model output to a gridded analysis field. Since
you're
> > > > doing grid-to-grid verification, you should be running the
Grid-Stat tool.
> > > > The Point-Stat tool is used to verify against point
observations.
> > > >
> > > > If you need me to take a closer look at the data you sent
> > > > through ARMDEC, just let me know.
> > > >
> > > > But please try running Grid-Stat to see if you have better
success.
> > > >
> > > > Thanks,
> > > > John
> > > >
> > > > On Fri, May 18, 2018 at 10:53 AM, robert.craig.2 at us.af.mil via
> > > > RT < met_help at ucar.edu> wrote:
> > > >
> > > >>
> > > >> Fri May 18 10:53:15 2018: Request 85223 was acted upon.
> > > >> Transaction: Ticket created by robert.craig.2 at us.af.mil
> > > >> Queue: met_help
> > > >> Subject: Point Stat Precip Issue
> > > >> Owner: Nobody
> > > >> Requestors: robert.craig.2 at us.af.mil
> > > >> Status: new
> > > >> Ticket <URL:
> > > >> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=85223
> > > >> >
> > > >>
> > > >>
> > > >> John, I have been following your dialog with Matt but I seem
to
> > > >> have a different issue then you worked with him.
> > > >>
> > > >> I am running MET 6.1 and verifying precip probabilities (>
.1in
> > > >> (2.54 mm)).
> > > >> I am able to read the precip grib file okay (checked it with
> > > >> plot_data_plane). The ob file is net cdf file in
millimeters,
> > > >> attached
> > > .
> > > >> The config file is also attached. When I run I get the
> > > >> following
> > error:
> > > >>
> > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > >> unrecognized
> > > >> GRIB2 field indexes - disc: 0, master table: 10, center: 57,
> > > >> local
> > > >> table: 1,
> > > >> parm_cat: 6, parm: 70
> > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > >> unrecognized
> > > >> GRIB2 field indexes - disc: 0, master table: 10, center: 57,
> > > >> local
> > > >> table: 1,
> > > >> parm_cat: 6, parm: 70
> > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > >> unrecognized
> > > >> GRIB2 field indexes - disc: 0, master table: 10, center: 57,
> > > >> local
> > > >> table: 1,
> > > >> parm_cat: 6, parm: 70
> > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > >> unrecognized
> > > >> GRIB2 field indexes - disc: 0, master table: 10, center: 57,
> > > >> local
> > > >> table: 1,
> > > >> parm_cat: 6, parm: 70
> > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > >> unrecognized
> > > >> GRIB2 field indexes - disc: 0, master table: 10, center: 57,
> > > >> local
> > > >> table: 1,
> > > >> parm_cat: 6, parm: 70
> > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > >> unrecognized
> > > >> GRIB2 field indexes - disc: 0, master table: 10, center: 57,
> > > >> local
> > > >> table: 1,
> > > >> parm_cat: 6, parm: 70
> > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > >> unrecognized
> > > >> GRIB2 field indexes - disc: 0, master table: 10, center: 57,
> > > >> local
> > > >> table: 1,
> > > >> parm_cat: 6, parm: 70
> > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > >> unrecognized
> > > >> GRIB2 field indexes - disc: 0, master table: 10, center: 57,
> > > >> local
> > > >> table: 1,
> > > >> parm_cat: 6, parm: 70
> > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > >> unrecognized
> > > >> GRIB2 field indexes - disc: 0, master table: 10, center: 57,
> > > >> local
> > > >> table: 1,
> > > >> parm_cat: 6, parm: 70
> > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > >> unrecognized
> > > >> GRIB2 field indexes - disc: 0, master table: 10, center: 57,
> > > >> local
> > > >> table: 1,
> > > >> parm_cat: 6, parm: 70
> > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > >> unrecognized
> > > >> GRIB2 field indexes - disc: 0, master table: 10, center: 57,
> > > >> local
> > > >> table: 1,
> > > >> parm_cat: 6, parm: 70
> > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > >> unrecognized
> > > >> GRIB2 field indexes - disc: 0, master table: 10, center: 57,
> > > >> local
> > > >> table: 1,
> > > >> parm_cat: 19, parm: 223
> > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > >> unrecognized
> > > >> GRIB2 field indexes - disc: 0, master table: 10, center: 57,
> > > >> local
> > > >> table: 1,
> > > >> parm_cat: 19, parm: 223
> > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > >> unrecognized
> > > >> GRIB2 field indexes - disc: 0, master table: 10, center: 57,
> > > >> local
> > > >> table: 1,
> > > >> parm_cat: 19, parm: 223
> > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > >> unrecognized
> > > >> GRIB2 field indexes - disc: 0, master table: 10, center: 57,
> > > >> local
> > > >> table: 1,
> > > >> parm_cat: 19, parm: 223
> > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > >> unrecognized
> > > >> GRIB2 field indexes - disc: 0, master table: 10, center: 57,
> > > >> local
> > > >> table: 1,
> > > >> parm_cat: 19, parm: 223
> > > >> ERROR :
> > > >> ERROR : PointStatConfInfo::process_config() -> The number of
> > > >> verification tasks in "obs.field" must be non-zero and match
> > > >> the number in "fcst.field".
> > > >> ERROR :
> > > >>
> > > >> The ob file contains a grib 1 kpds5 value of 61 which
> > > >> translates to APCP in the grib 1 table (attached).
> > > >>
> > > >> So what am I doing wrong? I sent the data files via AMRDEC
> > > >>
> > > >> Thanks
> > > >> Bob
> > > >>
> > > >>
> > > >
> > >
> > >
> > >
> > >
> >
> >
> >
> >
>
>
>
>
>
------------------------------------------------
Subject: Point Stat Precip Issue
From: John Halley Gotway
Time: Mon May 21 16:20:59 2018
Bob,
There really is no need to apply the threshold and replace the
observation
values with 0's and 1's. Instead, we use the "cat_thresh" to define
the
event category. My apologies for omitting that from the config file I
sent:
obs = {
message_type = [ "ADPSFC" ];
sid_exc = [];
field = [
{
name = "APCP";
level = "A0";
cat_thresh = [ >=2.54 ];
}
];
}
If for some reason, you really wanted the OBS column of the MPR output
lines to contain 0's and 1's, you could do so using the "censoring"
logic,
added in met-6.1:
obs = {
message_type = [ "ADPSFC" ];
sid_exc = [];
field = [
{
name = "APCP";
level = "A0";
censor_thresh = [ <2.54, >=2.54 ];
censor_val = [ 0, 1 ];
cat_thresh = [ ==1 ];
}
];
}
Notice though that I had to change the categorical threshold. After
the
input obs values are converted to 0 and 1, the event is now that the
obs is
equal to 1.
I wouldn't recommend using the censoring logic unless you have a good
reason to do so.
Thanks,
John
On Mon, May 21, 2018 at 3:45 PM, robert.craig.2 at us.af.mil via RT <
met_help at ucar.edu> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=85223 >
>
> John, I only had used the adjustment to the ob window before and ob
field
> definition, but when I used the entire config file it worked. When
I look
> in the stat file I see the ob column has precip values instead of
the 0 or
> 1 based on my threshold. What is the proper syntax to threshold
the ob
> data to 2.54 mm/.1 "?
>
> Thanks
>
> Bob
>
> -----Original Message-----
> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> Sent: Monday, May 21, 2018 4:30 PM
> To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
<robert.craig.2 at us.af.mil>
> Subject: Re: [Non-DoD Source] Re: [rt.rap.ucar.edu #85223] Point
Stat
> Precip Issue
>
> Bob,
>
> I attached a point-stat config file to my message with a "-NEW"
suffix at
> the end. That contained changes to get point-stat up and running.
>
> Did that attachment come through? If not, I could just cut-and-
paste it
> inline in an email.
>
> John
>
> On Mon, May 21, 2018 at 2:43 PM, robert.craig.2 at us.af.mil via RT <
> met_help at ucar.edu> wrote:
>
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=85223 >
> >
> > John, I tried the ob time window adjustment you provided but still
get
> the
> > same error. See below.
> >
> > DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> > GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> > table: 1,
> > parm_cat: 19, parm: 223
> > ERROR :
> > ERROR : PointStatConfInfo::process_config() -> The number of
> > verification tasks in "obs.field" must be non-zero and match the
> > number in "fcst.field".
> > ERROR :
> >
> > I noticed that you had the obs set to just APCP and A0 even though
is a
> > probability forecast. In the past I had to use the following:
> >
> > field = [
> > {cat_thresh=[>.1];
> > name="PROB";level="A006";prob={name="APCP";thresh_lo=.1;}}
> > ];
> >
> > How does MET know what to threshold the observation data by?
> >
> > Bob
> >
> > -----Original Message-----
> > From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> > Sent: Monday, May 21, 2018 3:17 PM
> > To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
> > <robert.craig.2 at us.af.mil>
> > Subject: Re: [Non-DoD Source] Re: [rt.rap.ucar.edu #85223] Point
Stat
> > Precip Issue
> >
> > OK, so does that band-aid make sense to you? Adjusting the time
> > window so that Point-Stat can find matches.
> >
> > John
> >
> > On Mon, May 21, 2018 at 2:00 PM, robert.craig.2 at us.af.mil via RT <
> > met_help at ucar.edu> wrote:
> >
> > >
> > > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=85223 >
> > >
> > > John,
> > >
> > > We are frozen until you deliver the version with the Fortify
error
> fixes.
> > > I was hoping to be running on MET entirely by now but the new
> > > security rules are not allowing that.
> > >
> > > Bob
> > >
> > >
> > > -----Original Message-----
> > > From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> > > Sent: Monday, May 21, 2018 2:39 PM
> > > To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
> > > <robert.craig.2 at us.af.mil>
> > > Subject: Re: [Non-DoD Source] Re: [rt.rap.ucar.edu #85223] Point
> > > Stat Precip Issue
> > >
> > > Bob,
> > >
> > > I was working on this last Friday. Unfortunately, I don't have
a
> > > good solution for you. MET is not parsing the timing
information
> > > for this data correctly.
> > >
> > > We need to update the GRIB library parsing logic to account for
this.
> > >
> > > setenv MET_GRIB_TABLES grib2_geps.txt met-
6.1/bin/plot_data_plane
> > > grib2.2018040100.0012 grib2.2018040100.0012.ps 'name="QP010";
> > > level="Z0";' -v 4
> > >
> > > DEBUG 4: valid time: 20180401_060000
> > > DEBUG 4: lead time: 060000
> > > DEBUG 4: init time: 20180401_000000
> > >
> > > MET gets the initialization time correct, but it processes the
data
> > > as a 6 hour forecast, rather than recognizing it as a 6-12 hour
> > accumulation.
> > > Therefore the lead time and valid times are wrong. And that
leads
> > > to zero matched pairs from Point-Stat. We need to patch MET to
> > > correctly parse the accumulation information from this file.
> > >
> > > In the meantime, one band-aid would be adjusting the matching
time
> > > window in Point-Stat to account for the 6 hour offset:
> > >
> > > met-6.1/bin/point_stat grib2.2018040100.0012 nc_2018040112
> > > PointStatConfig_geps_precip_updated-NEW -outdir out -v 3
> > >
> > > DEBUG 2: Processing QP010/Z0 versus APCP/A0, for observation
type
> > > ADPSFC, over region FULL, for interpolation method NEAREST(1),
using
> > > 448
> > pairs.
> > > DEBUG 3: Number of matched pairs = 448
> > > DEBUG 3: Observations processed = 449
> > >
> > > Since MET thinks the forecast is valid 6 hours earlier than it
> > > really is, I set the matching time window to select obs 6 hours
later:
> > > obs_window = {
> > > beg = 6*3600 - 600;
> > > end = 6*3600 + 600;
> > > }
> > >
> > > See that attached config file.
> > >
> > > Matt tells me that MET is "frozen" there. Are you able to
recompile
> > > with patches for met-6.1? Or stuck with what you've got?
> > >
> > > Thanks,
> > > John
> > >
> > >
> > >
> > > On Fri, May 18, 2018 at 11:57 AM, robert.craig.2 at us.af.mil via
RT <
> > > met_help at ucar.edu> wrote:
> > >
> > > >
> > > > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=85223
>
> > > >
> > > > John, I attached is my GRIB 2 table.
> > > >
> > > > -----Original Message-----
> > > > From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> > > > Sent: Friday, May 18, 2018 12:04 PM
> > > > To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
> > > > <robert.craig.2 at us.af.mil>
> > > > Subject: [Non-DoD Source] Re: [rt.rap.ucar.edu #85223] Point
Stat
> > > > Precip Issue
> > > >
> > > > Bob,
> > > >
> > > > Ah never mind, I apologize. That sample NetCDF file really
does
> > > > contain point obs. I'll take a closer look now.
> > > >
> > > > Thanks,
> > > > John
> > > >
> > > > On Fri, May 18, 2018 at 11:02 AM, John Halley Gotway
> > > > <johnhg at ucar.edu>
> > > > wrote:
> > > >
> > > > > Bob,
> > > > >
> > > > > Based on your description, it sounds like you're comparing
> > > > > gridded model output to a gridded analysis field. Since
you're
> > > > > doing grid-to-grid verification, you should be running the
> Grid-Stat tool.
> > > > > The Point-Stat tool is used to verify against point
observations.
> > > > >
> > > > > If you need me to take a closer look at the data you sent
> > > > > through ARMDEC, just let me know.
> > > > >
> > > > > But please try running Grid-Stat to see if you have better
success.
> > > > >
> > > > > Thanks,
> > > > > John
> > > > >
> > > > > On Fri, May 18, 2018 at 10:53 AM, robert.craig.2 at us.af.mil
via
> > > > > RT < met_help at ucar.edu> wrote:
> > > > >
> > > > >>
> > > > >> Fri May 18 10:53:15 2018: Request 85223 was acted upon.
> > > > >> Transaction: Ticket created by robert.craig.2 at us.af.mil
> > > > >> Queue: met_help
> > > > >> Subject: Point Stat Precip Issue
> > > > >> Owner: Nobody
> > > > >> Requestors: robert.craig.2 at us.af.mil
> > > > >> Status: new
> > > > >> Ticket <URL:
> > > > >> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=85223
> > > > >> >
> > > > >>
> > > > >>
> > > > >> John, I have been following your dialog with Matt but I
seem to
> > > > >> have a different issue then you worked with him.
> > > > >>
> > > > >> I am running MET 6.1 and verifying precip probabilities (>
.1in
> > > > >> (2.54 mm)).
> > > > >> I am able to read the precip grib file okay (checked it
with
> > > > >> plot_data_plane). The ob file is net cdf file in
millimeters,
> > > > >> attached
> > > > .
> > > > >> The config file is also attached. When I run I get the
> > > > >> following
> > > error:
> > > > >>
> > > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > > >> unrecognized
> > > > >> GRIB2 field indexes - disc: 0, master table: 10, center:
57,
> > > > >> local
> > > > >> table: 1,
> > > > >> parm_cat: 6, parm: 70
> > > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > > >> unrecognized
> > > > >> GRIB2 field indexes - disc: 0, master table: 10, center:
57,
> > > > >> local
> > > > >> table: 1,
> > > > >> parm_cat: 6, parm: 70
> > > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > > >> unrecognized
> > > > >> GRIB2 field indexes - disc: 0, master table: 10, center:
57,
> > > > >> local
> > > > >> table: 1,
> > > > >> parm_cat: 6, parm: 70
> > > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > > >> unrecognized
> > > > >> GRIB2 field indexes - disc: 0, master table: 10, center:
57,
> > > > >> local
> > > > >> table: 1,
> > > > >> parm_cat: 6, parm: 70
> > > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > > >> unrecognized
> > > > >> GRIB2 field indexes - disc: 0, master table: 10, center:
57,
> > > > >> local
> > > > >> table: 1,
> > > > >> parm_cat: 6, parm: 70
> > > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > > >> unrecognized
> > > > >> GRIB2 field indexes - disc: 0, master table: 10, center:
57,
> > > > >> local
> > > > >> table: 1,
> > > > >> parm_cat: 6, parm: 70
> > > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > > >> unrecognized
> > > > >> GRIB2 field indexes - disc: 0, master table: 10, center:
57,
> > > > >> local
> > > > >> table: 1,
> > > > >> parm_cat: 6, parm: 70
> > > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > > >> unrecognized
> > > > >> GRIB2 field indexes - disc: 0, master table: 10, center:
57,
> > > > >> local
> > > > >> table: 1,
> > > > >> parm_cat: 6, parm: 70
> > > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > > >> unrecognized
> > > > >> GRIB2 field indexes - disc: 0, master table: 10, center:
57,
> > > > >> local
> > > > >> table: 1,
> > > > >> parm_cat: 6, parm: 70
> > > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > > >> unrecognized
> > > > >> GRIB2 field indexes - disc: 0, master table: 10, center:
57,
> > > > >> local
> > > > >> table: 1,
> > > > >> parm_cat: 6, parm: 70
> > > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > > >> unrecognized
> > > > >> GRIB2 field indexes - disc: 0, master table: 10, center:
57,
> > > > >> local
> > > > >> table: 1,
> > > > >> parm_cat: 6, parm: 70
> > > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > > >> unrecognized
> > > > >> GRIB2 field indexes - disc: 0, master table: 10, center:
57,
> > > > >> local
> > > > >> table: 1,
> > > > >> parm_cat: 19, parm: 223
> > > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > > >> unrecognized
> > > > >> GRIB2 field indexes - disc: 0, master table: 10, center:
57,
> > > > >> local
> > > > >> table: 1,
> > > > >> parm_cat: 19, parm: 223
> > > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > > >> unrecognized
> > > > >> GRIB2 field indexes - disc: 0, master table: 10, center:
57,
> > > > >> local
> > > > >> table: 1,
> > > > >> parm_cat: 19, parm: 223
> > > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > > >> unrecognized
> > > > >> GRIB2 field indexes - disc: 0, master table: 10, center:
57,
> > > > >> local
> > > > >> table: 1,
> > > > >> parm_cat: 19, parm: 223
> > > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > > >> unrecognized
> > > > >> GRIB2 field indexes - disc: 0, master table: 10, center:
57,
> > > > >> local
> > > > >> table: 1,
> > > > >> parm_cat: 19, parm: 223
> > > > >> ERROR :
> > > > >> ERROR : PointStatConfInfo::process_config() -> The number
of
> > > > >> verification tasks in "obs.field" must be non-zero and
match
> > > > >> the number in "fcst.field".
> > > > >> ERROR :
> > > > >>
> > > > >> The ob file contains a grib 1 kpds5 value of 61 which
> > > > >> translates to APCP in the grib 1 table (attached).
> > > > >>
> > > > >> So what am I doing wrong? I sent the data files via AMRDEC
> > > > >>
> > > > >> Thanks
> > > > >> Bob
> > > > >>
> > > > >>
> > > > >
> > > >
> > > >
> > > >
> > > >
> > >
> > >
> > >
> > >
> >
> >
> >
> >
> >
>
>
>
>
>
------------------------------------------------
Subject: RE: [Non-DoD Source] Re: [rt.rap.ucar.edu #85223] Point Stat Precip Issue
From: robert.craig.2 at us.af.mil
Time: Tue May 22 09:26:40 2018
John, Unless I am miss something, since my goal is to calculate Brier
Skill Score, I would need to have 1 or 0 in the observation field to
go with the probability forecast data. Using the censoring logic
worked to generate this. If my MPR file contained a probability for
the forecast, and an precipitation amount for the observation, is stat
analysis smart enough to convert the precipitation amount to 1 or 0
based on a threshold to calculate a Brier Score and Brier Skill Score?
Thanks
Bob
-----Original Message-----
From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
Sent: Monday, May 21, 2018 5:21 PM
To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
<robert.craig.2 at us.af.mil>
Subject: Re: [Non-DoD Source] Re: [rt.rap.ucar.edu #85223] Point Stat
Precip Issue
Bob,
There really is no need to apply the threshold and replace the
observation values with 0's and 1's. Instead, we use the "cat_thresh"
to define the event category. My apologies for omitting that from the
config file I sent:
obs = {
message_type = [ "ADPSFC" ];
sid_exc = [];
field = [
{
name = "APCP";
level = "A0";
cat_thresh = [ >=2.54 ];
}
];
}
If for some reason, you really wanted the OBS column of the MPR output
lines to contain 0's and 1's, you could do so using the "censoring"
logic, added in met-6.1:
obs = {
message_type = [ "ADPSFC" ];
sid_exc = [];
field = [
{
name = "APCP";
level = "A0";
censor_thresh = [ <2.54, >=2.54 ];
censor_val = [ 0, 1 ];
cat_thresh = [ ==1 ];
}
];
}
Notice though that I had to change the categorical threshold. After
the input obs values are converted to 0 and 1, the event is now that
the obs is equal to 1.
I wouldn't recommend using the censoring logic unless you have a good
reason to do so.
Thanks,
John
On Mon, May 21, 2018 at 3:45 PM, robert.craig.2 at us.af.mil via RT <
met_help at ucar.edu> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=85223 >
>
> John, I only had used the adjustment to the ob window before and ob
field
> definition, but when I used the entire config file it worked. When
I look
> in the stat file I see the ob column has precip values instead of
the 0 or
> 1 based on my threshold. What is the proper syntax to threshold
the ob
> data to 2.54 mm/.1 "?
>
> Thanks
>
> Bob
>
> -----Original Message-----
> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> Sent: Monday, May 21, 2018 4:30 PM
> To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
> <robert.craig.2 at us.af.mil>
> Subject: Re: [Non-DoD Source] Re: [rt.rap.ucar.edu #85223] Point
Stat
> Precip Issue
>
> Bob,
>
> I attached a point-stat config file to my message with a "-NEW"
suffix
> at the end. That contained changes to get point-stat up and
running.
>
> Did that attachment come through? If not, I could just cut-and-
paste
> it inline in an email.
>
> John
>
> On Mon, May 21, 2018 at 2:43 PM, robert.craig.2 at us.af.mil via RT <
> met_help at ucar.edu> wrote:
>
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=85223 >
> >
> > John, I tried the ob time window adjustment you provided but still
> > get
> the
> > same error. See below.
> >
> > DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> > GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> > table: 1,
> > parm_cat: 19, parm: 223
> > ERROR :
> > ERROR : PointStatConfInfo::process_config() -> The number of
> > verification tasks in "obs.field" must be non-zero and match the
> > number in "fcst.field".
> > ERROR :
> >
> > I noticed that you had the obs set to just APCP and A0 even though
is a
> > probability forecast. In the past I had to use the following:
> >
> > field = [
> > {cat_thresh=[>.1];
> > name="PROB";level="A006";prob={name="APCP";thresh_lo=.1;}}
> > ];
> >
> > How does MET know what to threshold the observation data by?
> >
> > Bob
> >
> > -----Original Message-----
> > From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> > Sent: Monday, May 21, 2018 3:17 PM
> > To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
> > <robert.craig.2 at us.af.mil>
> > Subject: Re: [Non-DoD Source] Re: [rt.rap.ucar.edu #85223] Point
> > Stat Precip Issue
> >
> > OK, so does that band-aid make sense to you? Adjusting the time
> > window so that Point-Stat can find matches.
> >
> > John
> >
> > On Mon, May 21, 2018 at 2:00 PM, robert.craig.2 at us.af.mil via RT <
> > met_help at ucar.edu> wrote:
> >
> > >
> > > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=85223 >
> > >
> > > John,
> > >
> > > We are frozen until you deliver the version with the Fortify
error
> fixes.
> > > I was hoping to be running on MET entirely by now but the new
> > > security rules are not allowing that.
> > >
> > > Bob
> > >
> > >
> > > -----Original Message-----
> > > From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> > > Sent: Monday, May 21, 2018 2:39 PM
> > > To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
> > > <robert.craig.2 at us.af.mil>
> > > Subject: Re: [Non-DoD Source] Re: [rt.rap.ucar.edu #85223] Point
> > > Stat Precip Issue
> > >
> > > Bob,
> > >
> > > I was working on this last Friday. Unfortunately, I don't have
a
> > > good solution for you. MET is not parsing the timing
information
> > > for this data correctly.
> > >
> > > We need to update the GRIB library parsing logic to account for
this.
> > >
> > > setenv MET_GRIB_TABLES grib2_geps.txt met-
6.1/bin/plot_data_plane
> > > grib2.2018040100.0012 grib2.2018040100.0012.ps 'name="QP010";
> > > level="Z0";' -v 4
> > >
> > > DEBUG 4: valid time: 20180401_060000
> > > DEBUG 4: lead time: 060000
> > > DEBUG 4: init time: 20180401_000000
> > >
> > > MET gets the initialization time correct, but it processes the
> > > data as a 6 hour forecast, rather than recognizing it as a 6-12
> > > hour
> > accumulation.
> > > Therefore the lead time and valid times are wrong. And that
leads
> > > to zero matched pairs from Point-Stat. We need to patch MET to
> > > correctly parse the accumulation information from this file.
> > >
> > > In the meantime, one band-aid would be adjusting the matching
time
> > > window in Point-Stat to account for the 6 hour offset:
> > >
> > > met-6.1/bin/point_stat grib2.2018040100.0012 nc_2018040112
> > > PointStatConfig_geps_precip_updated-NEW -outdir out -v 3
> > >
> > > DEBUG 2: Processing QP010/Z0 versus APCP/A0, for observation
type
> > > ADPSFC, over region FULL, for interpolation method NEAREST(1),
> > > using
> > > 448
> > pairs.
> > > DEBUG 3: Number of matched pairs = 448
> > > DEBUG 3: Observations processed = 449
> > >
> > > Since MET thinks the forecast is valid 6 hours earlier than it
> > > really is, I set the matching time window to select obs 6 hours
later:
> > > obs_window = {
> > > beg = 6*3600 - 600;
> > > end = 6*3600 + 600;
> > > }
> > >
> > > See that attached config file.
> > >
> > > Matt tells me that MET is "frozen" there. Are you able to
> > > recompile with patches for met-6.1? Or stuck with what you've
got?
> > >
> > > Thanks,
> > > John
> > >
> > >
> > >
> > > On Fri, May 18, 2018 at 11:57 AM, robert.craig.2 at us.af.mil via
RT
> > > < met_help at ucar.edu> wrote:
> > >
> > > >
> > > > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=85223
>
> > > >
> > > > John, I attached is my GRIB 2 table.
> > > >
> > > > -----Original Message-----
> > > > From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> > > > Sent: Friday, May 18, 2018 12:04 PM
> > > > To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
> > > > <robert.craig.2 at us.af.mil>
> > > > Subject: [Non-DoD Source] Re: [rt.rap.ucar.edu #85223] Point
> > > > Stat Precip Issue
> > > >
> > > > Bob,
> > > >
> > > > Ah never mind, I apologize. That sample NetCDF file really
does
> > > > contain point obs. I'll take a closer look now.
> > > >
> > > > Thanks,
> > > > John
> > > >
> > > > On Fri, May 18, 2018 at 11:02 AM, John Halley Gotway
> > > > <johnhg at ucar.edu>
> > > > wrote:
> > > >
> > > > > Bob,
> > > > >
> > > > > Based on your description, it sounds like you're comparing
> > > > > gridded model output to a gridded analysis field. Since
> > > > > you're doing grid-to-grid verification, you should be
running
> > > > > the
> Grid-Stat tool.
> > > > > The Point-Stat tool is used to verify against point
observations.
> > > > >
> > > > > If you need me to take a closer look at the data you sent
> > > > > through ARMDEC, just let me know.
> > > > >
> > > > > But please try running Grid-Stat to see if you have better
success.
> > > > >
> > > > > Thanks,
> > > > > John
> > > > >
> > > > > On Fri, May 18, 2018 at 10:53 AM, robert.craig.2 at us.af.mil
via
> > > > > RT < met_help at ucar.edu> wrote:
> > > > >
> > > > >>
> > > > >> Fri May 18 10:53:15 2018: Request 85223 was acted upon.
> > > > >> Transaction: Ticket created by robert.craig.2 at us.af.mil
> > > > >> Queue: met_help
> > > > >> Subject: Point Stat Precip Issue
> > > > >> Owner: Nobody
> > > > >> Requestors: robert.craig.2 at us.af.mil
> > > > >> Status: new
> > > > >> Ticket <URL:
> > > > >> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=85223
> > > > >> >
> > > > >>
> > > > >>
> > > > >> John, I have been following your dialog with Matt but I
seem
> > > > >> to have a different issue then you worked with him.
> > > > >>
> > > > >> I am running MET 6.1 and verifying precip probabilities (>
> > > > >> .1in
> > > > >> (2.54 mm)).
> > > > >> I am able to read the precip grib file okay (checked it
with
> > > > >> plot_data_plane). The ob file is net cdf file in
> > > > >> millimeters, attached
> > > > .
> > > > >> The config file is also attached. When I run I get the
> > > > >> following
> > > error:
> > > > >>
> > > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > > >> unrecognized
> > > > >> GRIB2 field indexes - disc: 0, master table: 10, center:
57,
> > > > >> local
> > > > >> table: 1,
> > > > >> parm_cat: 6, parm: 70
> > > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > > >> unrecognized
> > > > >> GRIB2 field indexes - disc: 0, master table: 10, center:
57,
> > > > >> local
> > > > >> table: 1,
> > > > >> parm_cat: 6, parm: 70
> > > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > > >> unrecognized
> > > > >> GRIB2 field indexes - disc: 0, master table: 10, center:
57,
> > > > >> local
> > > > >> table: 1,
> > > > >> parm_cat: 6, parm: 70
> > > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > > >> unrecognized
> > > > >> GRIB2 field indexes - disc: 0, master table: 10, center:
57,
> > > > >> local
> > > > >> table: 1,
> > > > >> parm_cat: 6, parm: 70
> > > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > > >> unrecognized
> > > > >> GRIB2 field indexes - disc: 0, master table: 10, center:
57,
> > > > >> local
> > > > >> table: 1,
> > > > >> parm_cat: 6, parm: 70
> > > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > > >> unrecognized
> > > > >> GRIB2 field indexes - disc: 0, master table: 10, center:
57,
> > > > >> local
> > > > >> table: 1,
> > > > >> parm_cat: 6, parm: 70
> > > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > > >> unrecognized
> > > > >> GRIB2 field indexes - disc: 0, master table: 10, center:
57,
> > > > >> local
> > > > >> table: 1,
> > > > >> parm_cat: 6, parm: 70
> > > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > > >> unrecognized
> > > > >> GRIB2 field indexes - disc: 0, master table: 10, center:
57,
> > > > >> local
> > > > >> table: 1,
> > > > >> parm_cat: 6, parm: 70
> > > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > > >> unrecognized
> > > > >> GRIB2 field indexes - disc: 0, master table: 10, center:
57,
> > > > >> local
> > > > >> table: 1,
> > > > >> parm_cat: 6, parm: 70
> > > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > > >> unrecognized
> > > > >> GRIB2 field indexes - disc: 0, master table: 10, center:
57,
> > > > >> local
> > > > >> table: 1,
> > > > >> parm_cat: 6, parm: 70
> > > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > > >> unrecognized
> > > > >> GRIB2 field indexes - disc: 0, master table: 10, center:
57,
> > > > >> local
> > > > >> table: 1,
> > > > >> parm_cat: 6, parm: 70
> > > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > > >> unrecognized
> > > > >> GRIB2 field indexes - disc: 0, master table: 10, center:
57,
> > > > >> local
> > > > >> table: 1,
> > > > >> parm_cat: 19, parm: 223
> > > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > > >> unrecognized
> > > > >> GRIB2 field indexes - disc: 0, master table: 10, center:
57,
> > > > >> local
> > > > >> table: 1,
> > > > >> parm_cat: 19, parm: 223
> > > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > > >> unrecognized
> > > > >> GRIB2 field indexes - disc: 0, master table: 10, center:
57,
> > > > >> local
> > > > >> table: 1,
> > > > >> parm_cat: 19, parm: 223
> > > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > > >> unrecognized
> > > > >> GRIB2 field indexes - disc: 0, master table: 10, center:
57,
> > > > >> local
> > > > >> table: 1,
> > > > >> parm_cat: 19, parm: 223
> > > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > > >> unrecognized
> > > > >> GRIB2 field indexes - disc: 0, master table: 10, center:
57,
> > > > >> local
> > > > >> table: 1,
> > > > >> parm_cat: 19, parm: 223
> > > > >> ERROR :
> > > > >> ERROR : PointStatConfInfo::process_config() -> The number
of
> > > > >> verification tasks in "obs.field" must be non-zero and
match
> > > > >> the number in "fcst.field".
> > > > >> ERROR :
> > > > >>
> > > > >> The ob file contains a grib 1 kpds5 value of 61 which
> > > > >> translates to APCP in the grib 1 table (attached).
> > > > >>
> > > > >> So what am I doing wrong? I sent the data files via AMRDEC
> > > > >>
> > > > >> Thanks
> > > > >> Bob
> > > > >>
> > > > >>
> > > > >
> > > >
> > > >
> > > >
> > > >
> > >
> > >
> > >
> > >
> >
> >
> >
> >
> >
>
>
>
>
>
------------------------------------------------
Subject: Point Stat Precip Issue
From: John Halley Gotway
Time: Tue May 22 14:46:15 2018
Bob,
You do not need to have a 1 or 0 in the observation field. Instead,
you
use the categorical threshold (cat_thresh) to define the "event". Any
observation values meeting that threshold are counted as "events"...
which
is like it being a value of 1. And observation values not meeting
that
threshold are counted as "non-events"... which is like being a value
of 0.
To clarify, when evaluating probabilities in MET you...
(1) Select a forecast probability field of data (i.e. prob = TRUE;)
(2) Select forecast categorical thresholds which span the values of 0
to 1
to define probability bins. For example, cat_thresh = [ >=0, >=0.25,
>=0.50, >=0.75, >=1.0 ]; or instead, use the shorthand notation for
this:
cat_thresh = [ ==0.25 ];
(3) Select observation data is *not* a probability field.
(4) Select a single observation threshold which specifies the *event*
corresponding to the probability.
For example, let's say you have a probability of freezing surface
temperatures named "prob_freez", you'd configure it like this:
fcst = {
field = [
{ name="prob_freeze";
level="Z0";
prob=TRUE;
cat_thresh = [ ==0.10 ];
}
];
}
obs = {
field = [
{ name="TMP";
level="Z0";
cat_thresh = [ <=273 ];
}
];
}
I don't *convert* the observations of temperature to 0/1 values.
Instead,
I just define the event for probability of freezing... namely, the
temperature being less than or equal to 273 Kelvin.
Hopefully that helps clarify.
Thanks,
John
On Tue, May 22, 2018 at 9:26 AM, robert.craig.2 at us.af.mil via RT <
met_help at ucar.edu> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=85223 >
>
> John, Unless I am miss something, since my goal is to calculate
Brier
> Skill Score, I would need to have 1 or 0 in the observation field
to go
> with the probability forecast data. Using the censoring logic
worked to
> generate this. If my MPR file contained a probability for the
forecast,
> and an precipitation amount for the observation, is stat analysis
smart
> enough to convert the precipitation amount to 1 or 0 based on a
threshold
> to calculate a Brier Score and Brier Skill Score?
>
> Thanks
> Bob
>
> -----Original Message-----
> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> Sent: Monday, May 21, 2018 5:21 PM
> To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
<robert.craig.2 at us.af.mil>
> Subject: Re: [Non-DoD Source] Re: [rt.rap.ucar.edu #85223] Point
Stat
> Precip Issue
>
> Bob,
>
> There really is no need to apply the threshold and replace the
observation
> values with 0's and 1's. Instead, we use the "cat_thresh" to define
the
> event category. My apologies for omitting that from the config file
I sent:
>
> obs = {
> message_type = [ "ADPSFC" ];
> sid_exc = [];
> field = [
> {
> name = "APCP";
> level = "A0";
> cat_thresh = [ >=2.54 ];
> }
> ];
> }
>
> If for some reason, you really wanted the OBS column of the MPR
output
> lines to contain 0's and 1's, you could do so using the "censoring"
logic,
> added in met-6.1:
>
> obs = {
> message_type = [ "ADPSFC" ];
> sid_exc = [];
> field = [
> {
> name = "APCP";
> level = "A0";
> censor_thresh = [ <2.54, >=2.54 ];
> censor_val = [ 0, 1 ];
> cat_thresh = [ ==1 ];
> }
> ];
> }
>
> Notice though that I had to change the categorical threshold. After
the
> input obs values are converted to 0 and 1, the event is now that the
obs is
> equal to 1.
>
> I wouldn't recommend using the censoring logic unless you have a
good
> reason to do so.
>
> Thanks,
> John
>
> On Mon, May 21, 2018 at 3:45 PM, robert.craig.2 at us.af.mil via RT <
> met_help at ucar.edu> wrote:
>
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=85223 >
> >
> > John, I only had used the adjustment to the ob window before and
ob field
> > definition, but when I used the entire config file it worked.
When I
> look
> > in the stat file I see the ob column has precip values instead of
the 0
> or
> > 1 based on my threshold. What is the proper syntax to threshold
the ob
> > data to 2.54 mm/.1 "?
> >
> > Thanks
> >
> > Bob
> >
> > -----Original Message-----
> > From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> > Sent: Monday, May 21, 2018 4:30 PM
> > To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
> > <robert.craig.2 at us.af.mil>
> > Subject: Re: [Non-DoD Source] Re: [rt.rap.ucar.edu #85223] Point
Stat
> > Precip Issue
> >
> > Bob,
> >
> > I attached a point-stat config file to my message with a "-NEW"
suffix
> > at the end. That contained changes to get point-stat up and
running.
> >
> > Did that attachment come through? If not, I could just cut-and-
paste
> > it inline in an email.
> >
> > John
> >
> > On Mon, May 21, 2018 at 2:43 PM, robert.craig.2 at us.af.mil via RT <
> > met_help at ucar.edu> wrote:
> >
> > >
> > > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=85223 >
> > >
> > > John, I tried the ob time window adjustment you provided but
still
> > > get
> > the
> > > same error. See below.
> > >
> > > DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> > > GRIB2 field indexes - disc: 0, master table: 10, center: 57,
local
> > > table: 1,
> > > parm_cat: 19, parm: 223
> > > ERROR :
> > > ERROR : PointStatConfInfo::process_config() -> The number of
> > > verification tasks in "obs.field" must be non-zero and match the
> > > number in "fcst.field".
> > > ERROR :
> > >
> > > I noticed that you had the obs set to just APCP and A0 even
though is a
> > > probability forecast. In the past I had to use the following:
> > >
> > > field = [
> > > {cat_thresh=[>.1];
> > > name="PROB";level="A006";prob={name="APCP";thresh_lo=.1;}}
> > > ];
> > >
> > > How does MET know what to threshold the observation data by?
> > >
> > > Bob
> > >
> > > -----Original Message-----
> > > From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> > > Sent: Monday, May 21, 2018 3:17 PM
> > > To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
> > > <robert.craig.2 at us.af.mil>
> > > Subject: Re: [Non-DoD Source] Re: [rt.rap.ucar.edu #85223] Point
> > > Stat Precip Issue
> > >
> > > OK, so does that band-aid make sense to you? Adjusting the time
> > > window so that Point-Stat can find matches.
> > >
> > > John
> > >
> > > On Mon, May 21, 2018 at 2:00 PM, robert.craig.2 at us.af.mil via RT
<
> > > met_help at ucar.edu> wrote:
> > >
> > > >
> > > > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=85223
>
> > > >
> > > > John,
> > > >
> > > > We are frozen until you deliver the version with the Fortify
error
> > fixes.
> > > > I was hoping to be running on MET entirely by now but the new
> > > > security rules are not allowing that.
> > > >
> > > > Bob
> > > >
> > > >
> > > > -----Original Message-----
> > > > From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> > > > Sent: Monday, May 21, 2018 2:39 PM
> > > > To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
> > > > <robert.craig.2 at us.af.mil>
> > > > Subject: Re: [Non-DoD Source] Re: [rt.rap.ucar.edu #85223]
Point
> > > > Stat Precip Issue
> > > >
> > > > Bob,
> > > >
> > > > I was working on this last Friday. Unfortunately, I don't
have a
> > > > good solution for you. MET is not parsing the timing
information
> > > > for this data correctly.
> > > >
> > > > We need to update the GRIB library parsing logic to account
for this.
> > > >
> > > > setenv MET_GRIB_TABLES grib2_geps.txt met-
6.1/bin/plot_data_plane
> > > > grib2.2018040100.0012 grib2.2018040100.0012.ps 'name="QP010";
> > > > level="Z0";' -v 4
> > > >
> > > > DEBUG 4: valid time: 20180401_060000
> > > > DEBUG 4: lead time: 060000
> > > > DEBUG 4: init time: 20180401_000000
> > > >
> > > > MET gets the initialization time correct, but it processes the
> > > > data as a 6 hour forecast, rather than recognizing it as a 6-
12
> > > > hour
> > > accumulation.
> > > > Therefore the lead time and valid times are wrong. And that
leads
> > > > to zero matched pairs from Point-Stat. We need to patch MET
to
> > > > correctly parse the accumulation information from this file.
> > > >
> > > > In the meantime, one band-aid would be adjusting the matching
time
> > > > window in Point-Stat to account for the 6 hour offset:
> > > >
> > > > met-6.1/bin/point_stat grib2.2018040100.0012 nc_2018040112
> > > > PointStatConfig_geps_precip_updated-NEW -outdir out -v 3
> > > >
> > > > DEBUG 2: Processing QP010/Z0 versus APCP/A0, for observation
type
> > > > ADPSFC, over region FULL, for interpolation method NEAREST(1),
> > > > using
> > > > 448
> > > pairs.
> > > > DEBUG 3: Number of matched pairs = 448
> > > > DEBUG 3: Observations processed = 449
> > > >
> > > > Since MET thinks the forecast is valid 6 hours earlier than it
> > > > really is, I set the matching time window to select obs 6
hours
> later:
> > > > obs_window = {
> > > > beg = 6*3600 - 600;
> > > > end = 6*3600 + 600;
> > > > }
> > > >
> > > > See that attached config file.
> > > >
> > > > Matt tells me that MET is "frozen" there. Are you able to
> > > > recompile with patches for met-6.1? Or stuck with what you've
got?
> > > >
> > > > Thanks,
> > > > John
> > > >
> > > >
> > > >
> > > > On Fri, May 18, 2018 at 11:57 AM, robert.craig.2 at us.af.mil via
RT
> > > > < met_help at ucar.edu> wrote:
> > > >
> > > > >
> > > > > <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=85223 >
> > > > >
> > > > > John, I attached is my GRIB 2 table.
> > > > >
> > > > > -----Original Message-----
> > > > > From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> > > > > Sent: Friday, May 18, 2018 12:04 PM
> > > > > To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
> > > > > <robert.craig.2 at us.af.mil>
> > > > > Subject: [Non-DoD Source] Re: [rt.rap.ucar.edu #85223] Point
> > > > > Stat Precip Issue
> > > > >
> > > > > Bob,
> > > > >
> > > > > Ah never mind, I apologize. That sample NetCDF file really
does
> > > > > contain point obs. I'll take a closer look now.
> > > > >
> > > > > Thanks,
> > > > > John
> > > > >
> > > > > On Fri, May 18, 2018 at 11:02 AM, John Halley Gotway
> > > > > <johnhg at ucar.edu>
> > > > > wrote:
> > > > >
> > > > > > Bob,
> > > > > >
> > > > > > Based on your description, it sounds like you're comparing
> > > > > > gridded model output to a gridded analysis field. Since
> > > > > > you're doing grid-to-grid verification, you should be
running
> > > > > > the
> > Grid-Stat tool.
> > > > > > The Point-Stat tool is used to verify against point
observations.
> > > > > >
> > > > > > If you need me to take a closer look at the data you sent
> > > > > > through ARMDEC, just let me know.
> > > > > >
> > > > > > But please try running Grid-Stat to see if you have better
> success.
> > > > > >
> > > > > > Thanks,
> > > > > > John
> > > > > >
> > > > > > On Fri, May 18, 2018 at 10:53 AM, robert.craig.2 at us.af.mil
via
> > > > > > RT < met_help at ucar.edu> wrote:
> > > > > >
> > > > > >>
> > > > > >> Fri May 18 10:53:15 2018: Request 85223 was acted upon.
> > > > > >> Transaction: Ticket created by robert.craig.2 at us.af.mil
> > > > > >> Queue: met_help
> > > > > >> Subject: Point Stat Precip Issue
> > > > > >> Owner: Nobody
> > > > > >> Requestors: robert.craig.2 at us.af.mil
> > > > > >> Status: new
> > > > > >> Ticket <URL:
> > > > > >> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=85223
> > > > > >> >
> > > > > >>
> > > > > >>
> > > > > >> John, I have been following your dialog with Matt but I
seem
> > > > > >> to have a different issue then you worked with him.
> > > > > >>
> > > > > >> I am running MET 6.1 and verifying precip probabilities
(>
> > > > > >> .1in
> > > > > >> (2.54 mm)).
> > > > > >> I am able to read the precip grib file okay (checked it
with
> > > > > >> plot_data_plane). The ob file is net cdf file in
> > > > > >> millimeters, attached
> > > > > .
> > > > > >> The config file is also attached. When I run I get the
> > > > > >> following
> > > > error:
> > > > > >>
> > > > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > > > >> unrecognized
> > > > > >> GRIB2 field indexes - disc: 0, master table: 10, center:
57,
> > > > > >> local
> > > > > >> table: 1,
> > > > > >> parm_cat: 6, parm: 70
> > > > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > > > >> unrecognized
> > > > > >> GRIB2 field indexes - disc: 0, master table: 10, center:
57,
> > > > > >> local
> > > > > >> table: 1,
> > > > > >> parm_cat: 6, parm: 70
> > > > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > > > >> unrecognized
> > > > > >> GRIB2 field indexes - disc: 0, master table: 10, center:
57,
> > > > > >> local
> > > > > >> table: 1,
> > > > > >> parm_cat: 6, parm: 70
> > > > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > > > >> unrecognized
> > > > > >> GRIB2 field indexes - disc: 0, master table: 10, center:
57,
> > > > > >> local
> > > > > >> table: 1,
> > > > > >> parm_cat: 6, parm: 70
> > > > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > > > >> unrecognized
> > > > > >> GRIB2 field indexes - disc: 0, master table: 10, center:
57,
> > > > > >> local
> > > > > >> table: 1,
> > > > > >> parm_cat: 6, parm: 70
> > > > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > > > >> unrecognized
> > > > > >> GRIB2 field indexes - disc: 0, master table: 10, center:
57,
> > > > > >> local
> > > > > >> table: 1,
> > > > > >> parm_cat: 6, parm: 70
> > > > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > > > >> unrecognized
> > > > > >> GRIB2 field indexes - disc: 0, master table: 10, center:
57,
> > > > > >> local
> > > > > >> table: 1,
> > > > > >> parm_cat: 6, parm: 70
> > > > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > > > >> unrecognized
> > > > > >> GRIB2 field indexes - disc: 0, master table: 10, center:
57,
> > > > > >> local
> > > > > >> table: 1,
> > > > > >> parm_cat: 6, parm: 70
> > > > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > > > >> unrecognized
> > > > > >> GRIB2 field indexes - disc: 0, master table: 10, center:
57,
> > > > > >> local
> > > > > >> table: 1,
> > > > > >> parm_cat: 6, parm: 70
> > > > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > > > >> unrecognized
> > > > > >> GRIB2 field indexes - disc: 0, master table: 10, center:
57,
> > > > > >> local
> > > > > >> table: 1,
> > > > > >> parm_cat: 6, parm: 70
> > > > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > > > >> unrecognized
> > > > > >> GRIB2 field indexes - disc: 0, master table: 10, center:
57,
> > > > > >> local
> > > > > >> table: 1,
> > > > > >> parm_cat: 6, parm: 70
> > > > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > > > >> unrecognized
> > > > > >> GRIB2 field indexes - disc: 0, master table: 10, center:
57,
> > > > > >> local
> > > > > >> table: 1,
> > > > > >> parm_cat: 19, parm: 223
> > > > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > > > >> unrecognized
> > > > > >> GRIB2 field indexes - disc: 0, master table: 10, center:
57,
> > > > > >> local
> > > > > >> table: 1,
> > > > > >> parm_cat: 19, parm: 223
> > > > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > > > >> unrecognized
> > > > > >> GRIB2 field indexes - disc: 0, master table: 10, center:
57,
> > > > > >> local
> > > > > >> table: 1,
> > > > > >> parm_cat: 19, parm: 223
> > > > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > > > >> unrecognized
> > > > > >> GRIB2 field indexes - disc: 0, master table: 10, center:
57,
> > > > > >> local
> > > > > >> table: 1,
> > > > > >> parm_cat: 19, parm: 223
> > > > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > > > >> unrecognized
> > > > > >> GRIB2 field indexes - disc: 0, master table: 10, center:
57,
> > > > > >> local
> > > > > >> table: 1,
> > > > > >> parm_cat: 19, parm: 223
> > > > > >> ERROR :
> > > > > >> ERROR : PointStatConfInfo::process_config() -> The
number of
> > > > > >> verification tasks in "obs.field" must be non-zero and
match
> > > > > >> the number in "fcst.field".
> > > > > >> ERROR :
> > > > > >>
> > > > > >> The ob file contains a grib 1 kpds5 value of 61 which
> > > > > >> translates to APCP in the grib 1 table (attached).
> > > > > >>
> > > > > >> So what am I doing wrong? I sent the data files via
AMRDEC
> > > > > >>
> > > > > >> Thanks
> > > > > >> Bob
> > > > > >>
> > > > > >>
> > > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > >
> > > >
> > > >
> > > >
> > >
> > >
> > >
> > >
> > >
> >
> >
> >
> >
> >
>
>
>
>
>
------------------------------------------------
Subject: RE: [Non-DoD Source] Re: [rt.rap.ucar.edu #85223] Point Stat Precip Issue
From: robert.craig.2 at us.af.mil
Time: Tue May 22 14:52:38 2018
John, I will use that then instead of the censor logic.
Thanks
Bob
-----Original Message-----
From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
Sent: Tuesday, May 22, 2018 3:46 PM
To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
<robert.craig.2 at us.af.mil>
Subject: Re: [Non-DoD Source] Re: [rt.rap.ucar.edu #85223] Point Stat
Precip Issue
Bob,
You do not need to have a 1 or 0 in the observation field. Instead,
you use the categorical threshold (cat_thresh) to define the "event".
Any observation values meeting that threshold are counted as
"events"... which is like it being a value of 1. And observation
values not meeting that threshold are counted as "non-events"... which
is like being a value of 0.
To clarify, when evaluating probabilities in MET you...
(1) Select a forecast probability field of data (i.e. prob = TRUE;)
(2) Select forecast categorical thresholds which span the values of 0
to 1 to define probability bins. For example, cat_thresh = [ >=0,
>=0.25,
>=0.50, >=0.75, >=1.0 ]; or instead, use the shorthand notation for
this:
cat_thresh = [ ==0.25 ];
(3) Select observation data is *not* a probability field.
(4) Select a single observation threshold which specifies the *event*
corresponding to the probability.
For example, let's say you have a probability of freezing surface
temperatures named "prob_freez", you'd configure it like this:
fcst = {
field = [
{ name="prob_freeze";
level="Z0";
prob=TRUE;
cat_thresh = [ ==0.10 ];
}
];
}
obs = {
field = [
{ name="TMP";
level="Z0";
cat_thresh = [ <=273 ];
}
];
}
I don't *convert* the observations of temperature to 0/1 values.
Instead, I just define the event for probability of freezing...
namely, the temperature being less than or equal to 273 Kelvin.
Hopefully that helps clarify.
Thanks,
John
On Tue, May 22, 2018 at 9:26 AM, robert.craig.2 at us.af.mil via RT <
met_help at ucar.edu> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=85223 >
>
> John, Unless I am miss something, since my goal is to calculate
Brier
> Skill Score, I would need to have 1 or 0 in the observation field
to
> go with the probability forecast data. Using the censoring logic
> worked to generate this. If my MPR file contained a probability for
> the forecast, and an precipitation amount for the observation, is
stat
> analysis smart enough to convert the precipitation amount to 1 or 0
> based on a threshold to calculate a Brier Score and Brier Skill
Score?
>
> Thanks
> Bob
>
> -----Original Message-----
> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> Sent: Monday, May 21, 2018 5:21 PM
> To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
> <robert.craig.2 at us.af.mil>
> Subject: Re: [Non-DoD Source] Re: [rt.rap.ucar.edu #85223] Point
Stat
> Precip Issue
>
> Bob,
>
> There really is no need to apply the threshold and replace the
> observation values with 0's and 1's. Instead, we use the
"cat_thresh"
> to define the event category. My apologies for omitting that from
the config file I sent:
>
> obs = {
> message_type = [ "ADPSFC" ];
> sid_exc = [];
> field = [
> {
> name = "APCP";
> level = "A0";
> cat_thresh = [ >=2.54 ];
> }
> ];
> }
>
> If for some reason, you really wanted the OBS column of the MPR
output
> lines to contain 0's and 1's, you could do so using the "censoring"
> logic, added in met-6.1:
>
> obs = {
> message_type = [ "ADPSFC" ];
> sid_exc = [];
> field = [
> {
> name = "APCP";
> level = "A0";
> censor_thresh = [ <2.54, >=2.54 ];
> censor_val = [ 0, 1 ];
> cat_thresh = [ ==1 ];
> }
> ];
> }
>
> Notice though that I had to change the categorical threshold. After
> the input obs values are converted to 0 and 1, the event is now that
> the obs is equal to 1.
>
> I wouldn't recommend using the censoring logic unless you have a
good
> reason to do so.
>
> Thanks,
> John
>
> On Mon, May 21, 2018 at 3:45 PM, robert.craig.2 at us.af.mil via RT <
> met_help at ucar.edu> wrote:
>
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=85223 >
> >
> > John, I only had used the adjustment to the ob window before and
ob field
> > definition, but when I used the entire config file it worked.
When I
> look
> > in the stat file I see the ob column has precip values instead of
> > the 0
> or
> > 1 based on my threshold. What is the proper syntax to threshold
the ob
> > data to 2.54 mm/.1 "?
> >
> > Thanks
> >
> > Bob
> >
> > -----Original Message-----
> > From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> > Sent: Monday, May 21, 2018 4:30 PM
> > To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
> > <robert.craig.2 at us.af.mil>
> > Subject: Re: [Non-DoD Source] Re: [rt.rap.ucar.edu #85223] Point
> > Stat Precip Issue
> >
> > Bob,
> >
> > I attached a point-stat config file to my message with a "-NEW"
> > suffix at the end. That contained changes to get point-stat up
and running.
> >
> > Did that attachment come through? If not, I could just
> > cut-and-paste it inline in an email.
> >
> > John
> >
> > On Mon, May 21, 2018 at 2:43 PM, robert.craig.2 at us.af.mil via RT <
> > met_help at ucar.edu> wrote:
> >
> > >
> > > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=85223 >
> > >
> > > John, I tried the ob time window adjustment you provided but
still
> > > get
> > the
> > > same error. See below.
> > >
> > > DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> > > GRIB2 field indexes - disc: 0, master table: 10, center: 57,
local
> > > table: 1,
> > > parm_cat: 19, parm: 223
> > > ERROR :
> > > ERROR : PointStatConfInfo::process_config() -> The number of
> > > verification tasks in "obs.field" must be non-zero and match the
> > > number in "fcst.field".
> > > ERROR :
> > >
> > > I noticed that you had the obs set to just APCP and A0 even
though is a
> > > probability forecast. In the past I had to use the following:
> > >
> > > field = [
> > > {cat_thresh=[>.1];
> > > name="PROB";level="A006";prob={name="APCP";thresh_lo=.1;}}
> > > ];
> > >
> > > How does MET know what to threshold the observation data by?
> > >
> > > Bob
> > >
> > > -----Original Message-----
> > > From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> > > Sent: Monday, May 21, 2018 3:17 PM
> > > To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
> > > <robert.craig.2 at us.af.mil>
> > > Subject: Re: [Non-DoD Source] Re: [rt.rap.ucar.edu #85223] Point
> > > Stat Precip Issue
> > >
> > > OK, so does that band-aid make sense to you? Adjusting the time
> > > window so that Point-Stat can find matches.
> > >
> > > John
> > >
> > > On Mon, May 21, 2018 at 2:00 PM, robert.craig.2 at us.af.mil via RT
<
> > > met_help at ucar.edu> wrote:
> > >
> > > >
> > > > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=85223
>
> > > >
> > > > John,
> > > >
> > > > We are frozen until you deliver the version with the Fortify
> > > > error
> > fixes.
> > > > I was hoping to be running on MET entirely by now but the new
> > > > security rules are not allowing that.
> > > >
> > > > Bob
> > > >
> > > >
> > > > -----Original Message-----
> > > > From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> > > > Sent: Monday, May 21, 2018 2:39 PM
> > > > To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
> > > > <robert.craig.2 at us.af.mil>
> > > > Subject: Re: [Non-DoD Source] Re: [rt.rap.ucar.edu #85223]
Point
> > > > Stat Precip Issue
> > > >
> > > > Bob,
> > > >
> > > > I was working on this last Friday. Unfortunately, I don't
have
> > > > a good solution for you. MET is not parsing the timing
> > > > information for this data correctly.
> > > >
> > > > We need to update the GRIB library parsing logic to account
for this.
> > > >
> > > > setenv MET_GRIB_TABLES grib2_geps.txt
> > > > met-6.1/bin/plot_data_plane
> > > > grib2.2018040100.0012 grib2.2018040100.0012.ps 'name="QP010";
> > > > level="Z0";' -v 4
> > > >
> > > > DEBUG 4: valid time: 20180401_060000
> > > > DEBUG 4: lead time: 060000
> > > > DEBUG 4: init time: 20180401_000000
> > > >
> > > > MET gets the initialization time correct, but it processes the
> > > > data as a 6 hour forecast, rather than recognizing it as a 6-
12
> > > > hour
> > > accumulation.
> > > > Therefore the lead time and valid times are wrong. And that
> > > > leads to zero matched pairs from Point-Stat. We need to patch
> > > > MET to correctly parse the accumulation information from this
file.
> > > >
> > > > In the meantime, one band-aid would be adjusting the matching
> > > > time window in Point-Stat to account for the 6 hour offset:
> > > >
> > > > met-6.1/bin/point_stat grib2.2018040100.0012 nc_2018040112
> > > > PointStatConfig_geps_precip_updated-NEW -outdir out -v 3
> > > >
> > > > DEBUG 2: Processing QP010/Z0 versus APCP/A0, for observation
> > > > type ADPSFC, over region FULL, for interpolation method
> > > > NEAREST(1), using
> > > > 448
> > > pairs.
> > > > DEBUG 3: Number of matched pairs = 448
> > > > DEBUG 3: Observations processed = 449
> > > >
> > > > Since MET thinks the forecast is valid 6 hours earlier than it
> > > > really is, I set the matching time window to select obs 6
hours
> later:
> > > > obs_window = {
> > > > beg = 6*3600 - 600;
> > > > end = 6*3600 + 600;
> > > > }
> > > >
> > > > See that attached config file.
> > > >
> > > > Matt tells me that MET is "frozen" there. Are you able to
> > > > recompile with patches for met-6.1? Or stuck with what you've
got?
> > > >
> > > > Thanks,
> > > > John
> > > >
> > > >
> > > >
> > > > On Fri, May 18, 2018 at 11:57 AM, robert.craig.2 at us.af.mil via
> > > > RT < met_help at ucar.edu> wrote:
> > > >
> > > > >
> > > > > <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=85223
> > > > > >
> > > > >
> > > > > John, I attached is my GRIB 2 table.
> > > > >
> > > > > -----Original Message-----
> > > > > From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> > > > > Sent: Friday, May 18, 2018 12:04 PM
> > > > > To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
> > > > > <robert.craig.2 at us.af.mil>
> > > > > Subject: [Non-DoD Source] Re: [rt.rap.ucar.edu #85223] Point
> > > > > Stat Precip Issue
> > > > >
> > > > > Bob,
> > > > >
> > > > > Ah never mind, I apologize. That sample NetCDF file really
> > > > > does contain point obs. I'll take a closer look now.
> > > > >
> > > > > Thanks,
> > > > > John
> > > > >
> > > > > On Fri, May 18, 2018 at 11:02 AM, John Halley Gotway
> > > > > <johnhg at ucar.edu>
> > > > > wrote:
> > > > >
> > > > > > Bob,
> > > > > >
> > > > > > Based on your description, it sounds like you're comparing
> > > > > > gridded model output to a gridded analysis field. Since
> > > > > > you're doing grid-to-grid verification, you should be
> > > > > > running the
> > Grid-Stat tool.
> > > > > > The Point-Stat tool is used to verify against point
observations.
> > > > > >
> > > > > > If you need me to take a closer look at the data you sent
> > > > > > through ARMDEC, just let me know.
> > > > > >
> > > > > > But please try running Grid-Stat to see if you have better
> success.
> > > > > >
> > > > > > Thanks,
> > > > > > John
> > > > > >
> > > > > > On Fri, May 18, 2018 at 10:53 AM, robert.craig.2 at us.af.mil
> > > > > > via RT < met_help at ucar.edu> wrote:
> > > > > >
> > > > > >>
> > > > > >> Fri May 18 10:53:15 2018: Request 85223 was acted upon.
> > > > > >> Transaction: Ticket created by robert.craig.2 at us.af.mil
> > > > > >> Queue: met_help
> > > > > >> Subject: Point Stat Precip Issue
> > > > > >> Owner: Nobody
> > > > > >> Requestors: robert.craig.2 at us.af.mil
> > > > > >> Status: new
> > > > > >> Ticket <URL:
> > > > > >> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=85223
> > > > > >> >
> > > > > >>
> > > > > >>
> > > > > >> John, I have been following your dialog with Matt but I
> > > > > >> seem to have a different issue then you worked with him.
> > > > > >>
> > > > > >> I am running MET 6.1 and verifying precip probabilities
(>
> > > > > >> .1in
> > > > > >> (2.54 mm)).
> > > > > >> I am able to read the precip grib file okay (checked it
> > > > > >> with plot_data_plane). The ob file is net cdf file in
> > > > > >> millimeters, attached
> > > > > .
> > > > > >> The config file is also attached. When I run I get the
> > > > > >> following
> > > > error:
> > > > > >>
> > > > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > > > >> unrecognized
> > > > > >> GRIB2 field indexes - disc: 0, master table: 10, center:
> > > > > >> 57, local
> > > > > >> table: 1,
> > > > > >> parm_cat: 6, parm: 70
> > > > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > > > >> unrecognized
> > > > > >> GRIB2 field indexes - disc: 0, master table: 10, center:
> > > > > >> 57, local
> > > > > >> table: 1,
> > > > > >> parm_cat: 6, parm: 70
> > > > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > > > >> unrecognized
> > > > > >> GRIB2 field indexes - disc: 0, master table: 10, center:
> > > > > >> 57, local
> > > > > >> table: 1,
> > > > > >> parm_cat: 6, parm: 70
> > > > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > > > >> unrecognized
> > > > > >> GRIB2 field indexes - disc: 0, master table: 10, center:
> > > > > >> 57, local
> > > > > >> table: 1,
> > > > > >> parm_cat: 6, parm: 70
> > > > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > > > >> unrecognized
> > > > > >> GRIB2 field indexes - disc: 0, master table: 10, center:
> > > > > >> 57, local
> > > > > >> table: 1,
> > > > > >> parm_cat: 6, parm: 70
> > > > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > > > >> unrecognized
> > > > > >> GRIB2 field indexes - disc: 0, master table: 10, center:
> > > > > >> 57, local
> > > > > >> table: 1,
> > > > > >> parm_cat: 6, parm: 70
> > > > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > > > >> unrecognized
> > > > > >> GRIB2 field indexes - disc: 0, master table: 10, center:
> > > > > >> 57, local
> > > > > >> table: 1,
> > > > > >> parm_cat: 6, parm: 70
> > > > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > > > >> unrecognized
> > > > > >> GRIB2 field indexes - disc: 0, master table: 10, center:
> > > > > >> 57, local
> > > > > >> table: 1,
> > > > > >> parm_cat: 6, parm: 70
> > > > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > > > >> unrecognized
> > > > > >> GRIB2 field indexes - disc: 0, master table: 10, center:
> > > > > >> 57, local
> > > > > >> table: 1,
> > > > > >> parm_cat: 6, parm: 70
> > > > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > > > >> unrecognized
> > > > > >> GRIB2 field indexes - disc: 0, master table: 10, center:
> > > > > >> 57, local
> > > > > >> table: 1,
> > > > > >> parm_cat: 6, parm: 70
> > > > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > > > >> unrecognized
> > > > > >> GRIB2 field indexes - disc: 0, master table: 10, center:
> > > > > >> 57, local
> > > > > >> table: 1,
> > > > > >> parm_cat: 6, parm: 70
> > > > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > > > >> unrecognized
> > > > > >> GRIB2 field indexes - disc: 0, master table: 10, center:
> > > > > >> 57, local
> > > > > >> table: 1,
> > > > > >> parm_cat: 19, parm: 223
> > > > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > > > >> unrecognized
> > > > > >> GRIB2 field indexes - disc: 0, master table: 10, center:
> > > > > >> 57, local
> > > > > >> table: 1,
> > > > > >> parm_cat: 19, parm: 223
> > > > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > > > >> unrecognized
> > > > > >> GRIB2 field indexes - disc: 0, master table: 10, center:
> > > > > >> 57, local
> > > > > >> table: 1,
> > > > > >> parm_cat: 19, parm: 223
> > > > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > > > >> unrecognized
> > > > > >> GRIB2 field indexes - disc: 0, master table: 10, center:
> > > > > >> 57, local
> > > > > >> table: 1,
> > > > > >> parm_cat: 19, parm: 223
> > > > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > > > >> unrecognized
> > > > > >> GRIB2 field indexes - disc: 0, master table: 10, center:
> > > > > >> 57, local
> > > > > >> table: 1,
> > > > > >> parm_cat: 19, parm: 223
> > > > > >> ERROR :
> > > > > >> ERROR : PointStatConfInfo::process_config() -> The
number
> > > > > >> of verification tasks in "obs.field" must be non-zero and
> > > > > >> match the number in "fcst.field".
> > > > > >> ERROR :
> > > > > >>
> > > > > >> The ob file contains a grib 1 kpds5 value of 61 which
> > > > > >> translates to APCP in the grib 1 table (attached).
> > > > > >>
> > > > > >> So what am I doing wrong? I sent the data files via
AMRDEC
> > > > > >>
> > > > > >> Thanks
> > > > > >> Bob
> > > > > >>
> > > > > >>
> > > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > >
> > > >
> > > >
> > > >
> > >
> > >
> > >
> > >
> > >
> >
> >
> >
> >
> >
>
>
>
>
>
------------------------------------------------
Subject: Point Stat Precip Issue
From: John Halley Gotway
Time: Tue May 22 15:02:47 2018
Bob,
Great. And I'll turn the GEPS issue you raised into a development
issue
for us to address. So once the Fortify updates are in place, we
should
have the times from this dataset sorted out.
Thanks,
John
On Tue, May 22, 2018 at 2:52 PM, robert.craig.2 at us.af.mil via RT <
met_help at ucar.edu> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=85223 >
>
> John, I will use that then instead of the censor logic.
>
> Thanks
> Bob
>
> -----Original Message-----
> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> Sent: Tuesday, May 22, 2018 3:46 PM
> To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
<robert.craig.2 at us.af.mil>
> Subject: Re: [Non-DoD Source] Re: [rt.rap.ucar.edu #85223] Point
Stat
> Precip Issue
>
> Bob,
>
> You do not need to have a 1 or 0 in the observation field. Instead,
you
> use the categorical threshold (cat_thresh) to define the "event".
Any
> observation values meeting that threshold are counted as "events"...
which
> is like it being a value of 1. And observation values not meeting
that
> threshold are counted as "non-events"... which is like being a value
of 0.
>
> To clarify, when evaluating probabilities in MET you...
>
> (1) Select a forecast probability field of data (i.e. prob = TRUE;)
> (2) Select forecast categorical thresholds which span the values of
0 to 1
> to define probability bins. For example, cat_thresh = [ >=0,
>=0.25,
> >=0.50, >=0.75, >=1.0 ]; or instead, use the shorthand notation for
this:
> cat_thresh = [ ==0.25 ];
> (3) Select observation data is *not* a probability field.
> (4) Select a single observation threshold which specifies the
*event*
> corresponding to the probability.
>
> For example, let's say you have a probability of freezing surface
> temperatures named "prob_freez", you'd configure it like this:
>
> fcst = {
> field = [
> { name="prob_freeze";
> level="Z0";
> prob=TRUE;
> cat_thresh = [ ==0.10 ];
> }
> ];
> }
>
> obs = {
> field = [
> { name="TMP";
> level="Z0";
> cat_thresh = [ <=273 ];
> }
> ];
> }
>
> I don't *convert* the observations of temperature to 0/1 values.
Instead,
> I just define the event for probability of freezing... namely, the
> temperature being less than or equal to 273 Kelvin.
>
> Hopefully that helps clarify.
>
> Thanks,
> John
>
>
>
> On Tue, May 22, 2018 at 9:26 AM, robert.craig.2 at us.af.mil via RT <
> met_help at ucar.edu> wrote:
>
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=85223 >
> >
> > John, Unless I am miss something, since my goal is to calculate
Brier
> > Skill Score, I would need to have 1 or 0 in the observation field
to
> > go with the probability forecast data. Using the censoring logic
> > worked to generate this. If my MPR file contained a probability
for
> > the forecast, and an precipitation amount for the observation, is
stat
> > analysis smart enough to convert the precipitation amount to 1 or
0
> > based on a threshold to calculate a Brier Score and Brier Skill
Score?
> >
> > Thanks
> > Bob
> >
> > -----Original Message-----
> > From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> > Sent: Monday, May 21, 2018 5:21 PM
> > To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
> > <robert.craig.2 at us.af.mil>
> > Subject: Re: [Non-DoD Source] Re: [rt.rap.ucar.edu #85223] Point
Stat
> > Precip Issue
> >
> > Bob,
> >
> > There really is no need to apply the threshold and replace the
> > observation values with 0's and 1's. Instead, we use the
"cat_thresh"
> > to define the event category. My apologies for omitting that from
the
> config file I sent:
> >
> > obs = {
> > message_type = [ "ADPSFC" ];
> > sid_exc = [];
> > field = [
> > {
> > name = "APCP";
> > level = "A0";
> > cat_thresh = [ >=2.54 ];
> > }
> > ];
> > }
> >
> > If for some reason, you really wanted the OBS column of the MPR
output
> > lines to contain 0's and 1's, you could do so using the
"censoring"
> > logic, added in met-6.1:
> >
> > obs = {
> > message_type = [ "ADPSFC" ];
> > sid_exc = [];
> > field = [
> > {
> > name = "APCP";
> > level = "A0";
> > censor_thresh = [ <2.54, >=2.54 ];
> > censor_val = [ 0, 1 ];
> > cat_thresh = [ ==1 ];
> > }
> > ];
> > }
> >
> > Notice though that I had to change the categorical threshold.
After
> > the input obs values are converted to 0 and 1, the event is now
that
> > the obs is equal to 1.
> >
> > I wouldn't recommend using the censoring logic unless you have a
good
> > reason to do so.
> >
> > Thanks,
> > John
> >
> > On Mon, May 21, 2018 at 3:45 PM, robert.craig.2 at us.af.mil via RT <
> > met_help at ucar.edu> wrote:
> >
> > >
> > > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=85223 >
> > >
> > > John, I only had used the adjustment to the ob window before and
ob
> field
> > > definition, but when I used the entire config file it worked.
When I
> > look
> > > in the stat file I see the ob column has precip values instead
of
> > > the 0
> > or
> > > 1 based on my threshold. What is the proper syntax to
threshold the
> ob
> > > data to 2.54 mm/.1 "?
> > >
> > > Thanks
> > >
> > > Bob
> > >
> > > -----Original Message-----
> > > From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> > > Sent: Monday, May 21, 2018 4:30 PM
> > > To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
> > > <robert.craig.2 at us.af.mil>
> > > Subject: Re: [Non-DoD Source] Re: [rt.rap.ucar.edu #85223] Point
> > > Stat Precip Issue
> > >
> > > Bob,
> > >
> > > I attached a point-stat config file to my message with a "-NEW"
> > > suffix at the end. That contained changes to get point-stat up
and
> running.
> > >
> > > Did that attachment come through? If not, I could just
> > > cut-and-paste it inline in an email.
> > >
> > > John
> > >
> > > On Mon, May 21, 2018 at 2:43 PM, robert.craig.2 at us.af.mil via RT
<
> > > met_help at ucar.edu> wrote:
> > >
> > > >
> > > > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=85223
>
> > > >
> > > > John, I tried the ob time window adjustment you provided but
still
> > > > get
> > > the
> > > > same error. See below.
> > > >
> > > > DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> > > > GRIB2 field indexes - disc: 0, master table: 10, center: 57,
local
> > > > table: 1,
> > > > parm_cat: 19, parm: 223
> > > > ERROR :
> > > > ERROR : PointStatConfInfo::process_config() -> The number of
> > > > verification tasks in "obs.field" must be non-zero and match
the
> > > > number in "fcst.field".
> > > > ERROR :
> > > >
> > > > I noticed that you had the obs set to just APCP and A0 even
though
> is a
> > > > probability forecast. In the past I had to use the
following:
> > > >
> > > > field = [
> > > > {cat_thresh=[>.1];
> > > >
name="PROB";level="A006";prob={name="APCP";thresh_lo=.1;}}
> > > > ];
> > > >
> > > > How does MET know what to threshold the observation data by?
> > > >
> > > > Bob
> > > >
> > > > -----Original Message-----
> > > > From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> > > > Sent: Monday, May 21, 2018 3:17 PM
> > > > To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
> > > > <robert.craig.2 at us.af.mil>
> > > > Subject: Re: [Non-DoD Source] Re: [rt.rap.ucar.edu #85223]
Point
> > > > Stat Precip Issue
> > > >
> > > > OK, so does that band-aid make sense to you? Adjusting the
time
> > > > window so that Point-Stat can find matches.
> > > >
> > > > John
> > > >
> > > > On Mon, May 21, 2018 at 2:00 PM, robert.craig.2 at us.af.mil via
RT <
> > > > met_help at ucar.edu> wrote:
> > > >
> > > > >
> > > > > <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=85223 >
> > > > >
> > > > > John,
> > > > >
> > > > > We are frozen until you deliver the version with the Fortify
> > > > > error
> > > fixes.
> > > > > I was hoping to be running on MET entirely by now but the
new
> > > > > security rules are not allowing that.
> > > > >
> > > > > Bob
> > > > >
> > > > >
> > > > > -----Original Message-----
> > > > > From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> > > > > Sent: Monday, May 21, 2018 2:39 PM
> > > > > To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
> > > > > <robert.craig.2 at us.af.mil>
> > > > > Subject: Re: [Non-DoD Source] Re: [rt.rap.ucar.edu #85223]
Point
> > > > > Stat Precip Issue
> > > > >
> > > > > Bob,
> > > > >
> > > > > I was working on this last Friday. Unfortunately, I don't
have
> > > > > a good solution for you. MET is not parsing the timing
> > > > > information for this data correctly.
> > > > >
> > > > > We need to update the GRIB library parsing logic to account
for
> this.
> > > > >
> > > > > setenv MET_GRIB_TABLES grib2_geps.txt
> > > > > met-6.1/bin/plot_data_plane
> > > > > grib2.2018040100.0012 grib2.2018040100.0012.ps
'name="QP010";
> > > > > level="Z0";' -v 4
> > > > >
> > > > > DEBUG 4: valid time: 20180401_060000
> > > > > DEBUG 4: lead time: 060000
> > > > > DEBUG 4: init time: 20180401_000000
> > > > >
> > > > > MET gets the initialization time correct, but it processes
the
> > > > > data as a 6 hour forecast, rather than recognizing it as a
6-12
> > > > > hour
> > > > accumulation.
> > > > > Therefore the lead time and valid times are wrong. And that
> > > > > leads to zero matched pairs from Point-Stat. We need to
patch
> > > > > MET to correctly parse the accumulation information from
this file.
> > > > >
> > > > > In the meantime, one band-aid would be adjusting the
matching
> > > > > time window in Point-Stat to account for the 6 hour offset:
> > > > >
> > > > > met-6.1/bin/point_stat grib2.2018040100.0012 nc_2018040112
> > > > > PointStatConfig_geps_precip_updated-NEW -outdir out -v 3
> > > > >
> > > > > DEBUG 2: Processing QP010/Z0 versus APCP/A0, for observation
> > > > > type ADPSFC, over region FULL, for interpolation method
> > > > > NEAREST(1), using
> > > > > 448
> > > > pairs.
> > > > > DEBUG 3: Number of matched pairs = 448
> > > > > DEBUG 3: Observations processed = 449
> > > > >
> > > > > Since MET thinks the forecast is valid 6 hours earlier than
it
> > > > > really is, I set the matching time window to select obs 6
hours
> > later:
> > > > > obs_window = {
> > > > > beg = 6*3600 - 600;
> > > > > end = 6*3600 + 600;
> > > > > }
> > > > >
> > > > > See that attached config file.
> > > > >
> > > > > Matt tells me that MET is "frozen" there. Are you able to
> > > > > recompile with patches for met-6.1? Or stuck with what
you've got?
> > > > >
> > > > > Thanks,
> > > > > John
> > > > >
> > > > >
> > > > >
> > > > > On Fri, May 18, 2018 at 11:57 AM, robert.craig.2 at us.af.mil
via
> > > > > RT < met_help at ucar.edu> wrote:
> > > > >
> > > > > >
> > > > > > <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=85223
> > > > > > >
> > > > > >
> > > > > > John, I attached is my GRIB 2 table.
> > > > > >
> > > > > > -----Original Message-----
> > > > > > From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> > > > > > Sent: Friday, May 18, 2018 12:04 PM
> > > > > > To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
> > > > > > <robert.craig.2 at us.af.mil>
> > > > > > Subject: [Non-DoD Source] Re: [rt.rap.ucar.edu #85223]
Point
> > > > > > Stat Precip Issue
> > > > > >
> > > > > > Bob,
> > > > > >
> > > > > > Ah never mind, I apologize. That sample NetCDF file
really
> > > > > > does contain point obs. I'll take a closer look now.
> > > > > >
> > > > > > Thanks,
> > > > > > John
> > > > > >
> > > > > > On Fri, May 18, 2018 at 11:02 AM, John Halley Gotway
> > > > > > <johnhg at ucar.edu>
> > > > > > wrote:
> > > > > >
> > > > > > > Bob,
> > > > > > >
> > > > > > > Based on your description, it sounds like you're
comparing
> > > > > > > gridded model output to a gridded analysis field. Since
> > > > > > > you're doing grid-to-grid verification, you should be
> > > > > > > running the
> > > Grid-Stat tool.
> > > > > > > The Point-Stat tool is used to verify against point
> observations.
> > > > > > >
> > > > > > > If you need me to take a closer look at the data you
sent
> > > > > > > through ARMDEC, just let me know.
> > > > > > >
> > > > > > > But please try running Grid-Stat to see if you have
better
> > success.
> > > > > > >
> > > > > > > Thanks,
> > > > > > > John
> > > > > > >
> > > > > > > On Fri, May 18, 2018 at 10:53 AM,
robert.craig.2 at us.af.mil
> > > > > > > via RT < met_help at ucar.edu> wrote:
> > > > > > >
> > > > > > >>
> > > > > > >> Fri May 18 10:53:15 2018: Request 85223 was acted upon.
> > > > > > >> Transaction: Ticket created by robert.craig.2 at us.af.mil
> > > > > > >> Queue: met_help
> > > > > > >> Subject: Point Stat Precip Issue
> > > > > > >> Owner: Nobody
> > > > > > >> Requestors: robert.craig.2 at us.af.mil
> > > > > > >> Status: new
> > > > > > >> Ticket <URL:
> > > > > > >> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=85223
> > > > > > >> >
> > > > > > >>
> > > > > > >>
> > > > > > >> John, I have been following your dialog with Matt but I
> > > > > > >> seem to have a different issue then you worked with
him.
> > > > > > >>
> > > > > > >> I am running MET 6.1 and verifying precip probabilities
(>
> > > > > > >> .1in
> > > > > > >> (2.54 mm)).
> > > > > > >> I am able to read the precip grib file okay (checked it
> > > > > > >> with plot_data_plane). The ob file is net cdf file in
> > > > > > >> millimeters, attached
> > > > > > .
> > > > > > >> The config file is also attached. When I run I get the
> > > > > > >> following
> > > > > error:
> > > > > > >>
> > > > > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > > > > >> unrecognized
> > > > > > >> GRIB2 field indexes - disc: 0, master table: 10,
center:
> > > > > > >> 57, local
> > > > > > >> table: 1,
> > > > > > >> parm_cat: 6, parm: 70
> > > > > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > > > > >> unrecognized
> > > > > > >> GRIB2 field indexes - disc: 0, master table: 10,
center:
> > > > > > >> 57, local
> > > > > > >> table: 1,
> > > > > > >> parm_cat: 6, parm: 70
> > > > > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > > > > >> unrecognized
> > > > > > >> GRIB2 field indexes - disc: 0, master table: 10,
center:
> > > > > > >> 57, local
> > > > > > >> table: 1,
> > > > > > >> parm_cat: 6, parm: 70
> > > > > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > > > > >> unrecognized
> > > > > > >> GRIB2 field indexes - disc: 0, master table: 10,
center:
> > > > > > >> 57, local
> > > > > > >> table: 1,
> > > > > > >> parm_cat: 6, parm: 70
> > > > > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > > > > >> unrecognized
> > > > > > >> GRIB2 field indexes - disc: 0, master table: 10,
center:
> > > > > > >> 57, local
> > > > > > >> table: 1,
> > > > > > >> parm_cat: 6, parm: 70
> > > > > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > > > > >> unrecognized
> > > > > > >> GRIB2 field indexes - disc: 0, master table: 10,
center:
> > > > > > >> 57, local
> > > > > > >> table: 1,
> > > > > > >> parm_cat: 6, parm: 70
> > > > > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > > > > >> unrecognized
> > > > > > >> GRIB2 field indexes - disc: 0, master table: 10,
center:
> > > > > > >> 57, local
> > > > > > >> table: 1,
> > > > > > >> parm_cat: 6, parm: 70
> > > > > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > > > > >> unrecognized
> > > > > > >> GRIB2 field indexes - disc: 0, master table: 10,
center:
> > > > > > >> 57, local
> > > > > > >> table: 1,
> > > > > > >> parm_cat: 6, parm: 70
> > > > > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > > > > >> unrecognized
> > > > > > >> GRIB2 field indexes - disc: 0, master table: 10,
center:
> > > > > > >> 57, local
> > > > > > >> table: 1,
> > > > > > >> parm_cat: 6, parm: 70
> > > > > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > > > > >> unrecognized
> > > > > > >> GRIB2 field indexes - disc: 0, master table: 10,
center:
> > > > > > >> 57, local
> > > > > > >> table: 1,
> > > > > > >> parm_cat: 6, parm: 70
> > > > > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > > > > >> unrecognized
> > > > > > >> GRIB2 field indexes - disc: 0, master table: 10,
center:
> > > > > > >> 57, local
> > > > > > >> table: 1,
> > > > > > >> parm_cat: 6, parm: 70
> > > > > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > > > > >> unrecognized
> > > > > > >> GRIB2 field indexes - disc: 0, master table: 10,
center:
> > > > > > >> 57, local
> > > > > > >> table: 1,
> > > > > > >> parm_cat: 19, parm: 223
> > > > > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > > > > >> unrecognized
> > > > > > >> GRIB2 field indexes - disc: 0, master table: 10,
center:
> > > > > > >> 57, local
> > > > > > >> table: 1,
> > > > > > >> parm_cat: 19, parm: 223
> > > > > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > > > > >> unrecognized
> > > > > > >> GRIB2 field indexes - disc: 0, master table: 10,
center:
> > > > > > >> 57, local
> > > > > > >> table: 1,
> > > > > > >> parm_cat: 19, parm: 223
> > > > > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > > > > >> unrecognized
> > > > > > >> GRIB2 field indexes - disc: 0, master table: 10,
center:
> > > > > > >> 57, local
> > > > > > >> table: 1,
> > > > > > >> parm_cat: 19, parm: 223
> > > > > > >> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
> > > > > > >> unrecognized
> > > > > > >> GRIB2 field indexes - disc: 0, master table: 10,
center:
> > > > > > >> 57, local
> > > > > > >> table: 1,
> > > > > > >> parm_cat: 19, parm: 223
> > > > > > >> ERROR :
> > > > > > >> ERROR : PointStatConfInfo::process_config() -> The
number
> > > > > > >> of verification tasks in "obs.field" must be non-zero
and
> > > > > > >> match the number in "fcst.field".
> > > > > > >> ERROR :
> > > > > > >>
> > > > > > >> The ob file contains a grib 1 kpds5 value of 61 which
> > > > > > >> translates to APCP in the grib 1 table (attached).
> > > > > > >>
> > > > > > >> So what am I doing wrong? I sent the data files via
AMRDEC
> > > > > > >>
> > > > > > >> Thanks
> > > > > > >> Bob
> > > > > > >>
> > > > > > >>
> > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > >
> > >
> > >
> > >
> > >
> >
> >
> >
> >
> >
>
>
>
>
>
------------------------------------------------
More information about the Met_help
mailing list