[Met_help] [rt.rap.ucar.edu #80886] History for #80868 continued

John Halley Gotway via RT met_help at ucar.edu
Tue Jun 20 11:28:58 MDT 2017


----------------------------------------------------------------
  Initial Request
----------------------------------------------------------------

John, I tried setting the configuration file to what is in the manual for probability forecasts:

 fcst = {

   cat_thresh = [>=0,>=0.1,>=0.2,>=0.3,>=0.4,>=0.5,>=0.6,>=0.7,>=0.8,>=0.9,>=1.0];

   field = [
             { name = "PROB"; level = "Z10"; prob = { name = "PWS15"; thresh_lo = 7.7; }}
           ];
}

But I end up with the following:

[1156 qcteam hpc9-lsn-01d /h/WXQC/testenv/bin] /h/WXQC/met-6.0/bin/grid_stat /h/data/global/WXQC/data/geps_verify/qcsave/2017060500/grib2.2017060500.0024 /h/data/global/WXQC/data/met/tmp/03b4af71-f320-49>
DEBUG 1: Reading user-defined grib1 MET_GRIB_TABLES file: /h/data/global/WXQC/data/met/config/grib2/grib1_af_131_57.txt
DEBUG 1: Reading user-defined grib2 MET_GRIB_TABLES file: /h/data/global/WXQC/data/met/config/grib2/grib2_geps.txt
DEBUG 1: Default Config File: /h/WXQC/met-6.0/share/met/config/GridStatConfig_default
DEBUG 1: User Config File: /h/WXQC/met-6.0/data/config/GridStatConfig_geps_updated
DEBUG 3: Use the matching forecast and observation grids.
DEBUG 3: Grid Definition: Projection: Lat/Lon Nx: 360 Ny: 181 lat_ll: -90.000 lon_ll: -0.000 delta_lat: 1.000 delta_lon: 1.000
GSL_RNG_TYPE=mt19937
GSL_RNG_SEED=18446744073657729625
DEBUG 1: Forecast File: /h/data/global/WXQC/data/geps_verify/qcsave/2017060500/grib2.2017060500.0024
DEBUG 1: Observation File: /h/data/global/WXQC/data/met/tmp/03b4af71-f320-4985-a093-b51b555c7684
DEBUG 3: Reading forecast data for PROB(PWS15>7.700)/Z10/PROB.
WARNING:
WARNING: MetGrib2DataFile::data_plane() - No matching record found for 'PROB(PWS15>7.700)/Z10/PROB'
WARNING:
WARNING:
WARNING: process_scores() -> PROB(PWS15>7.700)/Z10/PROB not found in file: /h/data/global/WXQC/data/geps_verify/qcsave/2017060500/grib2.2017060500.0024
WARNING:
DEBUG 2:
DEBUG 2: --------------------------------------------------------------------------------
DEBUG 2:



----------------------------------------------------------------
  Complete Ticket History
----------------------------------------------------------------

Subject: #80868 continued
From: John Halley Gotway
Time: Thu Jun 15 14:45:32 2017

Bob,

NCEP has a rather particular way of encoding probability information
into
their GRIB files. They make use of the extended product description
section
(PDS), and the format you've used is designed to parse information out
of
there.

Instead, just go back to the config file setup that was working
previously
but add:

   prob = TRUE;

That tells MET that it should interpret and process the data that
you're
passing to it as probabilistic data.

fcst = {

   field = [
      {
        name = "PWS15";
        level = "Z10";
        prob = TRUE;
        cat_thresh = [ ==0.1 ];
      }
   ];
}

Does that produce PSTD output?  Also note that I've used a shorthand
convention by setting cat_thresh to "==0.1".  We enhance 6.0 to
interpret
that as >=0,>=0.1,... and so on.  Or you could set it to "==0.01" for
every
1 percent or "==0.25" for every 25 percent.

Thanks,
John


On Thu, Jun 15, 2017 at 2:16 PM, robert.craig.2 at us.af.mil via RT <
met_help at ucar.edu> wrote:

>
> Thu Jun 15 14:16:32 2017: Request 80886 was acted upon.
> Transaction: Ticket created by robert.craig.2 at us.af.mil
>        Queue: met_help
>      Subject: #80868 continued
>        Owner: Nobody
>   Requestors: robert.craig.2 at us.af.mil
>       Status: new
>  Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80886 >
>
>
> John, I tried setting the configuration file to what is in the
manual for
> probability forecasts:
>
>  fcst = {
>
>    cat_thresh = [>=0,>=0.1,>=0.2,>=0.3,>=0.4,>
> =0.5,>=0.6,>=0.7,>=0.8,>=0.9,>=1.0];
>
>    field = [
>              { name = "PROB"; level = "Z10"; prob = { name =
"PWS15";
> thresh_lo = 7.7; }}
>            ];
> }
>
> But I end up with the following:
>
> [1156 qcteam hpc9-lsn-01d /h/WXQC/testenv/bin]
> /h/WXQC/met-6.0/bin/grid_stat /h/data/global/WXQC/data/geps_
> verify/qcsave/2017060500/grib2.2017060500.0024
> /h/data/global/WXQC/data/met/tmp/03b4af71-f320-49>
> DEBUG 1: Reading user-defined grib1 MET_GRIB_TABLES file:
> /h/data/global/WXQC/data/met/config/grib2/grib1_af_131_57.txt
> DEBUG 1: Reading user-defined grib2 MET_GRIB_TABLES file:
> /h/data/global/WXQC/data/met/config/grib2/grib2_geps.txt
> DEBUG 1: Default Config File: /h/WXQC/met-6.0/share/met/
> config/GridStatConfig_default
> DEBUG 1: User Config File: /h/WXQC/met-6.0/data/config/
> GridStatConfig_geps_updated
> DEBUG 3: Use the matching forecast and observation grids.
> DEBUG 3: Grid Definition: Projection: Lat/Lon Nx: 360 Ny: 181
lat_ll:
> -90.000 lon_ll: -0.000 delta_lat: 1.000 delta_lon: 1.000
> GSL_RNG_TYPE=mt19937
> GSL_RNG_SEED=18446744073657729625
> DEBUG 1: Forecast File: /h/data/global/WXQC/data/geps_
> verify/qcsave/2017060500/grib2.2017060500.0024
> DEBUG 1: Observation File: /h/data/global/WXQC/data/met/
> tmp/03b4af71-f320-4985-a093-b51b555c7684
> DEBUG 3: Reading forecast data for PROB(PWS15>7.700)/Z10/PROB.
> WARNING:
> WARNING: MetGrib2DataFile::data_plane() - No matching record found
for
> 'PROB(PWS15>7.700)/Z10/PROB'
> WARNING:
> WARNING:
> WARNING: process_scores() -> PROB(PWS15>7.700)/Z10/PROB not found in
file:
> /h/data/global/WXQC/data/geps_verify/qcsave/2017060500/
> grib2.2017060500.0024
> WARNING:
> DEBUG 2:
> DEBUG 2:
------------------------------------------------------------
> --------------------
> DEBUG 2:
>
>
>

------------------------------------------------
Subject: RE: [Non-DoD Source] Re: [rt.rap.ucar.edu #80886] #80868 continued
From: robert.craig.2 at us.af.mil
Time: Thu Jun 15 15:14:02 2017

Well, it is running but still on data in PSTD file.  Per your previous
comments, for precip I have been using:

fcst = {

   name = "PROB";
   level = "A06";

   cat_thresh =
[>=0,>=0.1,>=0.2,>=0.3,>=0.4,>=0.5,>=0.6,>=0.7,>=0.8,>=0.9,>=1.0];

   field = [
      { name = "PROB"; level = "A06"; prob = { name = "APCP";
thresh_hi = .01; }},
      { name = "PROB"; level = "A06"; prob = { name = "APCP";
thresh_lo = .05; }},
      { name = "PROB"; level = "A06"; prob = { name = "APCP";
thresh_lo = .10; }},
      { name = "PROB"; level = "A06"; prob = { name = "APCP";
thresh_lo = .25; }},
      { name = "PROB"; level = "A06"; prob = { name = "APCP";
thresh_lo = .50; }},
      { name = "PROB"; level = "A06"; prob = { name = "APCP";
thresh_lo = 1.0; }}
   ];
}

obs = {
   message_type = [ "ADPSFC" ];
   sid_exc      = [];

   name = "APCP";
   level = [ "L0" ];
   GRIB1_ptv=131;
   GRIB1_center=57;
   GRIB1_subcenter=2;

   field = [
      { cat_thresh = [>=.01];},
      { cat_thresh = [>=.05];},
      { cat_thresh = [>=.10];},
      { cat_thresh = [>=.25];},
      { cat_thresh = [>=.50];},
      { cat_thresh = [>=1.0];}
   ];
}

and that worked for precip.

So I tried

fcst = {

   cat_thresh =
[>=0,>=0.1,>=0.2,>=0.3,>=0.4,>=0.5,>=0.6,>=0.7,>=0.8,>=0.9,>=1.0];

   field = [
             { name = "PWS15";
               level = "Z10";
               prob = TRUE;
               cat_thresh=[>=7.7];
             }
           ];

}

obs = {

   field = [
      {
        name = "PWS15";
        level = [ "(*,*)" ];
        GRIB1_ptv=131;
        GRIB1_center=57;
        GRIB1_subcenter=2;
        //cat_thresh =
[>=0,>=0.1,>=0.2,>=0.3,>=0.4,>=0.5,>=0.6,>=0.7,>=0.8,>=0.9,>=1.0];
        cat_thresh = [>=7.7];
      }
   ];
}

Per your comment, but still on PSTD data.  The fcst file is a
probability of windspeed > 15kts (7.7 m/s).  The observation is the
occurrence of that event at each grid point (1 or 0).

Not sure what else might be wrong.

Bob

-----Original Message-----
From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
Sent: Thursday, June 15, 2017 3:46 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 #80886] #80868
continued

Bob,

NCEP has a rather particular way of encoding probability information
into their GRIB files. They make use of the extended product
description section (PDS), and the format you've used is designed to
parse information out of there.

Instead, just go back to the config file setup that was working
previously but add:

   prob = TRUE;

That tells MET that it should interpret and process the data that
you're passing to it as probabilistic data.

fcst = {

   field = [
      {
        name = "PWS15";
        level = "Z10";
        prob = TRUE;
        cat_thresh = [ ==0.1 ];
      }
   ];
}

Does that produce PSTD output?  Also note that I've used a shorthand
convention by setting cat_thresh to "==0.1".  We enhance 6.0 to
interpret that as >=0,>=0.1,... and so on.  Or you could set it to
"==0.01" for every
1 percent or "==0.25" for every 25 percent.

Thanks,
John


On Thu, Jun 15, 2017 at 2:16 PM, robert.craig.2 at us.af.mil via RT <
met_help at ucar.edu> wrote:

>
> Thu Jun 15 14:16:32 2017: Request 80886 was acted upon.
> Transaction: Ticket created by robert.craig.2 at us.af.mil
>        Queue: met_help
>      Subject: #80868 continued
>        Owner: Nobody
>   Requestors: robert.craig.2 at us.af.mil
>       Status: new
>  Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80886
> >
>
>
> John, I tried setting the configuration file to what is in the
manual
> for probability forecasts:
>
>  fcst = {
>
>    cat_thresh = [>=0,>=0.1,>=0.2,>=0.3,>=0.4,>
> =0.5,>=0.6,>=0.7,>=0.8,>=0.9,>=1.0];
>
>    field = [
>              { name = "PROB"; level = "Z10"; prob = { name =
"PWS15";
> thresh_lo = 7.7; }}
>            ];
> }
>
> But I end up with the following:
>
> [1156 qcteam hpc9-lsn-01d /h/WXQC/testenv/bin]
> /h/WXQC/met-6.0/bin/grid_stat /h/data/global/WXQC/data/geps_
> verify/qcsave/2017060500/grib2.2017060500.0024
> /h/data/global/WXQC/data/met/tmp/03b4af71-f320-49>
> DEBUG 1: Reading user-defined grib1 MET_GRIB_TABLES file:
> /h/data/global/WXQC/data/met/config/grib2/grib1_af_131_57.txt
> DEBUG 1: Reading user-defined grib2 MET_GRIB_TABLES file:
> /h/data/global/WXQC/data/met/config/grib2/grib2_geps.txt
> DEBUG 1: Default Config File: /h/WXQC/met-6.0/share/met/
> config/GridStatConfig_default DEBUG 1: User Config File:
> /h/WXQC/met-6.0/data/config/ GridStatConfig_geps_updated DEBUG 3:
Use
> the matching forecast and observation grids.
> DEBUG 3: Grid Definition: Projection: Lat/Lon Nx: 360 Ny: 181
lat_ll:
> -90.000 lon_ll: -0.000 delta_lat: 1.000 delta_lon: 1.000
> GSL_RNG_TYPE=mt19937
> GSL_RNG_SEED=18446744073657729625
> DEBUG 1: Forecast File: /h/data/global/WXQC/data/geps_
> verify/qcsave/2017060500/grib2.2017060500.0024
> DEBUG 1: Observation File: /h/data/global/WXQC/data/met/
> tmp/03b4af71-f320-4985-a093-b51b555c7684
> DEBUG 3: Reading forecast data for PROB(PWS15>7.700)/Z10/PROB.
> WARNING:
> WARNING: MetGrib2DataFile::data_plane() - No matching record found
for
> 'PROB(PWS15>7.700)/Z10/PROB'
> WARNING:
> WARNING:
> WARNING: process_scores() -> PROB(PWS15>7.700)/Z10/PROB not found in
file:
> /h/data/global/WXQC/data/geps_verify/qcsave/2017060500/
> grib2.2017060500.0024
> WARNING:
> DEBUG 2:
> DEBUG 2:
------------------------------------------------------------
> --------------------
> DEBUG 2:
>
>
>




------------------------------------------------
Subject: #80868 continued
From: John Halley Gotway
Time: Thu Jun 15 17:32:09 2017

Bob,

Good news and bad news.  I was finally able to get some probabilistic
info
out of Grid-Stat using your data.  Unfortunately, it required two code
changes.  We have a development task defined for the next version of
MET to
review the GRIB1 and GRIB2 file interfaces and make their logic
consistent.

The processing of probabilistic data is one area where the are not
consistent.

Ultimately, I did the following:

(1) Updated src/libcode/vx_data2d_grib2/data2d_grib2.cc with the
attached
version.
(2) Updated src/libcode/vx_data2d_grib2/var_info_grib2.cc with the
attached
version.
(3) In your Grid-Stat config file, I set "cat_thresh" in the "fcst"
section
to "==0.1".
(4) In your Grid-Stat config file, I set "cat_thresh" in the "obs"
section
to "==1".

Looks like your observations are already a binary 0/1 field.  So
thresholding >=7.7 doesn't make sense.

Once I hear back from you that these changes produce the desired
result, I
can commit them and post a bugfix.

Thanks,
John

------------------------------------------------
Subject: RE: [Non-DoD Source] Re: [rt.rap.ucar.edu #80886] #80868 continued
From: robert.craig.2 at us.af.mil
Time: Fri Jun 16 08:13:12 2017

Okay that worked but I don't understand the cat_thresh=[==0.1].  What
is that telling MET to do?
When I do this in point stat the required items in the config file are
quite different - see below

  name = "PROB";
   level = "A06";

   cat_thresh =
[>=0,>=0.1,>=0.2,>=0.3,>=0.4,>=0.5,>=0.6,>=0.7,>=0.8,>=0.9,>=1.0];

   field = [
      { name = "PROB"; level = "A06"; prob = { name = "APCP";
thresh_hi = .01; }},
      { name = "PROB"; level = "A06"; prob = { name = "APCP";
thresh_lo = .05; }},
      { name = "PROB"; level = "A06"; prob = { name = "APCP";
thresh_lo = .10; }},
      { name = "PROB"; level = "A06"; prob = { name = "APCP";
thresh_lo = .25; }},
      { name = "PROB"; level = "A06"; prob = { name = "APCP";
thresh_lo = .50; }},
      { name = "PROB"; level = "A06"; prob = { name = "APCP";
thresh_lo = 1.0; }}
   ];
}

Specifically, why do I have to have cat_thresh defined as[
>=0,>=.1,etc] in point stat but have it set to cat_thresh=[==0.1] in
grid stat?  Why he difference?

Thanks
Bob
-----Original Message-----
From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
Sent: Thursday, June 15, 2017 6:32 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 #80886] #80868
continued

Bob,

Good news and bad news.  I was finally able to get some probabilistic
info out of Grid-Stat using your data.  Unfortunately, it required two
code changes.  We have a development task defined for the next version
of MET to review the GRIB1 and GRIB2 file interfaces and make their
logic consistent.

The processing of probabilistic data is one area where the are not
consistent.

Ultimately, I did the following:

(1) Updated src/libcode/vx_data2d_grib2/data2d_grib2.cc with the
attached version.
(2) Updated src/libcode/vx_data2d_grib2/var_info_grib2.cc with the
attached version.
(3) In your Grid-Stat config file, I set "cat_thresh" in the "fcst"
section to "==0.1".
(4) In your Grid-Stat config file, I set "cat_thresh" in the "obs"
section to "==1".

Looks like your observations are already a binary 0/1 field.  So
thresholding >=7.7 doesn't make sense.

Once I hear back from you that these changes produce the desired
result, I can commit them and post a bugfix.

Thanks,
John



------------------------------------------------
Subject: #80868 continued
From: John Halley Gotway
Time: Fri Jun 16 09:38:31 2017

Bob,

There is no real difference.  We added a feature in met-6.0 so that
when
verifying probabilities, the following are equivalent:

cat_thresh = [==0.1];
cat_thresh =
[>=0,>=0.1,>=0.2,>=0.3,>=0.4,>=0.5,>=0.6,>=0.7,>=0.8,>=0.9,>
=1.0];

We added this feature because we realized that defining every 1%
instead of
every 10% would be a very long list!  You can use either convention in
Point-Stat or Grid-Stat in met-6.0.

John



On Fri, Jun 16, 2017 at 8:13 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=80886 >
>
> Okay that worked but I don't understand the cat_thresh=[==0.1].
What is
> that telling MET to do?
> When I do this in point stat the required items in the config file
are
> quite different - see below
>
>   name = "PROB";
>    level = "A06";
>
>    cat_thresh = [>=0,>=0.1,>=0.2,>=0.3,>=0.4,>
> =0.5,>=0.6,>=0.7,>=0.8,>=0.9,>=1.0];
>
>    field = [
>       { name = "PROB"; level = "A06"; prob = { name = "APCP";
thresh_hi =
> .01; }},
>       { name = "PROB"; level = "A06"; prob = { name = "APCP";
thresh_lo =
> .05; }},
>       { name = "PROB"; level = "A06"; prob = { name = "APCP";
thresh_lo =
> .10; }},
>       { name = "PROB"; level = "A06"; prob = { name = "APCP";
thresh_lo =
> .25; }},
>       { name = "PROB"; level = "A06"; prob = { name = "APCP";
thresh_lo =
> .50; }},
>       { name = "PROB"; level = "A06"; prob = { name = "APCP";
thresh_lo =
> 1.0; }}
>    ];
> }
>
> Specifically, why do I have to have cat_thresh defined as[
>=0,>=.1,etc]
> in point stat but have it set to cat_thresh=[==0.1] in grid stat?
Why he
> difference?
>
> Thanks
> Bob
> -----Original Message-----
> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> Sent: Thursday, June 15, 2017 6:32 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 #80886] #80868
> continued
>
> Bob,
>
> Good news and bad news.  I was finally able to get some
probabilistic info
> out of Grid-Stat using your data.  Unfortunately, it required two
code
> changes.  We have a development task defined for the next version of
MET to
> review the GRIB1 and GRIB2 file interfaces and make their logic
consistent.
>
> The processing of probabilistic data is one area where the are not
> consistent.
>
> Ultimately, I did the following:
>
> (1) Updated src/libcode/vx_data2d_grib2/data2d_grib2.cc with the
attached
> version.
> (2) Updated src/libcode/vx_data2d_grib2/var_info_grib2.cc with the
> attached version.
> (3) In your Grid-Stat config file, I set "cat_thresh" in the "fcst"
> section to "==0.1".
> (4) In your Grid-Stat config file, I set "cat_thresh" in the "obs"
section
> to "==1".
>
> Looks like your observations are already a binary 0/1 field.  So
> thresholding >=7.7 doesn't make sense.
>
> Once I hear back from you that these changes produce the desired
result, I
> can commit them and post a bugfix.
>
> Thanks,
> John
>
>
>
>

------------------------------------------------
Subject: #80868 continued
From: John Halley Gotway
Time: Fri Jun 16 11:23:51 2017

Bob,

I just resolved the other met-help tickets you had open, but left this
one
open.

Since you've confirmed that the code changes I sent fixed the issue
you
found, I'll commit them to the repository and post them as a bugfix.
Thanks for uncovering this problem and working with me to resolve it.

Please let me know what other issues or questions come up.

Thanks,
John

On Fri, Jun 16, 2017 at 9:38 AM, John Halley Gotway <johnhg at ucar.edu>
wrote:

> Bob,
>
> There is no real difference.  We added a feature in met-6.0 so that
when
> verifying probabilities, the following are equivalent:
>
> cat_thresh = [==0.1];
> cat_thresh =
[>=0,>=0.1,>=0.2,>=0.3,>=0.4,>=0.5,>=0.6,>=0.7,>=0.8,>=0.9,>
> =1.0];
>
> We added this feature because we realized that defining every 1%
instead
> of every 10% would be a very long list!  You can use either
convention in
> Point-Stat or Grid-Stat in met-6.0.
>
> John
>
>
>
> On Fri, Jun 16, 2017 at 8:13 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=80886 >
>>
>> Okay that worked but I don't understand the cat_thresh=[==0.1].
What is
>> that telling MET to do?
>> When I do this in point stat the required items in the config file
are
>> quite different - see below
>>
>>   name = "PROB";
>>    level = "A06";
>>
>>    cat_thresh = [>=0,>=0.1,>=0.2,>=0.3,>=0.4,>
>> =0.5,>=0.6,>=0.7,>=0.8,>=0.9,>=1.0];
>>
>>    field = [
>>       { name = "PROB"; level = "A06"; prob = { name = "APCP";
thresh_hi =
>> .01; }},
>>       { name = "PROB"; level = "A06"; prob = { name = "APCP";
thresh_lo =
>> .05; }},
>>       { name = "PROB"; level = "A06"; prob = { name = "APCP";
thresh_lo =
>> .10; }},
>>       { name = "PROB"; level = "A06"; prob = { name = "APCP";
thresh_lo =
>> .25; }},
>>       { name = "PROB"; level = "A06"; prob = { name = "APCP";
thresh_lo =
>> .50; }},
>>       { name = "PROB"; level = "A06"; prob = { name = "APCP";
thresh_lo =
>> 1.0; }}
>>    ];
>> }
>>
>> Specifically, why do I have to have cat_thresh defined as[
>=0,>=.1,etc]
>> in point stat but have it set to cat_thresh=[==0.1] in grid stat?
Why he
>> difference?
>>
>> Thanks
>> Bob
>> -----Original Message-----
>> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
>> Sent: Thursday, June 15, 2017 6:32 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 #80886] #80868
>> continued
>>
>> Bob,
>>
>> Good news and bad news.  I was finally able to get some
probabilistic
>> info out of Grid-Stat using your data.  Unfortunately, it required
two code
>> changes.  We have a development task defined for the next version
of MET to
>> review the GRIB1 and GRIB2 file interfaces and make their logic
consistent.
>>
>> The processing of probabilistic data is one area where the are not
>> consistent.
>>
>> Ultimately, I did the following:
>>
>> (1) Updated src/libcode/vx_data2d_grib2/data2d_grib2.cc with the
>> attached version.
>> (2) Updated src/libcode/vx_data2d_grib2/var_info_grib2.cc with the
>> attached version.
>> (3) In your Grid-Stat config file, I set "cat_thresh" in the "fcst"
>> section to "==0.1".
>> (4) In your Grid-Stat config file, I set "cat_thresh" in the "obs"
>> section to "==1".
>>
>> Looks like your observations are already a binary 0/1 field.  So
>> thresholding >=7.7 doesn't make sense.
>>
>> Once I hear back from you that these changes produce the desired
result,
>> I can commit them and post a bugfix.
>>
>> Thanks,
>> John
>>
>>
>>
>>
>

------------------------------------------------


More information about the Met_help mailing list