[Met_help] [rt.rap.ucar.edu #79856] History for Request
John Halley Gotway via RT
met_help at ucar.edu
Mon Apr 3 14:57:13 MDT 2017
----------------------------------------------------------------
Initial Request
----------------------------------------------------------------
John, I have a question/suggestion for 6.0. We don't have the same GRIB2 table definitions as those at are in the grib2_vars_flat.txt table. I can retrieve my model values defining the discipline code, parmcat, and parm values but MET will then put variable name that comes from the subject table into the STAT file. So in my case, I am retrieving probability of wind > 25 kts but heatflux might be the name that ends up in the STAT file MET produces. This problem can be solved if we can point MET to the proper grib2_vars_flat.txt table to use. Different MET users in 557th/AFWA could point MET to their own version of the table and we wouldn't step on each other.
Thank
Bob
----------------------------------------------------------------
Complete Ticket History
----------------------------------------------------------------
Subject: Request
From: John Halley Gotway
Time: Wed Mar 22 10:43:59 2017
Bob,
Yes, there is a way of having different users point to different GRIB2
tables to use, and it's present in version 5.2 of MET. But we've
refined
it in the upcoming 6.0 release.
For version 5.2, you do this by setting an environment variable named
"GRIB_USER_TABLES". It must be set to a *directory* containing files
that
begin with "grib1" or "grib2" and end with ".txt". Just place your
version
of grib2_var_flat.txt in that directory an edit it as needed.
The MET tools will read the contents of the GRIB_USER_TABLES directory
first and then the default ones second. Any of your local settings
will
take precedence over the default ones.
For version 6.0, we're renaming that "GRIB_USER_TABLES" to be
"MET_GRIB_TABLES", using the "MET_" prefix to be consistent with other
MET-related environment variables. In 6.0, it can be set to a
directory
containing multiple files or to an explicit file name to be used.
Please let me know if any additional issues or questions arise.
Thanks,
John
On Thu, Mar 16, 2017 at 7:55 AM, robert.craig.2 at us.af.mil via RT <
met_help at ucar.edu> wrote:
>
> Thu Mar 16 07:55:51 2017: Request 79856 was acted upon.
> Transaction: Ticket created by robert.craig.2 at us.af.mil
> Queue: met_help
> Subject: Request
> Owner: Nobody
> Requestors: robert.craig.2 at us.af.mil
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=79856 >
>
>
> John, I have a question/suggestion for 6.0. We don't have the same
GRIB2
> table definitions as those at are in the grib2_vars_flat.txt table.
I can
> retrieve my model values defining the discipline code, parmcat, and
parm
> values but MET will then put variable name that comes from the
subject
> table into the STAT file. So in my case, I am retrieving
probability of
> wind > 25 kts but heatflux might be the name that ends up in the
STAT file
> MET produces. This problem can be solved if we can point MET to the
proper
> grib2_vars_flat.txt table to use. Different MET users in 557th/AFWA
could
> point MET to their own version of the table and we wouldn't step on
each
> other.
>
> Thank
> Bob
>
>
>
------------------------------------------------
Subject: Request
From: robert.craig.2 at us.af.mil
Time: Fri Mar 24 12:40:10 2017
John, I made the changes you recommended and am still having issues.
Attached
is my config file and grib2 file. What did I miss?
[2647 qcteam hpc9-lsn-02d /home/qcteam] env | grep GRIB
GRIB_USER_TABLES=/h/data/global/WXQC/data/met/config/grib2
MET_GRIB2CINC=/h/WXQC/met-5.1/lib/g2clib-1.4.0
MET_GRIB2CLIB=/h/WXQC/met-5.1/lib/g2clib-1.4.0
In /h/data/global/WXQC/data/met/config/grib2 is a file called
grib2_geps.txt.
When I run the code I get the the following if I use the "name"
parameter in
the config file:
DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2 field
indexes - disc: 0, master table: 10, center: 57, local table: 1,
parm_cat: 6,
parm: 70
DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2 field
indexes - disc: 0, master table: 10, center: 57, local table: 1,
parm_cat: 19,
parm: 223
DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2 field
indexes - disc: 0, master table: 10, center: 57, local table: 1,
parm_cat: 19,
parm: 223
DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2 field
indexes - disc: 0, master table: 10, center: 57, local table: 1,
parm_cat: 19,
parm: 223
DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2 field
indexes - disc: 0, master table: 10, center: 57, local table: 1,
parm_cat: 19,
parm: 223
DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2 field
indexes - disc: 0, master table: 10, center: 57, local table: 1,
parm_cat: 19,
parm: 223
DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created new
Met2dDataFile object of type "FileType_NcMet".
DEBUG 4: Latitude/Longitude Grid Data:
DEBUG 4: lat_ll = -89.9219
DEBUG 4: lon_ll = -0.117187
DEBUG 4: delta_lat = 0.234375
DEBUG 4: delta_lon = 0.15625
DEBUG 4: Nlat = 1152
DEBUG 4: Nlon = 1536
DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo object
of type
"FileType_Gb2".
DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo object
of type
"FileType_NcMet".
ERROR :
ERROR : VarInfoGrib2::set_dict() - unrecognized GRIB2 field
abbreviation
'PWS15'
ERROR :
If I use the three grib2 parameters I get the following:
DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2 field
indexes - disc: 0, master table: 10, center: 57, local table: 1,
parm_cat: 6,
parm: 70
DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2 field
indexes - disc: 0, master table: 10, center: 57, local table: 1,
parm_cat: 6,
parm: 70
DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2 field
indexes - disc: 0, master table: 10, center: 57, local table: 1,
parm_cat: 6,
parm: 70
DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2 field
indexes - disc: 0, master table: 10, center: 57, local table: 1,
parm_cat: 19,
parm: 223
DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2 field
indexes - disc: 0, master table: 10, center: 57, local table: 1,
parm_cat: 19,
parm: 223
DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2 field
indexes - disc: 0, master table: 10, center: 57, local table: 1,
parm_cat: 19,
parm: 223
DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2 field
indexes - disc: 0, master table: 10, center: 57, local table: 1,
parm_cat: 19,
parm: 223
DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2 field
indexes - disc: 0, master table: 10, center: 57, local table: 1,
parm_cat: 19,
parm: 223
DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created new
Met2dDataFile object of type "FileType_NcMet".
DEBUG 4: Latitude/Longitude Grid Data:
DEBUG 4: lat_ll = -89.9219
DEBUG 4: lon_ll = -0.117187
DEBUG 4: delta_lat = 0.234375
DEBUG 4: delta_lon = 0.15625
DEBUG 4: Nlat = 1152
DEBUG 4: Nlon = 1536
DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo object
of type
"FileType_Gb2".
DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo object
of type
"FileType_NcMet".
ERROR :
ERROR : VarInfoGrib2::set_dict() - either name or GRIB2_disc,
GRIB2_parm_cat
and GRIB2_parm must be specified in field information
ERROR :
-----Original Message-----
From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
Sent: Wednesday, March 22, 2017 11:44 AM
To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
<robert.craig.2 at us.af.mil>
Subject: Re: [rt.rap.ucar.edu #79856] Request
Bob,
Yes, there is a way of having different users point to different GRIB2
tables
to use, and it's present in version 5.2 of MET. But we've refined it
in the
upcoming 6.0 release.
For version 5.2, you do this by setting an environment variable named
"GRIB_USER_TABLES". It must be set to a *directory* containing files
that
begin with "grib1" or "grib2" and end with ".txt". Just place your
version of
grib2_var_flat.txt in that directory an edit it as needed.
The MET tools will read the contents of the GRIB_USER_TABLES directory
first
and then the default ones second. Any of your local settings will
take
precedence over the default ones.
For version 6.0, we're renaming that "GRIB_USER_TABLES" to be
"MET_GRIB_TABLES", using the "MET_" prefix to be consistent with other
MET-related environment variables. In 6.0, it can be set to a
directory
containing multiple files or to an explicit file name to be used.
Please let me know if any additional issues or questions arise.
Thanks,
John
On Thu, Mar 16, 2017 at 7:55 AM, robert.craig.2 at us.af.mil via RT <
met_help at ucar.edu> wrote:
>
> Thu Mar 16 07:55:51 2017: Request 79856 was acted upon.
> Transaction: Ticket created by robert.craig.2 at us.af.mil
> Queue: met_help
> Subject: Request
> Owner: Nobody
> Requestors: robert.craig.2 at us.af.mil
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=79856
> >
>
>
> John, I have a question/suggestion for 6.0. We don't have the same
GRIB2
> table definitions as those at are in the grib2_vars_flat.txt table.
I
> can retrieve my model values defining the discipline code, parmcat,
> and parm values but MET will then put variable name that comes from
> the subject table into the STAT file. So in my case, I am
retrieving
> probability of wind > 25 kts but heatflux might be the name that
ends
> up in the STAT file MET produces. This problem can be solved if we
> can point MET to the proper grib2_vars_flat.txt table to use.
> Different MET users in 557th/AFWA could point MET to their own
version
> of the table and we wouldn't step on each other.
>
> Thank
> Bob
>
>
>
------------------------------------------------
Subject: Request
From: robert.craig.2 at us.af.mil
Time: Fri Mar 24 12:40:10 2017
GRIB2
0 10 0 255 57 1 19 161 "PWS15" "Probabilty of 10 m winds above 15kts"
"%"
0 10 0 255 57 1 19 163 "PWS25" "Probabilty of 10 m winds above 25kts"
"%"
0 10 0 255 57 1 19 164 "PWS35" "Probabilty of 10 m winds above 35kts"
"%"
0 10 0 255 57 1 19 165 "PWS50" "Probabilty of 10 m winds above 50kts"
"%"
0 10 0 255 57 1 19 173 "PQP1" "Probability of precip accumulation >
.01" "%"
0 10 0 255 57 1 19 174 "PQP2" "Probability of precip accumulation >
.02" "%"
0 10 0 255 57 1 19 182 "PSN1" "Probability of snow accumulation > 1"
"%"
0 10 0 255 57 1 19 183 "PSN2" "Probability of snow accumulation > 2"
"%"
0 10 0 255 57 1 19 175 "QP005" "Probability of precip accumulation >
.05" "%"
0 10 0 255 57 1 19 176 "QP010" "Probability of precip accumulation >
.10" "%"
0 10 0 255 57 1 19 177 "QP025" "Probability of precip accumulation >
.25" "%"
0 10 0 255 57 1 19 178 "QP050" "Probability of precip accumulation >
.50" "%"
0 10 0 255 57 1 19 179 "QP075" "Probability of precip accumulation >
.75" "%"
0 10 0 255 57 1 19 180 "QP100" "Probability of precip accumulation >
1.0" "%"
0 10 0 255 57 1 19 181 "QP500" "Probability of precip accumulation >
5.0" "%"
0 10 0 255 57 1 19 212 "PT273" "Probability of 2m temperature > 273"
"%"
0 10 0 255 57 1 19 213 "PT305" "Probability of 2m temperature > 305"
"%"
0 10 0 255 57 1 19 207 "PHT58" "Probability of 500mb HGT > 5800 m" "%"
0 10 0 255 57 1 19 203 "PVIS1" "Probability of surface visiblity < 1
mi" "%"
0 10 0 255 57 1 19 202 "PVIS3" "Probability of surface visibility < 3
mi" "%"
0 10 0 255 57 1 19 201 "PVIS5" "Probability of surface visibility < 5
mi" "%"
0 10 0 255 57 1 19 224 "PC20" "Probabilty of Total Cloud < 20 %" "%"
0 10 0 255 57 1 19 225 "PC80" "Probablity of Total Cloud > 80 % "%"
------------------------------------------------
Subject: Request
From: John Halley Gotway
Time: Tue Mar 28 17:47:27 2017
Bob,
My apologies for sending you incorrect information. The environment
variable should be named "USER_GRIB_TABLES" but I had told you
"GRIB_USER_TABLES".
Please try "USER_GRIB_TABLES" and let me know how it goes.
And please note that in the upcoming version 6.0, we've renamed it to
MET_GRIB_TABLES to consistently prefix MET-related environment
variables
with "MET_". And we've added a paragraph to data/config/README and
the
user's guide about that environment variable.
Sorry for the confusion!
John
On Fri, Mar 24, 2017 at 12:40 PM, robert.craig.2 at us.af.mil via RT <
met_help at ucar.edu> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=79856 >
>
> John, I made the changes you recommended and am still having issues.
> Attached
> is my config file and grib2 file. What did I miss?
>
> [2647 qcteam hpc9-lsn-02d /home/qcteam] env | grep GRIB
> GRIB_USER_TABLES=/h/data/global/WXQC/data/met/config/grib2
> MET_GRIB2CINC=/h/WXQC/met-5.1/lib/g2clib-1.4.0
> MET_GRIB2CLIB=/h/WXQC/met-5.1/lib/g2clib-1.4.0
>
> In /h/data/global/WXQC/data/met/config/grib2 is a file called
> grib2_geps.txt.
>
> When I run the code I get the the following if I use the "name"
parameter
> in
> the config file:
>
> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2
> field
> indexes - disc: 0, master table: 10, center: 57, local table: 1,
parm_cat:
> 6,
> parm: 70
> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2
> field
> indexes - disc: 0, master table: 10, center: 57, local table: 1,
parm_cat:
> 19,
> parm: 223
> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2
> field
> indexes - disc: 0, master table: 10, center: 57, local table: 1,
parm_cat:
> 19,
> parm: 223
> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2
> field
> indexes - disc: 0, master table: 10, center: 57, local table: 1,
parm_cat:
> 19,
> parm: 223
> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2
> field
> indexes - disc: 0, master table: 10, center: 57, local table: 1,
parm_cat:
> 19,
> parm: 223
> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2
> field
> indexes - disc: 0, master table: 10, center: 57, local table: 1,
parm_cat:
> 19,
> parm: 223
> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created new
> Met2dDataFile object of type "FileType_NcMet".
> DEBUG 4: Latitude/Longitude Grid Data:
> DEBUG 4: lat_ll = -89.9219
> DEBUG 4: lon_ll = -0.117187
> DEBUG 4: delta_lat = 0.234375
> DEBUG 4: delta_lon = 0.15625
> DEBUG 4: Nlat = 1152
> DEBUG 4: Nlon = 1536
> DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
object of
> type
> "FileType_Gb2".
> DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
object of
> type
> "FileType_NcMet".
> ERROR :
> ERROR : VarInfoGrib2::set_dict() - unrecognized GRIB2 field
abbreviation
> 'PWS15'
> ERROR :
>
> If I use the three grib2 parameters I get the following:
>
> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2
> field
> indexes - disc: 0, master table: 10, center: 57, local table: 1,
parm_cat:
> 6,
> parm: 70
> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2
> field
> indexes - disc: 0, master table: 10, center: 57, local table: 1,
parm_cat:
> 6,
> parm: 70
> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2
> field
> indexes - disc: 0, master table: 10, center: 57, local table: 1,
parm_cat:
> 6,
> parm: 70
> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2
> field
> indexes - disc: 0, master table: 10, center: 57, local table: 1,
parm_cat:
> 19,
> parm: 223
> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2
> field
> indexes - disc: 0, master table: 10, center: 57, local table: 1,
parm_cat:
> 19,
> parm: 223
> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2
> field
> indexes - disc: 0, master table: 10, center: 57, local table: 1,
parm_cat:
> 19,
> parm: 223
> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2
> field
> indexes - disc: 0, master table: 10, center: 57, local table: 1,
parm_cat:
> 19,
> parm: 223
> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2
> field
> indexes - disc: 0, master table: 10, center: 57, local table: 1,
parm_cat:
> 19,
> parm: 223
> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created new
> Met2dDataFile object of type "FileType_NcMet".
> DEBUG 4: Latitude/Longitude Grid Data:
> DEBUG 4: lat_ll = -89.9219
> DEBUG 4: lon_ll = -0.117187
> DEBUG 4: delta_lat = 0.234375
> DEBUG 4: delta_lon = 0.15625
> DEBUG 4: Nlat = 1152
> DEBUG 4: Nlon = 1536
> DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
object of
> type
> "FileType_Gb2".
> DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
object of
> type
> "FileType_NcMet".
> ERROR :
> ERROR : VarInfoGrib2::set_dict() - either name or GRIB2_disc,
> GRIB2_parm_cat
> and GRIB2_parm must be specified in field information
> ERROR :
>
> -----Original Message-----
> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> Sent: Wednesday, March 22, 2017 11:44 AM
> To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
<robert.craig.2 at us.af.mil>
> Subject: Re: [rt.rap.ucar.edu #79856] Request
>
> Bob,
>
> Yes, there is a way of having different users point to different
GRIB2
> tables
> to use, and it's present in version 5.2 of MET. But we've refined
it in
> the
> upcoming 6.0 release.
>
> For version 5.2, you do this by setting an environment variable
named
> "GRIB_USER_TABLES". It must be set to a *directory* containing
files that
> begin with "grib1" or "grib2" and end with ".txt". Just place your
> version of
> grib2_var_flat.txt in that directory an edit it as needed.
>
> The MET tools will read the contents of the GRIB_USER_TABLES
directory
> first
> and then the default ones second. Any of your local settings will
take
> precedence over the default ones.
>
> For version 6.0, we're renaming that "GRIB_USER_TABLES" to be
> "MET_GRIB_TABLES", using the "MET_" prefix to be consistent with
other
> MET-related environment variables. In 6.0, it can be set to a
directory
> containing multiple files or to an explicit file name to be used.
>
> Please let me know if any additional issues or questions arise.
>
> Thanks,
> John
>
> On Thu, Mar 16, 2017 at 7:55 AM, robert.craig.2 at us.af.mil via RT <
> met_help at ucar.edu> wrote:
>
> >
> > Thu Mar 16 07:55:51 2017: Request 79856 was acted upon.
> > Transaction: Ticket created by robert.craig.2 at us.af.mil
> > Queue: met_help
> > Subject: Request
> > Owner: Nobody
> > Requestors: robert.craig.2 at us.af.mil
> > Status: new
> > Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=79856
> > >
> >
> >
> > John, I have a question/suggestion for 6.0. We don't have the
same
> GRIB2
> > table definitions as those at are in the grib2_vars_flat.txt
table. I
> > can retrieve my model values defining the discipline code,
parmcat,
> > and parm values but MET will then put variable name that comes
from
> > the subject table into the STAT file. So in my case, I am
retrieving
> > probability of wind > 25 kts but heatflux might be the name that
ends
> > up in the STAT file MET produces. This problem can be solved if
we
> > can point MET to the proper grib2_vars_flat.txt table to use.
> > Different MET users in 557th/AFWA could point MET to their own
version
> > of the table and we wouldn't step on each other.
> >
> > Thank
> > Bob
> >
> >
> >
>
>
>
------------------------------------------------
Subject: Request
From: robert.craig.2 at us.af.mil
Time: Wed Mar 29 08:02:24 2017
John, I changed the env variable name to USER_GRIB_TABLES but it still
is not
working. Does MET provide any messages indicating that it is using
an
alternate grib table? If so, I am not seeing any using error level 4
setting.
Does the format of the attached grib table look correct? The config
file is
attache - anything missing there? You should still have the grib file
on the
ftp server.
DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2 field
indexes - disc: 0, master table: 10, center: 57, local table: 1,
parm_cat: 6,
parm: 70
DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2 field
indexes - disc: 0, master table: 10, center: 57, local table: 1,
parm_cat: 6,
parm: 70
DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2 field
indexes - disc: 0, master table: 10, center: 57, local table: 1,
parm_cat: 19,
parm: 223
DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2 field
indexes - disc: 0, master table: 10, center: 57, local table: 1,
parm_cat: 19,
parm: 223
DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2 field
indexes - disc: 0, master table: 10, center: 57, local table: 1,
parm_cat: 19,
parm: 223
DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2 field
indexes - disc: 0, master table: 10, center: 57, local table: 1,
parm_cat: 19,
parm: 223
DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2 field
indexes - disc: 0, master table: 10, center: 57, local table: 1,
parm_cat: 19,
parm: 223
DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created new
Met2dDataFile object of type "FileType_NcMet".
DEBUG 4: Latitude/Longitude Grid Data:
DEBUG 4: lat_ll = -89.9219
DEBUG 4: lon_ll = -0.117187
DEBUG 4: delta_lat = 0.234375
DEBUG 4: delta_lon = 0.15625
DEBUG 4: Nlat = 1152
DEBUG 4: Nlon = 1536
DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo object
of type
"FileType_Gb2".
DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo object
of type
"FileType_NcMet".
ERROR :
ERROR : VarInfoGrib2::set_dict() - either name or GRIB2_disc,
GRIB2_parm_cat
and GRIB2_parm must be specified in field information
ERROR :
The environmental variable list is below:
SHELL=/bin/ksh
SHLVL=1
TERM=xterm-256color
USER=qcteam
USER_GRIB_TABLES=/h/data/global/WXQC/data/met/config/grib2
The attached file grib2_geps.txt is in the directory defined above by
the
environmental variable.
Bob
-----Original Message-----
From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
Sent: Tuesday, March 28, 2017 6:47 PM
To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
<robert.craig.2 at us.af.mil>
Subject: Re: [rt.rap.ucar.edu #79856] Request
Bob,
My apologies for sending you incorrect information. The environment
variable
should be named "USER_GRIB_TABLES" but I had told you
"GRIB_USER_TABLES".
Please try "USER_GRIB_TABLES" and let me know how it goes.
And please note that in the upcoming version 6.0, we've renamed it to
MET_GRIB_TABLES to consistently prefix MET-related environment
variables with
"MET_". And we've added a paragraph to data/config/README and the
user's
guide about that environment variable.
Sorry for the confusion!
John
On Fri, Mar 24, 2017 at 12:40 PM, robert.craig.2 at us.af.mil via RT <
met_help at ucar.edu> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=79856 >
>
> John, I made the changes you recommended and am still having issues.
> Attached
> is my config file and grib2 file. What did I miss?
>
> [2647 qcteam hpc9-lsn-02d /home/qcteam] env | grep GRIB
> GRIB_USER_TABLES=/h/data/global/WXQC/data/met/config/grib2
> MET_GRIB2CINC=/h/WXQC/met-5.1/lib/g2clib-1.4.0
> MET_GRIB2CLIB=/h/WXQC/met-5.1/lib/g2clib-1.4.0
>
> In /h/data/global/WXQC/data/met/config/grib2 is a file called
> grib2_geps.txt.
>
> When I run the code I get the the following if I use the "name"
> parameter in the config file:
>
> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> table: 1, parm_cat:
> 6,
> parm: 70
> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> table: 1, parm_cat:
> 19,
> parm: 223
> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> table: 1, parm_cat:
> 19,
> parm: 223
> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> table: 1, parm_cat:
> 19,
> parm: 223
> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> table: 1, parm_cat:
> 19,
> parm: 223
> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> table: 1, parm_cat:
> 19,
> parm: 223
> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created new
> Met2dDataFile object of type "FileType_NcMet".
> DEBUG 4: Latitude/Longitude Grid Data:
> DEBUG 4: lat_ll = -89.9219
> DEBUG 4: lon_ll = -0.117187
> DEBUG 4: delta_lat = 0.234375
> DEBUG 4: delta_lon = 0.15625
> DEBUG 4: Nlat = 1152
> DEBUG 4: Nlon = 1536
> DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
object
> of type "FileType_Gb2".
> DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
object
> of type "FileType_NcMet".
> ERROR :
> ERROR : VarInfoGrib2::set_dict() - unrecognized GRIB2 field
> abbreviation 'PWS15'
> ERROR :
>
> If I use the three grib2 parameters I get the following:
>
> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> table: 1, parm_cat:
> 6,
> parm: 70
> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> table: 1, parm_cat:
> 6,
> parm: 70
> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> table: 1, parm_cat:
> 6,
> parm: 70
> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> table: 1, parm_cat:
> 19,
> parm: 223
> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> table: 1, parm_cat:
> 19,
> parm: 223
> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> table: 1, parm_cat:
> 19,
> parm: 223
> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> table: 1, parm_cat:
> 19,
> parm: 223
> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> table: 1, parm_cat:
> 19,
> parm: 223
> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created new
> Met2dDataFile object of type "FileType_NcMet".
> DEBUG 4: Latitude/Longitude Grid Data:
> DEBUG 4: lat_ll = -89.9219
> DEBUG 4: lon_ll = -0.117187
> DEBUG 4: delta_lat = 0.234375
> DEBUG 4: delta_lon = 0.15625
> DEBUG 4: Nlat = 1152
> DEBUG 4: Nlon = 1536
> DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
object
> of type "FileType_Gb2".
> DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
object
> of type "FileType_NcMet".
> ERROR :
> ERROR : VarInfoGrib2::set_dict() - either name or GRIB2_disc,
> GRIB2_parm_cat and GRIB2_parm must be specified in field information
> ERROR :
>
> -----Original Message-----
> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> Sent: Wednesday, March 22, 2017 11:44 AM
> To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
> <robert.craig.2 at us.af.mil>
> Subject: Re: [rt.rap.ucar.edu #79856] Request
>
> Bob,
>
> Yes, there is a way of having different users point to different
GRIB2
> tables to use, and it's present in version 5.2 of MET. But we've
> refined it in the upcoming 6.0 release.
>
> For version 5.2, you do this by setting an environment variable
named
> "GRIB_USER_TABLES". It must be set to a *directory* containing
files
> that begin with "grib1" or "grib2" and end with ".txt". Just place
> your version of grib2_var_flat.txt in that directory an edit it as
> needed.
>
> The MET tools will read the contents of the GRIB_USER_TABLES
directory
> first and then the default ones second. Any of your local settings
> will take precedence over the default ones.
>
> For version 6.0, we're renaming that "GRIB_USER_TABLES" to be
> "MET_GRIB_TABLES", using the "MET_" prefix to be consistent with
other
> MET-related environment variables. In 6.0, it can be set to a
> directory containing multiple files or to an explicit file name to
be used.
>
> Please let me know if any additional issues or questions arise.
>
> Thanks,
> John
>
> On Thu, Mar 16, 2017 at 7:55 AM, robert.craig.2 at us.af.mil via RT <
> met_help at ucar.edu> wrote:
>
> >
> > Thu Mar 16 07:55:51 2017: Request 79856 was acted upon.
> > Transaction: Ticket created by robert.craig.2 at us.af.mil
> > Queue: met_help
> > Subject: Request
> > Owner: Nobody
> > Requestors: robert.craig.2 at us.af.mil
> > Status: new
> > Ticket <URL:
> > https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=79856
> > >
> >
> >
> > John, I have a question/suggestion for 6.0. We don't have the
same
> GRIB2
> > table definitions as those at are in the grib2_vars_flat.txt
table.
> > I can retrieve my model values defining the discipline code,
> > parmcat, and parm values but MET will then put variable name that
> > comes from the subject table into the STAT file. So in my case, I
> > am retrieving probability of wind > 25 kts but heatflux might be
the
> > name that ends up in the STAT file MET produces. This problem can
> > be solved if we can point MET to the proper grib2_vars_flat.txt
table to
> > use.
> > Different MET users in 557th/AFWA could point MET to their own
> > version of the table and we wouldn't step on each other.
> >
> > Thank
> > Bob
> >
> >
> >
>
>
>
------------------------------------------------
Subject: Request
From: robert.craig.2 at us.af.mil
Time: Wed Mar 29 08:02:24 2017
GRIB2
0 10 0 255 57 1 19 161 "PWS15" "Probabilty of 10 m winds above 15kts"
"%"
0 10 0 255 57 1 19 163 "PWS25" "Probabilty of 10 m winds above 25kts"
"%"
0 10 0 255 57 1 19 164 "PWS35" "Probabilty of 10 m winds above 35kts"
"%"
0 10 0 255 57 1 19 165 "PWS50" "Probabilty of 10 m winds above 50kts"
"%"
0 10 0 255 57 1 19 173 "PQP1" "Probability of precip accumulation >
.01" "%"
0 10 0 255 57 1 19 174 "PQP2" "Probability of precip accumulation >
.02" "%"
0 10 0 255 57 1 19 182 "PSN1" "Probability of snow accumulation > 1"
"%"
0 10 0 255 57 1 19 183 "PSN2" "Probability of snow accumulation > 2"
"%"
0 10 0 255 57 1 19 175 "QP005" "Probability of precip accumulation >
.05" "%"
0 10 0 255 57 1 19 176 "QP010" "Probability of precip accumulation >
.10" "%"
0 10 0 255 57 1 19 177 "QP025" "Probability of precip accumulation >
.25" "%"
0 10 0 255 57 1 19 178 "QP050" "Probability of precip accumulation >
.50" "%"
0 10 0 255 57 1 19 179 "QP075" "Probability of precip accumulation >
.75" "%"
0 10 0 255 57 1 19 180 "QP100" "Probability of precip accumulation >
1.0" "%"
0 10 0 255 57 1 19 181 "QP500" "Probability of precip accumulation >
5.0" "%"
0 10 0 255 57 1 19 212 "PT273" "Probability of 2m temperature > 273"
"%"
0 10 0 255 57 1 19 213 "PT305" "Probability of 2m temperature > 305"
"%"
0 10 0 255 57 1 19 207 "PHT58" "Probability of 500mb HGT > 5800 m" "%"
0 10 0 255 57 1 19 203 "PVIS1" "Probability of surface visiblity < 1
mi" "%"
0 10 0 255 57 1 19 202 "PVIS3" "Probability of surface visibility < 3
mi" "%"
0 10 0 255 57 1 19 201 "PVIS5" "Probability of surface visibility < 5
mi" "%"
0 10 0 255 57 1 19 224 "PC20" "Probabilty of Total Cloud < 20 %" "%"
0 10 0 255 57 1 19 225 "PC80" "Probablity of Total Cloud > 80 % "%"
------------------------------------------------
Subject: Request
From: John Halley Gotway
Time: Thu Mar 30 13:40:18 2017
Hi Bob,
I'm sorry but I don't see the sample GRIB2 file on our ftp site.
Perhaps
it was aged off before I was able to grab it.
Please let me know if/when you're able to repost it.
Thanks,
John
On Wed, Mar 29, 2017 at 8:02 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=79856 >
>
> John, I changed the env variable name to USER_GRIB_TABLES but it
still is
> not
> working. Does MET provide any messages indicating that it is using
an
> alternate grib table? If so, I am not seeing any using error level
4
> setting.
> Does the format of the attached grib table look correct? The config
file
> is
> attache - anything missing there? You should still have the grib
file on
> the
> ftp server.
>
> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2
> field
> indexes - disc: 0, master table: 10, center: 57, local table: 1,
parm_cat:
> 6,
> parm: 70
> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2
> field
> indexes - disc: 0, master table: 10, center: 57, local table: 1,
parm_cat:
> 6,
> parm: 70
> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2
> field
> indexes - disc: 0, master table: 10, center: 57, local table: 1,
parm_cat:
> 19,
> parm: 223
> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2
> field
> indexes - disc: 0, master table: 10, center: 57, local table: 1,
parm_cat:
> 19,
> parm: 223
> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2
> field
> indexes - disc: 0, master table: 10, center: 57, local table: 1,
parm_cat:
> 19,
> parm: 223
> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2
> field
> indexes - disc: 0, master table: 10, center: 57, local table: 1,
parm_cat:
> 19,
> parm: 223
> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2
> field
> indexes - disc: 0, master table: 10, center: 57, local table: 1,
parm_cat:
> 19,
> parm: 223
> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created new
> Met2dDataFile object of type "FileType_NcMet".
> DEBUG 4: Latitude/Longitude Grid Data:
> DEBUG 4: lat_ll = -89.9219
> DEBUG 4: lon_ll = -0.117187
> DEBUG 4: delta_lat = 0.234375
> DEBUG 4: delta_lon = 0.15625
> DEBUG 4: Nlat = 1152
> DEBUG 4: Nlon = 1536
> DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
object of
> type
> "FileType_Gb2".
> DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
object of
> type
> "FileType_NcMet".
> ERROR :
> ERROR : VarInfoGrib2::set_dict() - either name or GRIB2_disc,
> GRIB2_parm_cat
> and GRIB2_parm must be specified in field information
> ERROR :
>
> The environmental variable list is below:
>
> SHELL=/bin/ksh
> SHLVL=1
> TERM=xterm-256color
> USER=qcteam
> USER_GRIB_TABLES=/h/data/global/WXQC/data/met/config/grib2
>
> The attached file grib2_geps.txt is in the directory defined above
by the
> environmental variable.
>
> Bob
>
> -----Original Message-----
> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> Sent: Tuesday, March 28, 2017 6:47 PM
> To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
<robert.craig.2 at us.af.mil>
> Subject: Re: [rt.rap.ucar.edu #79856] Request
>
> Bob,
>
> My apologies for sending you incorrect information. The environment
> variable
> should be named "USER_GRIB_TABLES" but I had told you
"GRIB_USER_TABLES".
>
> Please try "USER_GRIB_TABLES" and let me know how it goes.
>
> And please note that in the upcoming version 6.0, we've renamed it
to
> MET_GRIB_TABLES to consistently prefix MET-related environment
variables
> with
> "MET_". And we've added a paragraph to data/config/README and the
user's
> guide about that environment variable.
>
> Sorry for the confusion!
>
> John
>
> On Fri, Mar 24, 2017 at 12:40 PM, robert.craig.2 at us.af.mil via RT <
> met_help at ucar.edu> wrote:
>
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=79856 >
> >
> > John, I made the changes you recommended and am still having
issues.
> > Attached
> > is my config file and grib2 file. What did I miss?
> >
> > [2647 qcteam hpc9-lsn-02d /home/qcteam] env | grep GRIB
> > GRIB_USER_TABLES=/h/data/global/WXQC/data/met/config/grib2
> > MET_GRIB2CINC=/h/WXQC/met-5.1/lib/g2clib-1.4.0
> > MET_GRIB2CLIB=/h/WXQC/met-5.1/lib/g2clib-1.4.0
> >
> > In /h/data/global/WXQC/data/met/config/grib2 is a file called
> > grib2_geps.txt.
> >
> > When I run the code I get the the following if I use the "name"
> > parameter in the config file:
> >
> > DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> > GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> > table: 1, parm_cat:
> > 6,
> > parm: 70
> > DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> > GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> > table: 1, parm_cat:
> > 19,
> > parm: 223
> > DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> > GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> > table: 1, parm_cat:
> > 19,
> > parm: 223
> > DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> > GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> > table: 1, parm_cat:
> > 19,
> > parm: 223
> > DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> > GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> > table: 1, parm_cat:
> > 19,
> > parm: 223
> > DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> > GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> > table: 1, parm_cat:
> > 19,
> > parm: 223
> > DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created
new
> > Met2dDataFile object of type "FileType_NcMet".
> > DEBUG 4: Latitude/Longitude Grid Data:
> > DEBUG 4: lat_ll = -89.9219
> > DEBUG 4: lon_ll = -0.117187
> > DEBUG 4: delta_lat = 0.234375
> > DEBUG 4: delta_lon = 0.15625
> > DEBUG 4: Nlat = 1152
> > DEBUG 4: Nlon = 1536
> > DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
object
> > of type "FileType_Gb2".
> > DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
object
> > of type "FileType_NcMet".
> > ERROR :
> > ERROR : VarInfoGrib2::set_dict() - unrecognized GRIB2 field
> > abbreviation 'PWS15'
> > ERROR :
> >
> > If I use the three grib2 parameters I get the following:
> >
> > DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> > GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> > table: 1, parm_cat:
> > 6,
> > parm: 70
> > DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> > GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> > table: 1, parm_cat:
> > 6,
> > parm: 70
> > DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> > GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> > table: 1, parm_cat:
> > 6,
> > parm: 70
> > DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> > GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> > table: 1, parm_cat:
> > 19,
> > parm: 223
> > DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> > GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> > table: 1, parm_cat:
> > 19,
> > parm: 223
> > DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> > GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> > table: 1, parm_cat:
> > 19,
> > parm: 223
> > DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> > GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> > table: 1, parm_cat:
> > 19,
> > parm: 223
> > DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> > GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> > table: 1, parm_cat:
> > 19,
> > parm: 223
> > DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created
new
> > Met2dDataFile object of type "FileType_NcMet".
> > DEBUG 4: Latitude/Longitude Grid Data:
> > DEBUG 4: lat_ll = -89.9219
> > DEBUG 4: lon_ll = -0.117187
> > DEBUG 4: delta_lat = 0.234375
> > DEBUG 4: delta_lon = 0.15625
> > DEBUG 4: Nlat = 1152
> > DEBUG 4: Nlon = 1536
> > DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
object
> > of type "FileType_Gb2".
> > DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
object
> > of type "FileType_NcMet".
> > ERROR :
> > ERROR : VarInfoGrib2::set_dict() - either name or GRIB2_disc,
> > GRIB2_parm_cat and GRIB2_parm must be specified in field
information
> > ERROR :
> >
> > -----Original Message-----
> > From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> > Sent: Wednesday, March 22, 2017 11:44 AM
> > To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
> > <robert.craig.2 at us.af.mil>
> > Subject: Re: [rt.rap.ucar.edu #79856] Request
> >
> > Bob,
> >
> > Yes, there is a way of having different users point to different
GRIB2
> > tables to use, and it's present in version 5.2 of MET. But we've
> > refined it in the upcoming 6.0 release.
> >
> > For version 5.2, you do this by setting an environment variable
named
> > "GRIB_USER_TABLES". It must be set to a *directory* containing
files
> > that begin with "grib1" or "grib2" and end with ".txt". Just
place
> > your version of grib2_var_flat.txt in that directory an edit it as
> > needed.
> >
> > The MET tools will read the contents of the GRIB_USER_TABLES
directory
> > first and then the default ones second. Any of your local
settings
> > will take precedence over the default ones.
> >
> > For version 6.0, we're renaming that "GRIB_USER_TABLES" to be
> > "MET_GRIB_TABLES", using the "MET_" prefix to be consistent with
other
> > MET-related environment variables. In 6.0, it can be set to a
> > directory containing multiple files or to an explicit file name to
be
> used.
> >
> > Please let me know if any additional issues or questions arise.
> >
> > Thanks,
> > John
> >
> > On Thu, Mar 16, 2017 at 7:55 AM, robert.craig.2 at us.af.mil via RT <
> > met_help at ucar.edu> wrote:
> >
> > >
> > > Thu Mar 16 07:55:51 2017: Request 79856 was acted upon.
> > > Transaction: Ticket created by robert.craig.2 at us.af.mil
> > > Queue: met_help
> > > Subject: Request
> > > Owner: Nobody
> > > Requestors: robert.craig.2 at us.af.mil
> > > Status: new
> > > Ticket <URL:
> > > https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=79856
> > > >
> > >
> > >
> > > John, I have a question/suggestion for 6.0. We don't have the
same
> > GRIB2
> > > table definitions as those at are in the grib2_vars_flat.txt
table.
> > > I can retrieve my model values defining the discipline code,
> > > parmcat, and parm values but MET will then put variable name
that
> > > comes from the subject table into the STAT file. So in my case,
I
> > > am retrieving probability of wind > 25 kts but heatflux might be
the
> > > name that ends up in the STAT file MET produces. This problem
can
> > > be solved if we can point MET to the proper grib2_vars_flat.txt
table
> to
> > > use.
> > > Different MET users in 557th/AFWA could point MET to their own
> > > version of the table and we wouldn't step on each other.
> > >
> > > Thank
> > > Bob
> > >
> > >
> > >
> >
> >
> >
>
>
>
------------------------------------------------
Subject: RE: [rt.rap.ucar.edu #79856] Request
From: robert.craig.2 at us.af.mil
Time: Thu Mar 30 13:44:23 2017
I will resend it.
-----Original Message-----
From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
Sent: Thursday, March 30, 2017 2:40 PM
To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
<robert.craig.2 at us.af.mil>
Subject: Re: [rt.rap.ucar.edu #79856] Request
Hi Bob,
I'm sorry but I don't see the sample GRIB2 file on our ftp site.
Perhaps it was aged off before I was able to grab it.
Please let me know if/when you're able to repost it.
Thanks,
John
On Wed, Mar 29, 2017 at 8:02 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=79856 >
>
> John, I changed the env variable name to USER_GRIB_TABLES but it
still
> is not
> working. Does MET provide any messages indicating that it is using
an
> alternate grib table? If so, I am not seeing any using error level
4
> setting.
> Does the format of the attached grib table look correct? The config
> file is attache - anything missing there? You should still have the
> grib file on the ftp server.
>
> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> table: 1, parm_cat:
> 6,
> parm: 70
> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> table: 1, parm_cat:
> 6,
> parm: 70
> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> table: 1, parm_cat:
> 19,
> parm: 223
> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> table: 1, parm_cat:
> 19,
> parm: 223
> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> table: 1, parm_cat:
> 19,
> parm: 223
> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> table: 1, parm_cat:
> 19,
> parm: 223
> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> table: 1, parm_cat:
> 19,
> parm: 223
> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created new
> Met2dDataFile object of type "FileType_NcMet".
> DEBUG 4: Latitude/Longitude Grid Data:
> DEBUG 4: lat_ll = -89.9219
> DEBUG 4: lon_ll = -0.117187
> DEBUG 4: delta_lat = 0.234375
> DEBUG 4: delta_lon = 0.15625
> DEBUG 4: Nlat = 1152
> DEBUG 4: Nlon = 1536
> DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
object
> of type "FileType_Gb2".
> DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
object
> of type "FileType_NcMet".
> ERROR :
> ERROR : VarInfoGrib2::set_dict() - either name or GRIB2_disc,
> GRIB2_parm_cat and GRIB2_parm must be specified in field information
> ERROR :
>
> The environmental variable list is below:
>
> SHELL=/bin/ksh
> SHLVL=1
> TERM=xterm-256color
> USER=qcteam
> USER_GRIB_TABLES=/h/data/global/WXQC/data/met/config/grib2
>
> The attached file grib2_geps.txt is in the directory defined above
by
> the environmental variable.
>
> Bob
>
> -----Original Message-----
> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> Sent: Tuesday, March 28, 2017 6:47 PM
> To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
> <robert.craig.2 at us.af.mil>
> Subject: Re: [rt.rap.ucar.edu #79856] Request
>
> Bob,
>
> My apologies for sending you incorrect information. The environment
> variable should be named "USER_GRIB_TABLES" but I had told you
> "GRIB_USER_TABLES".
>
> Please try "USER_GRIB_TABLES" and let me know how it goes.
>
> And please note that in the upcoming version 6.0, we've renamed it
to
> MET_GRIB_TABLES to consistently prefix MET-related environment
> variables with "MET_". And we've added a paragraph to
> data/config/README and the user's guide about that environment
> variable.
>
> Sorry for the confusion!
>
> John
>
> On Fri, Mar 24, 2017 at 12:40 PM, robert.craig.2 at us.af.mil via RT <
> met_help at ucar.edu> wrote:
>
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=79856 >
> >
> > John, I made the changes you recommended and am still having
issues.
> > Attached
> > is my config file and grib2 file. What did I miss?
> >
> > [2647 qcteam hpc9-lsn-02d /home/qcteam] env | grep GRIB
> > GRIB_USER_TABLES=/h/data/global/WXQC/data/met/config/grib2
> > MET_GRIB2CINC=/h/WXQC/met-5.1/lib/g2clib-1.4.0
> > MET_GRIB2CLIB=/h/WXQC/met-5.1/lib/g2clib-1.4.0
> >
> > In /h/data/global/WXQC/data/met/config/grib2 is a file called
> > grib2_geps.txt.
> >
> > When I run the code I get the the following if I use the "name"
> > parameter in the config file:
> >
> > DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> > GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> > table: 1, parm_cat:
> > 6,
> > parm: 70
> > DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> > GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> > table: 1, parm_cat:
> > 19,
> > parm: 223
> > DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> > GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> > table: 1, parm_cat:
> > 19,
> > parm: 223
> > DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> > GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> > table: 1, parm_cat:
> > 19,
> > parm: 223
> > DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> > GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> > table: 1, parm_cat:
> > 19,
> > parm: 223
> > DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> > GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> > table: 1, parm_cat:
> > 19,
> > parm: 223
> > DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created
new
> > Met2dDataFile object of type "FileType_NcMet".
> > DEBUG 4: Latitude/Longitude Grid Data:
> > DEBUG 4: lat_ll = -89.9219
> > DEBUG 4: lon_ll = -0.117187
> > DEBUG 4: delta_lat = 0.234375
> > DEBUG 4: delta_lon = 0.15625
> > DEBUG 4: Nlat = 1152
> > DEBUG 4: Nlon = 1536
> > DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
> > object of type "FileType_Gb2".
> > DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
> > object of type "FileType_NcMet".
> > ERROR :
> > ERROR : VarInfoGrib2::set_dict() - unrecognized GRIB2 field
> > abbreviation 'PWS15'
> > ERROR :
> >
> > If I use the three grib2 parameters I get the following:
> >
> > DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> > GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> > table: 1, parm_cat:
> > 6,
> > parm: 70
> > DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> > GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> > table: 1, parm_cat:
> > 6,
> > parm: 70
> > DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> > GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> > table: 1, parm_cat:
> > 6,
> > parm: 70
> > DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> > GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> > table: 1, parm_cat:
> > 19,
> > parm: 223
> > DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> > GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> > table: 1, parm_cat:
> > 19,
> > parm: 223
> > DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> > GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> > table: 1, parm_cat:
> > 19,
> > parm: 223
> > DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> > GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> > table: 1, parm_cat:
> > 19,
> > parm: 223
> > DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> > GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> > table: 1, parm_cat:
> > 19,
> > parm: 223
> > DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created
new
> > Met2dDataFile object of type "FileType_NcMet".
> > DEBUG 4: Latitude/Longitude Grid Data:
> > DEBUG 4: lat_ll = -89.9219
> > DEBUG 4: lon_ll = -0.117187
> > DEBUG 4: delta_lat = 0.234375
> > DEBUG 4: delta_lon = 0.15625
> > DEBUG 4: Nlat = 1152
> > DEBUG 4: Nlon = 1536
> > DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
> > object of type "FileType_Gb2".
> > DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
> > object of type "FileType_NcMet".
> > ERROR :
> > ERROR : VarInfoGrib2::set_dict() - either name or GRIB2_disc,
> > GRIB2_parm_cat and GRIB2_parm must be specified in field
information
> > ERROR :
> >
> > -----Original Message-----
> > From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> > Sent: Wednesday, March 22, 2017 11:44 AM
> > To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
> > <robert.craig.2 at us.af.mil>
> > Subject: Re: [rt.rap.ucar.edu #79856] Request
> >
> > Bob,
> >
> > Yes, there is a way of having different users point to different
> > GRIB2 tables to use, and it's present in version 5.2 of MET. But
> > we've refined it in the upcoming 6.0 release.
> >
> > For version 5.2, you do this by setting an environment variable
> > named "GRIB_USER_TABLES". It must be set to a *directory*
> > containing files that begin with "grib1" or "grib2" and end with
> > ".txt". Just place your version of grib2_var_flat.txt in that
> > directory an edit it as needed.
> >
> > The MET tools will read the contents of the GRIB_USER_TABLES
> > directory first and then the default ones second. Any of your
local
> > settings will take precedence over the default ones.
> >
> > For version 6.0, we're renaming that "GRIB_USER_TABLES" to be
> > "MET_GRIB_TABLES", using the "MET_" prefix to be consistent with
> > other MET-related environment variables. In 6.0, it can be set to
a
> > directory containing multiple files or to an explicit file name to
> > be
> used.
> >
> > Please let me know if any additional issues or questions arise.
> >
> > Thanks,
> > John
> >
> > On Thu, Mar 16, 2017 at 7:55 AM, robert.craig.2 at us.af.mil via RT <
> > met_help at ucar.edu> wrote:
> >
> > >
> > > Thu Mar 16 07:55:51 2017: Request 79856 was acted upon.
> > > Transaction: Ticket created by robert.craig.2 at us.af.mil
> > > Queue: met_help
> > > Subject: Request
> > > Owner: Nobody
> > > Requestors: robert.craig.2 at us.af.mil
> > > Status: new
> > > Ticket <URL:
> > > https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=79856
> > > >
> > >
> > >
> > > John, I have a question/suggestion for 6.0. We don't have the
same
> > GRIB2
> > > table definitions as those at are in the grib2_vars_flat.txt
table.
> > > I can retrieve my model values defining the discipline code,
> > > parmcat, and parm values but MET will then put variable name
that
> > > comes from the subject table into the STAT file. So in my case,
I
> > > am retrieving probability of wind > 25 kts but heatflux might be
> > > the name that ends up in the STAT file MET produces. This
problem
> > > can be solved if we can point MET to the proper
> > > grib2_vars_flat.txt table
> to
> > > use.
> > > Different MET users in 557th/AFWA could point MET to their own
> > > version of the table and we wouldn't step on each other.
> > >
> > > Thank
> > > Bob
> > >
> > >
> > >
> >
> >
> >
>
>
>
------------------------------------------------
Subject: RE: [rt.rap.ucar.edu #79856] Request
From: robert.craig.2 at us.af.mil
Time: Thu Mar 30 14:55:50 2017
John, I think the file transferred to your server - lots of weird
messages.
Let me know if you didn't get it.
Thanks
Bob Craig
-----Original Message-----
From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
Sent: Thursday, March 30, 2017 2:40 PM
To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
<robert.craig.2 at us.af.mil>
Subject: Re: [rt.rap.ucar.edu #79856] Request
Hi Bob,
I'm sorry but I don't see the sample GRIB2 file on our ftp site.
Perhaps it was aged off before I was able to grab it.
Please let me know if/when you're able to repost it.
Thanks,
John
On Wed, Mar 29, 2017 at 8:02 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=79856 >
>
> John, I changed the env variable name to USER_GRIB_TABLES but it
still
> is not
> working. Does MET provide any messages indicating that it is using
an
> alternate grib table? If so, I am not seeing any using error level
4
> setting.
> Does the format of the attached grib table look correct? The config
> file is attache - anything missing there? You should still have the
> grib file on the ftp server.
>
> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> table: 1, parm_cat:
> 6,
> parm: 70
> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> table: 1, parm_cat:
> 6,
> parm: 70
> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> table: 1, parm_cat:
> 19,
> parm: 223
> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> table: 1, parm_cat:
> 19,
> parm: 223
> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> table: 1, parm_cat:
> 19,
> parm: 223
> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> table: 1, parm_cat:
> 19,
> parm: 223
> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> table: 1, parm_cat:
> 19,
> parm: 223
> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created new
> Met2dDataFile object of type "FileType_NcMet".
> DEBUG 4: Latitude/Longitude Grid Data:
> DEBUG 4: lat_ll = -89.9219
> DEBUG 4: lon_ll = -0.117187
> DEBUG 4: delta_lat = 0.234375
> DEBUG 4: delta_lon = 0.15625
> DEBUG 4: Nlat = 1152
> DEBUG 4: Nlon = 1536
> DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
object
> of type "FileType_Gb2".
> DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
object
> of type "FileType_NcMet".
> ERROR :
> ERROR : VarInfoGrib2::set_dict() - either name or GRIB2_disc,
> GRIB2_parm_cat and GRIB2_parm must be specified in field information
> ERROR :
>
> The environmental variable list is below:
>
> SHELL=/bin/ksh
> SHLVL=1
> TERM=xterm-256color
> USER=qcteam
> USER_GRIB_TABLES=/h/data/global/WXQC/data/met/config/grib2
>
> The attached file grib2_geps.txt is in the directory defined above
by
> the environmental variable.
>
> Bob
>
> -----Original Message-----
> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> Sent: Tuesday, March 28, 2017 6:47 PM
> To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
> <robert.craig.2 at us.af.mil>
> Subject: Re: [rt.rap.ucar.edu #79856] Request
>
> Bob,
>
> My apologies for sending you incorrect information. The environment
> variable should be named "USER_GRIB_TABLES" but I had told you
> "GRIB_USER_TABLES".
>
> Please try "USER_GRIB_TABLES" and let me know how it goes.
>
> And please note that in the upcoming version 6.0, we've renamed it
to
> MET_GRIB_TABLES to consistently prefix MET-related environment
> variables with "MET_". And we've added a paragraph to
> data/config/README and the user's guide about that environment
> variable.
>
> Sorry for the confusion!
>
> John
>
> On Fri, Mar 24, 2017 at 12:40 PM, robert.craig.2 at us.af.mil via RT <
> met_help at ucar.edu> wrote:
>
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=79856 >
> >
> > John, I made the changes you recommended and am still having
issues.
> > Attached
> > is my config file and grib2 file. What did I miss?
> >
> > [2647 qcteam hpc9-lsn-02d /home/qcteam] env | grep GRIB
> > GRIB_USER_TABLES=/h/data/global/WXQC/data/met/config/grib2
> > MET_GRIB2CINC=/h/WXQC/met-5.1/lib/g2clib-1.4.0
> > MET_GRIB2CLIB=/h/WXQC/met-5.1/lib/g2clib-1.4.0
> >
> > In /h/data/global/WXQC/data/met/config/grib2 is a file called
> > grib2_geps.txt.
> >
> > When I run the code I get the the following if I use the "name"
> > parameter in the config file:
> >
> > DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> > GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> > table: 1, parm_cat:
> > 6,
> > parm: 70
> > DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> > GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> > table: 1, parm_cat:
> > 19,
> > parm: 223
> > DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> > GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> > table: 1, parm_cat:
> > 19,
> > parm: 223
> > DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> > GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> > table: 1, parm_cat:
> > 19,
> > parm: 223
> > DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> > GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> > table: 1, parm_cat:
> > 19,
> > parm: 223
> > DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> > GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> > table: 1, parm_cat:
> > 19,
> > parm: 223
> > DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created
new
> > Met2dDataFile object of type "FileType_NcMet".
> > DEBUG 4: Latitude/Longitude Grid Data:
> > DEBUG 4: lat_ll = -89.9219
> > DEBUG 4: lon_ll = -0.117187
> > DEBUG 4: delta_lat = 0.234375
> > DEBUG 4: delta_lon = 0.15625
> > DEBUG 4: Nlat = 1152
> > DEBUG 4: Nlon = 1536
> > DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
> > object of type "FileType_Gb2".
> > DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
> > object of type "FileType_NcMet".
> > ERROR :
> > ERROR : VarInfoGrib2::set_dict() - unrecognized GRIB2 field
> > abbreviation 'PWS15'
> > ERROR :
> >
> > If I use the three grib2 parameters I get the following:
> >
> > DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> > GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> > table: 1, parm_cat:
> > 6,
> > parm: 70
> > DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> > GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> > table: 1, parm_cat:
> > 6,
> > parm: 70
> > DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> > GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> > table: 1, parm_cat:
> > 6,
> > parm: 70
> > DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> > GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> > table: 1, parm_cat:
> > 19,
> > parm: 223
> > DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> > GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> > table: 1, parm_cat:
> > 19,
> > parm: 223
> > DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> > GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> > table: 1, parm_cat:
> > 19,
> > parm: 223
> > DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> > GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> > table: 1, parm_cat:
> > 19,
> > parm: 223
> > DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> > GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> > table: 1, parm_cat:
> > 19,
> > parm: 223
> > DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created
new
> > Met2dDataFile object of type "FileType_NcMet".
> > DEBUG 4: Latitude/Longitude Grid Data:
> > DEBUG 4: lat_ll = -89.9219
> > DEBUG 4: lon_ll = -0.117187
> > DEBUG 4: delta_lat = 0.234375
> > DEBUG 4: delta_lon = 0.15625
> > DEBUG 4: Nlat = 1152
> > DEBUG 4: Nlon = 1536
> > DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
> > object of type "FileType_Gb2".
> > DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
> > object of type "FileType_NcMet".
> > ERROR :
> > ERROR : VarInfoGrib2::set_dict() - either name or GRIB2_disc,
> > GRIB2_parm_cat and GRIB2_parm must be specified in field
information
> > ERROR :
> >
> > -----Original Message-----
> > From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> > Sent: Wednesday, March 22, 2017 11:44 AM
> > To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
> > <robert.craig.2 at us.af.mil>
> > Subject: Re: [rt.rap.ucar.edu #79856] Request
> >
> > Bob,
> >
> > Yes, there is a way of having different users point to different
> > GRIB2 tables to use, and it's present in version 5.2 of MET. But
> > we've refined it in the upcoming 6.0 release.
> >
> > For version 5.2, you do this by setting an environment variable
> > named "GRIB_USER_TABLES". It must be set to a *directory*
> > containing files that begin with "grib1" or "grib2" and end with
> > ".txt". Just place your version of grib2_var_flat.txt in that
> > directory an edit it as needed.
> >
> > The MET tools will read the contents of the GRIB_USER_TABLES
> > directory first and then the default ones second. Any of your
local
> > settings will take precedence over the default ones.
> >
> > For version 6.0, we're renaming that "GRIB_USER_TABLES" to be
> > "MET_GRIB_TABLES", using the "MET_" prefix to be consistent with
> > other MET-related environment variables. In 6.0, it can be set to
a
> > directory containing multiple files or to an explicit file name to
> > be
> used.
> >
> > Please let me know if any additional issues or questions arise.
> >
> > Thanks,
> > John
> >
> > On Thu, Mar 16, 2017 at 7:55 AM, robert.craig.2 at us.af.mil via RT <
> > met_help at ucar.edu> wrote:
> >
> > >
> > > Thu Mar 16 07:55:51 2017: Request 79856 was acted upon.
> > > Transaction: Ticket created by robert.craig.2 at us.af.mil
> > > Queue: met_help
> > > Subject: Request
> > > Owner: Nobody
> > > Requestors: robert.craig.2 at us.af.mil
> > > Status: new
> > > Ticket <URL:
> > > https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=79856
> > > >
> > >
> > >
> > > John, I have a question/suggestion for 6.0. We don't have the
same
> > GRIB2
> > > table definitions as those at are in the grib2_vars_flat.txt
table.
> > > I can retrieve my model values defining the discipline code,
> > > parmcat, and parm values but MET will then put variable name
that
> > > comes from the subject table into the STAT file. So in my case,
I
> > > am retrieving probability of wind > 25 kts but heatflux might be
> > > the name that ends up in the STAT file MET produces. This
problem
> > > can be solved if we can point MET to the proper
> > > grib2_vars_flat.txt table
> to
> > > use.
> > > Different MET users in 557th/AFWA could point MET to their own
> > > version of the table and we wouldn't step on each other.
> > >
> > > Thank
> > > Bob
> > >
> > >
> > >
> >
> >
> >
>
>
>
------------------------------------------------
Subject: Request
From: John Halley Gotway
Time: Thu Mar 30 20:27:36 2017
Bob,
Sorry for the delay in getting to this. There were two things I
needed to
change to get this to work:
(1) There was a typo on line 24 of grib2_geps.txt. You were missing a
closing double quote in one spot.
(2) This is pretty ridiculous but the current parsing logic requires
that
two spaces be used between the strings.
I've attached an updated version of that file with those changes. And
I
did the following:
- Placed that file into a directory: table_dir/grib2_geps.txt
- Set the environment variable:
setenv USER_GRIB_TABLES table_dir
- Ran plot_data_plane:
met-5.2/bin/plot_data_plane grib2.2017031700.0024 psw15.ps
'name="PWS15"; level="Z10";'
The resulting image is attached.
Obviously requiring two spaces is *NOT* very intuitive. If possible,
I'll
try to fix up that parsing logic to allow for one or more spaces prior
to
the 6.0 release.
I agree that it would be nice to print a debug message indicating that
the
user GRIB tables are being read. However, these are read by the
constructor of that class before the logging level is defined. So
there
would be no way to turn those messages off. Perhaps that's OK, if
USER_GRIB_TABLES (or MET_GRIB_TABLES in 6.0) is defined, perhaps it's
good
to see a DEBUG(0) message telling you what it's doing.
What do you think?
Thanks,
John
On Thu, Mar 30, 2017 at 2:55 PM, robert.craig.2 at us.af.mil via RT <
met_help at ucar.edu> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=79856 >
>
> John, I think the file transferred to your server - lots of weird
messages.
> Let me know if you didn't get it.
>
> Thanks
> Bob Craig
>
> -----Original Message-----
> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> Sent: Thursday, March 30, 2017 2:40 PM
> To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
<robert.craig.2 at us.af.mil>
> Subject: Re: [rt.rap.ucar.edu #79856] Request
>
> Hi Bob,
>
> I'm sorry but I don't see the sample GRIB2 file on our ftp site.
Perhaps
> it was aged off before I was able to grab it.
>
> Please let me know if/when you're able to repost it.
>
> Thanks,
> John
>
>
> On Wed, Mar 29, 2017 at 8:02 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=79856 >
> >
> > John, I changed the env variable name to USER_GRIB_TABLES but it
still
> > is not
> > working. Does MET provide any messages indicating that it is
using an
> > alternate grib table? If so, I am not seeing any using error
level 4
> > setting.
> > Does the format of the attached grib table look correct? The
config
> > file is attache - anything missing there? You should still have
the
> > grib file on the ftp server.
> >
> > DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> > GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> > table: 1, parm_cat:
> > 6,
> > parm: 70
> > DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> > GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> > table: 1, parm_cat:
> > 6,
> > parm: 70
> > DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> > GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> > table: 1, parm_cat:
> > 19,
> > parm: 223
> > DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> > GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> > table: 1, parm_cat:
> > 19,
> > parm: 223
> > DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> > GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> > table: 1, parm_cat:
> > 19,
> > parm: 223
> > DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> > GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> > table: 1, parm_cat:
> > 19,
> > parm: 223
> > DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> > GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> > table: 1, parm_cat:
> > 19,
> > parm: 223
> > DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created
new
> > Met2dDataFile object of type "FileType_NcMet".
> > DEBUG 4: Latitude/Longitude Grid Data:
> > DEBUG 4: lat_ll = -89.9219
> > DEBUG 4: lon_ll = -0.117187
> > DEBUG 4: delta_lat = 0.234375
> > DEBUG 4: delta_lon = 0.15625
> > DEBUG 4: Nlat = 1152
> > DEBUG 4: Nlon = 1536
> > DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
object
> > of type "FileType_Gb2".
> > DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
object
> > of type "FileType_NcMet".
> > ERROR :
> > ERROR : VarInfoGrib2::set_dict() - either name or GRIB2_disc,
> > GRIB2_parm_cat and GRIB2_parm must be specified in field
information
> > ERROR :
> >
> > The environmental variable list is below:
> >
> > SHELL=/bin/ksh
> > SHLVL=1
> > TERM=xterm-256color
> > USER=qcteam
> > USER_GRIB_TABLES=/h/data/global/WXQC/data/met/config/grib2
> >
> > The attached file grib2_geps.txt is in the directory defined above
by
> > the environmental variable.
> >
> > Bob
> >
> > -----Original Message-----
> > From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> > Sent: Tuesday, March 28, 2017 6:47 PM
> > To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
> > <robert.craig.2 at us.af.mil>
> > Subject: Re: [rt.rap.ucar.edu #79856] Request
> >
> > Bob,
> >
> > My apologies for sending you incorrect information. The
environment
> > variable should be named "USER_GRIB_TABLES" but I had told you
> > "GRIB_USER_TABLES".
> >
> > Please try "USER_GRIB_TABLES" and let me know how it goes.
> >
> > And please note that in the upcoming version 6.0, we've renamed it
to
> > MET_GRIB_TABLES to consistently prefix MET-related environment
> > variables with "MET_". And we've added a paragraph to
> > data/config/README and the user's guide about that environment
> > variable.
> >
> > Sorry for the confusion!
> >
> > John
> >
> > On Fri, Mar 24, 2017 at 12:40 PM, robert.craig.2 at us.af.mil via RT
<
> > met_help at ucar.edu> wrote:
> >
> > >
> > > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=79856 >
> > >
> > > John, I made the changes you recommended and am still having
issues.
> > > Attached
> > > is my config file and grib2 file. What did I miss?
> > >
> > > [2647 qcteam hpc9-lsn-02d /home/qcteam] env | grep GRIB
> > > GRIB_USER_TABLES=/h/data/global/WXQC/data/met/config/grib2
> > > MET_GRIB2CINC=/h/WXQC/met-5.1/lib/g2clib-1.4.0
> > > MET_GRIB2CLIB=/h/WXQC/met-5.1/lib/g2clib-1.4.0
> > >
> > > In /h/data/global/WXQC/data/met/config/grib2 is a file called
> > > grib2_geps.txt.
> > >
> > > When I run the code I get the the following if I use the "name"
> > > parameter in the config file:
> > >
> > > DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> > > GRIB2 field indexes - disc: 0, master table: 10, center: 57,
local
> > > table: 1, parm_cat:
> > > 6,
> > > parm: 70
> > > DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> > > GRIB2 field indexes - disc: 0, master table: 10, center: 57,
local
> > > table: 1, parm_cat:
> > > 19,
> > > parm: 223
> > > DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> > > GRIB2 field indexes - disc: 0, master table: 10, center: 57,
local
> > > table: 1, parm_cat:
> > > 19,
> > > parm: 223
> > > DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> > > GRIB2 field indexes - disc: 0, master table: 10, center: 57,
local
> > > table: 1, parm_cat:
> > > 19,
> > > parm: 223
> > > DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> > > GRIB2 field indexes - disc: 0, master table: 10, center: 57,
local
> > > table: 1, parm_cat:
> > > 19,
> > > parm: 223
> > > DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> > > GRIB2 field indexes - disc: 0, master table: 10, center: 57,
local
> > > table: 1, parm_cat:
> > > 19,
> > > parm: 223
> > > DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created
new
> > > Met2dDataFile object of type "FileType_NcMet".
> > > DEBUG 4: Latitude/Longitude Grid Data:
> > > DEBUG 4: lat_ll = -89.9219
> > > DEBUG 4: lon_ll = -0.117187
> > > DEBUG 4: delta_lat = 0.234375
> > > DEBUG 4: delta_lon = 0.15625
> > > DEBUG 4: Nlat = 1152
> > > DEBUG 4: Nlon = 1536
> > > DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
> > > object of type "FileType_Gb2".
> > > DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
> > > object of type "FileType_NcMet".
> > > ERROR :
> > > ERROR : VarInfoGrib2::set_dict() - unrecognized GRIB2 field
> > > abbreviation 'PWS15'
> > > ERROR :
> > >
> > > If I use the three grib2 parameters I get the following:
> > >
> > > DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> > > GRIB2 field indexes - disc: 0, master table: 10, center: 57,
local
> > > table: 1, parm_cat:
> > > 6,
> > > parm: 70
> > > DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> > > GRIB2 field indexes - disc: 0, master table: 10, center: 57,
local
> > > table: 1, parm_cat:
> > > 6,
> > > parm: 70
> > > DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> > > GRIB2 field indexes - disc: 0, master table: 10, center: 57,
local
> > > table: 1, parm_cat:
> > > 6,
> > > parm: 70
> > > DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> > > GRIB2 field indexes - disc: 0, master table: 10, center: 57,
local
> > > table: 1, parm_cat:
> > > 19,
> > > parm: 223
> > > DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> > > GRIB2 field indexes - disc: 0, master table: 10, center: 57,
local
> > > table: 1, parm_cat:
> > > 19,
> > > parm: 223
> > > DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> > > GRIB2 field indexes - disc: 0, master table: 10, center: 57,
local
> > > table: 1, parm_cat:
> > > 19,
> > > parm: 223
> > > DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> > > GRIB2 field indexes - disc: 0, master table: 10, center: 57,
local
> > > table: 1, parm_cat:
> > > 19,
> > > parm: 223
> > > DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> > > GRIB2 field indexes - disc: 0, master table: 10, center: 57,
local
> > > table: 1, parm_cat:
> > > 19,
> > > parm: 223
> > > DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created
new
> > > Met2dDataFile object of type "FileType_NcMet".
> > > DEBUG 4: Latitude/Longitude Grid Data:
> > > DEBUG 4: lat_ll = -89.9219
> > > DEBUG 4: lon_ll = -0.117187
> > > DEBUG 4: delta_lat = 0.234375
> > > DEBUG 4: delta_lon = 0.15625
> > > DEBUG 4: Nlat = 1152
> > > DEBUG 4: Nlon = 1536
> > > DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
> > > object of type "FileType_Gb2".
> > > DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
> > > object of type "FileType_NcMet".
> > > ERROR :
> > > ERROR : VarInfoGrib2::set_dict() - either name or GRIB2_disc,
> > > GRIB2_parm_cat and GRIB2_parm must be specified in field
information
> > > ERROR :
> > >
> > > -----Original Message-----
> > > From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> > > Sent: Wednesday, March 22, 2017 11:44 AM
> > > To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
> > > <robert.craig.2 at us.af.mil>
> > > Subject: Re: [rt.rap.ucar.edu #79856] Request
> > >
> > > Bob,
> > >
> > > Yes, there is a way of having different users point to different
> > > GRIB2 tables to use, and it's present in version 5.2 of MET.
But
> > > we've refined it in the upcoming 6.0 release.
> > >
> > > For version 5.2, you do this by setting an environment variable
> > > named "GRIB_USER_TABLES". It must be set to a *directory*
> > > containing files that begin with "grib1" or "grib2" and end with
> > > ".txt". Just place your version of grib2_var_flat.txt in that
> > > directory an edit it as needed.
> > >
> > > The MET tools will read the contents of the GRIB_USER_TABLES
> > > directory first and then the default ones second. Any of your
local
> > > settings will take precedence over the default ones.
> > >
> > > For version 6.0, we're renaming that "GRIB_USER_TABLES" to be
> > > "MET_GRIB_TABLES", using the "MET_" prefix to be consistent with
> > > other MET-related environment variables. In 6.0, it can be set
to a
> > > directory containing multiple files or to an explicit file name
to
> > > be
> > used.
> > >
> > > Please let me know if any additional issues or questions arise.
> > >
> > > Thanks,
> > > John
> > >
> > > On Thu, Mar 16, 2017 at 7:55 AM, robert.craig.2 at us.af.mil via RT
<
> > > met_help at ucar.edu> wrote:
> > >
> > > >
> > > > Thu Mar 16 07:55:51 2017: Request 79856 was acted upon.
> > > > Transaction: Ticket created by robert.craig.2 at us.af.mil
> > > > Queue: met_help
> > > > Subject: Request
> > > > Owner: Nobody
> > > > Requestors: robert.craig.2 at us.af.mil
> > > > Status: new
> > > > Ticket <URL:
> > > > https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=79856
> > > > >
> > > >
> > > >
> > > > John, I have a question/suggestion for 6.0. We don't have
the same
> > > GRIB2
> > > > table definitions as those at are in the grib2_vars_flat.txt
table.
> > > > I can retrieve my model values defining the discipline code,
> > > > parmcat, and parm values but MET will then put variable name
that
> > > > comes from the subject table into the STAT file. So in my
case, I
> > > > am retrieving probability of wind > 25 kts but heatflux might
be
> > > > the name that ends up in the STAT file MET produces. This
problem
> > > > can be solved if we can point MET to the proper
> > > > grib2_vars_flat.txt table
> > to
> > > > use.
> > > > Different MET users in 557th/AFWA could point MET to their own
> > > > version of the table and we wouldn't step on each other.
> > > >
> > > > Thank
> > > > Bob
> > > >
> > > >
> > > >
> > >
> > >
> > >
> >
> >
> >
>
>
>
>
------------------------------------------------
Subject: Request
From: John Halley Gotway
Time: Thu Mar 30 20:27:36 2017
GRIB2
0 10 0 255 57 1 19 161 "PWS15" "Probabilty of 10 m winds above
15kts" "%"
0 10 0 255 57 1 19 163 "PWS25" "Probabilty of 10 m winds above
25kts" "%"
0 10 0 255 57 1 19 164 "PWS35" "Probabilty of 10 m winds above
35kts" "%"
0 10 0 255 57 1 19 165 "PWS50" "Probabilty of 10 m winds above
50kts" "%"
0 10 0 255 57 1 19 173 "PQP1" "Probability of precip accumulation >
.01" "%"
0 10 0 255 57 1 19 174 "PQP2" "Probability of precip accumulation >
.02" "%"
0 10 0 255 57 1 19 182 "PSN1" "Probability of snow accumulation > 1"
"%"
0 10 0 255 57 1 19 183 "PSN2" "Probability of snow accumulation > 2"
"%"
0 10 0 255 57 1 19 175 "QP005" "Probability of precip accumulation >
.05" "%"
0 10 0 255 57 1 19 176 "QP010" "Probability of precip accumulation >
.10" "%"
0 10 0 255 57 1 19 177 "QP025" "Probability of precip accumulation >
.25" "%"
0 10 0 255 57 1 19 178 "QP050" "Probability of precip accumulation >
.50" "%"
0 10 0 255 57 1 19 179 "QP075" "Probability of precip accumulation >
.75" "%"
0 10 0 255 57 1 19 180 "QP100" "Probability of precip accumulation >
1.0" "%"
0 10 0 255 57 1 19 181 "QP500" "Probability of precip accumulation >
5.0" "%"
0 10 0 255 57 1 19 212 "PT273" "Probability of 2m temperature > 273"
"%"
0 10 0 255 57 1 19 213 "PT305" "Probability of 2m temperature > 305"
"%"
0 10 0 255 57 1 19 207 "PHT58" "Probability of 500mb HGT > 5800 m"
"%"
0 10 0 255 57 1 19 203 "PVIS1" "Probability of surface visiblity < 1
mi" "%"
0 10 0 255 57 1 19 202 "PVIS3" "Probability of surface visibility <
3 mi" "%"
0 10 0 255 57 1 19 201 "PVIS5" "Probability of surface visibility <
5 mi" "%"
0 10 0 255 57 1 19 224 "PC20" "Probabilty of Total Cloud < 20 %"
"%"
0 10 0 255 57 1 19 225 "PC80" "Probablity of Total Cloud > 80 %"
"%"
------------------------------------------------
Subject: RE: [rt.rap.ucar.edu #79856] Request
From: robert.craig.2 at us.af.mil
Time: Fri Mar 31 11:17:02 2017
Any message would be good to show the user things are working as
expected. The suggestions worked for the GRIB2 issues.
Also, I included Tara's comments on MET in the security package for
MET. What we hope is that the security people will say the risks
using MET are not high enough to exclude from our newest computer
systems. Would you guys be interested in the results from the FORTIFY
scan of MET?
Thanks for the help
Bob Craig
-----Original Message-----
From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
Sent: Thursday, March 30, 2017 9:28 PM
To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
<robert.craig.2 at us.af.mil>
Subject: Re: [rt.rap.ucar.edu #79856] Request
Bob,
Sorry for the delay in getting to this. There were two things I
needed to change to get this to work:
(1) There was a typo on line 24 of grib2_geps.txt. You were missing a
closing double quote in one spot.
(2) This is pretty ridiculous but the current parsing logic requires
that two spaces be used between the strings.
I've attached an updated version of that file with those changes. And
I did the following:
- Placed that file into a directory: table_dir/grib2_geps.txt
- Set the environment variable:
setenv USER_GRIB_TABLES table_dir
- Ran plot_data_plane:
met-5.2/bin/plot_data_plane grib2.2017031700.0024 psw15.ps
'name="PWS15"; level="Z10";'
The resulting image is attached.
Obviously requiring two spaces is *NOT* very intuitive. If possible,
I'll try to fix up that parsing logic to allow for one or more spaces
prior to the 6.0 release.
I agree that it would be nice to print a debug message indicating that
the user GRIB tables are being read. However, these are read by the
constructor of that class before the logging level is defined. So
there
would be no way to turn those messages off. Perhaps that's OK, if
USER_GRIB_TABLES (or MET_GRIB_TABLES in 6.0) is defined, perhaps it's
good to see a DEBUG(0) message telling you what it's doing.
What do you think?
Thanks,
John
On Thu, Mar 30, 2017 at 2:55 PM, robert.craig.2 at us.af.mil via RT <
met_help at ucar.edu> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=79856 >
>
> John, I think the file transferred to your server - lots of weird
messages.
> Let me know if you didn't get it.
>
> Thanks
> Bob Craig
>
> -----Original Message-----
> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> Sent: Thursday, March 30, 2017 2:40 PM
> To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
> <robert.craig.2 at us.af.mil>
> Subject: Re: [rt.rap.ucar.edu #79856] Request
>
> Hi Bob,
>
> I'm sorry but I don't see the sample GRIB2 file on our ftp site.
> Perhaps it was aged off before I was able to grab it.
>
> Please let me know if/when you're able to repost it.
>
> Thanks,
> John
>
>
> On Wed, Mar 29, 2017 at 8:02 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=79856 >
> >
> > John, I changed the env variable name to USER_GRIB_TABLES but it
> > still is not
> > working. Does MET provide any messages indicating that it is
using an
> > alternate grib table? If so, I am not seeing any using error
level
> > 4 setting.
> > Does the format of the attached grib table look correct? The
config
> > file is attache - anything missing there? You should still have
the
> > grib file on the ftp server.
> >
> > DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> > GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> > table: 1, parm_cat:
> > 6,
> > parm: 70
> > DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> > GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> > table: 1, parm_cat:
> > 6,
> > parm: 70
> > DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> > GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> > table: 1, parm_cat:
> > 19,
> > parm: 223
> > DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> > GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> > table: 1, parm_cat:
> > 19,
> > parm: 223
> > DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> > GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> > table: 1, parm_cat:
> > 19,
> > parm: 223
> > DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> > GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> > table: 1, parm_cat:
> > 19,
> > parm: 223
> > DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
> > GRIB2 field indexes - disc: 0, master table: 10, center: 57, local
> > table: 1, parm_cat:
> > 19,
> > parm: 223
> > DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created
new
> > Met2dDataFile object of type "FileType_NcMet".
> > DEBUG 4: Latitude/Longitude Grid Data:
> > DEBUG 4: lat_ll = -89.9219
> > DEBUG 4: lon_ll = -0.117187
> > DEBUG 4: delta_lat = 0.234375
> > DEBUG 4: delta_lon = 0.15625
> > DEBUG 4: Nlat = 1152
> > DEBUG 4: Nlon = 1536
> > DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
> > object of type "FileType_Gb2".
> > DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
> > object of type "FileType_NcMet".
> > ERROR :
> > ERROR : VarInfoGrib2::set_dict() - either name or GRIB2_disc,
> > GRIB2_parm_cat and GRIB2_parm must be specified in field
information
> > ERROR :
> >
> > The environmental variable list is below:
> >
> > SHELL=/bin/ksh
> > SHLVL=1
> > TERM=xterm-256color
> > USER=qcteam
> > USER_GRIB_TABLES=/h/data/global/WXQC/data/met/config/grib2
> >
> > The attached file grib2_geps.txt is in the directory defined above
> > by the environmental variable.
> >
> > Bob
> >
> > -----Original Message-----
> > From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> > Sent: Tuesday, March 28, 2017 6:47 PM
> > To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
> > <robert.craig.2 at us.af.mil>
> > Subject: Re: [rt.rap.ucar.edu #79856] Request
> >
> > Bob,
> >
> > My apologies for sending you incorrect information. The
environment
> > variable should be named "USER_GRIB_TABLES" but I had told you
> > "GRIB_USER_TABLES".
> >
> > Please try "USER_GRIB_TABLES" and let me know how it goes.
> >
> > And please note that in the upcoming version 6.0, we've renamed it
> > to MET_GRIB_TABLES to consistently prefix MET-related environment
> > variables with "MET_". And we've added a paragraph to
> > data/config/README and the user's guide about that environment
> > variable.
> >
> > Sorry for the confusion!
> >
> > John
> >
> > On Fri, Mar 24, 2017 at 12:40 PM, robert.craig.2 at us.af.mil via RT
<
> > met_help at ucar.edu> wrote:
> >
> > >
> > > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=79856 >
> > >
> > > John, I made the changes you recommended and am still having
issues.
> > > Attached
> > > is my config file and grib2 file. What did I miss?
> > >
> > > [2647 qcteam hpc9-lsn-02d /home/qcteam] env | grep GRIB
> > > GRIB_USER_TABLES=/h/data/global/WXQC/data/met/config/grib2
> > > MET_GRIB2CINC=/h/WXQC/met-5.1/lib/g2clib-1.4.0
> > > MET_GRIB2CLIB=/h/WXQC/met-5.1/lib/g2clib-1.4.0
> > >
> > > In /h/data/global/WXQC/data/met/config/grib2 is a file called
> > > grib2_geps.txt.
> > >
> > > When I run the code I get the the following if I use the "name"
> > > parameter in the config file:
> > >
> > > DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> > > GRIB2 field indexes - disc: 0, master table: 10, center: 57,
local
> > > table: 1, parm_cat:
> > > 6,
> > > parm: 70
> > > DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> > > GRIB2 field indexes - disc: 0, master table: 10, center: 57,
local
> > > table: 1, parm_cat:
> > > 19,
> > > parm: 223
> > > DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> > > GRIB2 field indexes - disc: 0, master table: 10, center: 57,
local
> > > table: 1, parm_cat:
> > > 19,
> > > parm: 223
> > > DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> > > GRIB2 field indexes - disc: 0, master table: 10, center: 57,
local
> > > table: 1, parm_cat:
> > > 19,
> > > parm: 223
> > > DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> > > GRIB2 field indexes - disc: 0, master table: 10, center: 57,
local
> > > table: 1, parm_cat:
> > > 19,
> > > parm: 223
> > > DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> > > GRIB2 field indexes - disc: 0, master table: 10, center: 57,
local
> > > table: 1, parm_cat:
> > > 19,
> > > parm: 223
> > > DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created
> > > new Met2dDataFile object of type "FileType_NcMet".
> > > DEBUG 4: Latitude/Longitude Grid Data:
> > > DEBUG 4: lat_ll = -89.9219
> > > DEBUG 4: lon_ll = -0.117187
> > > DEBUG 4: delta_lat = 0.234375
> > > DEBUG 4: delta_lon = 0.15625
> > > DEBUG 4: Nlat = 1152
> > > DEBUG 4: Nlon = 1536
> > > DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
> > > object of type "FileType_Gb2".
> > > DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
> > > object of type "FileType_NcMet".
> > > ERROR :
> > > ERROR : VarInfoGrib2::set_dict() - unrecognized GRIB2 field
> > > abbreviation 'PWS15'
> > > ERROR :
> > >
> > > If I use the three grib2 parameters I get the following:
> > >
> > > DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> > > GRIB2 field indexes - disc: 0, master table: 10, center: 57,
local
> > > table: 1, parm_cat:
> > > 6,
> > > parm: 70
> > > DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> > > GRIB2 field indexes - disc: 0, master table: 10, center: 57,
local
> > > table: 1, parm_cat:
> > > 6,
> > > parm: 70
> > > DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> > > GRIB2 field indexes - disc: 0, master table: 10, center: 57,
local
> > > table: 1, parm_cat:
> > > 6,
> > > parm: 70
> > > DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> > > GRIB2 field indexes - disc: 0, master table: 10, center: 57,
local
> > > table: 1, parm_cat:
> > > 19,
> > > parm: 223
> > > DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> > > GRIB2 field indexes - disc: 0, master table: 10, center: 57,
local
> > > table: 1, parm_cat:
> > > 19,
> > > parm: 223
> > > DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> > > GRIB2 field indexes - disc: 0, master table: 10, center: 57,
local
> > > table: 1, parm_cat:
> > > 19,
> > > parm: 223
> > > DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> > > GRIB2 field indexes - disc: 0, master table: 10, center: 57,
local
> > > table: 1, parm_cat:
> > > 19,
> > > parm: 223
> > > DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> > > GRIB2 field indexes - disc: 0, master table: 10, center: 57,
local
> > > table: 1, parm_cat:
> > > 19,
> > > parm: 223
> > > DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created
> > > new Met2dDataFile object of type "FileType_NcMet".
> > > DEBUG 4: Latitude/Longitude Grid Data:
> > > DEBUG 4: lat_ll = -89.9219
> > > DEBUG 4: lon_ll = -0.117187
> > > DEBUG 4: delta_lat = 0.234375
> > > DEBUG 4: delta_lon = 0.15625
> > > DEBUG 4: Nlat = 1152
> > > DEBUG 4: Nlon = 1536
> > > DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
> > > object of type "FileType_Gb2".
> > > DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
> > > object of type "FileType_NcMet".
> > > ERROR :
> > > ERROR : VarInfoGrib2::set_dict() - either name or GRIB2_disc,
> > > GRIB2_parm_cat and GRIB2_parm must be specified in field
> > > information ERROR :
> > >
> > > -----Original Message-----
> > > From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> > > Sent: Wednesday, March 22, 2017 11:44 AM
> > > To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
> > > <robert.craig.2 at us.af.mil>
> > > Subject: Re: [rt.rap.ucar.edu #79856] Request
> > >
> > > Bob,
> > >
> > > Yes, there is a way of having different users point to different
> > > GRIB2 tables to use, and it's present in version 5.2 of MET.
But
> > > we've refined it in the upcoming 6.0 release.
> > >
> > > For version 5.2, you do this by setting an environment variable
> > > named "GRIB_USER_TABLES". It must be set to a *directory*
> > > containing files that begin with "grib1" or "grib2" and end with
> > > ".txt". Just place your version of grib2_var_flat.txt in that
> > > directory an edit it as needed.
> > >
> > > The MET tools will read the contents of the GRIB_USER_TABLES
> > > directory first and then the default ones second. Any of your
> > > local settings will take precedence over the default ones.
> > >
> > > For version 6.0, we're renaming that "GRIB_USER_TABLES" to be
> > > "MET_GRIB_TABLES", using the "MET_" prefix to be consistent with
> > > other MET-related environment variables. In 6.0, it can be set
to
> > > a directory containing multiple files or to an explicit file
name
> > > to be
> > used.
> > >
> > > Please let me know if any additional issues or questions arise.
> > >
> > > Thanks,
> > > John
> > >
> > > On Thu, Mar 16, 2017 at 7:55 AM, robert.craig.2 at us.af.mil via RT
<
> > > met_help at ucar.edu> wrote:
> > >
> > > >
> > > > Thu Mar 16 07:55:51 2017: Request 79856 was acted upon.
> > > > Transaction: Ticket created by robert.craig.2 at us.af.mil
> > > > Queue: met_help
> > > > Subject: Request
> > > > Owner: Nobody
> > > > Requestors: robert.craig.2 at us.af.mil
> > > > Status: new
> > > > Ticket <URL:
> > > > https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=79856
> > > > >
> > > >
> > > >
> > > > John, I have a question/suggestion for 6.0. We don't have
the same
> > > GRIB2
> > > > table definitions as those at are in the grib2_vars_flat.txt
table.
> > > > I can retrieve my model values defining the discipline code,
> > > > parmcat, and parm values but MET will then put variable name
> > > > that comes from the subject table into the STAT file. So in
my
> > > > case, I am retrieving probability of wind > 25 kts but
heatflux
> > > > might be the name that ends up in the STAT file MET produces.
> > > > This problem can be solved if we can point MET to the proper
> > > > grib2_vars_flat.txt table
> > to
> > > > use.
> > > > Different MET users in 557th/AFWA could point MET to their own
> > > > version of the table and we wouldn't step on each other.
> > > >
> > > > Thank
> > > > Bob
> > > >
> > > >
> > > >
> > >
> > >
> > >
> >
> >
> >
>
>
>
>
------------------------------------------------
More information about the Met_help
mailing list