[Met_help] [rt.rap.ucar.edu #80051] History for NETcdf Obs File
John Halley Gotway via RT
met_help at ucar.edu
Thu Apr 6 11:13:23 MDT 2017
----------------------------------------------------------------
Initial Request
----------------------------------------------------------------
John, or Julie
I am having trouble reading a NETcdf file in point stat. Attached in my
configuration file. I get the following error when I run point stat:
DEBUG 1: Default Config File:
/h/WXQC/met-5.2/share/met/config/PointStatConfig_default
DEBUG 1: User Config File:
/h/WXQC/met-5.2/data/config/PointStatConfig_single_updated
DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created new
Met2dDataFile object of type "FileType_Gb2".
DEBUG 3: Switching the GRIB2 radius of the earth value of 6371.23 km to
6371.2 km for internal consistency.
DEBUG 4:
DEBUG 4: Latitude/Longitude Grid Data:
DEBUG 4: lat_ll: -89.9219
DEBUG 4: lon_ll: -0.117187
DEBUG 4: delta_lat: 0.15625
DEBUG 4: delta_lon: 0.234375
DEBUG 4: Nlat: 1152
DEBUG 4: Nlon: 1536
DEBUG 4:
DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo object of
type "FileType_Gb2".
DEBUG 4: parse_conf_sid_exc() -> Station ID exclusion list contains 0
entries.
ERROR :
ERROR : VarInfo::set_level_info_grib() - failed to parse level string
'(3,5)'
I am not sure what I should have in the level field in this case. Looking
in the NETcdf header, I see there are several dimensions listed :
dimensions:
mxstr = 40 ;
hdr_arr_len = 3 ;
obs_arr_len = 5 ;
nhdr = 7345 ;
nobs = UNLIMITED ; // (7345 currently)
Which ones should I be using?
The NETcdf file I am reading in on the FTP server.
Thanks
Bob Craig
----------------------------------------------------------------
Complete Ticket History
----------------------------------------------------------------
Subject: NETcdf Obs File
From: John Halley Gotway
Time: Tue Apr 04 13:16:56 2017
Bob,
I realize that this is a little confusing, but...
When passing to MET a gridded NetCDF file, you set the "name" as the
variable name which contains the gridded data you want to use.
However, when passing to MET a point observation NetCDF file, the
logic is
different. Each of the observations is currently assigned a GRIB
code.
That GRIB code is one of the entries in the "obs_arr" variable. In
Point-Stat and Ensemble-Stat, when setting up the "obs" section for
point
observations, you configure it as if it were GRIB1 data. Then the MET
tools look for observations that have the GRIB code you specified.
Looking at your config file, I'm guessing you want to verify using
observation with GRIB code = 140.
But now, what does 140 mean? Looking in this file:
grib1_af_131_57.txt
I see the following entry for 140:
140 131 57 2 "cloudHeightCeiling" "Ceiling" "m"
Is that the correct observation type? If so, I'd suggest trying:
obs = {
message_type = [ "ADPSFC" ];
sid_exc = [];
field = [
{
name = "cloudHeightCeiling";
level = "Z0";
GRIB1_ptv = 131;
cat_thresh = [ >0.0 ];
}
];
}
Please let me know how that goes.
Thanks,
John
On Tue, Apr 4, 2017 at 2:14 PM, robert.craig.2 at us.af.mil via RT <
met_help at ucar.edu> wrote:
>
> Tue Apr 04 12:14:44 2017: Request 80051 was acted upon.
> Transaction: Ticket created by robert.craig.2 at us.af.mil
> Queue: met_help
> Subject: NETcdf Obs File
> Owner: Nobody
> Requestors: robert.craig.2 at us.af.mil
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80051 >
>
>
> John, or Julie
>
> I am having trouble reading a NETcdf file in point stat. Attached
in my
> configuration file. I get the following error when I run point
stat:
>
> DEBUG 1: Default Config File:
> /h/WXQC/met-5.2/share/met/config/PointStatConfig_default
> DEBUG 1: User Config File:
> /h/WXQC/met-5.2/data/config/PointStatConfig_single_updated
> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created new
> Met2dDataFile object of type "FileType_Gb2".
> DEBUG 3: Switching the GRIB2 radius of the earth value of 6371.23 km
to
> 6371.2 km for internal consistency.
> DEBUG 4:
> DEBUG 4: Latitude/Longitude Grid Data:
> DEBUG 4: lat_ll: -89.9219
> DEBUG 4: lon_ll: -0.117187
> DEBUG 4: delta_lat: 0.15625
> DEBUG 4: delta_lon: 0.234375
> DEBUG 4: Nlat: 1152
> DEBUG 4: Nlon: 1536
> DEBUG 4:
> DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
object of
> type "FileType_Gb2".
> DEBUG 4: parse_conf_sid_exc() -> Station ID exclusion list contains
0
> entries.
> ERROR :
> ERROR : VarInfo::set_level_info_grib() - failed to parse level
string
> '(3,5)'
>
> I am not sure what I should have in the level field in this case.
Looking
> in the NETcdf header, I see there are several dimensions listed :
>
> dimensions:
> mxstr = 40 ;
> hdr_arr_len = 3 ;
> obs_arr_len = 5 ;
> nhdr = 7345 ;
> nobs = UNLIMITED ; // (7345 currently)
>
> Which ones should I be using?
>
> The NETcdf file I am reading in on the FTP server.
>
> Thanks
> Bob Craig
>
>
------------------------------------------------
Subject: RE: [Non-DoD Source] Re: [rt.rap.ucar.edu #80051] NETcdf Obs File
From: robert.craig.2 at us.af.mil
Time: Wed Apr 05 08:03:50 2017
Thanks John. I made the changes and things have progressed to Point
Stat running but it throws all the observations due to GRIB code. In
the NETCDF ob file, I set the ob value to the precip type GRIB 1 code
defined in the /h/WXQC/met-
5.2/share/met/table_files/grib1_af_131_57.txt. I originally only
changed the grib tables in met-5.2/data/table_files but found it is
looking at the shared version. In the grib1_af_131_57.txt file, the
columns for text have 1 space instead of 2 separating them. Do they
have to be two spaces like the grib2 tables? In the
grib1_af_131_57.txt I defined CRAIN as:
167 131 57 2 "CRAIN" "Categorical Rain" "code" and I have 167 as the
ob value in my NETCDF file I am using. An NCDUMP of the file shows
lots of observations with 167 as the obvalue. So why would I get all
the obs rejected for Grib code. The manual doesn't delve into this
subject with a lot of detail.
I know you guys are busy with the MET 6 roll out.
Thanks for your help.
Bob
-----Original Message-----
From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
Sent: Tuesday, April 04, 2017 2:17 PM
To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
<robert.craig.2 at us.af.mil>
Cc: SITTEL, MATTHEW C CTR USAF AFMC AFLCMC/HBAW-OL
<matthew.sittel.ctr at us.af.mil>
Subject: [Non-DoD Source] Re: [rt.rap.ucar.edu #80051] NETcdf Obs File
Bob,
I realize that this is a little confusing, but...
When passing to MET a gridded NetCDF file, you set the "name" as the
variable name which contains the gridded data you want to use.
However, when passing to MET a point observation NetCDF file, the
logic is different. Each of the observations is currently assigned a
GRIB code.
That GRIB code is one of the entries in the "obs_arr" variable. In
Point-Stat and Ensemble-Stat, when setting up the "obs" section for
point observations, you configure it as if it were GRIB1 data. Then
the MET tools look for observations that have the GRIB code you
specified.
Looking at your config file, I'm guessing you want to verify using
observation with GRIB code = 140.
But now, what does 140 mean? Looking in this file:
grib1_af_131_57.txt
I see the following entry for 140:
140 131 57 2 "cloudHeightCeiling" "Ceiling" "m"
Is that the correct observation type? If so, I'd suggest trying:
obs = {
message_type = [ "ADPSFC" ];
sid_exc = [];
field = [
{
name = "cloudHeightCeiling";
level = "Z0";
GRIB1_ptv = 131;
cat_thresh = [ >0.0 ];
}
];
}
Please let me know how that goes.
Thanks,
John
On Tue, Apr 4, 2017 at 2:14 PM, robert.craig.2 at us.af.mil via RT <
met_help at ucar.edu> wrote:
>
> Tue Apr 04 12:14:44 2017: Request 80051 was acted upon.
> Transaction: Ticket created by robert.craig.2 at us.af.mil
> Queue: met_help
> Subject: NETcdf Obs File
> Owner: Nobody
> Requestors: robert.craig.2 at us.af.mil
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80051
> >
>
>
> John, or Julie
>
> I am having trouble reading a NETcdf file in point stat. Attached
in my
> configuration file. I get the following error when I run point
stat:
>
> DEBUG 1: Default Config File:
> /h/WXQC/met-5.2/share/met/config/PointStatConfig_default
> DEBUG 1: User Config File:
> /h/WXQC/met-5.2/data/config/PointStatConfig_single_updated
> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created new
> Met2dDataFile object of type "FileType_Gb2".
> DEBUG 3: Switching the GRIB2 radius of the earth value of 6371.23 km
> to
> 6371.2 km for internal consistency.
> DEBUG 4:
> DEBUG 4: Latitude/Longitude Grid Data:
> DEBUG 4: lat_ll: -89.9219
> DEBUG 4: lon_ll: -0.117187
> DEBUG 4: delta_lat: 0.15625
> DEBUG 4: delta_lon: 0.234375
> DEBUG 4: Nlat: 1152
> DEBUG 4: Nlon: 1536
> DEBUG 4:
> DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
object
> of type "FileType_Gb2".
> DEBUG 4: parse_conf_sid_exc() -> Station ID exclusion list contains
0
> entries.
> ERROR :
> ERROR : VarInfo::set_level_info_grib() - failed to parse level
string
> '(3,5)'
>
> I am not sure what I should have in the level field in this case.
Looking
> in the NETcdf header, I see there are several dimensions listed :
>
> dimensions:
> mxstr = 40 ;
> hdr_arr_len = 3 ;
> obs_arr_len = 5 ;
> nhdr = 7345 ;
> nobs = UNLIMITED ; // (7345 currently)
>
> Which ones should I be using?
>
> The NETcdf file I am reading in on the FTP server.
>
> Thanks
> Bob Craig
>
>
------------------------------------------------
Subject: FW: [Non-DoD Source] Re: [rt.rap.ucar.edu #80051] NETcdf Obs File
From: robert.craig.2 at us.af.mil
Time: Wed Apr 05 09:10:31 2017
John, I figured out that even though I had updated the grib1 file
grib1_af_131_57.txt, MET is using the CRAIN code of 140 found in the
ncep tables in the table_files directory. I placed the
grib1_af_131_57.txt in the directory the USER_GRIB_TABLES points to
(Met-5.2). In my config file I added GRIB1_ptv=131 but I see there
is an NCEP table with the same number. What decides which table MET
uses? I will rename the grib1_ncep_131_7.txt table to something else
so hopefully MET can't find it.
Bob
-----Original Message-----
From: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
Sent: Wednesday, April 05, 2017 9:04 AM
To: 'met_help at ucar.edu' <met_help at ucar.edu>
Cc: SITTEL, MATTHEW C CTR USAF AFMC AFLCMC/HBAW-OL
<matthew.sittel.ctr at us.af.mil>
Subject: RE: [Non-DoD Source] Re: [rt.rap.ucar.edu #80051] NETcdf Obs
File
Thanks John. I made the changes and things have progressed to Point
Stat running but it throws all the observations due to GRIB code. In
the NETCDF ob file, I set the ob value to the precip type GRIB 1 code
defined in the /h/WXQC/met-
5.2/share/met/table_files/grib1_af_131_57.txt. I originally only
changed the grib tables in met-5.2/data/table_files but found it is
looking at the shared version. In the grib1_af_131_57.txt file, the
columns for text have 1 space instead of 2 separating them. Do they
have to be two spaces like the grib2 tables? In the
grib1_af_131_57.txt I defined CRAIN as:
167 131 57 2 "CRAIN" "Categorical Rain" "code" and I have 167 as the
ob value in my NETCDF file I am using. An NCDUMP of the file shows
lots of observations with 167 as the obvalue. So why would I get all
the obs rejected for Grib code. The manual doesn't delve into this
subject with a lot of detail.
I know you guys are busy with the MET 6 roll out.
Thanks for your help.
Bob
-----Original Message-----
From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
Sent: Tuesday, April 04, 2017 2:17 PM
To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
<robert.craig.2 at us.af.mil>
Cc: SITTEL, MATTHEW C CTR USAF AFMC AFLCMC/HBAW-OL
<matthew.sittel.ctr at us.af.mil>
Subject: [Non-DoD Source] Re: [rt.rap.ucar.edu #80051] NETcdf Obs File
Bob,
I realize that this is a little confusing, but...
When passing to MET a gridded NetCDF file, you set the "name" as the
variable name which contains the gridded data you want to use.
However, when passing to MET a point observation NetCDF file, the
logic is different. Each of the observations is currently assigned a
GRIB code.
That GRIB code is one of the entries in the "obs_arr" variable. In
Point-Stat and Ensemble-Stat, when setting up the "obs" section for
point observations, you configure it as if it were GRIB1 data. Then
the MET tools look for observations that have the GRIB code you
specified.
Looking at your config file, I'm guessing you want to verify using
observation with GRIB code = 140.
But now, what does 140 mean? Looking in this file:
grib1_af_131_57.txt
I see the following entry for 140:
140 131 57 2 "cloudHeightCeiling" "Ceiling" "m"
Is that the correct observation type? If so, I'd suggest trying:
obs = {
message_type = [ "ADPSFC" ];
sid_exc = [];
field = [
{
name = "cloudHeightCeiling";
level = "Z0";
GRIB1_ptv = 131;
cat_thresh = [ >0.0 ];
}
];
}
Please let me know how that goes.
Thanks,
John
On Tue, Apr 4, 2017 at 2:14 PM, robert.craig.2 at us.af.mil via RT <
met_help at ucar.edu> wrote:
>
> Tue Apr 04 12:14:44 2017: Request 80051 was acted upon.
> Transaction: Ticket created by robert.craig.2 at us.af.mil
> Queue: met_help
> Subject: NETcdf Obs File
> Owner: Nobody
> Requestors: robert.craig.2 at us.af.mil
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80051
> >
>
>
> John, or Julie
>
> I am having trouble reading a NETcdf file in point stat. Attached
in my
> configuration file. I get the following error when I run point
stat:
>
> DEBUG 1: Default Config File:
> /h/WXQC/met-5.2/share/met/config/PointStatConfig_default
> DEBUG 1: User Config File:
> /h/WXQC/met-5.2/data/config/PointStatConfig_single_updated
> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created new
> Met2dDataFile object of type "FileType_Gb2".
> DEBUG 3: Switching the GRIB2 radius of the earth value of 6371.23 km
> to
> 6371.2 km for internal consistency.
> DEBUG 4:
> DEBUG 4: Latitude/Longitude Grid Data:
> DEBUG 4: lat_ll: -89.9219
> DEBUG 4: lon_ll: -0.117187
> DEBUG 4: delta_lat: 0.15625
> DEBUG 4: delta_lon: 0.234375
> DEBUG 4: Nlat: 1152
> DEBUG 4: Nlon: 1536
> DEBUG 4:
> DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
object
> of type "FileType_Gb2".
> DEBUG 4: parse_conf_sid_exc() -> Station ID exclusion list contains
0
> entries.
> ERROR :
> ERROR : VarInfo::set_level_info_grib() - failed to parse level
string
> '(3,5)'
>
> I am not sure what I should have in the level field in this case.
Looking
> in the NETcdf header, I see there are several dimensions listed :
>
> dimensions:
> mxstr = 40 ;
> hdr_arr_len = 3 ;
> obs_arr_len = 5 ;
> nhdr = 7345 ;
> nobs = UNLIMITED ; // (7345 currently)
>
> Which ones should I be using?
>
> The NETcdf file I am reading in on the FTP server.
>
> Thanks
> Bob Craig
>
>
------------------------------------------------
Subject: NETcdf Obs File
From: John Halley Gotway
Time: Wed Apr 05 09:20:05 2017
Bob,
I see that we've failed to include this in the documentation, but you
should be able to define the GRIB1_center and GRIB1_subcenter
configuration
options. For example hopefully adding:
GRIB1_center = 57;
Will tell MET which table to use.
Please let me know how it goes.
Thanks and sorry for the omission in the documentation. We'll update
that.
John
On Wed, Apr 5, 2017 at 11:10 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=80051 >
>
> John, I figured out that even though I had updated the grib1 file
> grib1_af_131_57.txt, MET is using the CRAIN code of 140 found in the
ncep
> tables in the table_files directory. I placed the
grib1_af_131_57.txt in
> the directory the USER_GRIB_TABLES points to (Met-5.2). In my
config file
> I added GRIB1_ptv=131 but I see there is an NCEP table with the same
> number. What decides which table MET uses? I will rename the
> grib1_ncep_131_7.txt table to something else so hopefully MET can't
find it.
>
> Bob
>
> -----Original Message-----
> From: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
> Sent: Wednesday, April 05, 2017 9:04 AM
> To: 'met_help at ucar.edu' <met_help at ucar.edu>
> Cc: SITTEL, MATTHEW C CTR USAF AFMC AFLCMC/HBAW-OL <
> matthew.sittel.ctr at us.af.mil>
> Subject: RE: [Non-DoD Source] Re: [rt.rap.ucar.edu #80051] NETcdf
Obs File
>
> Thanks John. I made the changes and things have progressed to Point
Stat
> running but it throws all the observations due to GRIB code. In the
NETCDF
> ob file, I set the ob value to the precip type GRIB 1 code defined
in the
> /h/WXQC/met-5.2/share/met/table_files/grib1_af_131_57.txt. I
originally
> only changed the grib tables in met-5.2/data/table_files but found
it is
> looking at the shared version. In the grib1_af_131_57.txt file, the
> columns for text have 1 space instead of 2 separating them. Do
they have
> to be two spaces like the grib2 tables? In the grib1_af_131_57.txt
I
> defined CRAIN as:
> 167 131 57 2 "CRAIN" "Categorical Rain" "code" and I have 167 as
the ob
> value in my NETCDF file I am using. An NCDUMP of the file shows
lots of
> observations with 167 as the obvalue. So why would I get all the
obs
> rejected for Grib code. The manual doesn't delve into this subject
with a
> lot of detail.
>
> I know you guys are busy with the MET 6 roll out.
>
> Thanks for your help.
>
> Bob
>
>
>
> -----Original Message-----
> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> Sent: Tuesday, April 04, 2017 2:17 PM
> To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
<robert.craig.2 at us.af.mil>
> Cc: SITTEL, MATTHEW C CTR USAF AFMC AFLCMC/HBAW-OL <
> matthew.sittel.ctr at us.af.mil>
> Subject: [Non-DoD Source] Re: [rt.rap.ucar.edu #80051] NETcdf Obs
File
>
> Bob,
>
> I realize that this is a little confusing, but...
>
> When passing to MET a gridded NetCDF file, you set the "name" as the
> variable name which contains the gridded data you want to use.
>
> However, when passing to MET a point observation NetCDF file, the
logic is
> different. Each of the observations is currently assigned a GRIB
code.
> That GRIB code is one of the entries in the "obs_arr" variable. In
> Point-Stat and Ensemble-Stat, when setting up the "obs" section for
point
> observations, you configure it as if it were GRIB1 data. Then the
MET
> tools look for observations that have the GRIB code you specified.
>
> Looking at your config file, I'm guessing you want to verify using
> observation with GRIB code = 140.
>
> But now, what does 140 mean? Looking in this file:
grib1_af_131_57.txt
>
> I see the following entry for 140:
>
> 140 131 57 2 "cloudHeightCeiling" "Ceiling" "m"
>
> Is that the correct observation type? If so, I'd suggest trying:
>
> obs = {
>
> message_type = [ "ADPSFC" ];
>
> sid_exc = [];
>
> field = [
>
> {
>
> name = "cloudHeightCeiling";
>
> level = "Z0";
>
> GRIB1_ptv = 131;
>
> cat_thresh = [ >0.0 ];
>
> }
>
> ];
>
> }
>
> Please let me know how that goes.
>
> Thanks,
> John
>
> On Tue, Apr 4, 2017 at 2:14 PM, robert.craig.2 at us.af.mil via RT <
> met_help at ucar.edu> wrote:
>
> >
> > Tue Apr 04 12:14:44 2017: Request 80051 was acted upon.
> > Transaction: Ticket created by robert.craig.2 at us.af.mil
> > Queue: met_help
> > Subject: NETcdf Obs File
> > Owner: Nobody
> > Requestors: robert.craig.2 at us.af.mil
> > Status: new
> > Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80051
> > >
> >
> >
> > John, or Julie
> >
> > I am having trouble reading a NETcdf file in point stat.
Attached in my
> > configuration file. I get the following error when I run point
stat:
> >
> > DEBUG 1: Default Config File:
> > /h/WXQC/met-5.2/share/met/config/PointStatConfig_default
> > DEBUG 1: User Config File:
> > /h/WXQC/met-5.2/data/config/PointStatConfig_single_updated
> > DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created
new
> > Met2dDataFile object of type "FileType_Gb2".
> > DEBUG 3: Switching the GRIB2 radius of the earth value of 6371.23
km
> > to
> > 6371.2 km for internal consistency.
> > DEBUG 4:
> > DEBUG 4: Latitude/Longitude Grid Data:
> > DEBUG 4: lat_ll: -89.9219
> > DEBUG 4: lon_ll: -0.117187
> > DEBUG 4: delta_lat: 0.15625
> > DEBUG 4: delta_lon: 0.234375
> > DEBUG 4: Nlat: 1152
> > DEBUG 4: Nlon: 1536
> > DEBUG 4:
> > DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
object
> > of type "FileType_Gb2".
> > DEBUG 4: parse_conf_sid_exc() -> Station ID exclusion list
contains 0
> > entries.
> > ERROR :
> > ERROR : VarInfo::set_level_info_grib() - failed to parse level
string
> > '(3,5)'
> >
> > I am not sure what I should have in the level field in this case.
> Looking
> > in the NETcdf header, I see there are several dimensions listed :
> >
> > dimensions:
> > mxstr = 40 ;
> > hdr_arr_len = 3 ;
> > obs_arr_len = 5 ;
> > nhdr = 7345 ;
> > nobs = UNLIMITED ; // (7345 currently)
> >
> > Which ones should I be using?
> >
> > The NETcdf file I am reading in on the FTP server.
> >
> > Thanks
> > Bob Craig
> >
> >
>
>
>
>
------------------------------------------------
Subject: RE: FW: [Non-DoD Source] Re: [rt.rap.ucar.edu #80051] NETcdf Obs File
From: robert.craig.2 at us.af.mil
Time: Wed Apr 05 09:43:24 2017
Success - I add the GRIB1_center=57 but got the error that it
couldn't find CRAIN in any table. I had also moved all ncep tables
that defined CRAIN out of both the table_files directory so only the
af table with CRAIN remained. So I then added GRIB1_subcenter=2 to my
config file and that got it to work.
Thanks
-----Original Message-----
From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
Sent: Wednesday, April 05, 2017 10:20 AM
To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
<robert.craig.2 at us.af.mil>
Cc: SITTEL, MATTHEW C CTR USAF AFMC AFLCMC/HBAW-OL
<matthew.sittel.ctr at us.af.mil>
Subject: Re: FW: [Non-DoD Source] Re: [rt.rap.ucar.edu #80051] NETcdf
Obs File
Bob,
I see that we've failed to include this in the documentation, but you
should be able to define the GRIB1_center and GRIB1_subcenter
configuration options. For example hopefully adding:
GRIB1_center = 57;
Will tell MET which table to use.
Please let me know how it goes.
Thanks and sorry for the omission in the documentation. We'll update
that.
John
On Wed, Apr 5, 2017 at 11:10 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=80051 >
>
> John, I figured out that even though I had updated the grib1 file
> grib1_af_131_57.txt, MET is using the CRAIN code of 140 found in the
> ncep tables in the table_files directory. I placed the
grib1_af_131_57.txt in
> the directory the USER_GRIB_TABLES points to (Met-5.2). In my
config file
> I added GRIB1_ptv=131 but I see there is an NCEP table with the same
> number. What decides which table MET uses? I will rename the
> grib1_ncep_131_7.txt table to something else so hopefully MET can't
find it.
>
> Bob
>
> -----Original Message-----
> From: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
> Sent: Wednesday, April 05, 2017 9:04 AM
> To: 'met_help at ucar.edu' <met_help at ucar.edu>
> Cc: SITTEL, MATTHEW C CTR USAF AFMC AFLCMC/HBAW-OL <
> matthew.sittel.ctr at us.af.mil>
> Subject: RE: [Non-DoD Source] Re: [rt.rap.ucar.edu #80051] NETcdf
Obs
> File
>
> Thanks John. I made the changes and things have progressed to Point
> Stat running but it throws all the observations due to GRIB code.
In
> the NETCDF ob file, I set the ob value to the precip type GRIB 1
code
> defined in the
> /h/WXQC/met-5.2/share/met/table_files/grib1_af_131_57.txt. I
> originally only changed the grib tables in met-5.2/data/table_files
> but found it is looking at the shared version. In the
> grib1_af_131_57.txt file, the columns for text have 1 space instead
> of 2 separating them. Do they have to be two spaces like the grib2
tables? In the grib1_af_131_57.txt I defined CRAIN as:
> 167 131 57 2 "CRAIN" "Categorical Rain" "code" and I have 167 as
the
> ob value in my NETCDF file I am using. An NCDUMP of the file shows
> lots of observations with 167 as the obvalue. So why would I get
all
> the obs rejected for Grib code. The manual doesn't delve into this
> subject with a lot of detail.
>
> I know you guys are busy with the MET 6 roll out.
>
> Thanks for your help.
>
> Bob
>
>
>
> -----Original Message-----
> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> Sent: Tuesday, April 04, 2017 2:17 PM
> To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
> <robert.craig.2 at us.af.mil>
> Cc: SITTEL, MATTHEW C CTR USAF AFMC AFLCMC/HBAW-OL <
> matthew.sittel.ctr at us.af.mil>
> Subject: [Non-DoD Source] Re: [rt.rap.ucar.edu #80051] NETcdf Obs
File
>
> Bob,
>
> I realize that this is a little confusing, but...
>
> When passing to MET a gridded NetCDF file, you set the "name" as the
> variable name which contains the gridded data you want to use.
>
> However, when passing to MET a point observation NetCDF file, the
> logic is different. Each of the observations is currently assigned
a GRIB code.
> That GRIB code is one of the entries in the "obs_arr" variable. In
> Point-Stat and Ensemble-Stat, when setting up the "obs" section for
> point observations, you configure it as if it were GRIB1 data. Then
> the MET tools look for observations that have the GRIB code you
specified.
>
> Looking at your config file, I'm guessing you want to verify using
> observation with GRIB code = 140.
>
> But now, what does 140 mean? Looking in this file:
> grib1_af_131_57.txt
>
> I see the following entry for 140:
>
> 140 131 57 2 "cloudHeightCeiling" "Ceiling" "m"
>
> Is that the correct observation type? If so, I'd suggest trying:
>
> obs = {
>
> message_type = [ "ADPSFC" ];
>
> sid_exc = [];
>
> field = [
>
> {
>
> name = "cloudHeightCeiling";
>
> level = "Z0";
>
> GRIB1_ptv = 131;
>
> cat_thresh = [ >0.0 ];
>
> }
>
> ];
>
> }
>
> Please let me know how that goes.
>
> Thanks,
> John
>
> On Tue, Apr 4, 2017 at 2:14 PM, robert.craig.2 at us.af.mil via RT <
> met_help at ucar.edu> wrote:
>
> >
> > Tue Apr 04 12:14:44 2017: Request 80051 was acted upon.
> > Transaction: Ticket created by robert.craig.2 at us.af.mil
> > Queue: met_help
> > Subject: NETcdf Obs File
> > Owner: Nobody
> > Requestors: robert.craig.2 at us.af.mil
> > Status: new
> > Ticket <URL:
> > https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80051
> > >
> >
> >
> > John, or Julie
> >
> > I am having trouble reading a NETcdf file in point stat.
Attached in my
> > configuration file. I get the following error when I run point
stat:
> >
> > DEBUG 1: Default Config File:
> > /h/WXQC/met-5.2/share/met/config/PointStatConfig_default
> > DEBUG 1: User Config File:
> > /h/WXQC/met-5.2/data/config/PointStatConfig_single_updated
> > DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created
new
> > Met2dDataFile object of type "FileType_Gb2".
> > DEBUG 3: Switching the GRIB2 radius of the earth value of 6371.23
km
> > to
> > 6371.2 km for internal consistency.
> > DEBUG 4:
> > DEBUG 4: Latitude/Longitude Grid Data:
> > DEBUG 4: lat_ll: -89.9219
> > DEBUG 4: lon_ll: -0.117187
> > DEBUG 4: delta_lat: 0.15625
> > DEBUG 4: delta_lon: 0.234375
> > DEBUG 4: Nlat: 1152
> > DEBUG 4: Nlon: 1536
> > DEBUG 4:
> > DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
> > object of type "FileType_Gb2".
> > DEBUG 4: parse_conf_sid_exc() -> Station ID exclusion list
contains
> > 0 entries.
> > ERROR :
> > ERROR : VarInfo::set_level_info_grib() - failed to parse level
> > string '(3,5)'
> >
> > I am not sure what I should have in the level field in this case.
> Looking
> > in the NETcdf header, I see there are several dimensions listed :
> >
> > dimensions:
> > mxstr = 40 ;
> > hdr_arr_len = 3 ;
> > obs_arr_len = 5 ;
> > nhdr = 7345 ;
> > nobs = UNLIMITED ; // (7345 currently)
> >
> > Which ones should I be using?
> >
> > The NETcdf file I am reading in on the FTP server.
> >
> > Thanks
> > Bob Craig
> >
> >
>
>
>
>
------------------------------------------------
Subject: NETcdf Obs File
From: John Halley Gotway
Time: Wed Apr 05 09:49:06 2017
Bob,
Thanks for the feedback. I'm still a little confused though.
Is it true that you're able to get Point-Stat to do what you want it
do to
using the "name", "GRIB1_center", and "GRIB1_subcenter" options...
without
having to mess with the contents of the GRIB table directories?
John
On Wed, Apr 5, 2017 at 11:43 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=80051 >
>
> Success - I add the GRIB1_center=57 but got the error that it
couldn't
> find CRAIN in any table. I had also moved all ncep tables that
defined
> CRAIN out of both the table_files directory so only the af table
with CRAIN
> remained. So I then added GRIB1_subcenter=2 to my config file and
that got
> it to work.
>
> Thanks
>
>
>
> -----Original Message-----
> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> Sent: Wednesday, April 05, 2017 10:20 AM
> To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
<robert.craig.2 at us.af.mil>
> Cc: SITTEL, MATTHEW C CTR USAF AFMC AFLCMC/HBAW-OL <
> matthew.sittel.ctr at us.af.mil>
> Subject: Re: FW: [Non-DoD Source] Re: [rt.rap.ucar.edu #80051]
NETcdf Obs
> File
>
> Bob,
>
> I see that we've failed to include this in the documentation, but
you
> should be able to define the GRIB1_center and GRIB1_subcenter
configuration
> options. For example hopefully adding:
>
> GRIB1_center = 57;
>
> Will tell MET which table to use.
>
> Please let me know how it goes.
>
> Thanks and sorry for the omission in the documentation. We'll
update that.
>
> John
>
> On Wed, Apr 5, 2017 at 11:10 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=80051 >
> >
> > John, I figured out that even though I had updated the grib1 file
> > grib1_af_131_57.txt, MET is using the CRAIN code of 140 found in
the
> > ncep tables in the table_files directory. I placed the
> grib1_af_131_57.txt in
> > the directory the USER_GRIB_TABLES points to (Met-5.2). In my
config
> file
> > I added GRIB1_ptv=131 but I see there is an NCEP table with the
same
> > number. What decides which table MET uses? I will rename the
> > grib1_ncep_131_7.txt table to something else so hopefully MET
can't find
> it.
> >
> > Bob
> >
> > -----Original Message-----
> > From: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
> > Sent: Wednesday, April 05, 2017 9:04 AM
> > To: 'met_help at ucar.edu' <met_help at ucar.edu>
> > Cc: SITTEL, MATTHEW C CTR USAF AFMC AFLCMC/HBAW-OL <
> > matthew.sittel.ctr at us.af.mil>
> > Subject: RE: [Non-DoD Source] Re: [rt.rap.ucar.edu #80051] NETcdf
Obs
> > File
> >
> > Thanks John. I made the changes and things have progressed to
Point
> > Stat running but it throws all the observations due to GRIB code.
In
> > the NETCDF ob file, I set the ob value to the precip type GRIB 1
code
> > defined in the
> > /h/WXQC/met-5.2/share/met/table_files/grib1_af_131_57.txt. I
> > originally only changed the grib tables in met-
5.2/data/table_files
> > but found it is looking at the shared version. In the
> > grib1_af_131_57.txt file, the columns for text have 1 space
instead
> > of 2 separating them. Do they have to be two spaces like the
grib2
> tables? In the grib1_af_131_57.txt I defined CRAIN as:
> > 167 131 57 2 "CRAIN" "Categorical Rain" "code" and I have 167 as
the
> > ob value in my NETCDF file I am using. An NCDUMP of the file
shows
> > lots of observations with 167 as the obvalue. So why would I get
all
> > the obs rejected for Grib code. The manual doesn't delve into
this
> > subject with a lot of detail.
> >
> > I know you guys are busy with the MET 6 roll out.
> >
> > Thanks for your help.
> >
> > Bob
> >
> >
> >
> > -----Original Message-----
> > From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> > Sent: Tuesday, April 04, 2017 2:17 PM
> > To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
> > <robert.craig.2 at us.af.mil>
> > Cc: SITTEL, MATTHEW C CTR USAF AFMC AFLCMC/HBAW-OL <
> > matthew.sittel.ctr at us.af.mil>
> > Subject: [Non-DoD Source] Re: [rt.rap.ucar.edu #80051] NETcdf Obs
File
> >
> > Bob,
> >
> > I realize that this is a little confusing, but...
> >
> > When passing to MET a gridded NetCDF file, you set the "name" as
the
> > variable name which contains the gridded data you want to use.
> >
> > However, when passing to MET a point observation NetCDF file, the
> > logic is different. Each of the observations is currently
assigned a
> GRIB code.
> > That GRIB code is one of the entries in the "obs_arr" variable.
In
> > Point-Stat and Ensemble-Stat, when setting up the "obs" section
for
> > point observations, you configure it as if it were GRIB1 data.
Then
> > the MET tools look for observations that have the GRIB code you
> specified.
> >
> > Looking at your config file, I'm guessing you want to verify using
> > observation with GRIB code = 140.
> >
> > But now, what does 140 mean? Looking in this file:
> > grib1_af_131_57.txt
> >
> > I see the following entry for 140:
> >
> > 140 131 57 2 "cloudHeightCeiling" "Ceiling" "m"
> >
> > Is that the correct observation type? If so, I'd suggest trying:
> >
> > obs = {
> >
> > message_type = [ "ADPSFC" ];
> >
> > sid_exc = [];
> >
> > field = [
> >
> > {
> >
> > name = "cloudHeightCeiling";
> >
> > level = "Z0";
> >
> > GRIB1_ptv = 131;
> >
> > cat_thresh = [ >0.0 ];
> >
> > }
> >
> > ];
> >
> > }
> >
> > Please let me know how that goes.
> >
> > Thanks,
> > John
> >
> > On Tue, Apr 4, 2017 at 2:14 PM, robert.craig.2 at us.af.mil via RT <
> > met_help at ucar.edu> wrote:
> >
> > >
> > > Tue Apr 04 12:14:44 2017: Request 80051 was acted upon.
> > > Transaction: Ticket created by robert.craig.2 at us.af.mil
> > > Queue: met_help
> > > Subject: NETcdf Obs File
> > > Owner: Nobody
> > > Requestors: robert.craig.2 at us.af.mil
> > > Status: new
> > > Ticket <URL:
> > > https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80051
> > > >
> > >
> > >
> > > John, or Julie
> > >
> > > I am having trouble reading a NETcdf file in point stat.
Attached in
> my
> > > configuration file. I get the following error when I run point
stat:
> > >
> > > DEBUG 1: Default Config File:
> > > /h/WXQC/met-5.2/share/met/config/PointStatConfig_default
> > > DEBUG 1: User Config File:
> > > /h/WXQC/met-5.2/data/config/PointStatConfig_single_updated
> > > DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created
new
> > > Met2dDataFile object of type "FileType_Gb2".
> > > DEBUG 3: Switching the GRIB2 radius of the earth value of
6371.23 km
> > > to
> > > 6371.2 km for internal consistency.
> > > DEBUG 4:
> > > DEBUG 4: Latitude/Longitude Grid Data:
> > > DEBUG 4: lat_ll: -89.9219
> > > DEBUG 4: lon_ll: -0.117187
> > > DEBUG 4: delta_lat: 0.15625
> > > DEBUG 4: delta_lon: 0.234375
> > > DEBUG 4: Nlat: 1152
> > > DEBUG 4: Nlon: 1536
> > > DEBUG 4:
> > > DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
> > > object of type "FileType_Gb2".
> > > DEBUG 4: parse_conf_sid_exc() -> Station ID exclusion list
contains
> > > 0 entries.
> > > ERROR :
> > > ERROR : VarInfo::set_level_info_grib() - failed to parse level
> > > string '(3,5)'
> > >
> > > I am not sure what I should have in the level field in this
case.
> > Looking
> > > in the NETcdf header, I see there are several dimensions listed
:
> > >
> > > dimensions:
> > > mxstr = 40 ;
> > > hdr_arr_len = 3 ;
> > > obs_arr_len = 5 ;
> > > nhdr = 7345 ;
> > > nobs = UNLIMITED ; // (7345 currently)
> > >
> > > Which ones should I be using?
> > >
> > > The NETcdf file I am reading in on the FTP server.
> > >
> > > Thanks
> > > Bob Craig
> > >
> > >
> >
> >
> >
> >
>
>
>
>
------------------------------------------------
Subject: RE: FW: [Non-DoD Source] Re: [rt.rap.ucar.edu #80051] NETcdf Obs File
From: robert.craig.2 at us.af.mil
Time: Wed Apr 05 10:04:04 2017
Until I added the GRIB1_subcenter code, MET was pulling CRAIN from
NCEP tables. Even though I had the grib1_af_131_57.txt in both
directories and the directory the ENV variable was pointing to, when I
removed the grib1 ncep tables that defined CRAIN from both table_files
directory, MET said it could not find CRAIN defined in any grib table.
When I added GRIB1_subcenter code then it found the correct CRAIN
definition. It seemed to me that without subcenter number defined,
MET was only looking in the NCEP tables for CRAIN.
Bob
-----Original Message-----
From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
Sent: Wednesday, April 05, 2017 10:49 AM
To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
<robert.craig.2 at us.af.mil>
Cc: SITTEL, MATTHEW C CTR USAF AFMC AFLCMC/HBAW-OL
<matthew.sittel.ctr at us.af.mil>
Subject: Re: FW: [Non-DoD Source] Re: [rt.rap.ucar.edu #80051] NETcdf
Obs File
Bob,
Thanks for the feedback. I'm still a little confused though.
Is it true that you're able to get Point-Stat to do what you want it
do to using the "name", "GRIB1_center", and "GRIB1_subcenter"
options... without having to mess with the contents of the GRIB table
directories?
John
On Wed, Apr 5, 2017 at 11:43 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=80051 >
>
> Success - I add the GRIB1_center=57 but got the error that it
> couldn't find CRAIN in any table. I had also moved all ncep tables
> that defined CRAIN out of both the table_files directory so only the
> af table with CRAIN remained. So I then added GRIB1_subcenter=2 to
my
> config file and that got it to work.
>
> Thanks
>
>
>
> -----Original Message-----
> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> Sent: Wednesday, April 05, 2017 10:20 AM
> To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
> <robert.craig.2 at us.af.mil>
> Cc: SITTEL, MATTHEW C CTR USAF AFMC AFLCMC/HBAW-OL <
> matthew.sittel.ctr at us.af.mil>
> Subject: Re: FW: [Non-DoD Source] Re: [rt.rap.ucar.edu #80051]
NETcdf
> Obs File
>
> Bob,
>
> I see that we've failed to include this in the documentation, but
you
> should be able to define the GRIB1_center and GRIB1_subcenter
> configuration options. For example hopefully adding:
>
> GRIB1_center = 57;
>
> Will tell MET which table to use.
>
> Please let me know how it goes.
>
> Thanks and sorry for the omission in the documentation. We'll
update that.
>
> John
>
> On Wed, Apr 5, 2017 at 11:10 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=80051 >
> >
> > John, I figured out that even though I had updated the grib1 file
> > grib1_af_131_57.txt, MET is using the CRAIN code of 140 found in
the
> > ncep tables in the table_files directory. I placed the
> grib1_af_131_57.txt in
> > the directory the USER_GRIB_TABLES points to (Met-5.2). In my
config
> file
> > I added GRIB1_ptv=131 but I see there is an NCEP table with the
same
> > number. What decides which table MET uses? I will rename the
> > grib1_ncep_131_7.txt table to something else so hopefully MET
can't
> > find
> it.
> >
> > Bob
> >
> > -----Original Message-----
> > From: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
> > Sent: Wednesday, April 05, 2017 9:04 AM
> > To: 'met_help at ucar.edu' <met_help at ucar.edu>
> > Cc: SITTEL, MATTHEW C CTR USAF AFMC AFLCMC/HBAW-OL <
> > matthew.sittel.ctr at us.af.mil>
> > Subject: RE: [Non-DoD Source] Re: [rt.rap.ucar.edu #80051] NETcdf
> > Obs File
> >
> > Thanks John. I made the changes and things have progressed to
Point
> > Stat running but it throws all the observations due to GRIB code.
> > In the NETCDF ob file, I set the ob value to the precip type GRIB
1
> > code defined in the
> > /h/WXQC/met-5.2/share/met/table_files/grib1_af_131_57.txt. I
> > originally only changed the grib tables in met-
5.2/data/table_files
> > but found it is looking at the shared version. In the
> > grib1_af_131_57.txt file, the columns for text have 1 space
instead
> > of 2 separating them. Do they have to be two spaces like the
grib2
> tables? In the grib1_af_131_57.txt I defined CRAIN as:
> > 167 131 57 2 "CRAIN" "Categorical Rain" "code" and I have 167 as
> > the ob value in my NETCDF file I am using. An NCDUMP of the file
> > shows lots of observations with 167 as the obvalue. So why would
I
> > get all the obs rejected for Grib code. The manual doesn't delve
> > into this subject with a lot of detail.
> >
> > I know you guys are busy with the MET 6 roll out.
> >
> > Thanks for your help.
> >
> > Bob
> >
> >
> >
> > -----Original Message-----
> > From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> > Sent: Tuesday, April 04, 2017 2:17 PM
> > To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
> > <robert.craig.2 at us.af.mil>
> > Cc: SITTEL, MATTHEW C CTR USAF AFMC AFLCMC/HBAW-OL <
> > matthew.sittel.ctr at us.af.mil>
> > Subject: [Non-DoD Source] Re: [rt.rap.ucar.edu #80051] NETcdf Obs
> > File
> >
> > Bob,
> >
> > I realize that this is a little confusing, but...
> >
> > When passing to MET a gridded NetCDF file, you set the "name" as
the
> > variable name which contains the gridded data you want to use.
> >
> > However, when passing to MET a point observation NetCDF file, the
> > logic is different. Each of the observations is currently
assigned
> > a
> GRIB code.
> > That GRIB code is one of the entries in the "obs_arr" variable.
In
> > Point-Stat and Ensemble-Stat, when setting up the "obs" section
for
> > point observations, you configure it as if it were GRIB1 data.
Then
> > the MET tools look for observations that have the GRIB code you
> specified.
> >
> > Looking at your config file, I'm guessing you want to verify using
> > observation with GRIB code = 140.
> >
> > But now, what does 140 mean? Looking in this file:
> > grib1_af_131_57.txt
> >
> > I see the following entry for 140:
> >
> > 140 131 57 2 "cloudHeightCeiling" "Ceiling" "m"
> >
> > Is that the correct observation type? If so, I'd suggest trying:
> >
> > obs = {
> >
> > message_type = [ "ADPSFC" ];
> >
> > sid_exc = [];
> >
> > field = [
> >
> > {
> >
> > name = "cloudHeightCeiling";
> >
> > level = "Z0";
> >
> > GRIB1_ptv = 131;
> >
> > cat_thresh = [ >0.0 ];
> >
> > }
> >
> > ];
> >
> > }
> >
> > Please let me know how that goes.
> >
> > Thanks,
> > John
> >
> > On Tue, Apr 4, 2017 at 2:14 PM, robert.craig.2 at us.af.mil via RT <
> > met_help at ucar.edu> wrote:
> >
> > >
> > > Tue Apr 04 12:14:44 2017: Request 80051 was acted upon.
> > > Transaction: Ticket created by robert.craig.2 at us.af.mil
> > > Queue: met_help
> > > Subject: NETcdf Obs File
> > > Owner: Nobody
> > > Requestors: robert.craig.2 at us.af.mil
> > > Status: new
> > > Ticket <URL:
> > > https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80051
> > > >
> > >
> > >
> > > John, or Julie
> > >
> > > I am having trouble reading a NETcdf file in point stat.
Attached in
> my
> > > configuration file. I get the following error when I run point
stat:
> > >
> > > DEBUG 1: Default Config File:
> > > /h/WXQC/met-5.2/share/met/config/PointStatConfig_default
> > > DEBUG 1: User Config File:
> > > /h/WXQC/met-5.2/data/config/PointStatConfig_single_updated
> > > DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created
> > > new Met2dDataFile object of type "FileType_Gb2".
> > > DEBUG 3: Switching the GRIB2 radius of the earth value of
6371.23
> > > km to
> > > 6371.2 km for internal consistency.
> > > DEBUG 4:
> > > DEBUG 4: Latitude/Longitude Grid Data:
> > > DEBUG 4: lat_ll: -89.9219
> > > DEBUG 4: lon_ll: -0.117187
> > > DEBUG 4: delta_lat: 0.15625
> > > DEBUG 4: delta_lon: 0.234375
> > > DEBUG 4: Nlat: 1152
> > > DEBUG 4: Nlon: 1536
> > > DEBUG 4:
> > > DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
> > > object of type "FileType_Gb2".
> > > DEBUG 4: parse_conf_sid_exc() -> Station ID exclusion list
> > > contains
> > > 0 entries.
> > > ERROR :
> > > ERROR : VarInfo::set_level_info_grib() - failed to parse level
> > > string '(3,5)'
> > >
> > > I am not sure what I should have in the level field in this
case.
> > Looking
> > > in the NETcdf header, I see there are several dimensions listed
:
> > >
> > > dimensions:
> > > mxstr = 40 ;
> > > hdr_arr_len = 3 ;
> > > obs_arr_len = 5 ;
> > > nhdr = 7345 ;
> > > nobs = UNLIMITED ; // (7345 currently)
> > >
> > > Which ones should I be using?
> > >
> > > The NETcdf file I am reading in on the FTP server.
> > >
> > > Thanks
> > > Bob Craig
> > >
> > >
> >
> >
> >
> >
>
>
>
>
------------------------------------------------
Subject: NETcdf Obs File
From: robert.craig.2 at us.af.mil
Time: Wed Apr 05 17:25:15 2017
Well I solved my data problem and still can't get all 4 parts of the
contingency table to have values. What cat_thresh should I be using
for the
fcst and ob for category rain (1 occurred, 0 didn't occur)
Thanks
Bob
-----Original Message-----
From: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
Sent: Wednesday, April 05, 2017 4:38 PM
To: 'met_help at ucar.edu' <met_help at ucar.edu>
Subject: FW: FW: [Non-DoD Source] Re: [rt.rap.ucar.edu #80051] NETcdf
Obs File
John, Never mind, I see a problem with my data.
Bob
-----Original Message-----
From: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
Sent: Wednesday, April 05, 2017 3:39 PM
To: 'met_help at ucar.edu' <met_help at ucar.edu>
Cc: MELICK, CHRISTOPHER J GS-12 USAF ACC 16 WS/WXES
<christopher.melick at us.af.mil>
Subject: RE: FW: [Non-DoD Source] Re: [rt.rap.ucar.edu #80051] NETcdf
Obs File
John, hopefully one last question concerning my verification of CRAIN
(category of rain). In the Netcdf ob file, generated from an ascii
file I am
putting the grib code for CRAIN in the gribcode slot and the ob value
of 1 or
0 in the obval slot. The model data is either a 1 or 0. After
running point
stat and looking at the contingency table, all the counts are in the
FY-OY
column with the other columns being 0. However, looking in the MPR
file, the
fcsts are either 1 or 0 and the obs are either 1 or 0. So I should
have
values for all the boxes in the contingency table but MET thinks all
the pairs
fall into just the FY-OY box. Attached is my configuration file. Is
there a
flag I need to tell MET I am dealing with categorical forecasts and
obs
instead of continuous variables? I have tried >=0 and >0 in the obs
cat_thresh field with the same result in either case.
Thanks
Bob
-----Original Message-----
From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
Sent: Wednesday, April 05, 2017 10:49 AM
To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
<robert.craig.2 at us.af.mil>
Cc: SITTEL, MATTHEW C CTR USAF AFMC AFLCMC/HBAW-OL
<matthew.sittel.ctr at us.af.mil>
Subject: Re: FW: [Non-DoD Source] Re: [rt.rap.ucar.edu #80051] NETcdf
Obs File
Bob,
Thanks for the feedback. I'm still a little confused though.
Is it true that you're able to get Point-Stat to do what you want it
do to
using the "name", "GRIB1_center", and "GRIB1_subcenter" options...
without
having to mess with the contents of the GRIB table directories?
John
On Wed, Apr 5, 2017 at 11:43 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=80051 >
>
> Success - I add the GRIB1_center=57 but got the error that it
> couldn't find CRAIN in any table. I had also moved all ncep tables
> that defined CRAIN out of both the table_files directory so only the
> af table with CRAIN remained. So I then added GRIB1_subcenter=2 to
my
> config file and that got it to work.
>
> Thanks
>
>
>
> -----Original Message-----
> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> Sent: Wednesday, April 05, 2017 10:20 AM
> To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
> <robert.craig.2 at us.af.mil>
> Cc: SITTEL, MATTHEW C CTR USAF AFMC AFLCMC/HBAW-OL <
> matthew.sittel.ctr at us.af.mil>
> Subject: Re: FW: [Non-DoD Source] Re: [rt.rap.ucar.edu #80051]
NETcdf
> Obs File
>
> Bob,
>
> I see that we've failed to include this in the documentation, but
you
> should be able to define the GRIB1_center and GRIB1_subcenter
> configuration options. For example hopefully adding:
>
> GRIB1_center = 57;
>
> Will tell MET which table to use.
>
> Please let me know how it goes.
>
> Thanks and sorry for the omission in the documentation. We'll
update that.
>
> John
>
> On Wed, Apr 5, 2017 at 11:10 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=80051 >
> >
> > John, I figured out that even though I had updated the grib1 file
> > grib1_af_131_57.txt, MET is using the CRAIN code of 140 found in
the
> > ncep tables in the table_files directory. I placed the
> grib1_af_131_57.txt in
> > the directory the USER_GRIB_TABLES points to (Met-5.2). In my
config
> file
> > I added GRIB1_ptv=131 but I see there is an NCEP table with the
same
> > number. What decides which table MET uses? I will rename the
> > grib1_ncep_131_7.txt table to something else so hopefully MET
can't
> > find
> it.
> >
> > Bob
> >
> > -----Original Message-----
> > From: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
> > Sent: Wednesday, April 05, 2017 9:04 AM
> > To: 'met_help at ucar.edu' <met_help at ucar.edu>
> > Cc: SITTEL, MATTHEW C CTR USAF AFMC AFLCMC/HBAW-OL <
> > matthew.sittel.ctr at us.af.mil>
> > Subject: RE: [Non-DoD Source] Re: [rt.rap.ucar.edu #80051] NETcdf
> > Obs File
> >
> > Thanks John. I made the changes and things have progressed to
Point
> > Stat running but it throws all the observations due to GRIB code.
> > In the NETCDF ob file, I set the ob value to the precip type GRIB
1
> > code defined in the
> > /h/WXQC/met-5.2/share/met/table_files/grib1_af_131_57.txt. I
> > originally only changed the grib tables in met-
5.2/data/table_files
> > but found it is looking at the shared version. In the
> > grib1_af_131_57.txt file, the columns for text have 1 space
instead
> > of 2 separating them. Do they have to be two spaces like the
grib2
> tables? In the grib1_af_131_57.txt I defined CRAIN as:
> > 167 131 57 2 "CRAIN" "Categorical Rain" "code" and I have 167 as
> > the ob value in my NETCDF file I am using. An NCDUMP of the file
> > shows lots of observations with 167 as the obvalue. So why would
I
> > get all the obs rejected for Grib code. The manual doesn't delve
> > into this subject with a lot of detail.
> >
> > I know you guys are busy with the MET 6 roll out.
> >
> > Thanks for your help.
> >
> > Bob
> >
> >
> >
> > -----Original Message-----
> > From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> > Sent: Tuesday, April 04, 2017 2:17 PM
> > To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
> > <robert.craig.2 at us.af.mil>
> > Cc: SITTEL, MATTHEW C CTR USAF AFMC AFLCMC/HBAW-OL <
> > matthew.sittel.ctr at us.af.mil>
> > Subject: [Non-DoD Source] Re: [rt.rap.ucar.edu #80051] NETcdf Obs
> > File
> >
> > Bob,
> >
> > I realize that this is a little confusing, but...
> >
> > When passing to MET a gridded NetCDF file, you set the "name" as
the
> > variable name which contains the gridded data you want to use.
> >
> > However, when passing to MET a point observation NetCDF file, the
> > logic is different. Each of the observations is currently
assigned
> > a
> GRIB code.
> > That GRIB code is one of the entries in the "obs_arr" variable.
In
> > Point-Stat and Ensemble-Stat, when setting up the "obs" section
for
> > point observations, you configure it as if it were GRIB1 data.
Then
> > the MET tools look for observations that have the GRIB code you
> specified.
> >
> > Looking at your config file, I'm guessing you want to verify using
> > observation with GRIB code = 140.
> >
> > But now, what does 140 mean? Looking in this file:
> > grib1_af_131_57.txt
> >
> > I see the following entry for 140:
> >
> > 140 131 57 2 "cloudHeightCeiling" "Ceiling" "m"
> >
> > Is that the correct observation type? If so, I'd suggest trying:
> >
> > obs = {
> >
> > message_type = [ "ADPSFC" ];
> >
> > sid_exc = [];
> >
> > field = [
> >
> > {
> >
> > name = "cloudHeightCeiling";
> >
> > level = "Z0";
> >
> > GRIB1_ptv = 131;
> >
> > cat_thresh = [ >0.0 ];
> >
> > }
> >
> > ];
> >
> > }
> >
> > Please let me know how that goes.
> >
> > Thanks,
> > John
> >
> > On Tue, Apr 4, 2017 at 2:14 PM, robert.craig.2 at us.af.mil via RT <
> > met_help at ucar.edu> wrote:
> >
> > >
> > > Tue Apr 04 12:14:44 2017: Request 80051 was acted upon.
> > > Transaction: Ticket created by robert.craig.2 at us.af.mil
> > > Queue: met_help
> > > Subject: NETcdf Obs File
> > > Owner: Nobody
> > > Requestors: robert.craig.2 at us.af.mil
> > > Status: new
> > > Ticket <URL:
> > > https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80051
> > > >
> > >
> > >
> > > John, or Julie
> > >
> > > I am having trouble reading a NETcdf file in point stat.
Attached in
> my
> > > configuration file. I get the following error when I run point
stat:
> > >
> > > DEBUG 1: Default Config File:
> > > /h/WXQC/met-5.2/share/met/config/PointStatConfig_default
> > > DEBUG 1: User Config File:
> > > /h/WXQC/met-5.2/data/config/PointStatConfig_single_updated
> > > DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created
> > > new Met2dDataFile object of type "FileType_Gb2".
> > > DEBUG 3: Switching the GRIB2 radius of the earth value of
6371.23
> > > km to
> > > 6371.2 km for internal consistency.
> > > DEBUG 4:
> > > DEBUG 4: Latitude/Longitude Grid Data:
> > > DEBUG 4: lat_ll: -89.9219
> > > DEBUG 4: lon_ll: -0.117187
> > > DEBUG 4: delta_lat: 0.15625
> > > DEBUG 4: delta_lon: 0.234375
> > > DEBUG 4: Nlat: 1152
> > > DEBUG 4: Nlon: 1536
> > > DEBUG 4:
> > > DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
> > > object of type "FileType_Gb2".
> > > DEBUG 4: parse_conf_sid_exc() -> Station ID exclusion list
> > > contains
> > > 0 entries.
> > > ERROR :
> > > ERROR : VarInfo::set_level_info_grib() - failed to parse level
> > > string '(3,5)'
> > >
> > > I am not sure what I should have in the level field in this
case.
> > Looking
> > > in the NETcdf header, I see there are several dimensions listed
:
> > >
> > > dimensions:
> > > mxstr = 40 ;
> > > hdr_arr_len = 3 ;
> > > obs_arr_len = 5 ;
> > > nhdr = 7345 ;
> > > nobs = UNLIMITED ; // (7345 currently)
> > >
> > > Which ones should I be using?
> > >
> > > The NETcdf file I am reading in on the FTP server.
> > >
> > > Thanks
> > > Bob Craig
> > >
> > >
> >
> >
> >
> >
>
>
>
>
------------------------------------------------
Subject: NETcdf Obs File
From: robert.craig.2 at us.af.mil
Time: Wed Apr 05 17:25:32 2017
John, hopefully one last question concerning my verification of CRAIN
(category of rain). In the Netcdf ob file, generated from an ascii
file I am
putting the grib code for CRAIN in the gribcode slot and the ob value
of 1 or
0 in the obval slot. The model data is either a 1 or 0. After
running point
stat and looking at the contingency table, all the counts are in the
FY-OY
column with the other columns being 0. However, looking in the MPR
file, the
fcsts are either 1 or 0 and the obs are either 1 or 0. So I should
have
values for all the boxes in the contingency table but MET thinks all
the pairs
fall into just the FY-OY box. Attached is my configuration file. Is
there a
flag I need to tell MET I am dealing with categorical forecasts and
obs
instead of continuous variables? I have tried >=0 and >0 in the obs
cat_thresh field with the same result in either case.
Thanks
Bob
-----Original Message-----
From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
Sent: Wednesday, April 05, 2017 10:49 AM
To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
<robert.craig.2 at us.af.mil>
Cc: SITTEL, MATTHEW C CTR USAF AFMC AFLCMC/HBAW-OL
<matthew.sittel.ctr at us.af.mil>
Subject: Re: FW: [Non-DoD Source] Re: [rt.rap.ucar.edu #80051] NETcdf
Obs File
Bob,
Thanks for the feedback. I'm still a little confused though.
Is it true that you're able to get Point-Stat to do what you want it
do to
using the "name", "GRIB1_center", and "GRIB1_subcenter" options...
without
having to mess with the contents of the GRIB table directories?
John
On Wed, Apr 5, 2017 at 11:43 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=80051 >
>
> Success - I add the GRIB1_center=57 but got the error that it
> couldn't find CRAIN in any table. I had also moved all ncep tables
> that defined CRAIN out of both the table_files directory so only the
> af table with CRAIN remained. So I then added GRIB1_subcenter=2 to
my
> config file and that got it to work.
>
> Thanks
>
>
>
> -----Original Message-----
> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> Sent: Wednesday, April 05, 2017 10:20 AM
> To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
> <robert.craig.2 at us.af.mil>
> Cc: SITTEL, MATTHEW C CTR USAF AFMC AFLCMC/HBAW-OL <
> matthew.sittel.ctr at us.af.mil>
> Subject: Re: FW: [Non-DoD Source] Re: [rt.rap.ucar.edu #80051]
NETcdf
> Obs File
>
> Bob,
>
> I see that we've failed to include this in the documentation, but
you
> should be able to define the GRIB1_center and GRIB1_subcenter
> configuration options. For example hopefully adding:
>
> GRIB1_center = 57;
>
> Will tell MET which table to use.
>
> Please let me know how it goes.
>
> Thanks and sorry for the omission in the documentation. We'll
update that.
>
> John
>
> On Wed, Apr 5, 2017 at 11:10 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=80051 >
> >
> > John, I figured out that even though I had updated the grib1 file
> > grib1_af_131_57.txt, MET is using the CRAIN code of 140 found in
the
> > ncep tables in the table_files directory. I placed the
> grib1_af_131_57.txt in
> > the directory the USER_GRIB_TABLES points to (Met-5.2). In my
config
> file
> > I added GRIB1_ptv=131 but I see there is an NCEP table with the
same
> > number. What decides which table MET uses? I will rename the
> > grib1_ncep_131_7.txt table to something else so hopefully MET
can't
> > find
> it.
> >
> > Bob
> >
> > -----Original Message-----
> > From: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
> > Sent: Wednesday, April 05, 2017 9:04 AM
> > To: 'met_help at ucar.edu' <met_help at ucar.edu>
> > Cc: SITTEL, MATTHEW C CTR USAF AFMC AFLCMC/HBAW-OL <
> > matthew.sittel.ctr at us.af.mil>
> > Subject: RE: [Non-DoD Source] Re: [rt.rap.ucar.edu #80051] NETcdf
> > Obs File
> >
> > Thanks John. I made the changes and things have progressed to
Point
> > Stat running but it throws all the observations due to GRIB code.
> > In the NETCDF ob file, I set the ob value to the precip type GRIB
1
> > code defined in the
> > /h/WXQC/met-5.2/share/met/table_files/grib1_af_131_57.txt. I
> > originally only changed the grib tables in met-
5.2/data/table_files
> > but found it is looking at the shared version. In the
> > grib1_af_131_57.txt file, the columns for text have 1 space
instead
> > of 2 separating them. Do they have to be two spaces like the
grib2
> tables? In the grib1_af_131_57.txt I defined CRAIN as:
> > 167 131 57 2 "CRAIN" "Categorical Rain" "code" and I have 167 as
> > the ob value in my NETCDF file I am using. An NCDUMP of the file
> > shows lots of observations with 167 as the obvalue. So why would
I
> > get all the obs rejected for Grib code. The manual doesn't delve
> > into this subject with a lot of detail.
> >
> > I know you guys are busy with the MET 6 roll out.
> >
> > Thanks for your help.
> >
> > Bob
> >
> >
> >
> > -----Original Message-----
> > From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> > Sent: Tuesday, April 04, 2017 2:17 PM
> > To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
> > <robert.craig.2 at us.af.mil>
> > Cc: SITTEL, MATTHEW C CTR USAF AFMC AFLCMC/HBAW-OL <
> > matthew.sittel.ctr at us.af.mil>
> > Subject: [Non-DoD Source] Re: [rt.rap.ucar.edu #80051] NETcdf Obs
> > File
> >
> > Bob,
> >
> > I realize that this is a little confusing, but...
> >
> > When passing to MET a gridded NetCDF file, you set the "name" as
the
> > variable name which contains the gridded data you want to use.
> >
> > However, when passing to MET a point observation NetCDF file, the
> > logic is different. Each of the observations is currently
assigned
> > a
> GRIB code.
> > That GRIB code is one of the entries in the "obs_arr" variable.
In
> > Point-Stat and Ensemble-Stat, when setting up the "obs" section
for
> > point observations, you configure it as if it were GRIB1 data.
Then
> > the MET tools look for observations that have the GRIB code you
> specified.
> >
> > Looking at your config file, I'm guessing you want to verify using
> > observation with GRIB code = 140.
> >
> > But now, what does 140 mean? Looking in this file:
> > grib1_af_131_57.txt
> >
> > I see the following entry for 140:
> >
> > 140 131 57 2 "cloudHeightCeiling" "Ceiling" "m"
> >
> > Is that the correct observation type? If so, I'd suggest trying:
> >
> > obs = {
> >
> > message_type = [ "ADPSFC" ];
> >
> > sid_exc = [];
> >
> > field = [
> >
> > {
> >
> > name = "cloudHeightCeiling";
> >
> > level = "Z0";
> >
> > GRIB1_ptv = 131;
> >
> > cat_thresh = [ >0.0 ];
> >
> > }
> >
> > ];
> >
> > }
> >
> > Please let me know how that goes.
> >
> > Thanks,
> > John
> >
> > On Tue, Apr 4, 2017 at 2:14 PM, robert.craig.2 at us.af.mil via RT <
> > met_help at ucar.edu> wrote:
> >
> > >
> > > Tue Apr 04 12:14:44 2017: Request 80051 was acted upon.
> > > Transaction: Ticket created by robert.craig.2 at us.af.mil
> > > Queue: met_help
> > > Subject: NETcdf Obs File
> > > Owner: Nobody
> > > Requestors: robert.craig.2 at us.af.mil
> > > Status: new
> > > Ticket <URL:
> > > https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80051
> > > >
> > >
> > >
> > > John, or Julie
> > >
> > > I am having trouble reading a NETcdf file in point stat.
Attached in
> my
> > > configuration file. I get the following error when I run point
stat:
> > >
> > > DEBUG 1: Default Config File:
> > > /h/WXQC/met-5.2/share/met/config/PointStatConfig_default
> > > DEBUG 1: User Config File:
> > > /h/WXQC/met-5.2/data/config/PointStatConfig_single_updated
> > > DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created
> > > new Met2dDataFile object of type "FileType_Gb2".
> > > DEBUG 3: Switching the GRIB2 radius of the earth value of
6371.23
> > > km to
> > > 6371.2 km for internal consistency.
> > > DEBUG 4:
> > > DEBUG 4: Latitude/Longitude Grid Data:
> > > DEBUG 4: lat_ll: -89.9219
> > > DEBUG 4: lon_ll: -0.117187
> > > DEBUG 4: delta_lat: 0.15625
> > > DEBUG 4: delta_lon: 0.234375
> > > DEBUG 4: Nlat: 1152
> > > DEBUG 4: Nlon: 1536
> > > DEBUG 4:
> > > DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
> > > object of type "FileType_Gb2".
> > > DEBUG 4: parse_conf_sid_exc() -> Station ID exclusion list
> > > contains
> > > 0 entries.
> > > ERROR :
> > > ERROR : VarInfo::set_level_info_grib() - failed to parse level
> > > string '(3,5)'
> > >
> > > I am not sure what I should have in the level field in this
case.
> > Looking
> > > in the NETcdf header, I see there are several dimensions listed
:
> > >
> > > dimensions:
> > > mxstr = 40 ;
> > > hdr_arr_len = 3 ;
> > > obs_arr_len = 5 ;
> > > nhdr = 7345 ;
> > > nobs = UNLIMITED ; // (7345 currently)
> > >
> > > Which ones should I be using?
> > >
> > > The NETcdf file I am reading in on the FTP server.
> > >
> > > Thanks
> > > Bob Craig
> > >
> > >
> >
> >
> >
> >
>
>
>
>
------------------------------------------------
Subject: NETcdf Obs File
From: robert.craig.2 at us.af.mil
Time: Wed Apr 05 17:36:14 2017
John, Never mind, I see a problem with my data.
Bob
-----Original Message-----
From: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
Sent: Wednesday, April 05, 2017 3:39 PM
To: 'met_help at ucar.edu' <met_help at ucar.edu>
Cc: MELICK, CHRISTOPHER J GS-12 USAF ACC 16 WS/WXES
<christopher.melick at us.af.mil>
Subject: RE: FW: [Non-DoD Source] Re: [rt.rap.ucar.edu #80051] NETcdf
Obs File
John, hopefully one last question concerning my verification of CRAIN
(category of rain). In the Netcdf ob file, generated from an ascii
file I am
putting the grib code for CRAIN in the gribcode slot and the ob value
of 1 or
0 in the obval slot. The model data is either a 1 or 0. After
running point
stat and looking at the contingency table, all the counts are in the
FY-OY
column with the other columns being 0. However, looking in the MPR
file, the
fcsts are either 1 or 0 and the obs are either 1 or 0. So I should
have
values for all the boxes in the contingency table but MET thinks all
the pairs
fall into just the FY-OY box. Attached is my configuration file. Is
there a
flag I need to tell MET I am dealing with categorical forecasts and
obs
instead of continuous variables? I have tried >=0 and >0 in the obs
cat_thresh field with the same result in either case.
Thanks
Bob
-----Original Message-----
From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
Sent: Wednesday, April 05, 2017 10:49 AM
To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
<robert.craig.2 at us.af.mil>
Cc: SITTEL, MATTHEW C CTR USAF AFMC AFLCMC/HBAW-OL
<matthew.sittel.ctr at us.af.mil>
Subject: Re: FW: [Non-DoD Source] Re: [rt.rap.ucar.edu #80051] NETcdf
Obs File
Bob,
Thanks for the feedback. I'm still a little confused though.
Is it true that you're able to get Point-Stat to do what you want it
do to
using the "name", "GRIB1_center", and "GRIB1_subcenter" options...
without
having to mess with the contents of the GRIB table directories?
John
On Wed, Apr 5, 2017 at 11:43 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=80051 >
>
> Success - I add the GRIB1_center=57 but got the error that it
> couldn't find CRAIN in any table. I had also moved all ncep tables
> that defined CRAIN out of both the table_files directory so only the
> af table with CRAIN remained. So I then added GRIB1_subcenter=2 to
my
> config file and that got it to work.
>
> Thanks
>
>
>
> -----Original Message-----
> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> Sent: Wednesday, April 05, 2017 10:20 AM
> To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
> <robert.craig.2 at us.af.mil>
> Cc: SITTEL, MATTHEW C CTR USAF AFMC AFLCMC/HBAW-OL <
> matthew.sittel.ctr at us.af.mil>
> Subject: Re: FW: [Non-DoD Source] Re: [rt.rap.ucar.edu #80051]
NETcdf
> Obs File
>
> Bob,
>
> I see that we've failed to include this in the documentation, but
you
> should be able to define the GRIB1_center and GRIB1_subcenter
> configuration options. For example hopefully adding:
>
> GRIB1_center = 57;
>
> Will tell MET which table to use.
>
> Please let me know how it goes.
>
> Thanks and sorry for the omission in the documentation. We'll
update that.
>
> John
>
> On Wed, Apr 5, 2017 at 11:10 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=80051 >
> >
> > John, I figured out that even though I had updated the grib1 file
> > grib1_af_131_57.txt, MET is using the CRAIN code of 140 found in
the
> > ncep tables in the table_files directory. I placed the
> grib1_af_131_57.txt in
> > the directory the USER_GRIB_TABLES points to (Met-5.2). In my
config
> file
> > I added GRIB1_ptv=131 but I see there is an NCEP table with the
same
> > number. What decides which table MET uses? I will rename the
> > grib1_ncep_131_7.txt table to something else so hopefully MET
can't
> > find
> it.
> >
> > Bob
> >
> > -----Original Message-----
> > From: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
> > Sent: Wednesday, April 05, 2017 9:04 AM
> > To: 'met_help at ucar.edu' <met_help at ucar.edu>
> > Cc: SITTEL, MATTHEW C CTR USAF AFMC AFLCMC/HBAW-OL <
> > matthew.sittel.ctr at us.af.mil>
> > Subject: RE: [Non-DoD Source] Re: [rt.rap.ucar.edu #80051] NETcdf
> > Obs File
> >
> > Thanks John. I made the changes and things have progressed to
Point
> > Stat running but it throws all the observations due to GRIB code.
> > In the NETCDF ob file, I set the ob value to the precip type GRIB
1
> > code defined in the
> > /h/WXQC/met-5.2/share/met/table_files/grib1_af_131_57.txt. I
> > originally only changed the grib tables in met-
5.2/data/table_files
> > but found it is looking at the shared version. In the
> > grib1_af_131_57.txt file, the columns for text have 1 space
instead
> > of 2 separating them. Do they have to be two spaces like the
grib2
> tables? In the grib1_af_131_57.txt I defined CRAIN as:
> > 167 131 57 2 "CRAIN" "Categorical Rain" "code" and I have 167 as
> > the ob value in my NETCDF file I am using. An NCDUMP of the file
> > shows lots of observations with 167 as the obvalue. So why would
I
> > get all the obs rejected for Grib code. The manual doesn't delve
> > into this subject with a lot of detail.
> >
> > I know you guys are busy with the MET 6 roll out.
> >
> > Thanks for your help.
> >
> > Bob
> >
> >
> >
> > -----Original Message-----
> > From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> > Sent: Tuesday, April 04, 2017 2:17 PM
> > To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
> > <robert.craig.2 at us.af.mil>
> > Cc: SITTEL, MATTHEW C CTR USAF AFMC AFLCMC/HBAW-OL <
> > matthew.sittel.ctr at us.af.mil>
> > Subject: [Non-DoD Source] Re: [rt.rap.ucar.edu #80051] NETcdf Obs
> > File
> >
> > Bob,
> >
> > I realize that this is a little confusing, but...
> >
> > When passing to MET a gridded NetCDF file, you set the "name" as
the
> > variable name which contains the gridded data you want to use.
> >
> > However, when passing to MET a point observation NetCDF file, the
> > logic is different. Each of the observations is currently
assigned
> > a
> GRIB code.
> > That GRIB code is one of the entries in the "obs_arr" variable.
In
> > Point-Stat and Ensemble-Stat, when setting up the "obs" section
for
> > point observations, you configure it as if it were GRIB1 data.
Then
> > the MET tools look for observations that have the GRIB code you
> specified.
> >
> > Looking at your config file, I'm guessing you want to verify using
> > observation with GRIB code = 140.
> >
> > But now, what does 140 mean? Looking in this file:
> > grib1_af_131_57.txt
> >
> > I see the following entry for 140:
> >
> > 140 131 57 2 "cloudHeightCeiling" "Ceiling" "m"
> >
> > Is that the correct observation type? If so, I'd suggest trying:
> >
> > obs = {
> >
> > message_type = [ "ADPSFC" ];
> >
> > sid_exc = [];
> >
> > field = [
> >
> > {
> >
> > name = "cloudHeightCeiling";
> >
> > level = "Z0";
> >
> > GRIB1_ptv = 131;
> >
> > cat_thresh = [ >0.0 ];
> >
> > }
> >
> > ];
> >
> > }
> >
> > Please let me know how that goes.
> >
> > Thanks,
> > John
> >
> > On Tue, Apr 4, 2017 at 2:14 PM, robert.craig.2 at us.af.mil via RT <
> > met_help at ucar.edu> wrote:
> >
> > >
> > > Tue Apr 04 12:14:44 2017: Request 80051 was acted upon.
> > > Transaction: Ticket created by robert.craig.2 at us.af.mil
> > > Queue: met_help
> > > Subject: NETcdf Obs File
> > > Owner: Nobody
> > > Requestors: robert.craig.2 at us.af.mil
> > > Status: new
> > > Ticket <URL:
> > > https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80051
> > > >
> > >
> > >
> > > John, or Julie
> > >
> > > I am having trouble reading a NETcdf file in point stat.
Attached in
> my
> > > configuration file. I get the following error when I run point
stat:
> > >
> > > DEBUG 1: Default Config File:
> > > /h/WXQC/met-5.2/share/met/config/PointStatConfig_default
> > > DEBUG 1: User Config File:
> > > /h/WXQC/met-5.2/data/config/PointStatConfig_single_updated
> > > DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created
> > > new Met2dDataFile object of type "FileType_Gb2".
> > > DEBUG 3: Switching the GRIB2 radius of the earth value of
6371.23
> > > km to
> > > 6371.2 km for internal consistency.
> > > DEBUG 4:
> > > DEBUG 4: Latitude/Longitude Grid Data:
> > > DEBUG 4: lat_ll: -89.9219
> > > DEBUG 4: lon_ll: -0.117187
> > > DEBUG 4: delta_lat: 0.15625
> > > DEBUG 4: delta_lon: 0.234375
> > > DEBUG 4: Nlat: 1152
> > > DEBUG 4: Nlon: 1536
> > > DEBUG 4:
> > > DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
> > > object of type "FileType_Gb2".
> > > DEBUG 4: parse_conf_sid_exc() -> Station ID exclusion list
> > > contains
> > > 0 entries.
> > > ERROR :
> > > ERROR : VarInfo::set_level_info_grib() - failed to parse level
> > > string '(3,5)'
> > >
> > > I am not sure what I should have in the level field in this
case.
> > Looking
> > > in the NETcdf header, I see there are several dimensions listed
:
> > >
> > > dimensions:
> > > mxstr = 40 ;
> > > hdr_arr_len = 3 ;
> > > obs_arr_len = 5 ;
> > > nhdr = 7345 ;
> > > nobs = UNLIMITED ; // (7345 currently)
> > >
> > > Which ones should I be using?
> > >
> > > The NETcdf file I am reading in on the FTP server.
> > >
> > > Thanks
> > > Bob Craig
> > >
> > >
> >
> >
> >
> >
>
>
>
>
------------------------------------------------
More information about the Met_help
mailing list