[Met_help] [rt.rap.ucar.edu #80844] History for Missing Ob data in Model Ob Pair File

John Halley Gotway via RT met_help at ucar.edu
Fri Jun 16 11:20:32 MDT 2017


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

Hi John, I have progressed with our conversion of Global Ensemble verification to MET 6.0.   I am to the point where I am running grid stat using a model probability forecast and a netCDF file containing 1s or 0s, depending if the event occurred or not.  The command line I am running is:

/h/WXQC/met-6.0/bin/grid_stat /h/data/global/WXQC/data/geps_verify/qcsave/2017060200/grib2.2017060200.0024 /h/data/global/WXQC/data/met/tmp/f614c1f6-2480-46e8-928b-994913b2b1d0 /h/WXQC/met-6.0/data/config/GridStatConfig_geps_updated -outdir /h/data/global/WXQC/data/met/gdstat/geps -v 3

The listing from the run is below:

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 forecast grid.
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=1677737817
DEBUG 1: Forecast File: /h/data/global/WXQC/data/geps_verify/qcsave/2017060200/grib2.2017060200.0024
DEBUG 1: Observation File: /h/data/global/WXQC/data/met/tmp/f614c1f6-2480-46e8-928b-994913b2b1d0
DEBUG 3: Reading forecast data for PWS15/Z10.
DEBUG 3: MetGrib2DataFile::data_plane() - Found exact match for 'PWS15/Z10' in GRIB2 record 242 field 1 of GRIB2 file '/h/data/global/WXQC/data/geps_verify/qcsave/2017060200/grib2.2017060200.0024'
DEBUG 3: Reading observation data for PWS15(*,*).
DEBUG 1: Regridding forecast PWS15(*,*) to the verification grid.
WARNING:
WARNING: process_scores() -> Forecast and observation valid times do not match 20170603_000000 != 19700101_000000 for PWS15/Z10 versus PWS15(*,*).
WARNING:
DEBUG 3: Found 0 climatology mean field(s) for forecast PWS15/Z10.
DEBUG 2: Processing masking regions.
DEBUG 3: Processing grid mask: FULL
DEBUG 2:
DEBUG 2: --------------------------------------------------------------------------------
DEBUG 2:
DEBUG 3: Smoothing field using the NEAREST(1) RectangularTemplate interpolation method.
DEBUG 3: Smoothing field using the NEAREST(1) RectangularTemplate interpolation method.
DEBUG 2: Processing PWS15/Z10 versus PWS15(*,*), for interpolation method NEAREST(1), over region FULL, using 360 pairs.
DEBUG 2:
DEBUG 2: --------------------------------------------------------------------------------
DEBUG 2:
DEBUG 1: Output file: /h/data/global/WXQC/data/met/gdstat/geps/grid_stat_240000L_20170603_000000V.stat
DEBUG 1: Output file: /h/data/global/WXQC/data/met/gdstat/geps/grid_stat_240000L_20170603_000000V_pct.txt
DEBUG 1: Output file: /h/data/global/WXQC/data/met/gdstat/geps/grid_stat_240000L_20170603_000000V_pstd.txt
DEBUG 1: Output file: /h/data/global/WXQC/data/met/gdstat/geps/grid_stat_240000L_20170603_000000V_pairs.nc

When I check the pairs.nc file, the observation values are empty except for the last row.  The observations are all present in netCDF observation file so why are they missing in the pairs file?  Note the time mismatch warning - is this part of the problem?  All  of the files should need to check are on the ftp server.

Thanks
Bob



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

Subject: Missing Ob data in Model Ob Pair File
From: John Halley Gotway
Time: Tue Jun 13 16:06:01 2017

Bob,

Sorry for the delay.  Thanks for sending the sample data files.

Long story short... I think you have the "lat_ll" global attribute set
wrong in your NetCDF observation file.  You have it set to +90 degrees
but
it should be -90 degrees for the lower-left corner of your domain.

   :lat_ll = "90.0 degrees_north" ;

I updated the value using the ncatted utility:

   ncatted -a lat_ll,global,o,c,"-90.0 degrees_north"
f614c1f6-2480-46e8-928b-994913b2b1d0 new_obs.nc

And the problem you described in the NetCDF matched pairs output of
Grid-Stat goes away.

Hope that helps fix it.

Thanks,
John


On Mon, Jun 12, 2017 at 3:14 PM, robert.craig.2 at us.af.mil via RT <
met_help at ucar.edu> wrote:

>
> Mon Jun 12 15:14:11 2017: Request 80844 was acted upon.
> Transaction: Ticket created by robert.craig.2 at us.af.mil
>        Queue: met_help
>      Subject: Missing Ob data in Model Ob Pair File
>        Owner: Nobody
>   Requestors: robert.craig.2 at us.af.mil
>       Status: new
>  Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80844 >
>
>
> Hi John, I have progressed with our conversion of Global Ensemble
> verification to MET 6.0.   I am to the point where I am running grid
stat
> using a model probability forecast and a netCDF file containing 1s
or 0s,
> depending if the event occurred or not.  The command line I am
running is:
>
> /h/WXQC/met-6.0/bin/grid_stat
/h/data/global/WXQC/data/geps_verify/qcsave/
> 2017060200/grib2.2017060200.0024 /h/data/global/WXQC/data/met/
> tmp/f614c1f6-2480-46e8-928b-994913b2b1d0 /h/WXQC/met-
6.0/data/config/GridStatConfig_geps_updated
> -outdir /h/data/global/WXQC/data/met/gdstat/geps -v 3
>
> The listing from the run is below:
>
> 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 forecast grid.
> 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=1677737817
> DEBUG 1: Forecast File: /h/data/global/WXQC/data/geps_
> verify/qcsave/2017060200/grib2.2017060200.0024
> DEBUG 1: Observation File: /h/data/global/WXQC/data/met/
> tmp/f614c1f6-2480-46e8-928b-994913b2b1d0
> DEBUG 3: Reading forecast data for PWS15/Z10.
> DEBUG 3: MetGrib2DataFile::data_plane() - Found exact match for
> 'PWS15/Z10' in GRIB2 record 242 field 1 of GRIB2 file
> '/h/data/global/WXQC/data/geps_verify/qcsave/2017060200/
> grib2.2017060200.0024'
> DEBUG 3: Reading observation data for PWS15(*,*).
> DEBUG 1: Regridding forecast PWS15(*,*) to the verification grid.
> WARNING:
> WARNING: process_scores() -> Forecast and observation valid times do
not
> match 20170603_000000 != 19700101_000000 for PWS15/Z10 versus
PWS15(*,*).
> WARNING:
> DEBUG 3: Found 0 climatology mean field(s) for forecast PWS15/Z10.
> DEBUG 2: Processing masking regions.
> DEBUG 3: Processing grid mask: FULL
> DEBUG 2:
> DEBUG 2:
------------------------------------------------------------
> --------------------
> DEBUG 2:
> DEBUG 3: Smoothing field using the NEAREST(1) RectangularTemplate
> interpolation method.
> DEBUG 3: Smoothing field using the NEAREST(1) RectangularTemplate
> interpolation method.
> DEBUG 2: Processing PWS15/Z10 versus PWS15(*,*), for interpolation
method
> NEAREST(1), over region FULL, using 360 pairs.
> DEBUG 2:
> DEBUG 2:
------------------------------------------------------------
> --------------------
> DEBUG 2:
> DEBUG 1: Output file: /h/data/global/WXQC/data/met/
> gdstat/geps/grid_stat_240000L_20170603_000000V.stat
> DEBUG 1: Output file: /h/data/global/WXQC/data/met/
> gdstat/geps/grid_stat_240000L_20170603_000000V_pct.txt
> DEBUG 1: Output file: /h/data/global/WXQC/data/met/
> gdstat/geps/grid_stat_240000L_20170603_000000V_pstd.txt
> DEBUG 1: Output file: /h/data/global/WXQC/data/met/
> gdstat/geps/grid_stat_240000L_20170603_000000V_pairs.nc
>
> When I check the pairs.nc file, the observation values are empty
except
> for the last row.  The observations are all present in netCDF
observation
> file so why are they missing in the pairs file?  Note the time
mismatch
> warning - is this part of the problem?  All  of the files should
need to
> check are on the ftp server.
>
> Thanks
> Bob
>
>
>

------------------------------------------------
Subject: RE: [Non-DoD Source] Re: [rt.rap.ucar.edu #80844] Missing Ob data in Model Ob Pair File
From: robert.craig.2 at us.af.mil
Time: Wed Jun 14 09:23:35 2017

John, one follow up question.  Now that I am getting a good pairs.nc
file I need to confirm I have my data coded correctly.  The model fcst
data in the file is probabilities of WS gt 15 kts and the values range
from 0-100.  The ob data in the file is the occurrence of the event,
either 1 or 0.  The third set of data is the difference.   Should MET
have converted the model fcst data to 1 or 0s to match the obs type,
or do I have to do it.  The diff data is not correct.

Thanks
BOb

-----Original Message-----
From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
Sent: Tuesday, June 13, 2017 5:06 PM
To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
<robert.craig.2 at us.af.mil>
Cc: MELICK, CHRISTOPHER J GS-12 USAF ACC 16 WS/WXES
<christopher.melick at us.af.mil>
Subject: [Non-DoD Source] Re: [rt.rap.ucar.edu #80844] Missing Ob data
in Model Ob Pair File

Bob,

Sorry for the delay.  Thanks for sending the sample data files.

Long story short... I think you have the "lat_ll" global attribute set
wrong in your NetCDF observation file.  You have it set to +90 degrees
but it should be -90 degrees for the lower-left corner of your domain.

   :lat_ll = "90.0 degrees_north" ;

I updated the value using the ncatted utility:

   ncatted -a lat_ll,global,o,c,"-90.0 degrees_north"
f614c1f6-2480-46e8-928b-994913b2b1d0 new_obs.nc

And the problem you described in the NetCDF matched pairs output of
Grid-Stat goes away.

Hope that helps fix it.

Thanks,
John


On Mon, Jun 12, 2017 at 3:14 PM, robert.craig.2 at us.af.mil via RT <
met_help at ucar.edu> wrote:

>
> Mon Jun 12 15:14:11 2017: Request 80844 was acted upon.
> Transaction: Ticket created by robert.craig.2 at us.af.mil
>        Queue: met_help
>      Subject: Missing Ob data in Model Ob Pair File
>        Owner: Nobody
>   Requestors: robert.craig.2 at us.af.mil
>       Status: new
>  Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80844
> >
>
>
> Hi John, I have progressed with our conversion of Global Ensemble
> verification to MET 6.0.   I am to the point where I am running grid
stat
> using a model probability forecast and a netCDF file containing 1s
or
> 0s, depending if the event occurred or not.  The command line I am
running is:
>
> /h/WXQC/met-6.0/bin/grid_stat
> /h/data/global/WXQC/data/geps_verify/qcsave/
> 2017060200/grib2.2017060200.0024 /h/data/global/WXQC/data/met/
> tmp/f614c1f6-2480-46e8-928b-994913b2b1d0
> /h/WXQC/met-6.0/data/config/GridStatConfig_geps_updated
> -outdir /h/data/global/WXQC/data/met/gdstat/geps -v 3
>
> The listing from the run is below:
>
> 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 forecast grid.
> 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=1677737817
> DEBUG 1: Forecast File: /h/data/global/WXQC/data/geps_
> verify/qcsave/2017060200/grib2.2017060200.0024
> DEBUG 1: Observation File: /h/data/global/WXQC/data/met/
> tmp/f614c1f6-2480-46e8-928b-994913b2b1d0
> DEBUG 3: Reading forecast data for PWS15/Z10.
> DEBUG 3: MetGrib2DataFile::data_plane() - Found exact match for
> 'PWS15/Z10' in GRIB2 record 242 field 1 of GRIB2 file
> '/h/data/global/WXQC/data/geps_verify/qcsave/2017060200/
> grib2.2017060200.0024'
> DEBUG 3: Reading observation data for PWS15(*,*).
> DEBUG 1: Regridding forecast PWS15(*,*) to the verification grid.
> WARNING:
> WARNING: process_scores() -> Forecast and observation valid times do
> not match 20170603_000000 != 19700101_000000 for PWS15/Z10 versus
PWS15(*,*).
> WARNING:
> DEBUG 3: Found 0 climatology mean field(s) for forecast PWS15/Z10.
> DEBUG 2: Processing masking regions.
> DEBUG 3: Processing grid mask: FULL
> DEBUG 2:
> DEBUG 2:
------------------------------------------------------------
> --------------------
> DEBUG 2:
> DEBUG 3: Smoothing field using the NEAREST(1) RectangularTemplate
> interpolation method.
> DEBUG 3: Smoothing field using the NEAREST(1) RectangularTemplate
> interpolation method.
> DEBUG 2: Processing PWS15/Z10 versus PWS15(*,*), for interpolation
> method NEAREST(1), over region FULL, using 360 pairs.
> DEBUG 2:
> DEBUG 2:
------------------------------------------------------------
> --------------------
> DEBUG 2:
> DEBUG 1: Output file: /h/data/global/WXQC/data/met/
> gdstat/geps/grid_stat_240000L_20170603_000000V.stat
> DEBUG 1: Output file: /h/data/global/WXQC/data/met/
> gdstat/geps/grid_stat_240000L_20170603_000000V_pct.txt
> DEBUG 1: Output file: /h/data/global/WXQC/data/met/
> gdstat/geps/grid_stat_240000L_20170603_000000V_pstd.txt
> DEBUG 1: Output file: /h/data/global/WXQC/data/met/
> gdstat/geps/grid_stat_240000L_20170603_000000V_pairs.nc
>
> When I check the pairs.nc file, the observation values are empty
> except for the last row.  The observations are all present in netCDF
> observation file so why are they missing in the pairs file?  Note
the
> time mismatch warning - is this part of the problem?  All  of the
> files should need to check are on the ftp server.
>
> Thanks
> Bob
>
>
>




------------------------------------------------
Subject: Missing Ob data in Model Ob Pair File
From: John Halley Gotway
Time: Wed Jun 14 09:54:11 2017

Bob,

The NetCDF matched pairs file produced by Grid-Stat always contains
the
forecast data, observation data, and their difference for each field
being
verified.  When processing scalar fields, the difference makes sense.
When
processing probabilistic data, it does not.  Verification of
probabilistic
data is *not* based on the f-o differences.

We could enhance Grid-Stat to skip the writing of the difference field
for
probabilistic fields, but that logic is not currently in there.  So
you can
safely ignore the difference field for probabilistic fields.

John

On Wed, Jun 14, 2017 at 9:23 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=80844 >
>
> John, one follow up question.  Now that I am getting a good pairs.nc
file
> I need to confirm I have my data coded correctly.  The model fcst
data in
> the file is probabilities of WS gt 15 kts and the values range from
0-100.
> The ob data in the file is the occurrence of the event, either 1 or
0.  The
> third set of data is the difference.   Should MET have converted the
model
> fcst data to 1 or 0s to match the obs type, or do I have to do it.
The
> diff data is not correct.
>
> Thanks
> BOb
>
> -----Original Message-----
> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> Sent: Tuesday, June 13, 2017 5:06 PM
> To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
<robert.craig.2 at us.af.mil>
> Cc: MELICK, CHRISTOPHER J GS-12 USAF ACC 16 WS/WXES <
> christopher.melick at us.af.mil>
> Subject: [Non-DoD Source] Re: [rt.rap.ucar.edu #80844] Missing Ob
data in
> Model Ob Pair File
>
> Bob,
>
> Sorry for the delay.  Thanks for sending the sample data files.
>
> Long story short... I think you have the "lat_ll" global attribute
set
> wrong in your NetCDF observation file.  You have it set to +90
degrees but
> it should be -90 degrees for the lower-left corner of your domain.
>
>    :lat_ll = "90.0 degrees_north" ;
>
> I updated the value using the ncatted utility:
>
>    ncatted -a lat_ll,global,o,c,"-90.0 degrees_north"
> f614c1f6-2480-46e8-928b-994913b2b1d0 new_obs.nc
>
> And the problem you described in the NetCDF matched pairs output of
> Grid-Stat goes away.
>
> Hope that helps fix it.
>
> Thanks,
> John
>
>
> On Mon, Jun 12, 2017 at 3:14 PM, robert.craig.2 at us.af.mil via RT <
> met_help at ucar.edu> wrote:
>
> >
> > Mon Jun 12 15:14:11 2017: Request 80844 was acted upon.
> > Transaction: Ticket created by robert.craig.2 at us.af.mil
> >        Queue: met_help
> >      Subject: Missing Ob data in Model Ob Pair File
> >        Owner: Nobody
> >   Requestors: robert.craig.2 at us.af.mil
> >       Status: new
> >  Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80844
> > >
> >
> >
> > Hi John, I have progressed with our conversion of Global Ensemble
> > verification to MET 6.0.   I am to the point where I am running
grid stat
> > using a model probability forecast and a netCDF file containing 1s
or
> > 0s, depending if the event occurred or not.  The command line I am
> running is:
> >
> > /h/WXQC/met-6.0/bin/grid_stat
> > /h/data/global/WXQC/data/geps_verify/qcsave/
> > 2017060200/grib2.2017060200.0024 /h/data/global/WXQC/data/met/
> > tmp/f614c1f6-2480-46e8-928b-994913b2b1d0
> > /h/WXQC/met-6.0/data/config/GridStatConfig_geps_updated
> > -outdir /h/data/global/WXQC/data/met/gdstat/geps -v 3
> >
> > The listing from the run is below:
> >
> > 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 forecast grid.
> > 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=1677737817
> > DEBUG 1: Forecast File: /h/data/global/WXQC/data/geps_
> > verify/qcsave/2017060200/grib2.2017060200.0024
> > DEBUG 1: Observation File: /h/data/global/WXQC/data/met/
> > tmp/f614c1f6-2480-46e8-928b-994913b2b1d0
> > DEBUG 3: Reading forecast data for PWS15/Z10.
> > DEBUG 3: MetGrib2DataFile::data_plane() - Found exact match for
> > 'PWS15/Z10' in GRIB2 record 242 field 1 of GRIB2 file
> > '/h/data/global/WXQC/data/geps_verify/qcsave/2017060200/
> > grib2.2017060200.0024'
> > DEBUG 3: Reading observation data for PWS15(*,*).
> > DEBUG 1: Regridding forecast PWS15(*,*) to the verification grid.
> > WARNING:
> > WARNING: process_scores() -> Forecast and observation valid times
do
> > not match 20170603_000000 != 19700101_000000 for PWS15/Z10 versus
> PWS15(*,*).
> > WARNING:
> > DEBUG 3: Found 0 climatology mean field(s) for forecast PWS15/Z10.
> > DEBUG 2: Processing masking regions.
> > DEBUG 3: Processing grid mask: FULL
> > DEBUG 2:
> > DEBUG 2:
------------------------------------------------------------
> > --------------------
> > DEBUG 2:
> > DEBUG 3: Smoothing field using the NEAREST(1) RectangularTemplate
> > interpolation method.
> > DEBUG 3: Smoothing field using the NEAREST(1) RectangularTemplate
> > interpolation method.
> > DEBUG 2: Processing PWS15/Z10 versus PWS15(*,*), for interpolation
> > method NEAREST(1), over region FULL, using 360 pairs.
> > DEBUG 2:
> > DEBUG 2:
------------------------------------------------------------
> > --------------------
> > DEBUG 2:
> > DEBUG 1: Output file: /h/data/global/WXQC/data/met/
> > gdstat/geps/grid_stat_240000L_20170603_000000V.stat
> > DEBUG 1: Output file: /h/data/global/WXQC/data/met/
> > gdstat/geps/grid_stat_240000L_20170603_000000V_pct.txt
> > DEBUG 1: Output file: /h/data/global/WXQC/data/met/
> > gdstat/geps/grid_stat_240000L_20170603_000000V_pstd.txt
> > DEBUG 1: Output file: /h/data/global/WXQC/data/met/
> > gdstat/geps/grid_stat_240000L_20170603_000000V_pairs.nc
> >
> > When I check the pairs.nc file, the observation values are empty
> > except for the last row.  The observations are all present in
netCDF
> > observation file so why are they missing in the pairs file?  Note
the
> > time mismatch warning - is this part of the problem?  All  of the
> > files should need to check are on the ftp server.
> >
> > Thanks
> > Bob
> >
> >
> >
>
>
>
>
>

------------------------------------------------
Subject: RE: [Non-DoD Source] Re: [rt.rap.ucar.edu #80844] Missing Ob data in Model Ob Pair File
From: robert.craig.2 at us.af.mil
Time: Wed Jun 14 11:36:08 2017

Thanks John, if the forecast data is 0-100 and the ob data is 0-1,
will MET handle that or do I have to convert forecast data to 0-1.  I
will ignore the diff data.

Thanks
Bob

-----Original Message-----
From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
Sent: Wednesday, June 14, 2017 10:54 AM
To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
<robert.craig.2 at us.af.mil>
Cc: MELICK, CHRISTOPHER J GS-12 USAF ACC 16 WS/WXES
<christopher.melick at us.af.mil>
Subject: Re: [Non-DoD Source] Re: [rt.rap.ucar.edu #80844] Missing Ob
data in Model Ob Pair File

Bob,

The NetCDF matched pairs file produced by Grid-Stat always contains
the forecast data, observation data, and their difference for each
field being verified.  When processing scalar fields, the difference
makes sense.  When processing probabilistic data, it does not.
Verification of probabilistic data is *not* based on the f-o
differences.

We could enhance Grid-Stat to skip the writing of the difference field
for probabilistic fields, but that logic is not currently in there.
So you can safely ignore the difference field for probabilistic
fields.

John

On Wed, Jun 14, 2017 at 9:23 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=80844 >
>
> John, one follow up question.  Now that I am getting a good pairs.nc
> file I need to confirm I have my data coded correctly.  The model
fcst
> data in the file is probabilities of WS gt 15 kts and the values
range from 0-100.
> The ob data in the file is the occurrence of the event, either 1 or
0.  The
> third set of data is the difference.   Should MET have converted the
model
> fcst data to 1 or 0s to match the obs type, or do I have to do it.
> The diff data is not correct.
>
> Thanks
> BOb
>
> -----Original Message-----
> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> Sent: Tuesday, June 13, 2017 5:06 PM
> To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
> <robert.craig.2 at us.af.mil>
> Cc: MELICK, CHRISTOPHER J GS-12 USAF ACC 16 WS/WXES <
> christopher.melick at us.af.mil>
> Subject: [Non-DoD Source] Re: [rt.rap.ucar.edu #80844] Missing Ob
data
> in Model Ob Pair File
>
> Bob,
>
> Sorry for the delay.  Thanks for sending the sample data files.
>
> Long story short... I think you have the "lat_ll" global attribute
set
> wrong in your NetCDF observation file.  You have it set to +90
degrees
> but it should be -90 degrees for the lower-left corner of your
domain.
>
>    :lat_ll = "90.0 degrees_north" ;
>
> I updated the value using the ncatted utility:
>
>    ncatted -a lat_ll,global,o,c,"-90.0 degrees_north"
> f614c1f6-2480-46e8-928b-994913b2b1d0 new_obs.nc
>
> And the problem you described in the NetCDF matched pairs output of
> Grid-Stat goes away.
>
> Hope that helps fix it.
>
> Thanks,
> John
>
>
> On Mon, Jun 12, 2017 at 3:14 PM, robert.craig.2 at us.af.mil via RT <
> met_help at ucar.edu> wrote:
>
> >
> > Mon Jun 12 15:14:11 2017: Request 80844 was acted upon.
> > Transaction: Ticket created by robert.craig.2 at us.af.mil
> >        Queue: met_help
> >      Subject: Missing Ob data in Model Ob Pair File
> >        Owner: Nobody
> >   Requestors: robert.craig.2 at us.af.mil
> >       Status: new
> >  Ticket <URL:
> > https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80844
> > >
> >
> >
> > Hi John, I have progressed with our conversion of Global Ensemble
> > verification to MET 6.0.   I am to the point where I am running
grid stat
> > using a model probability forecast and a netCDF file containing 1s
> > or 0s, depending if the event occurred or not.  The command line I
> > am
> running is:
> >
> > /h/WXQC/met-6.0/bin/grid_stat
> > /h/data/global/WXQC/data/geps_verify/qcsave/
> > 2017060200/grib2.2017060200.0024 /h/data/global/WXQC/data/met/
> > tmp/f614c1f6-2480-46e8-928b-994913b2b1d0
> > /h/WXQC/met-6.0/data/config/GridStatConfig_geps_updated
> > -outdir /h/data/global/WXQC/data/met/gdstat/geps -v 3
> >
> > The listing from the run is below:
> >
> > 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 forecast grid.
> > 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=1677737817
> > DEBUG 1: Forecast File: /h/data/global/WXQC/data/geps_
> > verify/qcsave/2017060200/grib2.2017060200.0024
> > DEBUG 1: Observation File: /h/data/global/WXQC/data/met/
> > tmp/f614c1f6-2480-46e8-928b-994913b2b1d0
> > DEBUG 3: Reading forecast data for PWS15/Z10.
> > DEBUG 3: MetGrib2DataFile::data_plane() - Found exact match for
> > 'PWS15/Z10' in GRIB2 record 242 field 1 of GRIB2 file
> > '/h/data/global/WXQC/data/geps_verify/qcsave/2017060200/
> > grib2.2017060200.0024'
> > DEBUG 3: Reading observation data for PWS15(*,*).
> > DEBUG 1: Regridding forecast PWS15(*,*) to the verification grid.
> > WARNING:
> > WARNING: process_scores() -> Forecast and observation valid times
do
> > not match 20170603_000000 != 19700101_000000 for PWS15/Z10 versus
> PWS15(*,*).
> > WARNING:
> > DEBUG 3: Found 0 climatology mean field(s) for forecast PWS15/Z10.
> > DEBUG 2: Processing masking regions.
> > DEBUG 3: Processing grid mask: FULL
> > DEBUG 2:
> > DEBUG 2:
> > ------------------------------------------------------------
> > --------------------
> > DEBUG 2:
> > DEBUG 3: Smoothing field using the NEAREST(1) RectangularTemplate
> > interpolation method.
> > DEBUG 3: Smoothing field using the NEAREST(1) RectangularTemplate
> > interpolation method.
> > DEBUG 2: Processing PWS15/Z10 versus PWS15(*,*), for interpolation
> > method NEAREST(1), over region FULL, using 360 pairs.
> > DEBUG 2:
> > DEBUG 2:
> > ------------------------------------------------------------
> > --------------------
> > DEBUG 2:
> > DEBUG 1: Output file: /h/data/global/WXQC/data/met/
> > gdstat/geps/grid_stat_240000L_20170603_000000V.stat
> > DEBUG 1: Output file: /h/data/global/WXQC/data/met/
> > gdstat/geps/grid_stat_240000L_20170603_000000V_pct.txt
> > DEBUG 1: Output file: /h/data/global/WXQC/data/met/
> > gdstat/geps/grid_stat_240000L_20170603_000000V_pstd.txt
> > DEBUG 1: Output file: /h/data/global/WXQC/data/met/
> > gdstat/geps/grid_stat_240000L_20170603_000000V_pairs.nc
> >
> > When I check the pairs.nc file, the observation values are empty
> > except for the last row.  The observations are all present in
netCDF
> > observation file so why are they missing in the pairs file?  Note
> > the time mismatch warning - is this part of the problem?  All  of
> > the files should need to check are on the ftp server.
> >
> > Thanks
> > Bob
> >
> >
> >
>
>
>
>
>




------------------------------------------------
Subject: Missing Ob data in Model Ob Pair File
From: John Halley Gotway
Time: Wed Jun 14 13:22:14 2017

Bob,

The input probabilistic data can either have a range of 0 to 1 or 0 to
100.  When processing probabilistic data, Grid-Stat and Point-Stat
check
the range of the input values.  If they're 0 - 100, it automatically
rescales them to 0 - 1 by dividing by 100.

So you can use either range in the input, but the output will be in
the
range of 0 - 1.

John

On Wed, Jun 14, 2017 at 11:36 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=80844 >
>
> Thanks John, if the forecast data is 0-100 and the ob data is 0-1,
will
> MET handle that or do I have to convert forecast data to 0-1.  I
will
> ignore the diff data.
>
> Thanks
> Bob
>
> -----Original Message-----
> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> Sent: Wednesday, June 14, 2017 10:54 AM
> To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
<robert.craig.2 at us.af.mil>
> Cc: MELICK, CHRISTOPHER J GS-12 USAF ACC 16 WS/WXES <
> christopher.melick at us.af.mil>
> Subject: Re: [Non-DoD Source] Re: [rt.rap.ucar.edu #80844] Missing
Ob
> data in Model Ob Pair File
>
> Bob,
>
> The NetCDF matched pairs file produced by Grid-Stat always contains
the
> forecast data, observation data, and their difference for each field
being
> verified.  When processing scalar fields, the difference makes
sense.  When
> processing probabilistic data, it does not.  Verification of
probabilistic
> data is *not* based on the f-o differences.
>
> We could enhance Grid-Stat to skip the writing of the difference
field for
> probabilistic fields, but that logic is not currently in there.  So
you can
> safely ignore the difference field for probabilistic fields.
>
> John
>
> On Wed, Jun 14, 2017 at 9:23 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=80844 >
> >
> > John, one follow up question.  Now that I am getting a good
pairs.nc
> > file I need to confirm I have my data coded correctly.  The model
fcst
> > data in the file is probabilities of WS gt 15 kts and the values
range
> from 0-100.
> > The ob data in the file is the occurrence of the event, either 1
or 0.
> The
> > third set of data is the difference.   Should MET have converted
the
> model
> > fcst data to 1 or 0s to match the obs type, or do I have to do it.
> > The diff data is not correct.
> >
> > Thanks
> > BOb
> >
> > -----Original Message-----
> > From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> > Sent: Tuesday, June 13, 2017 5:06 PM
> > To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
> > <robert.craig.2 at us.af.mil>
> > Cc: MELICK, CHRISTOPHER J GS-12 USAF ACC 16 WS/WXES <
> > christopher.melick at us.af.mil>
> > Subject: [Non-DoD Source] Re: [rt.rap.ucar.edu #80844] Missing Ob
data
> > in Model Ob Pair File
> >
> > Bob,
> >
> > Sorry for the delay.  Thanks for sending the sample data files.
> >
> > Long story short... I think you have the "lat_ll" global attribute
set
> > wrong in your NetCDF observation file.  You have it set to +90
degrees
> > but it should be -90 degrees for the lower-left corner of your
domain.
> >
> >    :lat_ll = "90.0 degrees_north" ;
> >
> > I updated the value using the ncatted utility:
> >
> >    ncatted -a lat_ll,global,o,c,"-90.0 degrees_north"
> > f614c1f6-2480-46e8-928b-994913b2b1d0 new_obs.nc
> >
> > And the problem you described in the NetCDF matched pairs output
of
> > Grid-Stat goes away.
> >
> > Hope that helps fix it.
> >
> > Thanks,
> > John
> >
> >
> > On Mon, Jun 12, 2017 at 3:14 PM, robert.craig.2 at us.af.mil via RT <
> > met_help at ucar.edu> wrote:
> >
> > >
> > > Mon Jun 12 15:14:11 2017: Request 80844 was acted upon.
> > > Transaction: Ticket created by robert.craig.2 at us.af.mil
> > >        Queue: met_help
> > >      Subject: Missing Ob data in Model Ob Pair File
> > >        Owner: Nobody
> > >   Requestors: robert.craig.2 at us.af.mil
> > >       Status: new
> > >  Ticket <URL:
> > > https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80844
> > > >
> > >
> > >
> > > Hi John, I have progressed with our conversion of Global
Ensemble
> > > verification to MET 6.0.   I am to the point where I am running
grid
> stat
> > > using a model probability forecast and a netCDF file containing
1s
> > > or 0s, depending if the event occurred or not.  The command line
I
> > > am
> > running is:
> > >
> > > /h/WXQC/met-6.0/bin/grid_stat
> > > /h/data/global/WXQC/data/geps_verify/qcsave/
> > > 2017060200/grib2.2017060200.0024 /h/data/global/WXQC/data/met/
> > > tmp/f614c1f6-2480-46e8-928b-994913b2b1d0
> > > /h/WXQC/met-6.0/data/config/GridStatConfig_geps_updated
> > > -outdir /h/data/global/WXQC/data/met/gdstat/geps -v 3
> > >
> > > The listing from the run is below:
> > >
> > > 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 forecast grid.
> > > 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=1677737817
> > > DEBUG 1: Forecast File: /h/data/global/WXQC/data/geps_
> > > verify/qcsave/2017060200/grib2.2017060200.0024
> > > DEBUG 1: Observation File: /h/data/global/WXQC/data/met/
> > > tmp/f614c1f6-2480-46e8-928b-994913b2b1d0
> > > DEBUG 3: Reading forecast data for PWS15/Z10.
> > > DEBUG 3: MetGrib2DataFile::data_plane() - Found exact match for
> > > 'PWS15/Z10' in GRIB2 record 242 field 1 of GRIB2 file
> > > '/h/data/global/WXQC/data/geps_verify/qcsave/2017060200/
> > > grib2.2017060200.0024'
> > > DEBUG 3: Reading observation data for PWS15(*,*).
> > > DEBUG 1: Regridding forecast PWS15(*,*) to the verification
grid.
> > > WARNING:
> > > WARNING: process_scores() -> Forecast and observation valid
times do
> > > not match 20170603_000000 != 19700101_000000 for PWS15/Z10
versus
> > PWS15(*,*).
> > > WARNING:
> > > DEBUG 3: Found 0 climatology mean field(s) for forecast
PWS15/Z10.
> > > DEBUG 2: Processing masking regions.
> > > DEBUG 3: Processing grid mask: FULL
> > > DEBUG 2:
> > > DEBUG 2:
> > > ------------------------------------------------------------
> > > --------------------
> > > DEBUG 2:
> > > DEBUG 3: Smoothing field using the NEAREST(1)
RectangularTemplate
> > > interpolation method.
> > > DEBUG 3: Smoothing field using the NEAREST(1)
RectangularTemplate
> > > interpolation method.
> > > DEBUG 2: Processing PWS15/Z10 versus PWS15(*,*), for
interpolation
> > > method NEAREST(1), over region FULL, using 360 pairs.
> > > DEBUG 2:
> > > DEBUG 2:
> > > ------------------------------------------------------------
> > > --------------------
> > > DEBUG 2:
> > > DEBUG 1: Output file: /h/data/global/WXQC/data/met/
> > > gdstat/geps/grid_stat_240000L_20170603_000000V.stat
> > > DEBUG 1: Output file: /h/data/global/WXQC/data/met/
> > > gdstat/geps/grid_stat_240000L_20170603_000000V_pct.txt
> > > DEBUG 1: Output file: /h/data/global/WXQC/data/met/
> > > gdstat/geps/grid_stat_240000L_20170603_000000V_pstd.txt
> > > DEBUG 1: Output file: /h/data/global/WXQC/data/met/
> > > gdstat/geps/grid_stat_240000L_20170603_000000V_pairs.nc
> > >
> > > When I check the pairs.nc file, the observation values are empty
> > > except for the last row.  The observations are all present in
netCDF
> > > observation file so why are they missing in the pairs file?
Note
> > > the time mismatch warning - is this part of the problem?  All
of
> > > the files should need to check are on the ftp server.
> > >
> > > Thanks
> > > Bob
> > >
> > >
> > >
> >
> >
> >
> >
> >
>
>
>
>
>

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


More information about the Met_help mailing list