[Met_help] [rt.rap.ucar.edu #82163] History for GRIB1 Error

Tue Jul 9 12:04:17 MDT 2019

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

Hi John,

When running the following MET command on the GRIB1 file, Bob Craig and I
get this error:  

/h/WXQC/met-6.0/bin/plot_data_plane
/home/qcteam/fss/meps/grib.2017091422.0006 /home/qcteam/testimg
'name="QP010"; PROB="true"; level="Z0">
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: Opening data file: /home/qcteam/fss/meps/grib.2017091422.0006
DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created new
Met2dDataFile object of type "FileType_Gb1".
DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo object of
type "FileType_Gb1".
DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found 0 GRIB records
matching VarInfo "QP010/Z0" in GRIB file
"/home/qcteam/fss/meps/grib.2017091422.0006".
WARNING: 
WARNING: MetGrib1DataFile::data_plane() -> No exact match found for VarInfo
"QP010/Z0" in GRIB file "/home/qcteam/fss/meps/grib.2017091422.0006".
WARNING: 
ERROR  : 
ERROR  : plot_data_plane -> trouble getting field "name="QP010";
PROB="true"; level="Z0";" from file
"/home/qcteam/fss/meps/grib.2017091422.0006"
ERROR  :

Can you please assist in determining what the problem might be?

For your reference, Bob uploaded the GRIB1 file to the AMRDEC system and you
should be receiving notification about how to retrieve the data.  Please let
us know if you are unable or have problems in doing so.

Thanks,
Chris

//SIGNED//

Dr. Christopher J. Melick, DAF Civilian 
Meteorologist, Science Exploitation Team
16th Weather Squadron (16 WS/WXES)
557th Weather Wing, Offutt AFB, NE
DSN 271-3693; Comm (402) 294-3693

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

Subject: GRIB1 Error
From: John Halley Gotway
Time: Mon Oct 02 17:00:40 2017

Hello Chris,

I see that you're having trouble accessing a particular GRIB record.
You're looking for a field named "QP010" but plot_data_plane is unable
to
find it in the input file.

This is an issue with how the GRIB tables are defined... looking in
the
GRIB tables defined for MET in met-6.0/data/table_files, there is no
mention of a field named "QP010".

When I run the GRIB file you sent through wgrib, I get the following
warning message:

Undefined parameter table (center 57-4 table 3), using NCEP-opn

That means that wgrib doesn't have a table defining GRIB usage for
center
number 57, subcenter number 4, and table number 3... just like MET
doesn't.

Fortunately, there is a method you can use to define that GRIB table
and
tell MET how to use it.

Here are the steps I followed...

(1) Copy over the existing Air Force GRIB table, changing table number
131
to table number 3 and subcenter number 2 to 4:

cat met-6.0/share/met/table_files/grib1_af_131_57.txt | \
  sed 's/ 131 / 3 /g' | sed 's/ 57 2 / 57 4 /g' \
  > grib1_af_3_57.txt

(2) I wrote the output to a new file named "grib1_af_3_57.txt".

(3) Set the MET_GRIB_TABLES environment variable to point to either a
filename or a directory containing user-specified GRIB table files:

  setenv MET_GRIB_TABLES grib1_af_3_57.txt

(4) Here's the issue... I have no idea what your GRIB table usage
actually
is.  So I'll just make a very wild guess and assume that whatever is
in the
first GRIB record is QP010.  Here's the output from wgrib:

1:0:d=17091422:5WAVA:kpds5=230:kpds6=1:kpds7=0:TR=0:P1=6:P2=0:TimeU=1:sfc:6hr
fcst:NAve=0

That tells me this is GRIB number 230 (i.e. kpds5=230).

So I edited grib1_af_3_57.txt for GRIB number 230 as follows:

   230 3 57 4 "QP010" "Probability of Precip" "%"

(5) Rerun plot_data_plane requesting QP010:

met-6.0/bin/plot_data_plane \
   grib.2017091422.0006 plot.ps \
   'name="QP010"; PROB="true"; level="Z0";' -v 4

And sure enough, MET now finds QP010 in the first GRIB record:

DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found range match for
VarInfo "QP010/Z0" in GRIB record 1 of GRIB file
"grib.2017091422.0006".

And it created the attached plot.

Now I'm pretty sure that this is actually a plot of latitude... not
QP010.

But it's up to you to specify how you're using GRIB tables.  And once
you
finalize the settings, we'd be happy to include your version of
"grib1_af_3_57.txt" in the next MET release.

Hopefully you have your GRIB table usage for Air Force (center 57),
subcenter 4, and table number 3 defined somewhere.

Hope that helps clarify the situation.

Thanks,
John Halley Gotway

On Fri, Sep 29, 2017 at 2:12 PM, christopher.melick at us.af.mil via RT <
met_help at ucar.edu> wrote:

>
> Fri Sep 29 14:12:33 2017: Request 82163 was acted upon.
> Transaction: Ticket created by christopher.melick at us.af.mil
>        Queue: met_help
>      Subject: GRIB1 Error
>        Owner: Nobody
>   Requestors: christopher.melick at us.af.mil
>       Status: new
>  Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=82163 >
>
>
> Hi John,
>
> When running the following MET command on the GRIB1 file, Bob Craig
and I
> get this error:
>
> /h/WXQC/met-6.0/bin/plot_data_plane
> /home/qcteam/fss/meps/grib.2017091422.0006 /home/qcteam/testimg
> 'name="QP010"; PROB="true"; level="Z0">
> 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: Opening data file:
/home/qcteam/fss/meps/grib.2017091422.0006
> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created new
> Met2dDataFile object of type "FileType_Gb1".
> DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
object of
> type "FileType_Gb1".
> DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found 0 GRIB
records
> matching VarInfo "QP010/Z0" in GRIB file
> "/home/qcteam/fss/meps/grib.2017091422.0006".
> WARNING:
> WARNING: MetGrib1DataFile::data_plane() -> No exact match found for
VarInfo
> "QP010/Z0" in GRIB file
"/home/qcteam/fss/meps/grib.2017091422.0006".
> WARNING:
> ERROR  :
> ERROR  : plot_data_plane -> trouble getting field "name="QP010";
> PROB="true"; level="Z0";" from file
> "/home/qcteam/fss/meps/grib.2017091422.0006"
> ERROR  :
>
> Can you please assist in determining what the problem might be?
>
> For your reference, Bob uploaded the GRIB1 file to the AMRDEC system
and
> you
> should be receiving notification about how to retrieve the data.
Please
> let
> us know if you are unable or have problems in doing so.
>
> Thanks,
> Chris
>
> //SIGNED//
>
> Dr. Christopher J. Melick, DAF Civilian
> Meteorologist, Science Exploitation Team
> 16th Weather Squadron (16 WS/WXES)
> 557th Weather Wing, Offutt AFB, NE
> DSN 271-3693; Comm (402) 294-3693
>
>
>
>
>

------------------------------------------------
Subject: GRIB1 Error
From: robert.craig.2 at us.af.mil
Time: Tue Oct 03 07:07:42 2017

Hi john, attached is the grib 1 table pointed at by the
MET_GRIB_TABLES
environmental variable.  In this table Chris and I added qp010 to
record
number 224 (kpds5=222).   I the data file we are reading the kpds5
value is
222.  Why didn't that work?  We don't want to keep adding additional
grib
tables to get MET to work.  When we run data_plane, we don't get the
message
you got "Undefined parameter table (center 57-4 table 3), using NCEP-
opn",
instead we get the following:

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: Opening data file: /home/qcteam/fss/meps/grib.2017091422.0006
DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created new
Met2dDataFile object of type "FileType_Gb1".
DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo object
of type
"FileType_Gb1".
DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found 0 GRIB records
matching
VarInfo "QP010/Z0" in GRIB file
"/home/qcteam/fss/meps/grib.2017091422.0006".
WARNING:
WARNING: MetGrib1DataFile::data_plane() -> No exact match found for
VarInfo
"QP010/Z0" in GRIB file "/home/qcteam/fss/meps/grib.2017091422.0006".
WARNING:
ERROR  :
ERROR  : plot_data_plane -> trouble getting field "name="QP010";
PROB="true";
level="Z0";" from file "/home/qcteam/fss/meps/grib.2017091422.0006"
ERROR  :

So why didn't adding QP010 to our existing table work?

Thanks
Bob

-----Original Message-----
From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
Sent: Monday, October 02, 2017 6:01 PM
To: MELICK, CHRISTOPHER J GS-12 USAF ACC 16 WS/WXES
<christopher.melick at us.af.mil>
Cc: 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 #82163] GRIB1 Error

Hello Chris,

I see that you're having trouble accessing a particular GRIB record.
You're looking for a field named "QP010" but plot_data_plane is unable
to find
it in the input file.

This is an issue with how the GRIB tables are defined... looking in
the GRIB
tables defined for MET in met-6.0/data/table_files, there is no
mention of a
field named "QP010".

When I run the GRIB file you sent through wgrib, I get the following
warning
message:

Undefined parameter table (center 57-4 table 3), using NCEP-opn

That means that wgrib doesn't have a table defining GRIB usage for
center
number 57, subcenter number 4, and table number 3... just like MET
doesn't.

Fortunately, there is a method you can use to define that GRIB table
and tell
MET how to use it.

Here are the steps I followed...

(1) Copy over the existing Air Force GRIB table, changing table number
131 to
table number 3 and subcenter number 2 to 4:

cat met-6.0/share/met/table_files/grib1_af_131_57.txt | \
  sed 's/ 131 / 3 /g' | sed 's/ 57 2 / 57 4 /g' \
  > grib1_af_3_57.txt

(2) I wrote the output to a new file named "grib1_af_3_57.txt".

(3) Set the MET_GRIB_TABLES environment variable to point to either a
filename
or a directory containing user-specified GRIB table files:

  setenv MET_GRIB_TABLES grib1_af_3_57.txt

(4) Here's the issue... I have no idea what your GRIB table usage
actually is.
So I'll just make a very wild guess and assume that whatever is in the
first
GRIB record is QP010.  Here's the output from wgrib:

1:0:d=17091422:5WAVA:kpds5=230:kpds6=1:kpds7=0:TR=0:P1=6:P2=0:TimeU=1:sfc:6hr
fcst:NAve=0

That tells me this is GRIB number 230 (i.e. kpds5=230).

So I edited grib1_af_3_57.txt for GRIB number 230 as follows:

   230 3 57 4 "QP010" "Probability of Precip" "%"

(5) Rerun plot_data_plane requesting QP010:

met-6.0/bin/plot_data_plane \
   grib.2017091422.0006 plot.ps \
   'name="QP010"; PROB="true"; level="Z0";' -v 4

And sure enough, MET now finds QP010 in the first GRIB record:

DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found range match for
VarInfo
"QP010/Z0" in GRIB record 1 of GRIB file "grib.2017091422.0006".

And it created the attached plot.

Now I'm pretty sure that this is actually a plot of latitude... not
QP010.

But it's up to you to specify how you're using GRIB tables.  And once
you
finalize the settings, we'd be happy to include your version of
"grib1_af_3_57.txt" in the next MET release.

Hopefully you have your GRIB table usage for Air Force (center 57),
subcenter
4, and table number 3 defined somewhere.

Hope that helps clarify the situation.

Thanks,
John Halley Gotway

On Fri, Sep 29, 2017 at 2:12 PM, christopher.melick at us.af.mil via RT <
met_help at ucar.edu> wrote:

>
> Fri Sep 29 14:12:33 2017: Request 82163 was acted upon.
> Transaction: Ticket created by christopher.melick at us.af.mil
>        Queue: met_help
>      Subject: GRIB1 Error
>        Owner: Nobody
>   Requestors: christopher.melick at us.af.mil
>       Status: new
>  Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=82163
> >
>
>
> Hi John,
>
> When running the following MET command on the GRIB1 file, Bob Craig
> and I get this error:
>
> /h/WXQC/met-6.0/bin/plot_data_plane
> /home/qcteam/fss/meps/grib.2017091422.0006 /home/qcteam/testimg
> 'name="QP010"; PROB="true"; level="Z0"> 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: Opening data file:
/home/qcteam/fss/meps/grib.2017091422.0006
> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created new
> Met2dDataFile object of type "FileType_Gb1".
> DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
object
> of type "FileType_Gb1".
> DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found 0 GRIB
records
> matching VarInfo "QP010/Z0" in GRIB file
> "/home/qcteam/fss/meps/grib.2017091422.0006".
> WARNING:
> WARNING: MetGrib1DataFile::data_plane() -> No exact match found for
> VarInfo "QP010/Z0" in GRIB file
> "/home/qcteam/fss/meps/grib.2017091422.0006".
> WARNING:
> ERROR  :
> ERROR  : plot_data_plane -> trouble getting field "name="QP010";
> PROB="true"; level="Z0";" from file
> "/home/qcteam/fss/meps/grib.2017091422.0006"
> ERROR  :
>
> Can you please assist in determining what the problem might be?
>
> For your reference, Bob uploaded the GRIB1 file to the AMRDEC system
> and you should be receiving notification about how to retrieve the
> data.  Please let us know if you are unable or have problems in
doing
> so.
>
> Thanks,
> Chris
>
> //SIGNED//
>
> Dr. Christopher J. Melick, DAF Civilian Meteorologist, Science
> Exploitation Team 16th Weather Squadron (16 WS/WXES) 557th Weather
> Wing, Offutt AFB, NE DSN 271-3693; Comm (402) 294-3693
>
>
>
>
>

------------------------------------------------
Subject: GRIB1 Error
From: robert.craig.2 at us.af.mil
Time: Tue Oct 03 07:07:42 2017

GRIB1
0 131 57 2 "var0" "undefined" ""
1 131 57 2 "PRES" "Pressure" "Pa"
2 131 57 2 "PRMSL" "Pressure reduced to MSL" "Pa"
3 131 57 2 "PTEND" "Pressure tendency" "Pa/s"
4 131 57 2 "var4" "undefined" ""
5 131 57 2 "var5" "undefined" ""
6 131 57 2 "GP" "Geopotential" "m^2/s^2"
7 131 57 2 "HGT" "Geopotential height" "gpm"
8 131 57 2 "DIST" "Geometric height" "m"
9 131 57 2 "HSTDV" "Std dev of height" "m"
10 131 57 2 "HVAR" "Variance of height" "m^2"
11 131 57 2 "TMP" "Temp." "K"
12 131 57 2 "VTMP" "Virtual temp." "K"
13 131 57 2 "POT" "Potential temp." "K"
14 131 57 2 "EPOT" "Pseudo-adiabatic pot. temp." "K"
15 131 57 2 "TMAX" "Max. temp." "K"
16 131 57 2 "TMIN" "Min. temp." "K"
17 131 57 2 "DPT" "Dew point temp." "K"
18 131 57 2 "DEPR" "Dew point depression" "K"
19 131 57 2 "LAPR" "Lapse rate" "K/m"
20 131 57 2 "VIS" "Visibility" "m"
21 131 57 2 "RDSP1" "Radar spectra (1)" "non-dim"
22 131 57 2 "RDSP2" "Radar spectra (2)" "non-dim"
23 131 57 2 "RDSP3" "Radar spectra (3)" "non-dim"
24 131 57 2 "var24" "undefined" ""
25 131 57 2 "TMPA" "Temp. anomaly" "K"
26 131 57 2 "PRESA" "Pressure anomaly" "Pa"
27 131 57 2 "GPA" "Geopotential height anomaly" "gpm"
28 131 57 2 "WVSP1" "Wave spectra (1)" "non-dim"
29 131 57 2 "WVSP2" "Wave spectra (2)" "non-dim"
30 131 57 2 "WVSP3" "Wave spectra (3)" "non-dim"
31 131 57 2 "WDIR" "Wind direction" "deg"
32 131 57 2 "WIND" "Wind speed" "m/s"
33 131 57 2 "UGRD" "u wind" "m/s"
34 131 57 2 "VGRD" "v wind" "m/s"
35 131 57 2 "STRM" "Stream function" "m^2/s"
36 131 57 2 "VPOT" "Velocity potential" "m^2/s"
37 131 57 2 "MNTSF" "Montgomery stream function" "m^2/s^2"
38 131 57 2 "SGCVV" "Sigma coord. vertical velocity" "/s"
39 131 57 2 "VVEL" "Pressure vertical velocity" "Pa/s"
40 131 57 2 "DZDT" "Geometric vertical velocity" "m/s"
41 131 57 2 "ABSV" "Absolute vorticity" "/s"
42 131 57 2 "ABSD" "Absolute divergence" "/s"
43 131 57 2 "RELV" "Relative vorticity" "/s"
44 131 57 2 "RELD" "Relative divergence" "/s"
45 131 57 2 "VUCSH" "Vertical u shear" "/s"
46 131 57 2 "VVCSH" "Vertical v shear" "/s"
47 131 57 2 "DIRC" "Direction of current" "deg"
48 131 57 2 "SPC" "Speed of current" "m/s"
49 131 57 2 "UOGRD" "u of current" "m/s"
50 131 57 2 "VOGRD" "v of current" "m/s"
51 131 57 2 "SPFH" "Specific humidity" "kg/kg"
52 131 57 2 "RH" "Relative humidity" "%"
53 131 57 2 "MIXR" "Humidity mixing ratio" "kg/kg"
54 131 57 2 "PWAT" "Precipitable water" "kg/m^2"
55 131 57 2 "VAPP" "Vapor pressure" "Pa"
56 131 57 2 "SATD" "Saturation deficit" "Pa"
57 131 57 2 "EVP" "Evaporation" "kg/m^2"
58 131 57 2 "CICE" "Cloud Ice" "kg/kg"
59 131 57 2 "PRATE" "Precipitation rate" "kg/m^2/s"
60 131 57 2 "TSTM" "Thunderstorm probability" "%"
61 131 57 2 "APCP" "Total precipitation" "kg/m^2"
62 131 57 2 "NCPCP" "Large scale precipitation" "kg/m^2"
63 131 57 2 "ACPCP" "Convective precipitation" "kg/m^2"
64 131 57 2 "SRWEQ" "Snowfall rate water equiv." "kg/m^2/s"
65 131 57 2 "WEASD" "Accum. snow" "kg/m^2"
66 131 57 2 "SNOD" "Snow depth" "m"
67 131 57 2 "MIXHT" "Mixed layer depth" "m"
68 131 57 2 "TTHDP" "Transient thermocline depth" "m"
69 131 57 2 "MTHD" "Main thermocline depth" "m"
70 131 57 2 "MTHA" "Main thermocline anomaly" "m"
71 131 57 2 "TCDC" "Total cloud cover" "%"
72 131 57 2 "CDCON" "Convective cloud cover" "%"
73 131 57 2 "LCDC" "Low level cloud cover" "%"
74 131 57 2 "MCDC" "Mid level cloud cover" "%"
75 131 57 2 "HCDC" "High level cloud cover" "%"
76 131 57 2 "CWAT" "Cloud water" "kg/m^2"
77 131 57 2 "var77" "undefined" ""
78 131 57 2 "SNOC" "Convective snow" "kg/m^2"
79 131 57 2 "SNOL" "Large scale snow" "kg/m^2"
80 131 57 2 "WTMP" "Water temp." "K"
81 131 57 2 "LAND" "Land-sea mask" "1=land; 0=sea"
82 131 57 2 "DSLM" "Deviation of sea level from mean" "m"
83 131 57 2 "SFCR" "Surface roughness" "m"
84 131 57 2 "ALBDO" "Albedo" "%"
85 131 57 2 "TSOIL" "Soil temp." "K"
86 131 57 2 "SOILM" "Soil moisture content" "kg/m^2"
87 131 57 2 "VEG" "Vegetation" "%"
88 131 57 2 "SALTY" "Salinity" "kg/kg"
89 131 57 2 "DEN" "Density" "kg/m^3"
90 131 57 2 "RUNOF" "Runoff" "kg/m^2"
91 131 57 2 "ICEC" "Ice concentration" "ice=1;no ice=0"
92 131 57 2 "ICETK" "Ice thickness" "m"
93 131 57 2 "DICED" "Direction of ice drift" "deg"
94 131 57 2 "SICED" "Speed of ice drift" "m/s"
95 131 57 2 "UICE" "u of ice drift" "m/s"
96 131 57 2 "VICE" "v of ice drift" "m/s"
97 131 57 2 "ICEG" "Ice growth rate" "m/s"
98 131 57 2 "ICED" "Ice divergence" "/s"
99 131 57 2 "SNOM" "Snow melt" "kg/m^2"
100 131 57 2 "HTSGW" "Sig height of wind waves and swell" "m"
101 131 57 2 "WVDIR" "Direction of wind waves" "deg"
102 131 57 2 "WVHGT" "Sig height of wind waves" "m"
103 131 57 2 "WVPER" "Mean period of wind waves" "s"
104 131 57 2 "SWDIR" "Direction of swell waves" "deg"
105 131 57 2 "SWELL" "Sig height of swell waves" "m"
106 131 57 2 "SWPER" "Mean period of swell waves" "s"
107 131 57 2 "DIRPW" "Primary wave direction" "deg"
108 131 57 2 "PERPW" "Primary wave mean period" "s"
109 131 57 2 "DIRSW" "Secondary wave direction" "deg"
110 131 57 2 "PERSW" "Secondary wave mean period" "s"
111 131 57 2 "NSWRS" "Net short wave (surface)" "W/m^2"
112 131 57 2 "NLWRS" "Net long wave (surface)" "W/m^2"
113 131 57 2 "NSWRT" "Net short wave (top)" "W/m^2"
114 131 57 2 "NLWRT" "Net long wave (top)" "W/m^2"
115 131 57 2 "LWAVR" "Long wave" "W/m^2"
116 131 57 2 "SWAVR" "Short wave" "W/m^2"
117 131 57 2 "GRAD" "Global radiation" "W/m^2"
118 131 57 2 "var118" "undefined" ""
119 131 57 2 "var119" "undefined" ""
120 131 57 2 "var120" "undefined" ""
121 131 57 2 "LHTFL" "Latent heat flux" "W/m^2"
122 131 57 2 "SHTFL" "Sensible heat flux" "W/m^2"
123 131 57 2 "BLYDP" "Boundary layer dissipation" "W/m^2"a
124 131 57 2 "UFLX" "Zonal momentum flux" "N/m^2"
125 131 57 2 "VFLX" "Meridional momentum flux" "N/m^2"
126 131 57 2 "WMIXE" "Wind mixing energy" "J"
127 131 57 2 "IMGD" "Image data" "integer"
128 131 57 2 "iceCoverage" "Ice Concentration" "%"
129 131 57 2 "iceAge" "Ice Age" "days"
130 131 57 2 "var130" "undefined" ""
131 131 57 2 "var131" "undefined" ""
132 131 57 2 "var132" "undefined" ""
133 131 57 2 "var133" "undefined" ""
134 131 57 2 "var134" "undefined" ""
135 131 57 2 "DUST" "Dust Visibility" "m"
136 131 57 2 "dustConcentration" "Dust Concentration" "?g m^-3"
137 131 57 2 "var137" "undefined" ""
138 131 57 2 "var138" "undefined" ""
139 131 57 2 "var139" "undefined" ""
140 131 57 2 "cloudHeightCeiling" "Ceiling" "m"
141 131 57 2 "var141" "undefined" ""
142 131 57 2 "var142" "undefined" ""
143 131 57 2 "var143" "undefined" ""
144 131 57 2 "fluxLongWaveRadiationDownward" "Downward longwave
radiation flux" "W m^2"
145 131 57 2 "fluxShortWaveRadiationDownward" "Downward shortwave
radiation flux " "W m^2"
146 131 57 2 "var146" "undefined" ""
147 131 57 2 "var147" "undefined" ""
148 131 57 2 "var148" "undefined" ""
149 131 57 2 "var149" "undefined" ""
150 131 57 2 "var150" "undefined" ""
151 131 57 2 "var151" "undefined" ""
152 131 57 2 "var152" "undefined" ""
153 131 57 2 "var153" "undefined" ""
154 131 57 2 "var154" "undefined" ""
155 131 57 2 "fluxHeatSurface" "Ground Heat Flux" "W m^2"
156 131 57 2 "var156" "undefined" ""
157 131 57 2 "var157" "undefined" ""
158 131 57 2 "var158" "undefined" ""
159 131 57 2 "var159" "undefined" ""
160 131 57 2 "var160" "undefined" ""
161 131 57 2 "terrainSurfaceHeight" "Terrain height" "m"
162 131 57 2 "var162" "undefined" ""
163 131 57 2 "cloudAmountLayer" "Cloud Amount (layer)" "%"
164 131 57 2 "cloudTypeLayer" "Cloud Type (layer)" "code"
165 131 57 2 "cloudBrightnessInfrared" "Cloud Brightness IR" "non-dim"
166 131 57 2 "var166" "undefined" ""
167 131 57 2 "CRAIN" "Categorical Rain" "code"
168 131 57 2 "var168" "undefined" ""
169 131 57 2 "var169" "undefined" ""
170 131 57 2 "CSNOW" "Categorical Snow" "code"
171 131 57 2 "var171" "undefined" ""
172 131 57 2 "var172" "undefined" ""
173 131 57 2 "var173" "undefined" ""
174 131 57 2 "precipitationSnowDepthInches" "Snow Depth" "in"
175 131 57 2 "precipitationSnowAge" "Snow Age" "days"
176 131 57 2 "var176" "undefined" ""
177 131 57 2 "var177" "undefined" ""
178 131 57 2 "var178" "undefined" ""
179 131 57 2 "cloudAmountLayer" "Layer Cloud Amount" "%"
180 131 57 2 "cloudHeightBaseLayer" "Layer Cloud Base" "code"
181 131 57 2 "cloudHeightTopLayer" "Layer Cloud Top" "code"
182 131 57 2 "cloudTypeLayer" "Layer Cloud Type" "code"s
183 131 57 2 "timeLastUpdate" "Time of last update from base time"
"Minutes"
184 131 57 2 "var184" "undefined" ""
185 131 57 2 "cloudLayerOpticalDepth" "Layer Cloud Optical Depth"
"number"
186 131 57 2 "cloudLayerIcePercentage" "Layer Cloud Ice Percentage"
"%"
187 131 57 2 "cloudLayerWaterPath" "Layer Cloud Water Path" "g m^-2"
188 131 57 2 "cloudLayerParticleSize" "Layer Cloud Particle Size" "?m"
189 131 57 2 "var189" "undefined" ""
190 131 57 2 "cloudLayerNumber" "Cloud Layer Number" "number"
191 131 57 2 "cloudAnalysisQualityIndex" "Cloud Analysis Quality
Index" "%"
192 131 57 2 "var192" "undefined" ""
193 131 57 2 "precipitationQuality" "Precipitation Quality Factor
(Goodness)" "non-dim"
194 131 57 2 "satelliteIdentifier" "Satellite Identifier" "code"
195 131 57 2 "satelliteMerged" "Satellite Merged - CDFS II" "code"
196 131 57 2 "var196" "undefined" ""
197 131 57 2 "var197" "undefined" ""
198 131 57 2 "precipitationDerivedGeostationarySatelliteBased"
"Estimated precipitation - geostationary satellite based" "mm"
199 131 57 2 "precipitationRankGeostationarySatellite" "Geostationary
Satellite precipitation rank" "category"
200 131 57 2 "soilMoistureRelative" "Relative soil moisture" "numeric"
201 131 57 2 "soilMoistureVolumetricTotal" "Volumetric Soil Moisture
(liquid + frozen)" "volumetric;  m^3 m^-3"
202 131 57 2 "precipitationAccumulated" "Precipitation - real amounts"
"mm"
203 131 57 2 "VAFTAD" "Dust visiblity" "m"
204 131 57 2 "evapotranspirationActual" "Evapotranspiration - actual"
"mm/24 hrs"
205 131 57 2 "soilType" "Soil Type" "code"
206 131 57 2 "UVI" "Dust Visibility" "m"
207 131 57 2 "vegetationPlantCanopyMoistureContent" "Plant Canopy
moisture content" "mm"
208 131 57 2 "evapotranspirationPotential" "Evapotranspiration -
potential" "mm hr^-1"
209 131 57 2 "windRun" "Wind run" "km/24 hrs"
210 131 57 2 "humidityRelativeAtMinimumTemperature" "Relative Humidity
at minimum temperature" "%"
211 131 57 2 "soilMoistureVolumetricLiquid" "Volumetric Soil Moisture
(liquid only)" "volumetric;  m^3 ^m-3"
212 131 57 2 "vegetationType" "Vegetation Type Category" "category"
213 131 57 2 "vegetationGreennessCoverage" "Vegetation Greenness" "%"
214 131 57 2 "var214" "undefined" ""
215 131 57 2 "var215" "undefined" ""
216 131 57 2 "var216" "undefined" ""
217 131 57 2 "var217" "undefined" ""
218 131 57 2 "var218" "undefined" ""
219 131 57 2 "var219" "undefined" ""
220 131 57 2 "var220" "undefined" ""
221 131 57 2 "var221" "undefined" ""
222 131 57 2 "QP010" "Probability of QPF" "%"
223 131 57 2 "var223" "undefined" ""
224 131 57 2 "var224" "undefined" ""
225 131 57 2 "var225" "undefined" ""
226 131 57 2 "var226" "undefined" ""
227 131 57 2 "cloudHeightBase" "Cloud base" "m"
228 131 57 2 "cloudHeightTop" "Cloud top" "m"
229 131 57 2 "var229" "undefined" ""
230 131 57 2 "latitude" "Latitude" "deg"
231 131 57 2 "longitude" "Longitude" "deg"
232 131 57 2 "var232" "undefined" ""
233 131 57 2 "terrainSurfaceHeight" "Model terrain height" "m"
234 131 57 2 "runoffGroundwaterBaseflow" "Baseflow - groundwater
runoff" "mm"
235 131 57 2 "runoffStorm" "Storm surface runoff" "mm"
236 131 57 2 "var236" "undefined" ""
237 131 57 2 "var237" "undefined" ""
238 131 57 2 "var238" "undefined" ""
239 131 57 2 "var239" "undefined" ""
240 131 57 2 "var240" "undefined" ""
241 131 57 2 "landUseCategory" "Land-use" "category"
242 131 57 2 "var242" "undefined" ""
243 131 57 2 "var243" "undefined" ""
244 131 57 2 "var244" "undefined" ""
245 131 57 2 "var245" "undefined" ""
246 131 57 2 "var246" "undefined" ""
247 131 57 2 "var247" "undefined" ""
248 131 57 2 "var248" "undefined" ""
248 131 57 2 "var249" "undefined" ""
250 131 57 2 "N/A" "Quality Control Display " "code"
251 131 57 2 "var251" "undefined" ""
252 131 57 2 "var252" "undefined" ""
253 131 57 2 "var253" "undefined" ""
254 131 57 2 "var254" "undefined" ""
255 131 57 2 "CFRZR" "Categorical Freezing Rain" "code"

------------------------------------------------
Subject: GRIB1 Error
From: John Halley Gotway
Time: Tue Oct 03 07:50:04 2017

Bob,

The GRIB table you sent is for center 57, subcenter 2.  The GRIB file
you
sent is for center 57, subcenter 4.

I think that’s why there’s no match.

Make sense?

John

On Tue, Oct 3, 2017 at 7:07 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=82163 >
>
> Hi john, attached is the grib 1 table pointed at by the
MET_GRIB_TABLES
> environmental variable.  In this table Chris and I added qp010 to
record
> number 224 (kpds5=222).   I the data file we are reading the kpds5
value is
> 222.  Why didn't that work?  We don't want to keep adding additional
grib
> tables to get MET to work.  When we run data_plane, we don't get the
> message
> you got "Undefined parameter table (center 57-4 table 3), using
NCEP-opn",
> instead we get the following:
>
> 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: Opening data file:
/home/qcteam/fss/meps/grib.2017091422.0006
> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created new
> Met2dDataFile object of type "FileType_Gb1".
> DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
object of
> type
> "FileType_Gb1".
> DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found 0 GRIB
records
> matching
> VarInfo "QP010/Z0" in GRIB file
> "/home/qcteam/fss/meps/grib.2017091422.0006".
> WARNING:
> WARNING: MetGrib1DataFile::data_plane() -> No exact match found for
VarInfo
> "QP010/Z0" in GRIB file
"/home/qcteam/fss/meps/grib.2017091422.0006".
> WARNING:
> ERROR  :
> ERROR  : plot_data_plane -> trouble getting field "name="QP010";
> PROB="true";
> level="Z0";" from file "/home/qcteam/fss/meps/grib.2017091422.0006"
> ERROR  :
>
> So why didn't adding QP010 to our existing table work?
>
> Thanks
> Bob
>
> -----Original Message-----
> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> Sent: Monday, October 02, 2017 6:01 PM
> To: MELICK, CHRISTOPHER J GS-12 USAF ACC 16 WS/WXES
> <christopher.melick at us.af.mil>
> Cc: 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 #82163] GRIB1 Error
>
> Hello Chris,
>
> I see that you're having trouble accessing a particular GRIB record.
> You're looking for a field named "QP010" but plot_data_plane is
unable to
> find
> it in the input file.
>
> This is an issue with how the GRIB tables are defined... looking in
the
> GRIB
> tables defined for MET in met-6.0/data/table_files, there is no
mention of
> a
> field named "QP010".
>
> When I run the GRIB file you sent through wgrib, I get the following
> warning
> message:
>
> Undefined parameter table (center 57-4 table 3), using NCEP-opn
>
> That means that wgrib doesn't have a table defining GRIB usage for
center
> number 57, subcenter number 4, and table number 3... just like MET
doesn't.
>
> Fortunately, there is a method you can use to define that GRIB table
and
> tell
> MET how to use it.
>
> Here are the steps I followed...
>
> (1) Copy over the existing Air Force GRIB table, changing table
number 131
> to
> table number 3 and subcenter number 2 to 4:
>
> cat met-6.0/share/met/table_files/grib1_af_131_57.txt | \
>   sed 's/ 131 / 3 /g' | sed 's/ 57 2 / 57 4 /g' \
>   > grib1_af_3_57.txt
>
> (2) I wrote the output to a new file named "grib1_af_3_57.txt".
>
> (3) Set the MET_GRIB_TABLES environment variable to point to either
a
> filename
> or a directory containing user-specified GRIB table files:
>
>   setenv MET_GRIB_TABLES grib1_af_3_57.txt
>
> (4) Here's the issue... I have no idea what your GRIB table usage
actually
> is.
> So I'll just make a very wild guess and assume that whatever is in
the
> first
> GRIB record is QP010.  Here's the output from wgrib:
>
>
>
1:0:d=17091422:5WAVA:kpds5=230:kpds6=1:kpds7=0:TR=0:P1=6:P2=0:TimeU=1:sfc:6hr
> fcst:NAve=0
>
> That tells me this is GRIB number 230 (i.e. kpds5=230).
>
> So I edited grib1_af_3_57.txt for GRIB number 230 as follows:
>
>    230 3 57 4 "QP010" "Probability of Precip" "%"
>
> (5) Rerun plot_data_plane requesting QP010:
>
> met-6.0/bin/plot_data_plane \
>    grib.2017091422.0006 plot.ps \
>    'name="QP010"; PROB="true"; level="Z0";' -v 4
>
> And sure enough, MET now finds QP010 in the first GRIB record:
>
> DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found range match
for
> VarInfo
> "QP010/Z0" in GRIB record 1 of GRIB file "grib.2017091422.0006".
>
> And it created the attached plot.
>
> Now I'm pretty sure that this is actually a plot of latitude... not
QP010.
>
> But it's up to you to specify how you're using GRIB tables.  And
once you
> finalize the settings, we'd be happy to include your version of
> "grib1_af_3_57.txt" in the next MET release.
>
> Hopefully you have your GRIB table usage for Air Force (center 57),
> subcenter
> 4, and table number 3 defined somewhere.
>
> Hope that helps clarify the situation.
>
> Thanks,
> John Halley Gotway
>
>
> On Fri, Sep 29, 2017 at 2:12 PM, christopher.melick at us.af.mil via RT
<
> met_help at ucar.edu> wrote:
>
> >
> > Fri Sep 29 14:12:33 2017: Request 82163 was acted upon.
> > Transaction: Ticket created by christopher.melick at us.af.mil
> >        Queue: met_help
> >      Subject: GRIB1 Error
> >        Owner: Nobody
> >   Requestors: christopher.melick at us.af.mil
> >       Status: new
> >  Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=82163
> > >
> >
> >
> > Hi John,
> >
> > When running the following MET command on the GRIB1 file, Bob
Craig
> > and I get this error:
> >
> > /h/WXQC/met-6.0/bin/plot_data_plane
> > /home/qcteam/fss/meps/grib.2017091422.0006 /home/qcteam/testimg
> > 'name="QP010"; PROB="true"; level="Z0"> 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: Opening data file:
/home/qcteam/fss/meps/grib.2017091422.0006
> > DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created
new
> > Met2dDataFile object of type "FileType_Gb1".
> > DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
object
> > of type "FileType_Gb1".
> > DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found 0 GRIB
records
> > matching VarInfo "QP010/Z0" in GRIB file
> > "/home/qcteam/fss/meps/grib.2017091422.0006".
> > WARNING:
> > WARNING: MetGrib1DataFile::data_plane() -> No exact match found
for
> > VarInfo "QP010/Z0" in GRIB file
> > "/home/qcteam/fss/meps/grib.2017091422.0006".
> > WARNING:
> > ERROR  :
> > ERROR  : plot_data_plane -> trouble getting field "name="QP010";
> > PROB="true"; level="Z0";" from file
> > "/home/qcteam/fss/meps/grib.2017091422.0006"
> > ERROR  :
> >
> > Can you please assist in determining what the problem might be?
> >
> > For your reference, Bob uploaded the GRIB1 file to the AMRDEC
system
> > and you should be receiving notification about how to retrieve the
> > data.  Please let us know if you are unable or have problems in
doing
> > so.
> >
> > Thanks,
> > Chris
> >
> > //SIGNED//
> >
> > Dr. Christopher J. Melick, DAF Civilian Meteorologist, Science
> > Exploitation Team 16th Weather Squadron (16 WS/WXES) 557th Weather
> > Wing, Offutt AFB, NE DSN 271-3693; Comm (402) 294-3693
> >
> >
> >
> >
> >
>
>
>

------------------------------------------------
Subject: GRIB1 Error
From: robert.craig.2 at us.af.mil
Time: Tue Oct 03 08:20:28 2017

Okay, so in my MET_GRIB_TABLES directory, I created another table per
your instructions (see attached).   In that table made the changes you
recommended for the sub-center and table.  The QP010 parameter is at
record 224 (or KPDS5=222).  When I run I get the following:

DEBUG 1: Reading user-defined grib1 MET_GRIB_TABLES file:
/h/data/global/WXQC/data/met/config/grib2/grib1_af_3_57.txt
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: Opening data file: /home/qcteam/fss/meps/grib.2017091422.0006
DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created new
Met2dDataFile object of type "FileType_Gb1".
DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo object
of type "FileType_Gb1".
DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found 0 GRIB records
matching VarInfo "QP010/Z0" in GRIB file
"/home/qcteam/fss/meps/grib.2017091422.0006".
WARNING:
WARNING: MetGrib1DataFile::data_plane() -> No exact match found for
VarInfo "QP010/Z0" in GRIB file
"/home/qcteam/fss/meps/grib.2017091422.0006".
WARNING:
ERROR  :
ERROR  : plot_data_plane -> trouble getting field "name="QP010";
PROB="true"; level="Z0";" from file
"/home/qcteam/fss/meps/grib.2017091422.0006"
ERROR  :

So what did I do wrong?

Thanks
Bob

-----Original Message-----
From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
Sent: Tuesday, October 03, 2017 8:50 AM
To: MELICK, CHRISTOPHER J GS-12 USAF ACC 16 WS/WXES
<christopher.melick at us.af.mil>
Cc: 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 #82163] GRIB1 Error

Bob,

The GRIB table you sent is for center 57, subcenter 2.  The GRIB file
you sent is for center 57, subcenter 4.

I think that’s why there’s no match.

Make sense?

John

On Tue, Oct 3, 2017 at 7:07 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=82163 >
>
> Hi john, attached is the grib 1 table pointed at by the
> MET_GRIB_TABLES environmental variable.  In this table Chris and I
added qp010 to record
> number 224 (kpds5=222).   I the data file we are reading the kpds5
value is
> 222.  Why didn't that work?  We don't want to keep adding additional
> grib tables to get MET to work.  When we run data_plane, we don't
get
> the message you got "Undefined parameter table (center 57-4 table
3),
> using NCEP-opn", instead we get the following:
>
> 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: Opening data file:
/home/qcteam/fss/meps/grib.2017091422.0006
> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created new
> Met2dDataFile object of type "FileType_Gb1".
> DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
object
> of type "FileType_Gb1".
> DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found 0 GRIB
records
> matching VarInfo "QP010/Z0" in GRIB file
> "/home/qcteam/fss/meps/grib.2017091422.0006".
> WARNING:
> WARNING: MetGrib1DataFile::data_plane() -> No exact match found for
> VarInfo "QP010/Z0" in GRIB file
"/home/qcteam/fss/meps/grib.2017091422.0006".
> WARNING:
> ERROR  :
> ERROR  : plot_data_plane -> trouble getting field "name="QP010";
> PROB="true"; level="Z0";" from file
> "/home/qcteam/fss/meps/grib.2017091422.0006"
> ERROR  :
>
> So why didn't adding QP010 to our existing table work?
>
> Thanks
> Bob
>
> -----Original Message-----
> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> Sent: Monday, October 02, 2017 6:01 PM
> To: MELICK, CHRISTOPHER J GS-12 USAF ACC 16 WS/WXES
> <christopher.melick at us.af.mil>
> Cc: 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 #82163] GRIB1 Error
>
> Hello Chris,
>
> I see that you're having trouble accessing a particular GRIB record.
> You're looking for a field named "QP010" but plot_data_plane is
unable
> to find it in the input file.
>
> This is an issue with how the GRIB tables are defined... looking in
> the GRIB tables defined for MET in met-6.0/data/table_files, there
is
> no mention of a field named "QP010".
>
> When I run the GRIB file you sent through wgrib, I get the following
> warning
> message:
>
> Undefined parameter table (center 57-4 table 3), using NCEP-opn
>
> That means that wgrib doesn't have a table defining GRIB usage for
> center number 57, subcenter number 4, and table number 3... just
like MET doesn't.
>
> Fortunately, there is a method you can use to define that GRIB table
> and tell MET how to use it.
>
> Here are the steps I followed...
>
> (1) Copy over the existing Air Force GRIB table, changing table
number
> 131 to table number 3 and subcenter number 2 to 4:
>
> cat met-6.0/share/met/table_files/grib1_af_131_57.txt | \
>   sed 's/ 131 / 3 /g' | sed 's/ 57 2 / 57 4 /g' \
>   > grib1_af_3_57.txt
>
> (2) I wrote the output to a new file named "grib1_af_3_57.txt".
>
> (3) Set the MET_GRIB_TABLES environment variable to point to either
a
> filename or a directory containing user-specified GRIB table files:
>
>   setenv MET_GRIB_TABLES grib1_af_3_57.txt
>
> (4) Here's the issue... I have no idea what your GRIB table usage
> actually is.
> So I'll just make a very wild guess and assume that whatever is in
the
> first GRIB record is QP010.  Here's the output from wgrib:
>
>
>
1:0:d=17091422:5WAVA:kpds5=230:kpds6=1:kpds7=0:TR=0:P1=6:P2=0:TimeU=1:
> sfc:6hr
> fcst:NAve=0
>
> That tells me this is GRIB number 230 (i.e. kpds5=230).
>
> So I edited grib1_af_3_57.txt for GRIB number 230 as follows:
>
>    230 3 57 4 "QP010" "Probability of Precip" "%"
>
> (5) Rerun plot_data_plane requesting QP010:
>
> met-6.0/bin/plot_data_plane \
>    grib.2017091422.0006 plot.ps \
>    'name="QP010"; PROB="true"; level="Z0";' -v 4
>
> And sure enough, MET now finds QP010 in the first GRIB record:
>
> DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found range match
for
> VarInfo "QP010/Z0" in GRIB record 1 of GRIB file
> "grib.2017091422.0006".
>
> And it created the attached plot.
>
> Now I'm pretty sure that this is actually a plot of latitude... not
QP010.
>
> But it's up to you to specify how you're using GRIB tables.  And
once
> you finalize the settings, we'd be happy to include your version of
> "grib1_af_3_57.txt" in the next MET release.
>
> Hopefully you have your GRIB table usage for Air Force (center 57),
> subcenter 4, and table number 3 defined somewhere.
>
> Hope that helps clarify the situation.
>
> Thanks,
> John Halley Gotway
>
>
> On Fri, Sep 29, 2017 at 2:12 PM, christopher.melick at us.af.mil via RT
<
> met_help at ucar.edu> wrote:
>
> >
> > Fri Sep 29 14:12:33 2017: Request 82163 was acted upon.
> > Transaction: Ticket created by christopher.melick at us.af.mil
> >        Queue: met_help
> >      Subject: GRIB1 Error
> >        Owner: Nobody
> >   Requestors: christopher.melick at us.af.mil
> >       Status: new
> >  Ticket <URL:
> > https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=82163
> > >
> >
> >
> > Hi John,
> >
> > When running the following MET command on the GRIB1 file, Bob
Craig
> > and I get this error:
> >
> > /h/WXQC/met-6.0/bin/plot_data_plane
> > /home/qcteam/fss/meps/grib.2017091422.0006 /home/qcteam/testimg
> > 'name="QP010"; PROB="true"; level="Z0"> 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: Opening data file:
> > /home/qcteam/fss/meps/grib.2017091422.0006
> > DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created
new
> > Met2dDataFile object of type "FileType_Gb1".
> > DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
> > object of type "FileType_Gb1".
> > DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found 0 GRIB
> > records matching VarInfo "QP010/Z0" in GRIB file
> > "/home/qcteam/fss/meps/grib.2017091422.0006".
> > WARNING:
> > WARNING: MetGrib1DataFile::data_plane() -> No exact match found
for
> > VarInfo "QP010/Z0" in GRIB file
> > "/home/qcteam/fss/meps/grib.2017091422.0006".
> > WARNING:
> > ERROR  :
> > ERROR  : plot_data_plane -> trouble getting field "name="QP010";
> > PROB="true"; level="Z0";" from file
> > "/home/qcteam/fss/meps/grib.2017091422.0006"
> > ERROR  :
> >
> > Can you please assist in determining what the problem might be?
> >
> > For your reference, Bob uploaded the GRIB1 file to the AMRDEC
system
> > and you should be receiving notification about how to retrieve the
> > data.  Please let us know if you are unable or have problems in
> > doing so.
> >
> > Thanks,
> > Chris
> >
> > //SIGNED//
> >
> > Dr. Christopher J. Melick, DAF Civilian Meteorologist, Science
> > Exploitation Team 16th Weather Squadron (16 WS/WXES) 557th Weather
> > Wing, Offutt AFB, NE DSN 271-3693; Comm (402) 294-3693
> >
> >
> >
> >
> >
>
>
>

------------------------------------------------
Subject: GRIB1 Error
From: robert.craig.2 at us.af.mil
Time: Tue Oct 03 08:20:28 2017

GRIB1
0 3 57 4 "var0" "undefined" ""
1 3 57 4 "PRES" "Pressure" "Pa"
2 3 57 4 "PRMSL" "Pressure reduced to MSL" "Pa"
3 3 57 4 "PTEND" "Pressure tendency" "Pa/s"
4 3 57 4 "var4" "undefined" ""
5 3 57 4 "var5" "undefined" ""
6 3 57 4 "GP" "Geopotential" "m^2/s^2"
7 3 57 4 "HGT" "Geopotential height" "gpm"
8 3 57 4 "DIST" "Geometric height" "m"
9 3 57 4 "HSTDV" "Std dev of height" "m"
10 3 57 4 "HVAR" "Variance of height" "m^2"
11 3 57 4 "TMP" "Temp." "K"
12 3 57 4 "VTMP" "Virtual temp." "K"
13 3 57 4 "POT" "Potential temp." "K"
14 3 57 4 "EPOT" "Pseudo-adiabatic pot. temp." "K"
15 3 57 4 "TMAX" "Max. temp." "K"
16 3 57 4 "TMIN" "Min. temp." "K"
17 3 57 4 "DPT" "Dew point temp." "K"
18 3 57 4 "DEPR" "Dew point depression" "K"
19 3 57 4 "LAPR" "Lapse rate" "K/m"
20 3 57 4 "VISIB" "Visibility" "m"
21 3 57 4 "RDSP1" "Radar spectra (1)" "non-dim"
22 3 57 4 "RDSP2" "Radar spectra (2)" "non-dim"
23 3 57 4 "RDSP3" "Radar spectra (3)" "non-dim"
24 3 57 4 "var24" "undefined" ""
25 3 57 4 "TMPA" "Temp. anomaly" "K"
26 3 57 4 "PRESA" "Pressure anomaly" "Pa"
27 3 57 4 "GPA" "Geopotential height anomaly" "gpm"
28 3 57 4 "WVSP1" "Wave spectra (1)" "non-dim"
29 3 57 4 "WVSP2" "Wave spectra (2)" "non-dim"
30 3 57 4 "WVSP3" "Wave spectra (3)" "non-dim"
31 3 57 4 "WDIR" "Wind direction" "deg"
32 3 57 4 "WIND" "Wind speed" "m/s"
33 3 57 4 "UGRD" "u wind" "m/s"
34 3 57 4 "VGRD" "v wind" "m/s"
35 3 57 4 "STRM" "Stream function" "m^2/s"
36 3 57 4 "VPOT" "Velocity potential" "m^2/s"
37 3 57 4 "MNTSF" "Montgomery stream function" "m^2/s^2"
38 3 57 4 "SGCVV" "Sigma coord. vertical velocity" "/s"
39 3 57 4 "VVEL" "Pressure vertical velocity" "Pa/s"
40 3 57 4 "DZDT" "Geometric vertical velocity" "m/s"
41 3 57 4 "ABSV" "Absolute vorticity" "/s"
42 3 57 4 "ABSD" "Absolute divergence" "/s"
43 3 57 4 "RELV" "Relative vorticity" "/s"
44 3 57 4 "RELD" "Relative divergence" "/s"
45 3 57 4 "VUCSH" "Vertical u shear" "/s"
46 3 57 4 "VVCSH" "Vertical v shear" "/s"
47 3 57 4 "DIRC" "Direction of current" "deg"
48 3 57 4 "SPC" "Speed of current" "m/s"
49 3 57 4 "UOGRD" "u of current" "m/s"
50 3 57 4 "VOGRD" "v of current" "m/s"
51 3 57 4 "SPFH" "Specific humidity" "kg/kg"
52 3 57 4 "RH" "Relative humidity" "%"
53 3 57 4 "MIXR" "Humidity mixing ratio" "kg/kg"
54 3 57 4 "PWAT" "Precipitable water" "kg/m^2"
55 3 57 4 "VAPP" "Vapor pressure" "Pa"
56 3 57 4 "SATD" "Saturation deficit" "Pa"
57 3 57 4 "EVP" "Evaporation" "kg/m^2"
58 3 57 4 "CICE" "Cloud Ice" "kg/kg"
59 3 57 4 "PRATE" "Precipitation rate" "kg/m^2/s"
60 3 57 4 "TSTM" "Thunderstorm probability" "%"
61 3 57 4 "APCP" "Total precipitation" "kg/m^2"
62 3 57 4 "NCPCP" "Large scale precipitation" "kg/m^2"
63 3 57 4 "ACPCP" "Convective precipitation" "kg/m^2"
64 3 57 4 "SRWEQ" "Snowfall rate water equiv." "kg/m^2/s"
65 3 57 4 "WEASD" "Accum. snow" "kg/m^2"
66 3 57 4 "SNOD" "Snow depth" "m"
67 3 57 4 "MIXHT" "Mixed layer depth" "m"
68 3 57 4 "TTHDP" "Transient thermocline depth" "m"
69 3 57 4 "MTHD" "Main thermocline depth" "m"
70 3 57 4 "MTHA" "Main thermocline anomaly" "m"
71 3 57 4 "TCDC" "Total cloud cover" "%"
72 3 57 4 "CDCON" "Convective cloud cover" "%"
73 3 57 4 "LCDC" "Low level cloud cover" "%"
74 3 57 4 "MCDC" "Mid level cloud cover" "%"
75 3 57 4 "HCDC" "High level cloud cover" "%"
76 3 57 4 "CWAT" "Cloud water" "kg/m^2"
77 3 57 4 "var77" "undefined" ""
78 3 57 4 "SNOC" "Convective snow" "kg/m^2"
79 3 57 4 "SNOL" "Large scale snow" "kg/m^2"
80 3 57 4 "WTMP" "Water temp." "K"
81 3 57 4 "LAND" "Land-sea mask" "1=land; 0=sea"
82 3 57 4 "DSLM" "Deviation of sea level from mean" "m"
83 3 57 4 "SFCR" "Surface roughness" "m"
84 3 57 4 "ALBDO" "Albedo" "%"
85 3 57 4 "TSOIL" "Soil temp." "K"
86 3 57 4 "SOILM" "Soil moisture content" "kg/m^2"
87 3 57 4 "VEG" "Vegetation" "%"
88 3 57 4 "SALTY" "Salinity" "kg/kg"
89 3 57 4 "DEN" "Density" "kg/m^3"
90 3 57 4 "RUNOF" "Runoff" "kg/m^2"
91 3 57 4 "ICEC" "Ice concentration" "ice=1;no ice=0"
92 3 57 4 "ICETK" "Ice thickness" "m"
93 3 57 4 "DICED" "Direction of ice drift" "deg"
94 3 57 4 "SICED" "Speed of ice drift" "m/s"
95 3 57 4 "UICE" "u of ice drift" "m/s"
96 3 57 4 "VICE" "v of ice drift" "m/s"
97 3 57 4 "ICEG" "Ice growth rate" "m/s"
98 3 57 4 "ICED" "Ice divergence" "/s"
99 3 57 4 "SNOM" "Snow melt" "kg/m^2"
100 3 57 4 "HTSGW" "Sig height of wind waves and swell" "m"
101 3 57 4 "WVDIR" "Direction of wind waves" "deg"
102 3 57 4 "WVHGT" "Sig height of wind waves" "m"
103 3 57 4 "WVPER" "Mean period of wind waves" "s"
104 3 57 4 "SWDIR" "Direction of swell waves" "deg"
105 3 57 4 "SWELL" "Sig height of swell waves" "m"
106 3 57 4 "SWPER" "Mean period of swell waves" "s"
107 3 57 4 "DIRPW" "Primary wave direction" "deg"
108 3 57 4 "PERPW" "Primary wave mean period" "s"
109 3 57 4 "DIRSW" "Secondary wave direction" "deg"
110 3 57 4 "PERSW" "Secondary wave mean period" "s"
111 3 57 4 "NSWRS" "Net short wave (surface)" "W/m^2"
112 3 57 4 "NLWRS" "Net long wave (surface)" "W/m^2"
113 3 57 4 "NSWRT" "Net short wave (top)" "W/m^2"
114 3 57 4 "NLWRT" "Net long wave (top)" "W/m^2"
115 3 57 4 "LWAVR" "Long wave" "W/m^2"
116 3 57 4 "SWAVR" "Short wave" "W/m^2"
117 3 57 4 "GRAD" "Global radiation" "W/m^2"
118 3 57 4 "var118" "undefined" ""
119 3 57 4 "var119" "undefined" ""
120 3 57 4 "var120" "undefined" ""
121 3 57 4 "LHTFL" "Latent heat flux" "W/m^2"
122 3 57 4 "SHTFL" "Sensible heat flux" "W/m^2"
123 3 57 4 "BLYDP" "Boundary layer dissipation" "W/m^2"a
124 3 57 4 "UFLX" "Zonal momentum flux" "N/m^2"
125 3 57 4 "VFLX" "Meridional momentum flux" "N/m^2"
126 3 57 4 "WMIXE" "Wind mixing energy" "J"
127 3 57 4 "IMGD" "Image data" "integer"
128 3 57 4 "iceCoverage" "Ice Concentration" "%"
129 3 57 4 "iceAge" "Ice Age" "days"
130 3 57 4 "var130" "undefined" ""
131 3 57 4 "var131" "undefined" ""
132 3 57 4 "var132" "undefined" ""
133 3 57 4 "var133" "undefined" ""
134 3 57 4 "var134" "undefined" ""
135 3 57 4 "dustVisibility" "Dust Visibility" "m"
136 3 57 4  "dustConcentration" "Dust Concentration" "?g m^-3"
137 3 57 4 "var137" "undefined" ""
138 3 57 4 "var138" "undefined" ""
139 3 57 4 "var139" "undefined" ""
140 3 57 4 "cloudHeightCeiling" "Ceiling" "m"
141 3 57 4 "var141" "undefined" ""
142 3 57 4 "var142" "undefined" ""
143 3 57 4 "var143" "undefined" ""
144 3 57 4 "fluxLongWaveRadiationDownward" "Downward longwave
radiation flux" "W m^2"
145 3 57 4 "fluxShortWaveRadiationDownward" "Downward shortwave
radiation flux " "W m^2"
146 3 57 4 "var146" "undefined" ""
147 3 57 4 "var147" "undefined" ""
148 3 57 4 "var148" "undefined" ""
149 3 57 4 "var149" "undefined" ""
150 3 57 4 "var150" "undefined" ""
151 3 57 4 "var151" "undefined" ""
152 3 57 4 "var152" "undefined" ""
153 3 57 4 "var153" "undefined" ""
154 3 57 4 "var154" "undefined" ""
155 3 57 4 "fluxHeatSurface" "Ground Heat Flux" "W m^2"
156 3 57 4 "var156" "undefined" ""
157 3 57 4 "var157" "undefined" ""
158 3 57 4 "var158" "undefined" ""
159 3 57 4 "var159" "undefined" ""
160 3 57 4 "var160" "undefined" ""
161 3 57 4 "terrainSurfaceHeight" "Terrain height" "m"
162 3 57 4 "var162" "undefined" ""
163 3 57 4 "cloudAmountLayer" "Cloud Amount (layer)" "%"
164 3 57 4 "cloudTypeLayer" "Cloud Type (layer)" "code"
165 3 57 4 "cloudBrightnessInfrared" "Cloud Brightness IR" "non-dim"
166 3 57 4 "var166" "undefined" ""
167 3 57 4 "var167" "undefined" ""
168 3 57 4 "var168" "undefined" ""
169 3 57 4 "var169" "undefined" ""
170 3 57 4 "var170" "undefined" ""
171 3 57 4 "var171" "undefined" ""
172 3 57 4 "var172" "undefined" ""
173 3 57 4 "var173" "undefined" ""
174 3 57 4 "precipitationSnowDepthInches" "Snow Depth" "in"
175 3 57 4 "precipitationSnowAge" "Snow Age" "days"
176 3 57 4 "var176" "undefined" ""
177 3 57 4 "var177" "undefined" ""
178 3 57 4 "var178" "undefined" ""
179 3 57 4 "cloudAmountLayer" "Layer Cloud Amount" "%"
180 3 57 4 "cloudHeightBaseLayer" "Layer Cloud Base" "code"
181 3 57 4 "cloudHeightTopLayer" "Layer Cloud Top" "code"
182 3 57 4 "cloudTypeLayer" "Layer Cloud Type" "code"s
183 3 57 4 "timeLastUpdate" "Time of last update from base time"
"Minutes"
184 3 57 4 "var184" "undefined" ""
185 3 57 4 "cloudLayerOpticalDepth" "Layer Cloud Optical Depth"
"number"
186 3 57 4 "cloudLayerIcePercentage" "Layer Cloud Ice Percentage" "%"
187 3 57 4 "cloudLayerWaterPath" "Layer Cloud Water Path" "g m^-2"
188 3 57 4 "cloudLayerParticleSize" "Layer Cloud Particle Size" "?m"
189 3 57 4 "var189" "undefined" ""
190 3 57 4 "cloudLayerNumber" "Cloud Layer Number" "number"
191 3 57 4 "cloudAnalysisQualityIndex" "Cloud Analysis Quality Index"
"%"
192 3 57 4 "var192" "undefined" ""
193 3 57 4 "precipitationQuality" "Precipitation Quality Factor
(Goodness)" "non-dim"
194 3 57 4 "satelliteIdentifier" "Satellite Identifier" "code"
195 3 57 4 "satelliteMerged" "Satellite Merged - CDFS II" "code"
196 3 57 4 "var196" "undefined" ""
197 3 57 4 "var197" "undefined" ""
198 3 57 4 "precipitationDerivedGeostationarySatelliteBased"
"Estimated precipitation - geostationary satellite based" "mm"
199 3 57 4 "precipitationRankGeostationarySatellite" "Geostationary
Satellite precipitation rank" "category"
200 3 57 4 "soilMoistureRelative" "Relative soil moisture" "numeric"
201 3 57 4 "soilMoistureVolumetricTotal" "Volumetric Soil Moisture
(liquid + frozen)" "volumetric;  m^3 m^-3"
202 3 57 4 "precipitationAccumulated" "Precipitation - real amounts"
"mm"
203 3 57 4 "precipitationAccumulatedMerged" "Precipitation - merged
analysis" "mm/24 hrs"
204 3 57 4 "evapotranspirationActual" "Evapotranspiration - actual"
"mm/24 hrs"
205 3 57 4 "soilType" "Soil Type" "code"
206 3 57 4 "var206" "undefined" ""
207 3 57 4 "vegetationPlantCanopyMoistureContent" "Plant Canopy
moisture content" "mm"
208 3 57 4 "evapotranspirationPotential" "Evapotranspiration -
potential" "mm hr^-1"
209 3 57 4 "windRun" "Wind run" "km/24 hrs"
210 3 57 4 "humidityRelativeAtMinimumTemperature" "Relative Humidity
at minimum temperature" "%"
211 3 57 4 "soilMoistureVolumetricLiquid" "Volumetric Soil Moisture
(liquid only)" "volumetric;  m^3 ^m-3"
212 3 57 4 "vegetationType" "Vegetation Type Category" "category"
213 3 57 4 "vegetationGreennessCoverage" "Vegetation Greenness" "%"
214 3 57 4 "var214" "undefined" ""
215 3 57 4 "var215" "undefined" ""
216 3 57 4 "var216" "undefined" ""
217 3 57 4 "var217" "undefined" ""
218 3 57 4 "var218" "undefined" ""
219 3 57 4 "var219" "undefined" ""
220 3 57 4 "var220" "undefined" ""
221 3 57 4 "var221" "undefined" ""
222 3 57 4 "var222" "undefined" ""
223 3 57 4 "var223" "undefined" ""
224 3 57 4 "var224" "undefined" ""
225 3 57 4 "var225" "undefined" ""
226 3 57 4 "var226" "undefined" ""
227 3 57 4 "cloudHeightBase" "Cloud base" "m"
228 3 57 4 "cloudHeightTop" "Cloud top" "m"
229 3 57 4 "var229" "undefined" ""
230 3 57 4 "latitude" "Latitude" "deg"
231 3 57 4 "longitude" "Longitude" "deg"
232 3 57 4 "var232" "undefined" ""
233 3 57 4 "terrainSurfaceHeight" "Model terrain height" "m"
234 3 57 4 "runoffGroundwaterBaseflow" "Baseflow - groundwater runoff"
"mm"
235 3 57 4 "runoffStorm" "Storm surface runoff" "mm"
236 3 57 4 "var236" "undefined" ""
237 3 57 4 "var237" "undefined" ""
238 3 57 4 "var238" "undefined" ""
239 3 57 4 "var239" "undefined" ""
240 3 57 4 "var240" "undefined" ""
241 3 57 4 "landUseCategory" "Land-use" "category"
242 3 57 4 "var242" "undefined" ""
243 3 57 4 "var243" "undefined" ""
244 3 57 4 "var244" "undefined" ""
245 3 57 4 "var245" "undefined" ""
246 3 57 4 "var246" "undefined" ""
247 3 57 4 "var247" "undefined" ""
248 3 57 4 "var248" "undefined" ""
248 3 57 4 "var249" "undefined" ""
250 3 57 4 "N/A" "Quality Control Display " "code"
251 3 57 4 "var251" "undefined" ""
252 3 57 4 "var252" "undefined" ""
253 3 57 4 "var253" "undefined" ""
254 3 57 4 "var254" "undefined" ""
255 3 57 4 "var255" "undefined" ""

------------------------------------------------
Subject: RE: [Non-DoD Source] Re: [rt.rap.ucar.edu #82163] GRIB1 Error
From: robert.craig.2 at us.af.mil
Time: Tue Oct 03 08:35:23 2017

John, I got it working - I forgot to include qp010 in my new table
that you suggested.

Thanks
Bob

-----Original Message-----
From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
Sent: Tuesday, October 03, 2017 8:50 AM
To: MELICK, CHRISTOPHER J GS-12 USAF ACC 16 WS/WXES
<christopher.melick at us.af.mil>
Cc: 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 #82163] GRIB1 Error

Bob,

The GRIB table you sent is for center 57, subcenter 2.  The GRIB file
you sent is for center 57, subcenter 4.

I think that’s why there’s no match.

Make sense?

John

On Tue, Oct 3, 2017 at 7:07 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=82163 >
>
> Hi john, attached is the grib 1 table pointed at by the
> MET_GRIB_TABLES environmental variable.  In this table Chris and I
added qp010 to record
> number 224 (kpds5=222).   I the data file we are reading the kpds5
value is
> 222.  Why didn't that work?  We don't want to keep adding additional
> grib tables to get MET to work.  When we run data_plane, we don't
get
> the message you got "Undefined parameter table (center 57-4 table
3),
> using NCEP-opn", instead we get the following:
>
> 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: Opening data file:
/home/qcteam/fss/meps/grib.2017091422.0006
> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created new
> Met2dDataFile object of type "FileType_Gb1".
> DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
object
> of type "FileType_Gb1".
> DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found 0 GRIB
records
> matching VarInfo "QP010/Z0" in GRIB file
> "/home/qcteam/fss/meps/grib.2017091422.0006".
> WARNING:
> WARNING: MetGrib1DataFile::data_plane() -> No exact match found for
> VarInfo "QP010/Z0" in GRIB file
"/home/qcteam/fss/meps/grib.2017091422.0006".
> WARNING:
> ERROR  :
> ERROR  : plot_data_plane -> trouble getting field "name="QP010";
> PROB="true"; level="Z0";" from file
> "/home/qcteam/fss/meps/grib.2017091422.0006"
> ERROR  :
>
> So why didn't adding QP010 to our existing table work?
>
> Thanks
> Bob
>
> -----Original Message-----
> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> Sent: Monday, October 02, 2017 6:01 PM
> To: MELICK, CHRISTOPHER J GS-12 USAF ACC 16 WS/WXES
> <christopher.melick at us.af.mil>
> Cc: 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 #82163] GRIB1 Error
>
> Hello Chris,
>
> I see that you're having trouble accessing a particular GRIB record.
> You're looking for a field named "QP010" but plot_data_plane is
unable
> to find it in the input file.
>
> This is an issue with how the GRIB tables are defined... looking in
> the GRIB tables defined for MET in met-6.0/data/table_files, there
is
> no mention of a field named "QP010".
>
> When I run the GRIB file you sent through wgrib, I get the following
> warning
> message:
>
> Undefined parameter table (center 57-4 table 3), using NCEP-opn
>
> That means that wgrib doesn't have a table defining GRIB usage for
> center number 57, subcenter number 4, and table number 3... just
like MET doesn't.
>
> Fortunately, there is a method you can use to define that GRIB table
> and tell MET how to use it.
>
> Here are the steps I followed...
>
> (1) Copy over the existing Air Force GRIB table, changing table
number
> 131 to table number 3 and subcenter number 2 to 4:
>
> cat met-6.0/share/met/table_files/grib1_af_131_57.txt | \
>   sed 's/ 131 / 3 /g' | sed 's/ 57 2 / 57 4 /g' \
>   > grib1_af_3_57.txt
>
> (2) I wrote the output to a new file named "grib1_af_3_57.txt".
>
> (3) Set the MET_GRIB_TABLES environment variable to point to either
a
> filename or a directory containing user-specified GRIB table files:
>
>   setenv MET_GRIB_TABLES grib1_af_3_57.txt
>
> (4) Here's the issue... I have no idea what your GRIB table usage
> actually is.
> So I'll just make a very wild guess and assume that whatever is in
the
> first GRIB record is QP010.  Here's the output from wgrib:
>
>
>
1:0:d=17091422:5WAVA:kpds5=230:kpds6=1:kpds7=0:TR=0:P1=6:P2=0:TimeU=1:
> sfc:6hr
> fcst:NAve=0
>
> That tells me this is GRIB number 230 (i.e. kpds5=230).
>
> So I edited grib1_af_3_57.txt for GRIB number 230 as follows:
>
>    230 3 57 4 "QP010" "Probability of Precip" "%"
>
> (5) Rerun plot_data_plane requesting QP010:
>
> met-6.0/bin/plot_data_plane \
>    grib.2017091422.0006 plot.ps \
>    'name="QP010"; PROB="true"; level="Z0";' -v 4
>
> And sure enough, MET now finds QP010 in the first GRIB record:
>
> DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found range match
for
> VarInfo "QP010/Z0" in GRIB record 1 of GRIB file
> "grib.2017091422.0006".
>
> And it created the attached plot.
>
> Now I'm pretty sure that this is actually a plot of latitude... not
QP010.
>
> But it's up to you to specify how you're using GRIB tables.  And
once
> you finalize the settings, we'd be happy to include your version of
> "grib1_af_3_57.txt" in the next MET release.
>
> Hopefully you have your GRIB table usage for Air Force (center 57),
> subcenter 4, and table number 3 defined somewhere.
>
> Hope that helps clarify the situation.
>
> Thanks,
> John Halley Gotway
>
>
> On Fri, Sep 29, 2017 at 2:12 PM, christopher.melick at us.af.mil via RT
<
> met_help at ucar.edu> wrote:
>
> >
> > Fri Sep 29 14:12:33 2017: Request 82163 was acted upon.
> > Transaction: Ticket created by christopher.melick at us.af.mil
> >        Queue: met_help
> >      Subject: GRIB1 Error
> >        Owner: Nobody
> >   Requestors: christopher.melick at us.af.mil
> >       Status: new
> >  Ticket <URL:
> > https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=82163
> > >
> >
> >
> > Hi John,
> >
> > When running the following MET command on the GRIB1 file, Bob
Craig
> > and I get this error:
> >
> > /h/WXQC/met-6.0/bin/plot_data_plane
> > /home/qcteam/fss/meps/grib.2017091422.0006 /home/qcteam/testimg
> > 'name="QP010"; PROB="true"; level="Z0"> 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: Opening data file:
> > /home/qcteam/fss/meps/grib.2017091422.0006
> > DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created
new
> > Met2dDataFile object of type "FileType_Gb1".
> > DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
> > object of type "FileType_Gb1".
> > DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found 0 GRIB
> > records matching VarInfo "QP010/Z0" in GRIB file
> > "/home/qcteam/fss/meps/grib.2017091422.0006".
> > WARNING:
> > WARNING: MetGrib1DataFile::data_plane() -> No exact match found
for
> > VarInfo "QP010/Z0" in GRIB file
> > "/home/qcteam/fss/meps/grib.2017091422.0006".
> > WARNING:
> > ERROR  :
> > ERROR  : plot_data_plane -> trouble getting field "name="QP010";
> > PROB="true"; level="Z0";" from file
> > "/home/qcteam/fss/meps/grib.2017091422.0006"
> > ERROR  :
> >
> > Can you please assist in determining what the problem might be?
> >
> > For your reference, Bob uploaded the GRIB1 file to the AMRDEC
system
> > and you should be receiving notification about how to retrieve the
> > data.  Please let us know if you are unable or have problems in
> > doing so.
> >
> > Thanks,
> > Chris
> >
> > //SIGNED//
> >
> > Dr. Christopher J. Melick, DAF Civilian Meteorologist, Science
> > Exploitation Team 16th Weather Squadron (16 WS/WXES) 557th Weather
> > Wing, Offutt AFB, NE DSN 271-3693; Comm (402) 294-3693
> >
> >
> >
> >
> >
>
>
>

------------------------------------------------
Subject: GRIB1 Error
From: John Halley Gotway
Time: Tue Oct 03 09:06:14 2017

Bob,

OK, great.  Glad you figured it out.

If these tables that you're working on represent somewhat "official"
GRIB
table usage at the Air Force, we'd be happy to distribute them with
the
next MET release so that you don't have to keep working through these
details.

But if they're really custom to you, or your specific group's usage,
then
continuing to use MET_GRIB_TABLES is probably the way to go.

Thanks,
John

On Tue, Oct 3, 2017 at 8:35 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=82163 >
>
> John, I got it working - I forgot to include qp010 in my new table
that
> you suggested.
>
> Thanks
> Bob
>
> -----Original Message-----
> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> Sent: Tuesday, October 03, 2017 8:50 AM
> To: MELICK, CHRISTOPHER J GS-12 USAF ACC 16 WS/WXES <
> christopher.melick at us.af.mil>
> Cc: 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 #82163] GRIB1
Error
>
> Bob,
>
> The GRIB table you sent is for center 57, subcenter 2.  The GRIB
file you
> sent is for center 57, subcenter 4.
>
> I think that’s why there’s no match.
>
> Make sense?
>
> John
>
> On Tue, Oct 3, 2017 at 7:07 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=82163 >
> >
> > Hi john, attached is the grib 1 table pointed at by the
> > MET_GRIB_TABLES environmental variable.  In this table Chris and I
added
> qp010 to record
> > number 224 (kpds5=222).   I the data file we are reading the kpds5
value
> is
> > 222.  Why didn't that work?  We don't want to keep adding
additional
> > grib tables to get MET to work.  When we run data_plane, we don't
get
> > the message you got "Undefined parameter table (center 57-4 table
3),
> > using NCEP-opn", instead we get the following:
> >
> > 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: Opening data file:
/home/qcteam/fss/meps/grib.2017091422.0006
> > DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created
new
> > Met2dDataFile object of type "FileType_Gb1".
> > DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
object
> > of type "FileType_Gb1".
> > DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found 0 GRIB
records
> > matching VarInfo "QP010/Z0" in GRIB file
> > "/home/qcteam/fss/meps/grib.2017091422.0006".
> > WARNING:
> > WARNING: MetGrib1DataFile::data_plane() -> No exact match found
for
> > VarInfo "QP010/Z0" in GRIB file "/home/qcteam/fss/meps/grib.
> 2017091422.0006".
> > WARNING:
> > ERROR  :
> > ERROR  : plot_data_plane -> trouble getting field "name="QP010";
> > PROB="true"; level="Z0";" from file
> > "/home/qcteam/fss/meps/grib.2017091422.0006"
> > ERROR  :
> >
> > So why didn't adding QP010 to our existing table work?
> >
> > Thanks
> > Bob
> >
> > -----Original Message-----
> > From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> > Sent: Monday, October 02, 2017 6:01 PM
> > To: MELICK, CHRISTOPHER J GS-12 USAF ACC 16 WS/WXES
> > <christopher.melick at us.af.mil>
> > Cc: 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 #82163] GRIB1 Error
> >
> > Hello Chris,
> >
> > I see that you're having trouble accessing a particular GRIB
record.
> > You're looking for a field named "QP010" but plot_data_plane is
unable
> > to find it in the input file.
> >
> > This is an issue with how the GRIB tables are defined... looking
in
> > the GRIB tables defined for MET in met-6.0/data/table_files, there
is
> > no mention of a field named "QP010".
> >
> > When I run the GRIB file you sent through wgrib, I get the
following
> > warning
> > message:
> >
> > Undefined parameter table (center 57-4 table 3), using NCEP-opn
> >
> > That means that wgrib doesn't have a table defining GRIB usage for
> > center number 57, subcenter number 4, and table number 3... just
like
> MET doesn't.
> >
> > Fortunately, there is a method you can use to define that GRIB
table
> > and tell MET how to use it.
> >
> > Here are the steps I followed...
> >
> > (1) Copy over the existing Air Force GRIB table, changing table
number
> > 131 to table number 3 and subcenter number 2 to 4:
> >
> > cat met-6.0/share/met/table_files/grib1_af_131_57.txt | \
> >   sed 's/ 131 / 3 /g' | sed 's/ 57 2 / 57 4 /g' \
> >   > grib1_af_3_57.txt
> >
> > (2) I wrote the output to a new file named "grib1_af_3_57.txt".
> >
> > (3) Set the MET_GRIB_TABLES environment variable to point to
either a
> > filename or a directory containing user-specified GRIB table
files:
> >
> >   setenv MET_GRIB_TABLES grib1_af_3_57.txt
> >
> > (4) Here's the issue... I have no idea what your GRIB table usage
> > actually is.
> > So I'll just make a very wild guess and assume that whatever is in
the
> > first GRIB record is QP010.  Here's the output from wgrib:
> >
> >
> >
1:0:d=17091422:5WAVA:kpds5=230:kpds6=1:kpds7=0:TR=0:P1=6:P2=0:TimeU=1:
> > sfc:6hr
> > fcst:NAve=0
> >
> > That tells me this is GRIB number 230 (i.e. kpds5=230).
> >
> > So I edited grib1_af_3_57.txt for GRIB number 230 as follows:
> >
> >    230 3 57 4 "QP010" "Probability of Precip" "%"
> >
> > (5) Rerun plot_data_plane requesting QP010:
> >
> > met-6.0/bin/plot_data_plane \
> >    grib.2017091422.0006 plot.ps \
> >    'name="QP010"; PROB="true"; level="Z0";' -v 4
> >
> > And sure enough, MET now finds QP010 in the first GRIB record:
> >
> > DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found range match
for
> > VarInfo "QP010/Z0" in GRIB record 1 of GRIB file
> > "grib.2017091422.0006".
> >
> > And it created the attached plot.
> >
> > Now I'm pretty sure that this is actually a plot of latitude...
not
> QP010.
> >
> > But it's up to you to specify how you're using GRIB tables.  And
once
> > you finalize the settings, we'd be happy to include your version
of
> > "grib1_af_3_57.txt" in the next MET release.
> >
> > Hopefully you have your GRIB table usage for Air Force (center
57),
> > subcenter 4, and table number 3 defined somewhere.
> >
> > Hope that helps clarify the situation.
> >
> > Thanks,
> > John Halley Gotway
> >
> >
> > On Fri, Sep 29, 2017 at 2:12 PM, christopher.melick at us.af.mil via
RT <
> > met_help at ucar.edu> wrote:
> >
> > >
> > > Fri Sep 29 14:12:33 2017: Request 82163 was acted upon.
> > > Transaction: Ticket created by christopher.melick at us.af.mil
> > >        Queue: met_help
> > >      Subject: GRIB1 Error
> > >        Owner: Nobody
> > >   Requestors: christopher.melick at us.af.mil
> > >       Status: new
> > >  Ticket <URL:
> > > https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=82163
> > > >
> > >
> > >
> > > Hi John,
> > >
> > > When running the following MET command on the GRIB1 file, Bob
Craig
> > > and I get this error:
> > >
> > > /h/WXQC/met-6.0/bin/plot_data_plane
> > > /home/qcteam/fss/meps/grib.2017091422.0006 /home/qcteam/testimg
> > > 'name="QP010"; PROB="true"; level="Z0"> 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: Opening data file:
> > > /home/qcteam/fss/meps/grib.2017091422.0006
> > > DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created
new
> > > Met2dDataFile object of type "FileType_Gb1".
> > > DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
> > > object of type "FileType_Gb1".
> > > DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found 0 GRIB
> > > records matching VarInfo "QP010/Z0" in GRIB file
> > > "/home/qcteam/fss/meps/grib.2017091422.0006".
> > > WARNING:
> > > WARNING: MetGrib1DataFile::data_plane() -> No exact match found
for
> > > VarInfo "QP010/Z0" in GRIB file
> > > "/home/qcteam/fss/meps/grib.2017091422.0006".
> > > WARNING:
> > > ERROR  :
> > > ERROR  : plot_data_plane -> trouble getting field "name="QP010";
> > > PROB="true"; level="Z0";" from file
> > > "/home/qcteam/fss/meps/grib.2017091422.0006"
> > > ERROR  :
> > >
> > > Can you please assist in determining what the problem might be?
> > >
> > > For your reference, Bob uploaded the GRIB1 file to the AMRDEC
system
> > > and you should be receiving notification about how to retrieve
the
> > > data.  Please let us know if you are unable or have problems in
> > > doing so.
> > >
> > > Thanks,
> > > Chris
> > >
> > > //SIGNED//
> > >
> > > Dr. Christopher J. Melick, DAF Civilian Meteorologist, Science
> > > Exploitation Team 16th Weather Squadron (16 WS/WXES) 557th
Weather
> > > Wing, Offutt AFB, NE DSN 271-3693; Comm (402) 294-3693
> > >
> > >
> > >
> > >
> > >
> >
> >
> >
>
>
>
>
>

------------------------------------------------
Subject: RE: [Non-DoD Source] Re: [rt.rap.ucar.edu #82163] GRIB1 Error
From: robert.craig.2 at us.af.mil
Time: Tue Oct 03 10:05:03 2017

John, they are somewhat custom I guess - we have added parameters to
them that weren't in the tables that came from MET.   A while back you
mentioned you were going to rewrite the GRIB definition portion of
MET.  Is that still in the works?

Thanks
Bob

-----Original Message-----
From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
Sent: Tuesday, October 03, 2017 10:06 AM
To: MELICK, CHRISTOPHER J GS-12 USAF ACC 16 WS/WXES
<christopher.melick at us.af.mil>
Cc: 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 #82163] GRIB1 Error

Bob,

OK, great.  Glad you figured it out.

If these tables that you're working on represent somewhat "official"
GRIB table usage at the Air Force, we'd be happy to distribute them
with the next MET release so that you don't have to keep working
through these details.

But if they're really custom to you, or your specific group's usage,
then continuing to use MET_GRIB_TABLES is probably the way to go.

Thanks,
John

On Tue, Oct 3, 2017 at 8:35 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=82163 >
>
> John, I got it working - I forgot to include qp010 in my new table
> that you suggested.
>
> Thanks
> Bob
>
> -----Original Message-----
> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> Sent: Tuesday, October 03, 2017 8:50 AM
> To: MELICK, CHRISTOPHER J GS-12 USAF ACC 16 WS/WXES <
> christopher.melick at us.af.mil>
> Cc: 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 #82163] GRIB1
Error
>
> Bob,
>
> The GRIB table you sent is for center 57, subcenter 2.  The GRIB
file
> you sent is for center 57, subcenter 4.
>
> I think that’s why there’s no match.
>
> Make sense?
>
> John
>
> On Tue, Oct 3, 2017 at 7:07 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=82163 >
> >
> > Hi john, attached is the grib 1 table pointed at by the
> > MET_GRIB_TABLES environmental variable.  In this table Chris and I
> > added
> qp010 to record
> > number 224 (kpds5=222).   I the data file we are reading the kpds5
value
> is
> > 222.  Why didn't that work?  We don't want to keep adding
additional
> > grib tables to get MET to work.  When we run data_plane, we don't
> > get the message you got "Undefined parameter table (center 57-4
> > table 3), using NCEP-opn", instead we get the following:
> >
> > 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: Opening data file:
> > /home/qcteam/fss/meps/grib.2017091422.0006
> > DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created
new
> > Met2dDataFile object of type "FileType_Gb1".
> > DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
> > object of type "FileType_Gb1".
> > DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found 0 GRIB
> > records matching VarInfo "QP010/Z0" in GRIB file
> > "/home/qcteam/fss/meps/grib.2017091422.0006".
> > WARNING:
> > WARNING: MetGrib1DataFile::data_plane() -> No exact match found
for
> > VarInfo "QP010/Z0" in GRIB file "/home/qcteam/fss/meps/grib.
> 2017091422.0006".
> > WARNING:
> > ERROR  :
> > ERROR  : plot_data_plane -> trouble getting field "name="QP010";
> > PROB="true"; level="Z0";" from file
> > "/home/qcteam/fss/meps/grib.2017091422.0006"
> > ERROR  :
> >
> > So why didn't adding QP010 to our existing table work?
> >
> > Thanks
> > Bob
> >
> > -----Original Message-----
> > From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> > Sent: Monday, October 02, 2017 6:01 PM
> > To: MELICK, CHRISTOPHER J GS-12 USAF ACC 16 WS/WXES
> > <christopher.melick at us.af.mil>
> > Cc: 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 #82163] GRIB1 Error
> >
> > Hello Chris,
> >
> > I see that you're having trouble accessing a particular GRIB
record.
> > You're looking for a field named "QP010" but plot_data_plane is
> > unable to find it in the input file.
> >
> > This is an issue with how the GRIB tables are defined... looking
in
> > the GRIB tables defined for MET in met-6.0/data/table_files, there
> > is no mention of a field named "QP010".
> >
> > When I run the GRIB file you sent through wgrib, I get the
following
> > warning
> > message:
> >
> > Undefined parameter table (center 57-4 table 3), using NCEP-opn
> >
> > That means that wgrib doesn't have a table defining GRIB usage for
> > center number 57, subcenter number 4, and table number 3... just
> > like
> MET doesn't.
> >
> > Fortunately, there is a method you can use to define that GRIB
table
> > and tell MET how to use it.
> >
> > Here are the steps I followed...
> >
> > (1) Copy over the existing Air Force GRIB table, changing table
> > number
> > 131 to table number 3 and subcenter number 2 to 4:
> >
> > cat met-6.0/share/met/table_files/grib1_af_131_57.txt | \
> >   sed 's/ 131 / 3 /g' | sed 's/ 57 2 / 57 4 /g' \
> >   > grib1_af_3_57.txt
> >
> > (2) I wrote the output to a new file named "grib1_af_3_57.txt".
> >
> > (3) Set the MET_GRIB_TABLES environment variable to point to
either
> > a filename or a directory containing user-specified GRIB table
files:
> >
> >   setenv MET_GRIB_TABLES grib1_af_3_57.txt
> >
> > (4) Here's the issue... I have no idea what your GRIB table usage
> > actually is.
> > So I'll just make a very wild guess and assume that whatever is in
> > the first GRIB record is QP010.  Here's the output from wgrib:
> >
> >
> >
1:0:d=17091422:5WAVA:kpds5=230:kpds6=1:kpds7=0:TR=0:P1=6:P2=0:TimeU=1:
> > sfc:6hr
> > fcst:NAve=0
> >
> > That tells me this is GRIB number 230 (i.e. kpds5=230).
> >
> > So I edited grib1_af_3_57.txt for GRIB number 230 as follows:
> >
> >    230 3 57 4 "QP010" "Probability of Precip" "%"
> >
> > (5) Rerun plot_data_plane requesting QP010:
> >
> > met-6.0/bin/plot_data_plane \
> >    grib.2017091422.0006 plot.ps \
> >    'name="QP010"; PROB="true"; level="Z0";' -v 4
> >
> > And sure enough, MET now finds QP010 in the first GRIB record:
> >
> > DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found range match
> > for VarInfo "QP010/Z0" in GRIB record 1 of GRIB file
> > "grib.2017091422.0006".
> >
> > And it created the attached plot.
> >
> > Now I'm pretty sure that this is actually a plot of latitude...
not
> QP010.
> >
> > But it's up to you to specify how you're using GRIB tables.  And
> > once you finalize the settings, we'd be happy to include your
> > version of "grib1_af_3_57.txt" in the next MET release.
> >
> > Hopefully you have your GRIB table usage for Air Force (center
57),
> > subcenter 4, and table number 3 defined somewhere.
> >
> > Hope that helps clarify the situation.
> >
> > Thanks,
> > John Halley Gotway
> >
> >
> > On Fri, Sep 29, 2017 at 2:12 PM, christopher.melick at us.af.mil via
RT
> > < met_help at ucar.edu> wrote:
> >
> > >
> > > Fri Sep 29 14:12:33 2017: Request 82163 was acted upon.
> > > Transaction: Ticket created by christopher.melick at us.af.mil
> > >        Queue: met_help
> > >      Subject: GRIB1 Error
> > >        Owner: Nobody
> > >   Requestors: christopher.melick at us.af.mil
> > >       Status: new
> > >  Ticket <URL:
> > > https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=82163
> > > >
> > >
> > >
> > > Hi John,
> > >
> > > When running the following MET command on the GRIB1 file, Bob
> > > Craig and I get this error:
> > >
> > > /h/WXQC/met-6.0/bin/plot_data_plane
> > > /home/qcteam/fss/meps/grib.2017091422.0006 /home/qcteam/testimg
> > > 'name="QP010"; PROB="true"; level="Z0"> 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: Opening data file:
> > > /home/qcteam/fss/meps/grib.2017091422.0006
> > > DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created
> > > new Met2dDataFile object of type "FileType_Gb1".
> > > DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
> > > object of type "FileType_Gb1".
> > > DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found 0 GRIB
> > > records matching VarInfo "QP010/Z0" in GRIB file
> > > "/home/qcteam/fss/meps/grib.2017091422.0006".
> > > WARNING:
> > > WARNING: MetGrib1DataFile::data_plane() -> No exact match found
> > > for VarInfo "QP010/Z0" in GRIB file
> > > "/home/qcteam/fss/meps/grib.2017091422.0006".
> > > WARNING:
> > > ERROR  :
> > > ERROR  : plot_data_plane -> trouble getting field "name="QP010";
> > > PROB="true"; level="Z0";" from file
> > > "/home/qcteam/fss/meps/grib.2017091422.0006"
> > > ERROR  :
> > >
> > > Can you please assist in determining what the problem might be?
> > >
> > > For your reference, Bob uploaded the GRIB1 file to the AMRDEC
> > > system and you should be receiving notification about how to
> > > retrieve the data.  Please let us know if you are unable or have
> > > problems in doing so.
> > >
> > > Thanks,
> > > Chris
> > >
> > > //SIGNED//
> > >
> > > Dr. Christopher J. Melick, DAF Civilian Meteorologist, Science
> > > Exploitation Team 16th Weather Squadron (16 WS/WXES) 557th
Weather
> > > Wing, Offutt AFB, NE DSN 271-3693; Comm (402) 294-3693
> > >
> > >
> > >
> > >
> > >
> >
> >
> >
>
>
>
>
>

------------------------------------------------
Subject: GRIB1 Error
From: John Halley Gotway
Time: Tue Oct 03 13:51:06 2017

Bob,

We do still have that task listed in JIRA, where we store future
development tasks.  To be honest though, it is not specific enough to
be
actionable.  After working though these issues, is there some specific
functionality you would envision to make the selection of GRIB1 and
GRIB2
records much easier?

Thanks,
John

On Tue, Oct 3, 2017 at 10:05 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=82163 >
>
> John, they are somewhat custom I guess - we have added parameters to
them
> that weren't in the tables that came from MET.   A while back you
mentioned
> you were going to rewrite the GRIB definition portion of MET.  Is
that
> still in the works?
>
> Thanks
> Bob
>
> -----Original Message-----
> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> Sent: Tuesday, October 03, 2017 10:06 AM
> To: MELICK, CHRISTOPHER J GS-12 USAF ACC 16 WS/WXES <
> christopher.melick at us.af.mil>
> Cc: 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 #82163] GRIB1
Error
>
> Bob,
>
> OK, great.  Glad you figured it out.
>
> If these tables that you're working on represent somewhat "official"
GRIB
> table usage at the Air Force, we'd be happy to distribute them with
the
> next MET release so that you don't have to keep working through
these
> details.
>
> But if they're really custom to you, or your specific group's usage,
then
> continuing to use MET_GRIB_TABLES is probably the way to go.
>
> Thanks,
> John
>
>
> On Tue, Oct 3, 2017 at 8:35 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=82163 >
> >
> > John, I got it working - I forgot to include qp010 in my new table
> > that you suggested.
> >
> > Thanks
> > Bob
> >
> > -----Original Message-----
> > From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> > Sent: Tuesday, October 03, 2017 8:50 AM
> > To: MELICK, CHRISTOPHER J GS-12 USAF ACC 16 WS/WXES <
> > christopher.melick at us.af.mil>
> > Cc: 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 #82163] GRIB1
Error
> >
> > Bob,
> >
> > The GRIB table you sent is for center 57, subcenter 2.  The GRIB
file
> > you sent is for center 57, subcenter 4.
> >
> > I think that’s why there’s no match.
> >
> > Make sense?
> >
> > John
> >
> > On Tue, Oct 3, 2017 at 7:07 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=82163 >
> > >
> > > Hi john, attached is the grib 1 table pointed at by the
> > > MET_GRIB_TABLES environmental variable.  In this table Chris and
I
> > > added
> > qp010 to record
> > > number 224 (kpds5=222).   I the data file we are reading the
kpds5
> value
> > is
> > > 222.  Why didn't that work?  We don't want to keep adding
additional
> > > grib tables to get MET to work.  When we run data_plane, we
don't
> > > get the message you got "Undefined parameter table (center 57-4
> > > table 3), using NCEP-opn", instead we get the following:
> > >
> > > 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: Opening data file:
> > > /home/qcteam/fss/meps/grib.2017091422.0006
> > > DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created
new
> > > Met2dDataFile object of type "FileType_Gb1".
> > > DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
> > > object of type "FileType_Gb1".
> > > DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found 0 GRIB
> > > records matching VarInfo "QP010/Z0" in GRIB file
> > > "/home/qcteam/fss/meps/grib.2017091422.0006".
> > > WARNING:
> > > WARNING: MetGrib1DataFile::data_plane() -> No exact match found
for
> > > VarInfo "QP010/Z0" in GRIB file "/home/qcteam/fss/meps/grib.
> > 2017091422.0006".
> > > WARNING:
> > > ERROR  :
> > > ERROR  : plot_data_plane -> trouble getting field "name="QP010";
> > > PROB="true"; level="Z0";" from file
> > > "/home/qcteam/fss/meps/grib.2017091422.0006"
> > > ERROR  :
> > >
> > > So why didn't adding QP010 to our existing table work?
> > >
> > > Thanks
> > > Bob
> > >
> > > -----Original Message-----
> > > From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> > > Sent: Monday, October 02, 2017 6:01 PM
> > > To: MELICK, CHRISTOPHER J GS-12 USAF ACC 16 WS/WXES
> > > <christopher.melick at us.af.mil>
> > > Cc: 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 #82163] GRIB1
Error
> > >
> > > Hello Chris,
> > >
> > > I see that you're having trouble accessing a particular GRIB
record.
> > > You're looking for a field named "QP010" but plot_data_plane is
> > > unable to find it in the input file.
> > >
> > > This is an issue with how the GRIB tables are defined... looking
in
> > > the GRIB tables defined for MET in met-6.0/data/table_files,
there
> > > is no mention of a field named "QP010".
> > >
> > > When I run the GRIB file you sent through wgrib, I get the
following
> > > warning
> > > message:
> > >
> > > Undefined parameter table (center 57-4 table 3), using NCEP-opn
> > >
> > > That means that wgrib doesn't have a table defining GRIB usage
for
> > > center number 57, subcenter number 4, and table number 3... just
> > > like
> > MET doesn't.
> > >
> > > Fortunately, there is a method you can use to define that GRIB
table
> > > and tell MET how to use it.
> > >
> > > Here are the steps I followed...
> > >
> > > (1) Copy over the existing Air Force GRIB table, changing table
> > > number
> > > 131 to table number 3 and subcenter number 2 to 4:
> > >
> > > cat met-6.0/share/met/table_files/grib1_af_131_57.txt | \
> > >   sed 's/ 131 / 3 /g' | sed 's/ 57 2 / 57 4 /g' \
> > >   > grib1_af_3_57.txt
> > >
> > > (2) I wrote the output to a new file named "grib1_af_3_57.txt".
> > >
> > > (3) Set the MET_GRIB_TABLES environment variable to point to
either
> > > a filename or a directory containing user-specified GRIB table
files:
> > >
> > >   setenv MET_GRIB_TABLES grib1_af_3_57.txt
> > >
> > > (4) Here's the issue... I have no idea what your GRIB table
usage
> > > actually is.
> > > So I'll just make a very wild guess and assume that whatever is
in
> > > the first GRIB record is QP010.  Here's the output from wgrib:
> > >
> > >
> > >
1:0:d=17091422:5WAVA:kpds5=230:kpds6=1:kpds7=0:TR=0:P1=6:P2=0:TimeU=1:
> > > sfc:6hr
> > > fcst:NAve=0
> > >
> > > That tells me this is GRIB number 230 (i.e. kpds5=230).
> > >
> > > So I edited grib1_af_3_57.txt for GRIB number 230 as follows:
> > >
> > >    230 3 57 4 "QP010" "Probability of Precip" "%"
> > >
> > > (5) Rerun plot_data_plane requesting QP010:
> > >
> > > met-6.0/bin/plot_data_plane \
> > >    grib.2017091422.0006 plot.ps \
> > >    'name="QP010"; PROB="true"; level="Z0";' -v 4
> > >
> > > And sure enough, MET now finds QP010 in the first GRIB record:
> > >
> > > DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found range
match
> > > for VarInfo "QP010/Z0" in GRIB record 1 of GRIB file
> > > "grib.2017091422.0006".
> > >
> > > And it created the attached plot.
> > >
> > > Now I'm pretty sure that this is actually a plot of latitude...
not
> > QP010.
> > >
> > > But it's up to you to specify how you're using GRIB tables.  And
> > > once you finalize the settings, we'd be happy to include your
> > > version of "grib1_af_3_57.txt" in the next MET release.
> > >
> > > Hopefully you have your GRIB table usage for Air Force (center
57),
> > > subcenter 4, and table number 3 defined somewhere.
> > >
> > > Hope that helps clarify the situation.
> > >
> > > Thanks,
> > > John Halley Gotway
> > >
> > >
> > > On Fri, Sep 29, 2017 at 2:12 PM, christopher.melick at us.af.mil
via RT
> > > < met_help at ucar.edu> wrote:
> > >
> > > >
> > > > Fri Sep 29 14:12:33 2017: Request 82163 was acted upon.
> > > > Transaction: Ticket created by christopher.melick at us.af.mil
> > > >        Queue: met_help
> > > >      Subject: GRIB1 Error
> > > >        Owner: Nobody
> > > >   Requestors: christopher.melick at us.af.mil
> > > >       Status: new
> > > >  Ticket <URL:
> > > > https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=82163
> > > > >
> > > >
> > > >
> > > > Hi John,
> > > >
> > > > When running the following MET command on the GRIB1 file, Bob
> > > > Craig and I get this error:
> > > >
> > > > /h/WXQC/met-6.0/bin/plot_data_plane
> > > > /home/qcteam/fss/meps/grib.2017091422.0006
/home/qcteam/testimg
> > > > 'name="QP010"; PROB="true"; level="Z0"> 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: Opening data file:
> > > > /home/qcteam/fss/meps/grib.2017091422.0006
> > > > DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() ->
created
> > > > new Met2dDataFile object of type "FileType_Gb1".
> > > > DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
> > > > object of type "FileType_Gb1".
> > > > DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found 0 GRIB
> > > > records matching VarInfo "QP010/Z0" in GRIB file
> > > > "/home/qcteam/fss/meps/grib.2017091422.0006".
> > > > WARNING:
> > > > WARNING: MetGrib1DataFile::data_plane() -> No exact match
found
> > > > for VarInfo "QP010/Z0" in GRIB file
> > > > "/home/qcteam/fss/meps/grib.2017091422.0006".
> > > > WARNING:
> > > > ERROR  :
> > > > ERROR  : plot_data_plane -> trouble getting field
"name="QP010";
> > > > PROB="true"; level="Z0";" from file
> > > > "/home/qcteam/fss/meps/grib.2017091422.0006"
> > > > ERROR  :
> > > >
> > > > Can you please assist in determining what the problem might
be?
> > > >
> > > > For your reference, Bob uploaded the GRIB1 file to the AMRDEC
> > > > system and you should be receiving notification about how to
> > > > retrieve the data.  Please let us know if you are unable or
have
> > > > problems in doing so.
> > > >
> > > > Thanks,
> > > > Chris
> > > >
> > > > //SIGNED//
> > > >
> > > > Dr. Christopher J. Melick, DAF Civilian Meteorologist, Science
> > > > Exploitation Team 16th Weather Squadron (16 WS/WXES) 557th
Weather
> > > > Wing, Offutt AFB, NE DSN 271-3693; Comm (402) 294-3693
> > > >
> > > >
> > > >
> > > >
> > > >
> > >
> > >
> > >
> >
> >
> >
> >
> >
>
>
>
>
>

------------------------------------------------
Subject: RE: [Non-DoD Source] Re: [rt.rap.ucar.edu #82163] GRIB1 Error
From: robert.craig.2 at us.af.mil
Time: Tue Oct 03 15:26:20 2017

John, I would think a more informational error message would help.  In
this case it could say that no table was found with the subcenter = 4,
table number = 3.  Error messages should try to point to a solution if
possible.

Thanks
Bob

-----Original Message-----
From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
Sent: Tuesday, October 03, 2017 2:51 PM
To: MELICK, CHRISTOPHER J GS-12 USAF ACC 16 WS/WXES
<christopher.melick at us.af.mil>
Cc: 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 #82163] GRIB1 Error

Bob,

We do still have that task listed in JIRA, where we store future
development tasks.  To be honest though, it is not specific enough to
be actionable.  After working though these issues, is there some
specific functionality you would envision to make the selection of
GRIB1 and GRIB2 records much easier?

Thanks,
John

On Tue, Oct 3, 2017 at 10:05 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=82163 >
>
> John, they are somewhat custom I guess - we have added parameters to
them
> that weren't in the tables that came from MET.   A while back you
mentioned
> you were going to rewrite the GRIB definition portion of MET.  Is
that
> still in the works?
>
> Thanks
> Bob
>
> -----Original Message-----
> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> Sent: Tuesday, October 03, 2017 10:06 AM
> To: MELICK, CHRISTOPHER J GS-12 USAF ACC 16 WS/WXES <
> christopher.melick at us.af.mil>
> Cc: 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 #82163] GRIB1
Error
>
> Bob,
>
> OK, great.  Glad you figured it out.
>
> If these tables that you're working on represent somewhat "official"
> GRIB table usage at the Air Force, we'd be happy to distribute them
> with the next MET release so that you don't have to keep working
> through these details.
>
> But if they're really custom to you, or your specific group's usage,
> then continuing to use MET_GRIB_TABLES is probably the way to go.
>
> Thanks,
> John
>
>
> On Tue, Oct 3, 2017 at 8:35 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=82163 >
> >
> > John, I got it working - I forgot to include qp010 in my new table
> > that you suggested.
> >
> > Thanks
> > Bob
> >
> > -----Original Message-----
> > From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> > Sent: Tuesday, October 03, 2017 8:50 AM
> > To: MELICK, CHRISTOPHER J GS-12 USAF ACC 16 WS/WXES <
> > christopher.melick at us.af.mil>
> > Cc: 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 #82163] GRIB1
> > Error
> >
> > Bob,
> >
> > The GRIB table you sent is for center 57, subcenter 2.  The GRIB
> > file you sent is for center 57, subcenter 4.
> >
> > I think that’s why there’s no match.
> >
> > Make sense?
> >
> > John
> >
> > On Tue, Oct 3, 2017 at 7:07 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=82163 >
> > >
> > > Hi john, attached is the grib 1 table pointed at by the
> > > MET_GRIB_TABLES environmental variable.  In this table Chris and
I
> > > added
> > qp010 to record
> > > number 224 (kpds5=222).   I the data file we are reading the
kpds5
> value
> > is
> > > 222.  Why didn't that work?  We don't want to keep adding
> > > additional grib tables to get MET to work.  When we run
> > > data_plane, we don't get the message you got "Undefined
parameter
> > > table (center 57-4 table 3), using NCEP-opn", instead we get the
following:
> > >
> > > 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: Opening data file:
> > > /home/qcteam/fss/meps/grib.2017091422.0006
> > > DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created
> > > new Met2dDataFile object of type "FileType_Gb1".
> > > DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
> > > object of type "FileType_Gb1".
> > > DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found 0 GRIB
> > > records matching VarInfo "QP010/Z0" in GRIB file
> > > "/home/qcteam/fss/meps/grib.2017091422.0006".
> > > WARNING:
> > > WARNING: MetGrib1DataFile::data_plane() -> No exact match found
> > > for VarInfo "QP010/Z0" in GRIB file "/home/qcteam/fss/meps/grib.
> > 2017091422.0006".
> > > WARNING:
> > > ERROR  :
> > > ERROR  : plot_data_plane -> trouble getting field "name="QP010";
> > > PROB="true"; level="Z0";" from file
> > > "/home/qcteam/fss/meps/grib.2017091422.0006"
> > > ERROR  :
> > >
> > > So why didn't adding QP010 to our existing table work?
> > >
> > > Thanks
> > > Bob
> > >
> > > -----Original Message-----
> > > From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> > > Sent: Monday, October 02, 2017 6:01 PM
> > > To: MELICK, CHRISTOPHER J GS-12 USAF ACC 16 WS/WXES
> > > <christopher.melick at us.af.mil>
> > > Cc: 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 #82163] GRIB1
Error
> > >
> > > Hello Chris,
> > >
> > > I see that you're having trouble accessing a particular GRIB
record.
> > > You're looking for a field named "QP010" but plot_data_plane is
> > > unable to find it in the input file.
> > >
> > > This is an issue with how the GRIB tables are defined... looking
> > > in the GRIB tables defined for MET in met-6.0/data/table_files,
> > > there is no mention of a field named "QP010".
> > >
> > > When I run the GRIB file you sent through wgrib, I get the
> > > following warning
> > > message:
> > >
> > > Undefined parameter table (center 57-4 table 3), using NCEP-opn
> > >
> > > That means that wgrib doesn't have a table defining GRIB usage
for
> > > center number 57, subcenter number 4, and table number 3... just
> > > like
> > MET doesn't.
> > >
> > > Fortunately, there is a method you can use to define that GRIB
> > > table and tell MET how to use it.
> > >
> > > Here are the steps I followed...
> > >
> > > (1) Copy over the existing Air Force GRIB table, changing table
> > > number
> > > 131 to table number 3 and subcenter number 2 to 4:
> > >
> > > cat met-6.0/share/met/table_files/grib1_af_131_57.txt | \
> > >   sed 's/ 131 / 3 /g' | sed 's/ 57 2 / 57 4 /g' \
> > >   > grib1_af_3_57.txt
> > >
> > > (2) I wrote the output to a new file named "grib1_af_3_57.txt".
> > >
> > > (3) Set the MET_GRIB_TABLES environment variable to point to
> > > either a filename or a directory containing user-specified GRIB
table files:
> > >
> > >   setenv MET_GRIB_TABLES grib1_af_3_57.txt
> > >
> > > (4) Here's the issue... I have no idea what your GRIB table
usage
> > > actually is.
> > > So I'll just make a very wild guess and assume that whatever is
in
> > > the first GRIB record is QP010.  Here's the output from wgrib:
> > >
> > >
> > >
1:0:d=17091422:5WAVA:kpds5=230:kpds6=1:kpds7=0:TR=0:P1=6:P2=0:TimeU=1:
> > > sfc:6hr
> > > fcst:NAve=0
> > >
> > > That tells me this is GRIB number 230 (i.e. kpds5=230).
> > >
> > > So I edited grib1_af_3_57.txt for GRIB number 230 as follows:
> > >
> > >    230 3 57 4 "QP010" "Probability of Precip" "%"
> > >
> > > (5) Rerun plot_data_plane requesting QP010:
> > >
> > > met-6.0/bin/plot_data_plane \
> > >    grib.2017091422.0006 plot.ps \
> > >    'name="QP010"; PROB="true"; level="Z0";' -v 4
> > >
> > > And sure enough, MET now finds QP010 in the first GRIB record:
> > >
> > > DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found range
match
> > > for VarInfo "QP010/Z0" in GRIB record 1 of GRIB file
> > > "grib.2017091422.0006".
> > >
> > > And it created the attached plot.
> > >
> > > Now I'm pretty sure that this is actually a plot of latitude...
> > > not
> > QP010.
> > >
> > > But it's up to you to specify how you're using GRIB tables.  And
> > > once you finalize the settings, we'd be happy to include your
> > > version of "grib1_af_3_57.txt" in the next MET release.
> > >
> > > Hopefully you have your GRIB table usage for Air Force (center
> > > 57), subcenter 4, and table number 3 defined somewhere.
> > >
> > > Hope that helps clarify the situation.
> > >
> > > Thanks,
> > > John Halley Gotway
> > >
> > >
> > > On Fri, Sep 29, 2017 at 2:12 PM, christopher.melick at us.af.mil
via
> > > RT < met_help at ucar.edu> wrote:
> > >
> > > >
> > > > Fri Sep 29 14:12:33 2017: Request 82163 was acted upon.
> > > > Transaction: Ticket created by christopher.melick at us.af.mil
> > > >        Queue: met_help
> > > >      Subject: GRIB1 Error
> > > >        Owner: Nobody
> > > >   Requestors: christopher.melick at us.af.mil
> > > >       Status: new
> > > >  Ticket <URL:
> > > > https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=82163
> > > > >
> > > >
> > > >
> > > > Hi John,
> > > >
> > > > When running the following MET command on the GRIB1 file, Bob
> > > > Craig and I get this error:
> > > >
> > > > /h/WXQC/met-6.0/bin/plot_data_plane
> > > > /home/qcteam/fss/meps/grib.2017091422.0006
/home/qcteam/testimg
> > > > 'name="QP010"; PROB="true"; level="Z0"> 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: Opening data file:
> > > > /home/qcteam/fss/meps/grib.2017091422.0006
> > > > DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() ->
created
> > > > new Met2dDataFile object of type "FileType_Gb1".
> > > > DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
> > > > object of type "FileType_Gb1".
> > > > DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found 0 GRIB
> > > > records matching VarInfo "QP010/Z0" in GRIB file
> > > > "/home/qcteam/fss/meps/grib.2017091422.0006".
> > > > WARNING:
> > > > WARNING: MetGrib1DataFile::data_plane() -> No exact match
found
> > > > for VarInfo "QP010/Z0" in GRIB file
> > > > "/home/qcteam/fss/meps/grib.2017091422.0006".
> > > > WARNING:
> > > > ERROR  :
> > > > ERROR  : plot_data_plane -> trouble getting field
"name="QP010";
> > > > PROB="true"; level="Z0";" from file
> > > > "/home/qcteam/fss/meps/grib.2017091422.0006"
> > > > ERROR  :
> > > >
> > > > Can you please assist in determining what the problem might
be?
> > > >
> > > > For your reference, Bob uploaded the GRIB1 file to the AMRDEC
> > > > system and you should be receiving notification about how to
> > > > retrieve the data.  Please let us know if you are unable or
have
> > > > problems in doing so.
> > > >
> > > > Thanks,
> > > > Chris
> > > >
> > > > //SIGNED//
> > > >
> > > > Dr. Christopher J. Melick, DAF Civilian Meteorologist, Science
> > > > Exploitation Team 16th Weather Squadron (16 WS/WXES) 557th
> > > > Weather Wing, Offutt AFB, NE DSN 271-3693; Comm (402) 294-3693
> > > >
> > > >
> > > >
> > > >
> > > >
> > >
> > >
> > >
> >
> >
> >
> >
> >
>
>
>
>
>

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