[Met_help] [rt.rap.ucar.edu #91147] History for Point Stat wants LANDSF

Fri Jul 19 13:53:19 MDT 2019

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

John, I have run into a new error message I haven't seen before in 8.1.
When running point_stat I get the following error message:

Using config file ->
/h/data/global/WXQC/data/met/config/met_config/PointStatConfig_precip_hira_b
altic4

Running MET command string ->  ['/h/MET/bin/point_stat',
'/home/specmdev/scratch/test/baltic4/PS.557WW_SC.U_DI.C_GP.GALWEM-RD_GR.C4KM
_AR.BALTIC_DD.20180102_CY.00_FH.018_DF.GR2',
'/h/data/global/WXQC/data/met/tmp/eda2fe80-a698-4d9f-b515-1199794d5df4',
'/h/data/global/WXQC/data/met/config/met_config/PointStatConfig_precip_hira_
baltic4_updated', '-outdir',
'/h/data/global/WXQC/data/met/ptstat/mdlob_pairs/baltic4/TP', '-v', '3']

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/MET/share/met/config/PointStatConfig_default

DEBUG 1: User Config File:
/h/data/global/WXQC/data/met/config/met_config/PointStatConfig_precip_hira_b
altic4_updated

DEBUG 3: 

DEBUG 3: Multiple GRIB2 table entries match lookup criteria (parm_name =
APCP):

DEBUG 3:   parm_name: APCP, index_a = 0, grib2_mtab = 1, grib2_cntr = 57,
grib2_ltab = 1, index_b = 1, index_c = 8

DEBUG 3:   parm_name: APCP, index_a = 0, grib2_mtab = 1, grib2_cntr = 57,
grib2_ltab = 1, index_b = 1, index_c = 8

DEBUG 3:   parm_name: APCP, index_a = 0, grib2_mtab = 1, grib2_cntr = 57,
grib2_ltab = 1, index_b = 1, index_c = 8

DEBUG 3:   parm_name: APCP, index_a = 0, grib2_mtab = 1, grib2_cntr = 57,
grib2_ltab = 1, index_b = 1, index_c = 8

DEBUG 3:   parm_name: APCP, index_a = 0, grib2_mtab = 1, grib2_cntr = 57,
grib2_ltab = 1, index_b = 1, index_c = 8

DEBUG 3:   parm_name: APCP, index_a = 0, grib2_mtab = 1, grib2_cntr = 57,
grib2_ltab = 1, index_b = 1, index_c = 8

DEBUG 3:   parm_name: APCP, index_a = 0, grib2_mtab = 14, grib2_cntr = 57,
grib2_ltab = 0, index_b = 1, index_c = 8

DEBUG 3:   parm_name: APCP, index_a = 0, grib2_mtab = 1, grib2_cntr = 57,
grib2_ltab = 1, index_b = 1, index_c = 8

DEBUG 3:   parm_name: APCP, index_a = 0, grib2_mtab = 1, grib2_cntr = 57,
grib2_ltab = 1, index_b = 1, index_c = 8

DEBUG 3:   parm_name: APCP, index_a = 0, grib2_mtab = 1, grib2_cntr = 57,
grib2_ltab = 1, index_b = 1, index_c = 8

DEBUG 3:   parm_name: APCP, index_a = 0, grib2_mtab = 1, grib2_cntr = 0,
grib2_ltab = 0, index_b = 1, index_c = 8

DEBUG 3: Using the first match found:   parm_name: APCP, index_a = 0,
grib2_mtab = 1, grib2_cntr = 57, grib2_ltab = 1, index_b = 1, index_c = 8

DEBUG 3: 

GSL_RNG_TYPE=mt19937

GSL_RNG_SEED=1304572253

DEBUG 1: Forecast File:
/home/specmdev/scratch/test/baltic4/PS.557WW_SC.U_DI.C_GP.GALWEM-RD_GR.C4KM_
AR.BALTIC_DD.20180102_CY.00_FH.018_DF.GR2

DEBUG 1: Observation File:
/h/data/global/WXQC/data/met/tmp/eda2fe80-a698-4d9f-b515-1199794d5df4

DEBUG 3: MetGrib2DataFile::data_plane_array() -> Found exact match for
"APCP/A1" in GRIB2 record 164 field 1 of GRIB2 file
"/home/specmdev/scratch/test/baltic4/PS.557WW_SC.U_DI.C_GP.GALWEM-RD_GR.C4KM
_AR.BALTIC_DD.20180102_CY.00_FH.018_DF.GR2"

DEBUG 3: Applying conversion function.

DEBUG 2: 

DEBUG 2:
----------------------------------------------------------------------------
----

DEBUG 2: 

DEBUG 2: Reading data for APCP/A1.

DEBUG 3: Use the forecast grid.

DEBUG 3: Grid Definition: Projection: Rotated Lat/Lon Nx: 408 Ny: 420
rot_lat_ll: -7.542 rot_lon_ll: 8.326 delta_rot_lat: 0.036 delta_rot_lon:
0.036 true_lat_south_pole: -34.515 true_lon_south_pole: -22.179
aux_rotation: 0.000

DEBUG 2: Processing masking regions.

DEBUG 3: Processing grid mask: FULL

DEBUG 2: Processing geography data.

ERROR  : 

ERROR  : PointStatVxOpt::set_vx_pd() -> "message_type_group_map" must
contain an entry for "LANDSF".

ERROR  :

So, I went back to my config file and added LANDSF to the values where keys
implied the surface but that didn't fix the problem ( see attached).  Does
LANDSF need to be a key and if so what would the value be?  What am I
missing?

Thanks

Bob

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

Subject: Point Stat wants LANDSF
From: John Halley Gotway
Time: Fri Jul 19 10:26:58 2019

Hi Bob,

OK, this one is pretty easy to address.  met-8.1 includes some logic
for
using land and topography information when verifying against point
observations.  But that enhancement requires additional entries in the
config file to control it.  Specifically, the entries in the
message_type_group_map need to be updated.  I assume you are using an
earlier version of that config file when running the met-8.1 code,
which we
do here a lot too.

Listed below is the setting from the met-8.1 default point_stat config
file
(
https://github.com/NCAR/MET/blob/master_v8.1/met/data/config/PointStatConfig_default
):
//
// Mapping of message type group name to comma-separated list of
values.
//
message_type_group_map = [
{ key = "SURFACE"; val = "ADPSFC,SFCSHP,MSONET"; },
{ key = "ANYAIR"; val = "AIRCAR,AIRCFT"; },
{ key = "ANYSFC"; val = "ADPSFC,SFCSHP,ADPUPA,PROFLR,MSONET"; },
{ key = "ONLYSF"; val = "ADPSFC,SFCSHP"; },
{ key = "LANDSF"; val = "ADPSFC,MSONET"; },
{ key = "WATERSF"; val = "SFCSHP"; }
];

You can either remove that setting entirely from your point_stat
config
file (and the default will be used), or you can update the one in your
point_stat config file to include all of the entries listed above.

Thanks,
John
On Fri, Jul 19, 2019 at 7:36 AM robert.craig.2 at us.af.mil via RT <
met_help at ucar.edu> wrote:

>
> Fri Jul 19 07:36:26 2019: Request 91147 was acted upon.
> Transaction: Ticket created by robert.craig.2 at us.af.mil
>        Queue: met_help
>      Subject: Point Stat wants LANDSF
>        Owner: Nobody
>   Requestors: robert.craig.2 at us.af.mil
>       Status: new
>  Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=91147 >
>
>
> John, I have run into a new error message I haven't seen before in
8.1.
> When running point_stat I get the following error message:
>
>
>
> Using config file ->
>
>
/h/data/global/WXQC/data/met/config/met_config/PointStatConfig_precip_hira_b
> altic4
>
> Running MET command string ->  ['/h/MET/bin/point_stat',
>
> '/home/specmdev/scratch/test/baltic4/PS.557WW_SC.U_DI.C_GP.GALWEM-
RD_GR.C4KM
> _AR.BALTIC_DD.20180102_CY.00_FH.018_DF.GR2',
> '/h/data/global/WXQC/data/met/tmp/eda2fe80-a698-4d9f-b515-
1199794d5df4',
>
>
'/h/data/global/WXQC/data/met/config/met_config/PointStatConfig_precip_hira_
> baltic4_updated', '-outdir',
> '/h/data/global/WXQC/data/met/ptstat/mdlob_pairs/baltic4/TP', '-v',
'3']
>
> 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/MET/share/met/config/PointStatConfig_default
>
> DEBUG 1: User Config File:
>
>
/h/data/global/WXQC/data/met/config/met_config/PointStatConfig_precip_hira_b
> altic4_updated
>
> DEBUG 3:
>
> DEBUG 3: Multiple GRIB2 table entries match lookup criteria
(parm_name =
> APCP):
>
> DEBUG 3:   parm_name: APCP, index_a = 0, grib2_mtab = 1, grib2_cntr
= 57,
> grib2_ltab = 1, index_b = 1, index_c = 8
>
> DEBUG 3:   parm_name: APCP, index_a = 0, grib2_mtab = 1, grib2_cntr
= 57,
> grib2_ltab = 1, index_b = 1, index_c = 8
>
> DEBUG 3:   parm_name: APCP, index_a = 0, grib2_mtab = 1, grib2_cntr
= 57,
> grib2_ltab = 1, index_b = 1, index_c = 8
>
> DEBUG 3:   parm_name: APCP, index_a = 0, grib2_mtab = 1, grib2_cntr
= 57,
> grib2_ltab = 1, index_b = 1, index_c = 8
>
> DEBUG 3:   parm_name: APCP, index_a = 0, grib2_mtab = 1, grib2_cntr
= 57,
> grib2_ltab = 1, index_b = 1, index_c = 8
>
> DEBUG 3:   parm_name: APCP, index_a = 0, grib2_mtab = 1, grib2_cntr
= 57,
> grib2_ltab = 1, index_b = 1, index_c = 8
>
> DEBUG 3:   parm_name: APCP, index_a = 0, grib2_mtab = 14, grib2_cntr
= 57,
> grib2_ltab = 0, index_b = 1, index_c = 8
>
> DEBUG 3:   parm_name: APCP, index_a = 0, grib2_mtab = 1, grib2_cntr
= 57,
> grib2_ltab = 1, index_b = 1, index_c = 8
>
> DEBUG 3:   parm_name: APCP, index_a = 0, grib2_mtab = 1, grib2_cntr
= 57,
> grib2_ltab = 1, index_b = 1, index_c = 8
>
> DEBUG 3:   parm_name: APCP, index_a = 0, grib2_mtab = 1, grib2_cntr
= 57,
> grib2_ltab = 1, index_b = 1, index_c = 8
>
> DEBUG 3:   parm_name: APCP, index_a = 0, grib2_mtab = 1, grib2_cntr
= 0,
> grib2_ltab = 0, index_b = 1, index_c = 8
>
> DEBUG 3: Using the first match found:   parm_name: APCP, index_a =
0,
> grib2_mtab = 1, grib2_cntr = 57, grib2_ltab = 1, index_b = 1,
index_c = 8
>
> DEBUG 3:
>
> GSL_RNG_TYPE=mt19937
>
> GSL_RNG_SEED=1304572253
>
> DEBUG 1: Forecast File:
>
> /home/specmdev/scratch/test/baltic4/PS.557WW_SC.U_DI.C_GP.GALWEM-
RD_GR.C4KM_
> AR.BALTIC_DD.20180102_CY.00_FH.018_DF.GR2
>
> DEBUG 1: Observation File:
> /h/data/global/WXQC/data/met/tmp/eda2fe80-a698-4d9f-b515-
1199794d5df4
>
> DEBUG 3: MetGrib2DataFile::data_plane_array() -> Found exact match
for
> "APCP/A1" in GRIB2 record 164 field 1 of GRIB2 file
>
> "/home/specmdev/scratch/test/baltic4/PS.557WW_SC.U_DI.C_GP.GALWEM-
RD_GR.C4KM
> _AR.BALTIC_DD.20180102_CY.00_FH.018_DF.GR2"
>
> DEBUG 3: Applying conversion function.
>
> DEBUG 2:
>
> DEBUG 2:
>
>
----------------------------------------------------------------------------
> ----
>
> DEBUG 2:
>
> DEBUG 2: Reading data for APCP/A1.
>
> DEBUG 3: Use the forecast grid.
>
> DEBUG 3: Grid Definition: Projection: Rotated Lat/Lon Nx: 408 Ny:
420
> rot_lat_ll: -7.542 rot_lon_ll: 8.326 delta_rot_lat: 0.036
delta_rot_lon:
> 0.036 true_lat_south_pole: -34.515 true_lon_south_pole: -22.179
> aux_rotation: 0.000
>
> DEBUG 2: Processing masking regions.
>
> DEBUG 3: Processing grid mask: FULL
>
> DEBUG 2: Processing geography data.
>
> ERROR  :
>
> ERROR  : PointStatVxOpt::set_vx_pd() -> "message_type_group_map"
must
> contain an entry for "LANDSF".
>
> ERROR  :
>
>
>
> So, I went back to my config file and added LANDSF to the values
where keys
> implied the surface but that didn't fix the problem ( see attached).
Does
> LANDSF need to be a key and if so what would the value be?  What am
I
> missing?
>
>
>
> Thanks
>
> Bob
>
>
>

------------------------------------------------
Subject: RE: [Non-DoD Source] Re: [rt.rap.ucar.edu #91147] Point Stat wants LANDSF
From: robert.craig.2 at us.af.mil
Time: Fri Jul 19 12:52:14 2019

Thanks John - that fixed the problem but revealed another which I will
put in separate ticket.

-----Original Message-----
From: John Halley Gotway via RT <met_help at ucar.edu>
Sent: Friday, July 19, 2019 11:27 AM
To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
<robert.craig.2 at us.af.mil>
Cc: SITTEL, MATTHEW C CTR USAF AFMC AFLCMC/HBAW-OL
<matthew.sittel.ctr at us.af.mil>
Subject: [Non-DoD Source] Re: [rt.rap.ucar.edu #91147] Point Stat
wants LANDSF

Hi Bob,

OK, this one is pretty easy to address.  met-8.1 includes some logic
for using land and topography information when verifying against point
observations.  But that enhancement requires additional entries in the
config file to control it.  Specifically, the entries in the
message_type_group_map need to be updated.  I assume you are using an
earlier version of that config file when running the met-8.1 code,
which we do here a lot too.

Listed below is the setting from the met-8.1 default point_stat config
file (
https://github.com/NCAR/MET/blob/master_v8.1/met/data/config/PointStatConfig_default
):
//
// Mapping of message type group name to comma-separated list of
values.
//
message_type_group_map = [
{ key = "SURFACE"; val = "ADPSFC,SFCSHP,MSONET"; }, { key = "ANYAIR";
val = "AIRCAR,AIRCFT"; }, { key = "ANYSFC"; val =
"ADPSFC,SFCSHP,ADPUPA,PROFLR,MSONET"; }, { key = "ONLYSF"; val =
"ADPSFC,SFCSHP"; }, { key = "LANDSF"; val = "ADPSFC,MSONET"; }, { key
= "WATERSF"; val = "SFCSHP"; } ];

You can either remove that setting entirely from your point_stat
config file (and the default will be used), or you can update the one
in your point_stat config file to include all of the entries listed
above.

Thanks,
John
On Fri, Jul 19, 2019 at 7:36 AM robert.craig.2 at us.af.mil via RT <
met_help at ucar.edu> wrote:

>
> Fri Jul 19 07:36:26 2019: Request 91147 was acted upon.
> Transaction: Ticket created by robert.craig.2 at us.af.mil
>        Queue: met_help
>      Subject: Point Stat wants LANDSF
>        Owner: Nobody
>   Requestors: robert.craig.2 at us.af.mil
>       Status: new
>  Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=91147
> >
>
>
> John, I have run into a new error message I haven't seen before in
8.1.
> When running point_stat I get the following error message:
>
>
>
> Using config file ->
>
>
/h/data/global/WXQC/data/met/config/met_config/PointStatConfig_precip_
> hira_b
> altic4
>
> Running MET command string ->  ['/h/MET/bin/point_stat',
>
> '/home/specmdev/scratch/test/baltic4/PS.557WW_SC.U_DI.C_GP.GALWEM-
RD_G
> R.C4KM _AR.BALTIC_DD.20180102_CY.00_FH.018_DF.GR2',
> '/h/data/global/WXQC/data/met/tmp/eda2fe80-a698-4d9f-b515-
1199794d5df4
> ',
>
>
'/h/data/global/WXQC/data/met/config/met_config/PointStatConfig_precip
> _hira_
> baltic4_updated', '-outdir',
> '/h/data/global/WXQC/data/met/ptstat/mdlob_pairs/baltic4/TP', '-v',
> '3']
>
> 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/MET/share/met/config/PointStatConfig_default
>
> DEBUG 1: User Config File:
>
>
/h/data/global/WXQC/data/met/config/met_config/PointStatConfig_precip_
> hira_b
> altic4_updated
>
> DEBUG 3:
>
> DEBUG 3: Multiple GRIB2 table entries match lookup criteria
(parm_name
> =
> APCP):
>
> DEBUG 3:   parm_name: APCP, index_a = 0, grib2_mtab = 1, grib2_cntr
= 57,
> grib2_ltab = 1, index_b = 1, index_c = 8
>
> DEBUG 3:   parm_name: APCP, index_a = 0, grib2_mtab = 1, grib2_cntr
= 57,
> grib2_ltab = 1, index_b = 1, index_c = 8
>
> DEBUG 3:   parm_name: APCP, index_a = 0, grib2_mtab = 1, grib2_cntr
= 57,
> grib2_ltab = 1, index_b = 1, index_c = 8
>
> DEBUG 3:   parm_name: APCP, index_a = 0, grib2_mtab = 1, grib2_cntr
= 57,
> grib2_ltab = 1, index_b = 1, index_c = 8
>
> DEBUG 3:   parm_name: APCP, index_a = 0, grib2_mtab = 1, grib2_cntr
= 57,
> grib2_ltab = 1, index_b = 1, index_c = 8
>
> DEBUG 3:   parm_name: APCP, index_a = 0, grib2_mtab = 1, grib2_cntr
= 57,
> grib2_ltab = 1, index_b = 1, index_c = 8
>
> DEBUG 3:   parm_name: APCP, index_a = 0, grib2_mtab = 14, grib2_cntr
= 57,
> grib2_ltab = 0, index_b = 1, index_c = 8
>
> DEBUG 3:   parm_name: APCP, index_a = 0, grib2_mtab = 1, grib2_cntr
= 57,
> grib2_ltab = 1, index_b = 1, index_c = 8
>
> DEBUG 3:   parm_name: APCP, index_a = 0, grib2_mtab = 1, grib2_cntr
= 57,
> grib2_ltab = 1, index_b = 1, index_c = 8
>
> DEBUG 3:   parm_name: APCP, index_a = 0, grib2_mtab = 1, grib2_cntr
= 57,
> grib2_ltab = 1, index_b = 1, index_c = 8
>
> DEBUG 3:   parm_name: APCP, index_a = 0, grib2_mtab = 1, grib2_cntr
= 0,
> grib2_ltab = 0, index_b = 1, index_c = 8
>
> DEBUG 3: Using the first match found:   parm_name: APCP, index_a =
0,
> grib2_mtab = 1, grib2_cntr = 57, grib2_ltab = 1, index_b = 1,
index_c
> = 8
>
> DEBUG 3:
>
> GSL_RNG_TYPE=mt19937
>
> GSL_RNG_SEED=1304572253
>
> DEBUG 1: Forecast File:
>
> /home/specmdev/scratch/test/baltic4/PS.557WW_SC.U_DI.C_GP.GALWEM-
RD_GR
> .C4KM_
> AR.BALTIC_DD.20180102_CY.00_FH.018_DF.GR2
>
> DEBUG 1: Observation File:
> /h/data/global/WXQC/data/met/tmp/eda2fe80-a698-4d9f-b515-
1199794d5df4
>
> DEBUG 3: MetGrib2DataFile::data_plane_array() -> Found exact match
for
> "APCP/A1" in GRIB2 record 164 field 1 of GRIB2 file
>
> "/home/specmdev/scratch/test/baltic4/PS.557WW_SC.U_DI.C_GP.GALWEM-
RD_G
> R.C4KM _AR.BALTIC_DD.20180102_CY.00_FH.018_DF.GR2"
>
> DEBUG 3: Applying conversion function.
>
> DEBUG 2:
>
> DEBUG 2:
>
>
----------------------------------------------------------------------
> ------
> ----
>
> DEBUG 2:
>
> DEBUG 2: Reading data for APCP/A1.
>
> DEBUG 3: Use the forecast grid.
>
> DEBUG 3: Grid Definition: Projection: Rotated Lat/Lon Nx: 408 Ny:
420
> rot_lat_ll: -7.542 rot_lon_ll: 8.326 delta_rot_lat: 0.036
delta_rot_lon:
> 0.036 true_lat_south_pole: -34.515 true_lon_south_pole: -22.179
> aux_rotation: 0.000
>
> DEBUG 2: Processing masking regions.
>
> DEBUG 3: Processing grid mask: FULL
>
> DEBUG 2: Processing geography data.
>
> ERROR  :
>
> ERROR  : PointStatVxOpt::set_vx_pd() -> "message_type_group_map"
must
> contain an entry for "LANDSF".
>
> ERROR  :
>
>
>
> So, I went back to my config file and added LANDSF to the values
where
> keys implied the surface but that didn't fix the problem ( see
> attached).  Does LANDSF need to be a key and if so what would the
> value be?  What am I missing?
>
>
>
> Thanks
>
> Bob
>
>
>

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