[Met_help] [rt.rap.ucar.edu #83072] History for Point-Stats Error
Howard Soh via RT
met_help at ucar.edu
Thu Nov 30 13:44:56 MST 2017
----------------------------------------------------------------
Initial Request
----------------------------------------------------------------
To whom it may concern,
Hopefully this is a small user error that I am encountering, but I cannot
seem to find matches after running point_Stat.Do you know why the
observations may not be matching? I get no errors when I run ascii2nc and
I clearly define two points with correct stations and lat/lon.
I was wondering if I am possibly having errors since it is polar projection
or grib2 data. Right away I receive an error about unrecognised GRIB2
field indexes. However I don't think this is the main problem since I still
end up with no matching pairs even if I convert it to grib1. The only other
thing I can think of is that I incorrectly defined the QC variable. What
value do you suggest?
I seem to get similar errors when I try prepbufr files, and if I try to
verify with HRRR or URMA files. Thanks!
DEBUG 1: User Config File: nPointStatConfig_default
DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created new
Met2dDataFile object of type "FileType_Gb2".
DEBUG 4: Switching the GRIB2 radius of the earth value of 6371.23 km to
6371.2 km for internal consistency.
DEBUG 4:
DEBUG 4: Stereographic Grid Data:
DEBUG 4: hemisphere: N
DEBUG 4: scale_lat: 60
DEBUG 4: lat_pin: 41.6129
DEBUG 4: lon_pin: 174.883
DEBUG 4: x_pin: 0
DEBUG 4: y_pin: 0
DEBUG 4: lon_orient: 135
DEBUG 4: d_km: 3
DEBUG 4: r_km: 6371.2
DEBUG 4: nx: 1299
DEBUG 4: ny: 919
DEBUG 4:
DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized GRIB2
field indexes - disc: 0, master table: 2, center: 59, local table: 1,
parm_cat: 16, parm: 196
DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized GRIB2
field indexes - disc: 0, master table: 2, center: 59, local table: 1,
parm_cat: 16, parm: 201
DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized GRIB2
field indexes - disc: 0, master table: 2, center: 59, local table: 1,
parm_cat: 16, parm: 195
DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized GRIB2
field indexes - disc: 0, master table: 2, center: 59, local table: 1,
parm_cat: 16, parm: 195
DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized GRIB2
field indexes - disc: 0, master table: 2, center: 59, local table: 1,
parm_cat: 16, parm: 195
ARNING: Multiple GRIB2 table entries match lookup criteria (parm_name =
GUST):
WARNING: parm_name: GUST, index_a = 0, grib2_mtab = 1, grib2_cntr = 0,
grib2_ltab = 0, index_b = 2, index_c = 22
WARNING: parm_name: GUST, index_a = 0, grib2_mtab = 14, grib2_cntr = 57,
grib2_ltab = 0, index_b = 2, index_c = 22
WARNING: Using: parm_name: GUST, index_a = 0, grib2_mtab = 1, grib2_cntr
= 0, grib2_ltab = 0, index_b = 2, index_c = 22
Reading data for TMP/Z2.
DEBUG 3: MetGrib2DataFile::data_plane_array() - Found exact match for
"TMP/Z2" in GRIB2 record 59 field 1 of GRIB2 file "1732021000000.grb2"
DEBUG 4:
DEBUG 4: Data plane information:
DEBUG 4: plane min: 234.527
DEBUG 4: plane max: 286.34
DEBUG 4: scan mode: 64
DEBUG 4: valid time: 20171116_210000
DEBUG 4: lead time: 000000
DEBUG 4: init time: 20171116_210000
DEBUG 4: bitmap flag: 255
DEBUG 4:
DEBUG 2: For TMP/Z2 found 1 forecast levels and 0 climatology levels.
Processing TMP/Z2 versus TMP/Z2, for observation type APDSFC, over region
FULL, for interpolation method NEAREST(1), using 0 pairs.
DEBUG 3: Number of matched pairs = 0
DEBUG 3: Observations processed = 210
DEBUG 3: Rejected: SID exclusion = 0
DEBUG 3: Rejected: GRIB code = 168
DEBUG 3: Rejected: valid time = 42
DEBUG 3: Rejected: bad obs value = 0
DEBUG 3: Rejected: off the grid = 0
DEBUG 3: Rejected: level mismatch = 0
DEBUG 3: Rejected: quality marker = 0
DEBUG 3: Rejected: message type = 0
DEBUG 3: Rejected: masking region = 0
DEBUG 3: Rejected: bad fcst value = 0
DEBUG 3: Rejected: duplicates = 0
DEBUG 2:
Config file:
/
// Verification grid
//
regrid = {
to_grid = NONE;
method = NEAREST;
width = 1;
vld_thresh = 0.5;
}
////////////////////////////////////////////////////////////////////////////////
cat_thresh = [ NA ];
cnt_thresh = [ NA ];
cnt_logic = UNION;
wind_thresh = [ NA ];
wind_logic = UNION;
//
// Forecast and observation fields to be verified
//
// Gust height unclear assumed 10 m like wind
fcst = {
field = [
{
name = "GUST";
level = [ "Z10" ];
cat_thresh = [ >5.0 ];
},
{
name = "DPT";
level = [ "Z2" ];
cat_thresh = [ >-100.0 ];
},
{
name = "TMP";
level = [ "Z2" ];
cat_thresh = [ >-100.0 ];
},
{
name = "WIND";
level = [ "Z10" ];
cat_thresh = [ >0.0 ];
}
obs = fcst;
////////////////////////////////////////////////////////////////////////////////
//
// Point observation filtering options
// May be set separately in each "obs.field" entry
//
message_type = ["APDSFC"];
sid_exc = [];
obs_quality = [];
duplicate_flag = NONE;
obs_summary = NONE;
obs_perc_value = 50;
////////////////////////////////////////////////////////////////////////////////
//
// Climatology mean data
//
climo_mean = {
file_name = [];
field = [];
regrid = {
method = NEAREST;
width = 1;
vld_thresh = 0.5;
}
time_interp_method = DW_MEAN;
match_day = FALSE;
time_step = 21600;
}
////////////////////////////////////////////////////////////////////////////////
//
// Point observation time window
//
obs_window = {
beg = -54000;
end = 54000;
// Verification masking regions
//
mask = {
grid = [ "FULL" ];
poly = [];
sid = [];
}
////////////////////////////////////////////////////////////////////////////////
//
// Confidence interval settings
//
ci_alpha = [ 0.05 ];
boot = {
interval = PCTILE;
rep_prop = 1.0;
n_rep = 0;
rng = "mt19937";
seed = "";
}
----------------------------------------------------------------
Complete Ticket History
----------------------------------------------------------------
Subject: Point-Stats Error
From: John Halley Gotway
Time: Fri Nov 17 19:19:40 2017
Hi Emily,
That’s great that you ran Point-Stat at verbosity level 3 to dump out
the
counts for the reasons why observations weren’t used for each
verification
task.
Looking at those counts I see that 42 weren’t used because of their
valid
time. Mid suggest starting there. Perhaps your observations aren’t
close
enough in time to your forecast valid time?
One way of testing this would be rerunning point_stat using these
command
line options:
-obs_valid_beg 20000101 -obs_valid_end 21000101
That tells point-stat to use all obs between the years 2000 and 2100!
And
that should include all of yours.
Once you get some matches pairs, you can decide how you’d really like
to
set the matching time window for the point obs.
Hope that helps.
Thanks,
John
On Fri, Nov 17, 2017 at 7:00 PM emily niebuhr via RT
<met_help at ucar.edu>
wrote:
>
> Fri Nov 17 19:00:18 2017: Request 83072 was acted upon.
> Transaction: Ticket created by elniebuhr at gmail.com
> Queue: met_help
> Subject: Point-Stats Error
> Owner: Nobody
> Requestors: elniebuhr at gmail.com
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=83072 >
>
>
> To whom it may concern,
>
> Hopefully this is a small user error that I am encountering, but I
cannot
> seem to find matches after running point_Stat.Do you know why the
> observations may not be matching? I get no errors when I run
ascii2nc and
> I clearly define two points with correct stations and lat/lon.
>
>
> I was wondering if I am possibly having errors since it is polar
projection
> or grib2 data. Right away I receive an error about unrecognised
GRIB2
> field indexes. However I don't think this is the main problem since
I still
> end up with no matching pairs even if I convert it to grib1. The
only other
> thing I can think of is that I incorrectly defined the QC variable.
What
> value do you suggest?
>
> I seem to get similar errors when I try prepbufr files, and if I try
to
> verify with HRRR or URMA files. Thanks!
>
>
>
> DEBUG 1: User Config File: nPointStatConfig_default
> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created new
> Met2dDataFile object of type "FileType_Gb2".
> DEBUG 4: Switching the GRIB2 radius of the earth value of 6371.23 km
to
> 6371.2 km for internal consistency.
> DEBUG 4:
> DEBUG 4: Stereographic Grid Data:
> DEBUG 4: hemisphere: N
> DEBUG 4: scale_lat: 60
> DEBUG 4: lat_pin: 41.6129
> DEBUG 4: lon_pin: 174.883
> DEBUG 4: x_pin: 0
> DEBUG 4: y_pin: 0
> DEBUG 4: lon_orient: 135
> DEBUG 4: d_km: 3
> DEBUG 4: r_km: 6371.2
> DEBUG 4: nx: 1299
> DEBUG 4: ny: 919
> DEBUG 4:
> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2
> field indexes - disc: 0, master table: 2, center: 59, local table:
1,
> parm_cat: 16, parm: 196
> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2
> field indexes - disc: 0, master table: 2, center: 59, local table:
1,
> parm_cat: 16, parm: 201
> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2
> field indexes - disc: 0, master table: 2, center: 59, local table:
1,
> parm_cat: 16, parm: 195
> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2
> field indexes - disc: 0, master table: 2, center: 59, local table:
1,
> parm_cat: 16, parm: 195
> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2
> field indexes - disc: 0, master table: 2, center: 59, local table:
1,
> parm_cat: 16, parm: 195
>
>
> ARNING: Multiple GRIB2 table entries match lookup criteria
(parm_name =
> GUST):
> WARNING: parm_name: GUST, index_a = 0, grib2_mtab = 1, grib2_cntr
= 0,
> grib2_ltab = 0, index_b = 2, index_c = 22
> WARNING: parm_name: GUST, index_a = 0, grib2_mtab = 14, grib2_cntr
= 57,
> grib2_ltab = 0, index_b = 2, index_c = 22
> WARNING: Using: parm_name: GUST, index_a = 0, grib2_mtab = 1,
grib2_cntr
> = 0, grib2_ltab = 0, index_b = 2, index_c = 22
>
>
> Reading data for TMP/Z2.
> DEBUG 3: MetGrib2DataFile::data_plane_array() - Found exact match
for
> "TMP/Z2" in GRIB2 record 59 field 1 of GRIB2 file
"1732021000000.grb2"
> DEBUG 4:
> DEBUG 4: Data plane information:
> DEBUG 4: plane min: 234.527
> DEBUG 4: plane max: 286.34
> DEBUG 4: scan mode: 64
> DEBUG 4: valid time: 20171116_210000
> DEBUG 4: lead time: 000000
> DEBUG 4: init time: 20171116_210000
> DEBUG 4: bitmap flag: 255
> DEBUG 4:
> DEBUG 2: For TMP/Z2 found 1 forecast levels and 0 climatology
levels.
>
>
>
> Processing TMP/Z2 versus TMP/Z2, for observation type APDSFC, over
region
> FULL, for interpolation method NEAREST(1), using 0 pairs.
> DEBUG 3: Number of matched pairs = 0
> DEBUG 3: Observations processed = 210
> DEBUG 3: Rejected: SID exclusion = 0
> DEBUG 3: Rejected: GRIB code = 168
> DEBUG 3: Rejected: valid time = 42
> DEBUG 3: Rejected: bad obs value = 0
> DEBUG 3: Rejected: off the grid = 0
> DEBUG 3: Rejected: level mismatch = 0
> DEBUG 3: Rejected: quality marker = 0
> DEBUG 3: Rejected: message type = 0
> DEBUG 3: Rejected: masking region = 0
> DEBUG 3: Rejected: bad fcst value = 0
> DEBUG 3: Rejected: duplicates = 0
> DEBUG 2:
>
>
> Config file:
>
> /
> // Verification grid
> //
> regrid = {
> to_grid = NONE;
> method = NEAREST;
> width = 1;
> vld_thresh = 0.5;
> }
>
>
>
////////////////////////////////////////////////////////////////////////////////
>
> cat_thresh = [ NA ];
> cnt_thresh = [ NA ];
> cnt_logic = UNION;
> wind_thresh = [ NA ];
> wind_logic = UNION;
>
> //
> // Forecast and observation fields to be verified
> //
>
> // Gust height unclear assumed 10 m like wind
> fcst = {
> field = [
>
> {
> name = "GUST";
> level = [ "Z10" ];
> cat_thresh = [ >5.0 ];
> },
>
>
>
> {
> name = "DPT";
> level = [ "Z2" ];
> cat_thresh = [ >-100.0 ];
> },
>
> {
> name = "TMP";
> level = [ "Z2" ];
> cat_thresh = [ >-100.0 ];
> },
> {
> name = "WIND";
> level = [ "Z10" ];
> cat_thresh = [ >0.0 ];
> }
>
> obs = fcst;
>
>
>
////////////////////////////////////////////////////////////////////////////////
>
> //
> // Point observation filtering options
> // May be set separately in each "obs.field" entry
> //
> message_type = ["APDSFC"];
> sid_exc = [];
> obs_quality = [];
> duplicate_flag = NONE;
> obs_summary = NONE;
> obs_perc_value = 50;
>
>
>
////////////////////////////////////////////////////////////////////////////////
>
> //
> // Climatology mean data
> //
> climo_mean = {
>
> file_name = [];
> field = [];
>
> regrid = {
> method = NEAREST;
> width = 1;
> vld_thresh = 0.5;
> }
>
> time_interp_method = DW_MEAN;
> match_day = FALSE;
> time_step = 21600;
> }
>
>
>
////////////////////////////////////////////////////////////////////////////////
>
> //
> // Point observation time window
> //
> obs_window = {
> beg = -54000;
> end = 54000;
>
> // Verification masking regions
> //
> mask = {
> grid = [ "FULL" ];
> poly = [];
> sid = [];
> }
>
>
>
////////////////////////////////////////////////////////////////////////////////
>
> //
> // Confidence interval settings
> //
> ci_alpha = [ 0.05 ];
>
> boot = {
> interval = PCTILE;
> rep_prop = 1.0;
> n_rep = 0;
> rng = "mt19937";
> seed = "";
> }
>
>
------------------------------------------------
Subject: Point-Stats Error
From: emily niebuhr
Time: Mon Nov 20 11:02:16 2017
John,
Thank you for the fast reply and suggestion, but unfortunately it did
not
work. Taking a fresh Monday look at things, I noticed that many of
the
observations were rejected for GRIB Code or message type. I have
included
my input observations. Do you see something incorrect here? I put QC
as 9
as the tutorial indicated, but maybe this is not appropriate for this
case.
ADPSFC 702730 20171116_000000 61.17 -149.99 46 11 1007.0 46 9
268.15
ADPSFC 702730 20171116_000000 61.17 -149.99 46 52 1007.0 46 9
62.7
ADPSFC 702730 20171116_000000 61.17 -149.99 46 31 1007.0 46 9
-9999
ADPSFC 702730 20171116_000000 61.17 -149.99 46 01 1007.0 46 9
1007.0
ADPSFC 702730 20171116_000000 61.17 -149.99 46 32 1007.0 46 9
-9999
ADPSFC 702730 20171116_000000 61.17 -149.99 46 180 1007.0 46 9
-9999
ADPSFC 702730 20171116_000500 61.17 -149.99 46 11 1007.0 46 9
267.15
ADPSFC 702730 20171116_000500 61.17 -149.99 46 52 1007.0 46 9
73.25
ADPSFC 702730 20171116_000500 61.17 -149.99 46 31 1007.0 46 9
-9999
Processing WIND/Z10 versus WIND/Z10, for observation type APDSFC,
over
region FULL, for interpolation method NEAREST(1), using 0 pairs.
DEBUG 3: Number of matched pairs = 0
DEBUG 3: Observations processed = 2016
DEBUG 3: Rejected: SID exclusion = 0
DEBUG 3: Rejected: GRIB code = 1680
DEBUG 3: Rejected: valid time = 0
DEBUG 3: Rejected: bad obs value = 256
DEBUG 3: Rejected: off the grid = 0
DEBUG 3: Rejected: level mismatch = 0
DEBUG 3: Rejected: quality marker = 0
DEBUG 3: Rejected: message type = 80
DEBUG 3: Rejected: masking region = 0
DEBUG 3: Rejected: bad fcst value = 0
DEBUG 3: Rejected: duplicates = 0
Processing TMP/Z2 versus TMP/Z2, for observation type APDSFC, over
region
FULL, for interpolation method NEAREST(1), using 0 pairs.
DEBUG 3: Number of matched pairs = 0
DEBUG 3: Observations processed = 2016
DEBUG 3: Rejected: SID exclusion = 0
DEBUG 3: Rejected: GRIB code = 1680
DEBUG 3: Rejected: valid time = 0
DEBUG 3: Rejected: bad obs value = 0
DEBUG 3: Rejected: off the grid = 0
DEBUG 3: Rejected: level mismatch = 0
DEBUG 3: Rejected: quality marker = 0
DEBUG 3: Rejected: message type = 336
DEBUG 3: Rejected: masking region = 0
DEBUG 3: Rejected: bad fcst value = 0
DEBUG 3: Rejected: duplicates = 0
On 17 November 2017 at 17:19, John Halley Gotway via RT
<met_help at ucar.edu>
wrote:
> Hi Emily,
>
> That’s great that you ran Point-Stat at verbosity level 3 to dump
out the
> counts for the reasons why observations weren’t used for each
verification
> task.
>
> Looking at those counts I see that 42 weren’t used because of their
valid
> time. Mid suggest starting there. Perhaps your observations aren’t
close
> enough in time to your forecast valid time?
>
> One way of testing this would be rerunning point_stat using these
command
> line options:
> -obs_valid_beg 20000101 -obs_valid_end 21000101
>
> That tells point-stat to use all obs between the years 2000 and
2100! And
> that should include all of yours.
>
> Once you get some matches pairs, you can decide how you’d really
like to
> set the matching time window for the point obs.
>
> Hope that helps.
>
> Thanks,
> John
>
> On Fri, Nov 17, 2017 at 7:00 PM emily niebuhr via RT
<met_help at ucar.edu>
> wrote:
>
> >
> > Fri Nov 17 19:00:18 2017: Request 83072 was acted upon.
> > Transaction: Ticket created by elniebuhr at gmail.com
> > Queue: met_help
> > Subject: Point-Stats Error
> > Owner: Nobody
> > Requestors: elniebuhr at gmail.com
> > Status: new
> > Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=83072 >
> >
> >
> > To whom it may concern,
> >
> > Hopefully this is a small user error that I am encountering, but I
cannot
> > seem to find matches after running point_Stat.Do you know why the
> > observations may not be matching? I get no errors when I run
ascii2nc
> and
> > I clearly define two points with correct stations and lat/lon.
> >
> >
> > I was wondering if I am possibly having errors since it is polar
> projection
> > or grib2 data. Right away I receive an error about unrecognised
GRIB2
> > field indexes. However I don't think this is the main problem
since I
> still
> > end up with no matching pairs even if I convert it to grib1. The
only
> other
> > thing I can think of is that I incorrectly defined the QC
variable. What
> > value do you suggest?
> >
> > I seem to get similar errors when I try prepbufr files, and if I
try to
> > verify with HRRR or URMA files. Thanks!
> >
> >
> >
> > DEBUG 1: User Config File: nPointStatConfig_default
> > DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created
new
> > Met2dDataFile object of type "FileType_Gb2".
> > DEBUG 4: Switching the GRIB2 radius of the earth value of 6371.23
km to
> > 6371.2 km for internal consistency.
> > DEBUG 4:
> > DEBUG 4: Stereographic Grid Data:
> > DEBUG 4: hemisphere: N
> > DEBUG 4: scale_lat: 60
> > DEBUG 4: lat_pin: 41.6129
> > DEBUG 4: lon_pin: 174.883
> > DEBUG 4: x_pin: 0
> > DEBUG 4: y_pin: 0
> > DEBUG 4: lon_orient: 135
> > DEBUG 4: d_km: 3
> > DEBUG 4: r_km: 6371.2
> > DEBUG 4: nx: 1299
> > DEBUG 4: ny: 919
> > DEBUG 4:
> > DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2
> > field indexes - disc: 0, master table: 2, center: 59, local table:
1,
> > parm_cat: 16, parm: 196
> > DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2
> > field indexes - disc: 0, master table: 2, center: 59, local table:
1,
> > parm_cat: 16, parm: 201
> > DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2
> > field indexes - disc: 0, master table: 2, center: 59, local table:
1,
> > parm_cat: 16, parm: 195
> > DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2
> > field indexes - disc: 0, master table: 2, center: 59, local table:
1,
> > parm_cat: 16, parm: 195
> > DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2
> > field indexes - disc: 0, master table: 2, center: 59, local table:
1,
> > parm_cat: 16, parm: 195
> >
> >
> > ARNING: Multiple GRIB2 table entries match lookup criteria
(parm_name =
> > GUST):
> > WARNING: parm_name: GUST, index_a = 0, grib2_mtab = 1,
grib2_cntr = 0,
> > grib2_ltab = 0, index_b = 2, index_c = 22
> > WARNING: parm_name: GUST, index_a = 0, grib2_mtab = 14,
grib2_cntr =
> 57,
> > grib2_ltab = 0, index_b = 2, index_c = 22
> > WARNING: Using: parm_name: GUST, index_a = 0, grib2_mtab = 1,
> grib2_cntr
> > = 0, grib2_ltab = 0, index_b = 2, index_c = 22
> >
> >
> > Reading data for TMP/Z2.
> > DEBUG 3: MetGrib2DataFile::data_plane_array() - Found exact match
for
> > "TMP/Z2" in GRIB2 record 59 field 1 of GRIB2 file
"1732021000000.grb2"
> > DEBUG 4:
> > DEBUG 4: Data plane information:
> > DEBUG 4: plane min: 234.527
> > DEBUG 4: plane max: 286.34
> > DEBUG 4: scan mode: 64
> > DEBUG 4: valid time: 20171116_210000
> > DEBUG 4: lead time: 000000
> > DEBUG 4: init time: 20171116_210000
> > DEBUG 4: bitmap flag: 255
> > DEBUG 4:
> > DEBUG 2: For TMP/Z2 found 1 forecast levels and 0 climatology
levels.
> >
> >
> >
> > Processing TMP/Z2 versus TMP/Z2, for observation type APDSFC, over
region
> > FULL, for interpolation method NEAREST(1), using 0 pairs.
> > DEBUG 3: Number of matched pairs = 0
> > DEBUG 3: Observations processed = 210
> > DEBUG 3: Rejected: SID exclusion = 0
> > DEBUG 3: Rejected: GRIB code = 168
> > DEBUG 3: Rejected: valid time = 42
> > DEBUG 3: Rejected: bad obs value = 0
> > DEBUG 3: Rejected: off the grid = 0
> > DEBUG 3: Rejected: level mismatch = 0
> > DEBUG 3: Rejected: quality marker = 0
> > DEBUG 3: Rejected: message type = 0
> > DEBUG 3: Rejected: masking region = 0
> > DEBUG 3: Rejected: bad fcst value = 0
> > DEBUG 3: Rejected: duplicates = 0
> > DEBUG 2:
> >
> >
> > Config file:
> >
> > /
> > // Verification grid
> > //
> > regrid = {
> > to_grid = NONE;
> > method = NEAREST;
> > width = 1;
> > vld_thresh = 0.5;
> > }
> >
> >
> > ////////////////////////////////////////////////////////////
> ////////////////////
> >
> > cat_thresh = [ NA ];
> > cnt_thresh = [ NA ];
> > cnt_logic = UNION;
> > wind_thresh = [ NA ];
> > wind_logic = UNION;
> >
> > //
> > // Forecast and observation fields to be verified
> > //
> >
> > // Gust height unclear assumed 10 m like wind
> > fcst = {
> > field = [
> >
> > {
> > name = "GUST";
> > level = [ "Z10" ];
> > cat_thresh = [ >5.0 ];
> > },
> >
> >
> >
> > {
> > name = "DPT";
> > level = [ "Z2" ];
> > cat_thresh = [ >-100.0 ];
> > },
> >
> > {
> > name = "TMP";
> > level = [ "Z2" ];
> > cat_thresh = [ >-100.0 ];
> > },
> > {
> > name = "WIND";
> > level = [ "Z10" ];
> > cat_thresh = [ >0.0 ];
> > }
> >
> > obs = fcst;
> >
> >
> > ////////////////////////////////////////////////////////////
> ////////////////////
> >
> > //
> > // Point observation filtering options
> > // May be set separately in each "obs.field" entry
> > //
> > message_type = ["APDSFC"];
> > sid_exc = [];
> > obs_quality = [];
> > duplicate_flag = NONE;
> > obs_summary = NONE;
> > obs_perc_value = 50;
> >
> >
> > ////////////////////////////////////////////////////////////
> ////////////////////
> >
> > //
> > // Climatology mean data
> > //
> > climo_mean = {
> >
> > file_name = [];
> > field = [];
> >
> > regrid = {
> > method = NEAREST;
> > width = 1;
> > vld_thresh = 0.5;
> > }
> >
> > time_interp_method = DW_MEAN;
> > match_day = FALSE;
> > time_step = 21600;
> > }
> >
> >
> > ////////////////////////////////////////////////////////////
> ////////////////////
> >
> > //
> > // Point observation time window
> > //
> > obs_window = {
> > beg = -54000;
> > end = 54000;
> >
> > // Verification masking regions
> > //
> > mask = {
> > grid = [ "FULL" ];
> > poly = [];
> > sid = [];
> > }
> >
> >
> > ////////////////////////////////////////////////////////////
> ////////////////////
> >
> > //
> > // Confidence interval settings
> > //
> > ci_alpha = [ 0.05 ];
> >
> > boot = {
> > interval = PCTILE;
> > rep_prop = 1.0;
> > n_rep = 0;
> > rng = "mt19937";
> > seed = "";
> > }
> >
> >
>
>
------------------------------------------------
Subject: Re: [rt.rap.ucar.edu #83072] Point-Stats Error
From: Howard Soh
Time: Mon Nov 20 11:59:37 2017
Hi Emily,
John is out of office this week.
The main issues are GRIB code and messgae type. The pair was not
rejected by QC value.
DEBUG 3: Rejected: quality marker = 0
I'm sorry if you already did this but I would check
1. MET version
2. the GRIB names at the configuration file
3. the existence of GRIB variables at the forecast file and the
observation.
It would probably be easiest to have you send us the files. You
can post it to our anonymous ftp site following these instructions:
http://www.dtcenter.org/met/users/support/met_help.php#ftp
Three files: the forecast file, observation file, and configuration
file
Please write back once you have posted it, and I'll grab it.
Cheers,
Howard
FYI:
The text file (observation data) shows following GRIB codes exist:
- code 01: PRES
- code 11: TMP
- code 52: RH
- code 31: WDIR
- code 32: WIND
- code 180: GUST
==> DPT (code 17 from point_stat config file below) is missing
On 11/20/2017 11:02 AM, emily niebuhr via RT wrote:
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=83072 >
>
> John,
>
> Thank you for the fast reply and suggestion, but unfortunately it
did not
> work. Taking a fresh Monday look at things, I noticed that many of
the
> observations were rejected for GRIB Code or message type. I have
included
> my input observations. Do you see something incorrect here? I put
QC as 9
> as the tutorial indicated, but maybe this is not appropriate for
this case.
>
> ADPSFC 702730 20171116_000000 61.17 -149.99 46 11 1007.0 46 9
268.15
> ADPSFC 702730 20171116_000000 61.17 -149.99 46 52 1007.0 46 9
62.7
> ADPSFC 702730 20171116_000000 61.17 -149.99 46 31 1007.0 46 9
-9999
> ADPSFC 702730 20171116_000000 61.17 -149.99 46 01 1007.0 46 9
1007.0
> ADPSFC 702730 20171116_000000 61.17 -149.99 46 32 1007.0 46 9
-9999
> ADPSFC 702730 20171116_000000 61.17 -149.99 46 180 1007.0 46 9
-9999
> ADPSFC 702730 20171116_000500 61.17 -149.99 46 11 1007.0 46 9
267.15
> ADPSFC 702730 20171116_000500 61.17 -149.99 46 52 1007.0 46 9
73.25
> ADPSFC 702730 20171116_000500 61.17 -149.99 46 31 1007.0 46 9
-9999
>
> Processing WIND/Z10 versus WIND/Z10, for observation type APDSFC,
over
> region FULL, for interpolation method NEAREST(1), using 0 pairs.
> DEBUG 3: Number of matched pairs = 0
> DEBUG 3: Observations processed = 2016
> DEBUG 3: Rejected: SID exclusion = 0
> DEBUG 3: Rejected: GRIB code = 1680
> DEBUG 3: Rejected: valid time = 0
> DEBUG 3: Rejected: bad obs value = 256
> DEBUG 3: Rejected: off the grid = 0
> DEBUG 3: Rejected: level mismatch = 0
> DEBUG 3: Rejected: quality marker = 0
> DEBUG 3: Rejected: message type = 80
> DEBUG 3: Rejected: masking region = 0
> DEBUG 3: Rejected: bad fcst value = 0
> DEBUG 3: Rejected: duplicates = 0
>
> Processing TMP/Z2 versus TMP/Z2, for observation type APDSFC, over
region
> FULL, for interpolation method NEAREST(1), using 0 pairs.
> DEBUG 3: Number of matched pairs = 0
> DEBUG 3: Observations processed = 2016
> DEBUG 3: Rejected: SID exclusion = 0
> DEBUG 3: Rejected: GRIB code = 1680
> DEBUG 3: Rejected: valid time = 0
> DEBUG 3: Rejected: bad obs value = 0
> DEBUG 3: Rejected: off the grid = 0
> DEBUG 3: Rejected: level mismatch = 0
> DEBUG 3: Rejected: quality marker = 0
> DEBUG 3: Rejected: message type = 336
> DEBUG 3: Rejected: masking region = 0
> DEBUG 3: Rejected: bad fcst value = 0
> DEBUG 3: Rejected: duplicates = 0
>
>
> On 17 November 2017 at 17:19, John Halley Gotway via RT
<met_help at ucar.edu>
> wrote:
>
>> Hi Emily,
>>
>> That’s great that you ran Point-Stat at verbosity level 3 to dump
out the
>> counts for the reasons why observations weren’t used for each
verification
>> task.
>>
>> Looking at those counts I see that 42 weren’t used because of their
valid
>> time. Mid suggest starting there. Perhaps your observations aren’t
close
>> enough in time to your forecast valid time?
>>
>> One way of testing this would be rerunning point_stat using these
command
>> line options:
>> -obs_valid_beg 20000101 -obs_valid_end 21000101
>>
>> That tells point-stat to use all obs between the years 2000 and
2100! And
>> that should include all of yours.
>>
>> Once you get some matches pairs, you can decide how you’d really
like to
>> set the matching time window for the point obs.
>>
>> Hope that helps.
>>
>> Thanks,
>> John
>>
>> On Fri, Nov 17, 2017 at 7:00 PM emily niebuhr via RT
<met_help at ucar.edu>
>> wrote:
>>
>>> Fri Nov 17 19:00:18 2017: Request 83072 was acted upon.
>>> Transaction: Ticket created by elniebuhr at gmail.com
>>> Queue: met_help
>>> Subject: Point-Stats Error
>>> Owner: Nobody
>>> Requestors: elniebuhr at gmail.com
>>> Status: new
>>> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=83072 >
>>>
>>>
>>> To whom it may concern,
>>>
>>> Hopefully this is a small user error that I am encountering, but I
cannot
>>> seem to find matches after running point_Stat.Do you know why the
>>> observations may not be matching? I get no errors when I run
ascii2nc
>> and
>>> I clearly define two points with correct stations and lat/lon.
>>>
>>>
>>> I was wondering if I am possibly having errors since it is polar
>> projection
>>> or grib2 data. Right away I receive an error about unrecognised
GRIB2
>>> field indexes. However I don't think this is the main problem
since I
>> still
>>> end up with no matching pairs even if I convert it to grib1. The
only
>> other
>>> thing I can think of is that I incorrectly defined the QC
variable. What
>>> value do you suggest?
>>>
>>> I seem to get similar errors when I try prepbufr files, and if I
try to
>>> verify with HRRR or URMA files. Thanks!
>>>
>>>
>>>
>>> DEBUG 1: User Config File: nPointStatConfig_default
>>> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created
new
>>> Met2dDataFile object of type "FileType_Gb2".
>>> DEBUG 4: Switching the GRIB2 radius of the earth value of 6371.23
km to
>>> 6371.2 km for internal consistency.
>>> DEBUG 4:
>>> DEBUG 4: Stereographic Grid Data:
>>> DEBUG 4: hemisphere: N
>>> DEBUG 4: scale_lat: 60
>>> DEBUG 4: lat_pin: 41.6129
>>> DEBUG 4: lon_pin: 174.883
>>> DEBUG 4: x_pin: 0
>>> DEBUG 4: y_pin: 0
>>> DEBUG 4: lon_orient: 135
>>> DEBUG 4: d_km: 3
>>> DEBUG 4: r_km: 6371.2
>>> DEBUG 4: nx: 1299
>>> DEBUG 4: ny: 919
>>> DEBUG 4:
>>> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2
>>> field indexes - disc: 0, master table: 2, center: 59, local table:
1,
>>> parm_cat: 16, parm: 196
>>> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2
>>> field indexes - disc: 0, master table: 2, center: 59, local table:
1,
>>> parm_cat: 16, parm: 201
>>> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2
>>> field indexes - disc: 0, master table: 2, center: 59, local table:
1,
>>> parm_cat: 16, parm: 195
>>> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2
>>> field indexes - disc: 0, master table: 2, center: 59, local table:
1,
>>> parm_cat: 16, parm: 195
>>> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() - unrecognized
GRIB2
>>> field indexes - disc: 0, master table: 2, center: 59, local table:
1,
>>> parm_cat: 16, parm: 195
>>>
>>>
>>> ARNING: Multiple GRIB2 table entries match lookup criteria
(parm_name =
>>> GUST):
>>> WARNING: parm_name: GUST, index_a = 0, grib2_mtab = 1,
grib2_cntr = 0,
>>> grib2_ltab = 0, index_b = 2, index_c = 22
>>> WARNING: parm_name: GUST, index_a = 0, grib2_mtab = 14,
grib2_cntr =
>> 57,
>>> grib2_ltab = 0, index_b = 2, index_c = 22
>>> WARNING: Using: parm_name: GUST, index_a = 0, grib2_mtab = 1,
>> grib2_cntr
>>> = 0, grib2_ltab = 0, index_b = 2, index_c = 22
>>>
>>>
>>> Reading data for TMP/Z2.
>>> DEBUG 3: MetGrib2DataFile::data_plane_array() - Found exact match
for
>>> "TMP/Z2" in GRIB2 record 59 field 1 of GRIB2 file
"1732021000000.grb2"
>>> DEBUG 4:
>>> DEBUG 4: Data plane information:
>>> DEBUG 4: plane min: 234.527
>>> DEBUG 4: plane max: 286.34
>>> DEBUG 4: scan mode: 64
>>> DEBUG 4: valid time: 20171116_210000
>>> DEBUG 4: lead time: 000000
>>> DEBUG 4: init time: 20171116_210000
>>> DEBUG 4: bitmap flag: 255
>>> DEBUG 4:
>>> DEBUG 2: For TMP/Z2 found 1 forecast levels and 0 climatology
levels.
>>>
>>>
>>>
>>> Processing TMP/Z2 versus TMP/Z2, for observation type APDSFC, over
region
>>> FULL, for interpolation method NEAREST(1), using 0 pairs.
>>> DEBUG 3: Number of matched pairs = 0
>>> DEBUG 3: Observations processed = 210
>>> DEBUG 3: Rejected: SID exclusion = 0
>>> DEBUG 3: Rejected: GRIB code = 168
>>> DEBUG 3: Rejected: valid time = 42
>>> DEBUG 3: Rejected: bad obs value = 0
>>> DEBUG 3: Rejected: off the grid = 0
>>> DEBUG 3: Rejected: level mismatch = 0
>>> DEBUG 3: Rejected: quality marker = 0
>>> DEBUG 3: Rejected: message type = 0
>>> DEBUG 3: Rejected: masking region = 0
>>> DEBUG 3: Rejected: bad fcst value = 0
>>> DEBUG 3: Rejected: duplicates = 0
>>> DEBUG 2:
>>>
>>>
>>> Config file:
>>>
>>> /
>>> // Verification grid
>>> //
>>> regrid = {
>>> to_grid = NONE;
>>> method = NEAREST;
>>> width = 1;
>>> vld_thresh = 0.5;
>>> }
>>>
>>>
>>> ////////////////////////////////////////////////////////////
>> ////////////////////
>>> cat_thresh = [ NA ];
>>> cnt_thresh = [ NA ];
>>> cnt_logic = UNION;
>>> wind_thresh = [ NA ];
>>> wind_logic = UNION;
>>>
>>> //
>>> // Forecast and observation fields to be verified
>>> //
>>>
>>> // Gust height unclear assumed 10 m like wind
>>> fcst = {
>>> field = [
>>>
>>> {
>>> name = "GUST";
>>> level = [ "Z10" ];
>>> cat_thresh = [ >5.0 ];
>>> },
>>>
>>>
>>>
>>> {
>>> name = "DPT";
>>> level = [ "Z2" ];
>>> cat_thresh = [ >-100.0 ];
>>> },
>>>
>>> {
>>> name = "TMP";
>>> level = [ "Z2" ];
>>> cat_thresh = [ >-100.0 ];
>>> },
>>> {
>>> name = "WIND";
>>> level = [ "Z10" ];
>>> cat_thresh = [ >0.0 ];
>>> }
>>>
>>> obs = fcst;
>>>
>>>
>>> ////////////////////////////////////////////////////////////
>> ////////////////////
>>> //
>>> // Point observation filtering options
>>> // May be set separately in each "obs.field" entry
>>> //
>>> message_type = ["APDSFC"];
>>> sid_exc = [];
>>> obs_quality = [];
>>> duplicate_flag = NONE;
>>> obs_summary = NONE;
>>> obs_perc_value = 50;
>>>
>>>
>>> ////////////////////////////////////////////////////////////
>> ////////////////////
>>> //
>>> // Climatology mean data
>>> //
>>> climo_mean = {
>>>
>>> file_name = [];
>>> field = [];
>>>
>>> regrid = {
>>> method = NEAREST;
>>> width = 1;
>>> vld_thresh = 0.5;
>>> }
>>>
>>> time_interp_method = DW_MEAN;
>>> match_day = FALSE;
>>> time_step = 21600;
>>> }
>>>
>>>
>>> ////////////////////////////////////////////////////////////
>> ////////////////////
>>> //
>>> // Point observation time window
>>> //
>>> obs_window = {
>>> beg = -54000;
>>> end = 54000;
>>>
>>> // Verification masking regions
>>> //
>>> mask = {
>>> grid = [ "FULL" ];
>>> poly = [];
>>> sid = [];
>>> }
>>>
>>>
>>> ////////////////////////////////////////////////////////////
>> ////////////////////
>>> //
>>> // Confidence interval settings
>>> //
>>> ci_alpha = [ 0.05 ];
>>>
>>> boot = {
>>> interval = PCTILE;
>>> rep_prop = 1.0;
>>> n_rep = 0;
>>> rng = "mt19937";
>>> seed = "";
>>> }
>>>
>>>
>>
------------------------------------------------
Subject: Point-Stats Error
From: emily niebuhr
Time: Tue Nov 21 17:48:54 2017
Thank you for the help Howard- I have shared my files! I even double
checked my g2lib errors and none of them are any of the variables that
I
use for Point_Stat - i.e. none of them are TMP etc. So I have run out
of
ideas since I have similar Point Stat errors for BUFR. Thank you for
your
help!
Just in case, I receive the following error for HRRR files but not for
URMA
when I run cnvgrib, which varifies to me that these errors are not the
variables I am interested in and I am looking at grib tables
correctly.
param_g2_to_g1:GRIB2 param 0 16 3 not
found.
param_g2_to_g1:GRIB2 param 0 16 201 not
found.
param_g2_to_g1:GRIB2 param 0 1 74 not
found.
param_g2_to_g1:GRIB2 param 0 17 1 not
found.
param_g2_to_g1:GRIB2 param 0 17 1 not
found.
param_g2_to_g1:GRIB2 param 10 191 0 not
found.
param_g2_to_g1:GRIB2 param 10 191 0 not
found.
param_g2_to_g1:GRIB2 param 10 191 0 not
found.
param_g2_to_g1:GRIB2 param 10 191 0 not
found.
param_g2_to_g1:GRIB2 param 10 191 0 not
found.
param_g2_to_g1:GRIB2 param 10 191 0 not
found.
param_g2_to_g1:GRIB2 param 2 0 13 not
found.
param_g2_to_g1:GRIB2 param 0 1 42 not
found.
param_g2_to_g1:GRIB2 param 1 0 6 not
found.
param_g2_to_g1:GRIB2 param 1 0 5 not
found.
param_g2_to_g1:GRIB2 param 0 1 36 not
found.
param_g2_to_g1:GRIB2 param 0 1 35 not
found.
param_g2_to_g1:GRIB2 param 0 1 34 not
found.
param_g2_to_g1:GRIB2 param 0 1 33 not
found.
param_g2_to_g1:GRIB2 param 0 2 30 not
found.
param_g2_to_g1:GRIB2 param 2 0 10 not
found.
param_g2_to_g1:GRIB2 param 0 7 10 not
found.
param_g2_to_g1:GRIB2 param 0 5 4 not
found.
param_g2_to_g1:GRIB2 param 0 4 7 not
found.
param_g2_to_g1:GRIB2 param 0 5 3 not
found.
param_g2_to_g1:GRIB2 param 0 4 8 not
found.
param_g2_to_g1:GRIB2 param 0 5 4 not
found.
param_g2_to_g1:GRIB2 param 0 2 27 not
found.
param_g2_to_g1:GRIB2 param 0 2 28 not
found.
param_g2_to_g1:GRIB2 param 0 3 18 not
found.
On 20 November 2017 at 09:59, Howard Soh via RT <met_help at ucar.edu>
wrote:
> Hi Emily,
>
> John is out of office this week.
>
> The main issues are GRIB code and messgae type. The pair was not
> rejected by QC value.
>
> DEBUG 3: Rejected: quality marker = 0
>
>
> I'm sorry if you already did this but I would check
> 1. MET version
> 2. the GRIB names at the configuration file
> 3. the existence of GRIB variables at the forecast file and the
> observation.
>
> It would probably be easiest to have you send us the files. You
> can post it to our anonymous ftp site following these instructions:
>
> http://www.dtcenter.org/met/users/support/met_help.php#ftp
>
> Three files: the forecast file, observation file, and configuration
file
>
> Please write back once you have posted it, and I'll grab it.
>
> Cheers,
> Howard
>
> FYI:
> The text file (observation data) shows following GRIB codes exist:
> - code 01: PRES
> - code 11: TMP
> - code 52: RH
> - code 31: WDIR
> - code 32: WIND
> - code 180: GUST
> ==> DPT (code 17 from point_stat config file below) is missing
>
>
> On 11/20/2017 11:02 AM, emily niebuhr via RT wrote:
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=83072 >
> >
> > John,
> >
> > Thank you for the fast reply and suggestion, but unfortunately it
did not
> > work. Taking a fresh Monday look at things, I noticed that many
of the
> > observations were rejected for GRIB Code or message type. I have
included
> > my input observations. Do you see something incorrect here? I
put QC
> as 9
> > as the tutorial indicated, but maybe this is not appropriate for
this
> case.
> >
> > ADPSFC 702730 20171116_000000 61.17 -149.99 46 11 1007.0 46 9
268.15
> > ADPSFC 702730 20171116_000000 61.17 -149.99 46 52 1007.0 46
9 62.7
> > ADPSFC 702730 20171116_000000 61.17 -149.99 46 31 1007.0 46
9 -9999
> > ADPSFC 702730 20171116_000000 61.17 -149.99 46 01 1007.0 46
9
> 1007.0
> > ADPSFC 702730 20171116_000000 61.17 -149.99 46 32 1007.0 46
9 -9999
> > ADPSFC 702730 20171116_000000 61.17 -149.99 46 180 1007.0 46
9
> -9999
> > ADPSFC 702730 20171116_000500 61.17 -149.99 46 11 1007.0 46
9
> 267.15
> > ADPSFC 702730 20171116_000500 61.17 -149.99 46 52 1007.0 46
9 73.25
> > ADPSFC 702730 20171116_000500 61.17 -149.99 46 31 1007.0 46
9 -9999
> >
> > Processing WIND/Z10 versus WIND/Z10, for observation type
APDSFC, over
> > region FULL, for interpolation method NEAREST(1), using 0 pairs.
> > DEBUG 3: Number of matched pairs = 0
> > DEBUG 3: Observations processed = 2016
> > DEBUG 3: Rejected: SID exclusion = 0
> > DEBUG 3: Rejected: GRIB code = 1680
> > DEBUG 3: Rejected: valid time = 0
> > DEBUG 3: Rejected: bad obs value = 256
> > DEBUG 3: Rejected: off the grid = 0
> > DEBUG 3: Rejected: level mismatch = 0
> > DEBUG 3: Rejected: quality marker = 0
> > DEBUG 3: Rejected: message type = 80
> > DEBUG 3: Rejected: masking region = 0
> > DEBUG 3: Rejected: bad fcst value = 0
> > DEBUG 3: Rejected: duplicates = 0
> >
> > Processing TMP/Z2 versus TMP/Z2, for observation type APDSFC, over
region
> > FULL, for interpolation method NEAREST(1), using 0 pairs.
> > DEBUG 3: Number of matched pairs = 0
> > DEBUG 3: Observations processed = 2016
> > DEBUG 3: Rejected: SID exclusion = 0
> > DEBUG 3: Rejected: GRIB code = 1680
> > DEBUG 3: Rejected: valid time = 0
> > DEBUG 3: Rejected: bad obs value = 0
> > DEBUG 3: Rejected: off the grid = 0
> > DEBUG 3: Rejected: level mismatch = 0
> > DEBUG 3: Rejected: quality marker = 0
> > DEBUG 3: Rejected: message type = 336
> > DEBUG 3: Rejected: masking region = 0
> > DEBUG 3: Rejected: bad fcst value = 0
> > DEBUG 3: Rejected: duplicates = 0
> >
> >
> > On 17 November 2017 at 17:19, John Halley Gotway via RT <
> met_help at ucar.edu>
> > wrote:
> >
> >> Hi Emily,
> >>
> >> That’s great that you ran Point-Stat at verbosity level 3 to dump
out
> the
> >> counts for the reasons why observations weren’t used for each
> verification
> >> task.
> >>
> >> Looking at those counts I see that 42 weren’t used because of
their
> valid
> >> time. Mid suggest starting there. Perhaps your observations
aren’t
> close
> >> enough in time to your forecast valid time?
> >>
> >> One way of testing this would be rerunning point_stat using these
> command
> >> line options:
> >> -obs_valid_beg 20000101 -obs_valid_end 21000101
> >>
> >> That tells point-stat to use all obs between the years 2000 and
2100!
> And
> >> that should include all of yours.
> >>
> >> Once you get some matches pairs, you can decide how you’d really
like to
> >> set the matching time window for the point obs.
> >>
> >> Hope that helps.
> >>
> >> Thanks,
> >> John
> >>
> >> On Fri, Nov 17, 2017 at 7:00 PM emily niebuhr via RT
<met_help at ucar.edu
> >
> >> wrote:
> >>
> >>> Fri Nov 17 19:00:18 2017: Request 83072 was acted upon.
> >>> Transaction: Ticket created by elniebuhr at gmail.com
> >>> Queue: met_help
> >>> Subject: Point-Stats Error
> >>> Owner: Nobody
> >>> Requestors: elniebuhr at gmail.com
> >>> Status: new
> >>> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=83072
> >
> >>>
> >>>
> >>> To whom it may concern,
> >>>
> >>> Hopefully this is a small user error that I am encountering, but
I
> cannot
> >>> seem to find matches after running point_Stat.Do you know why
the
> >>> observations may not be matching? I get no errors when I run
ascii2nc
> >> and
> >>> I clearly define two points with correct stations and lat/lon.
> >>>
> >>>
> >>> I was wondering if I am possibly having errors since it is polar
> >> projection
> >>> or grib2 data. Right away I receive an error about unrecognised
GRIB2
> >>> field indexes. However I don't think this is the main problem
since I
> >> still
> >>> end up with no matching pairs even if I convert it to grib1. The
only
> >> other
> >>> thing I can think of is that I incorrectly defined the QC
variable.
> What
> >>> value do you suggest?
> >>>
> >>> I seem to get similar errors when I try prepbufr files, and if I
try to
> >>> verify with HRRR or URMA files. Thanks!
> >>>
> >>>
> >>>
> >>> DEBUG 1: User Config File: nPointStatConfig_default
> >>> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created
new
> >>> Met2dDataFile object of type "FileType_Gb2".
> >>> DEBUG 4: Switching the GRIB2 radius of the earth value of
6371.23 km to
> >>> 6371.2 km for internal consistency.
> >>> DEBUG 4:
> >>> DEBUG 4: Stereographic Grid Data:
> >>> DEBUG 4: hemisphere: N
> >>> DEBUG 4: scale_lat: 60
> >>> DEBUG 4: lat_pin: 41.6129
> >>> DEBUG 4: lon_pin: 174.883
> >>> DEBUG 4: x_pin: 0
> >>> DEBUG 4: y_pin: 0
> >>> DEBUG 4: lon_orient: 135
> >>> DEBUG 4: d_km: 3
> >>> DEBUG 4: r_km: 6371.2
> >>> DEBUG 4: nx: 1299
> >>> DEBUG 4: ny: 919
> >>> DEBUG 4:
> >>> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> GRIB2
> >>> field indexes - disc: 0, master table: 2, center: 59, local
table: 1,
> >>> parm_cat: 16, parm: 196
> >>> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> GRIB2
> >>> field indexes - disc: 0, master table: 2, center: 59, local
table: 1,
> >>> parm_cat: 16, parm: 201
> >>> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> GRIB2
> >>> field indexes - disc: 0, master table: 2, center: 59, local
table: 1,
> >>> parm_cat: 16, parm: 195
> >>> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> GRIB2
> >>> field indexes - disc: 0, master table: 2, center: 59, local
table: 1,
> >>> parm_cat: 16, parm: 195
> >>> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> GRIB2
> >>> field indexes - disc: 0, master table: 2, center: 59, local
table: 1,
> >>> parm_cat: 16, parm: 195
> >>>
> >>>
> >>> ARNING: Multiple GRIB2 table entries match lookup criteria
(parm_name =
> >>> GUST):
> >>> WARNING: parm_name: GUST, index_a = 0, grib2_mtab = 1,
grib2_cntr =
> 0,
> >>> grib2_ltab = 0, index_b = 2, index_c = 22
> >>> WARNING: parm_name: GUST, index_a = 0, grib2_mtab = 14,
grib2_cntr =
> >> 57,
> >>> grib2_ltab = 0, index_b = 2, index_c = 22
> >>> WARNING: Using: parm_name: GUST, index_a = 0, grib2_mtab = 1,
> >> grib2_cntr
> >>> = 0, grib2_ltab = 0, index_b = 2, index_c = 22
> >>>
> >>>
> >>> Reading data for TMP/Z2.
> >>> DEBUG 3: MetGrib2DataFile::data_plane_array() - Found exact
match for
> >>> "TMP/Z2" in GRIB2 record 59 field 1 of GRIB2 file
"1732021000000.grb2"
> >>> DEBUG 4:
> >>> DEBUG 4: Data plane information:
> >>> DEBUG 4: plane min: 234.527
> >>> DEBUG 4: plane max: 286.34
> >>> DEBUG 4: scan mode: 64
> >>> DEBUG 4: valid time: 20171116_210000
> >>> DEBUG 4: lead time: 000000
> >>> DEBUG 4: init time: 20171116_210000
> >>> DEBUG 4: bitmap flag: 255
> >>> DEBUG 4:
> >>> DEBUG 2: For TMP/Z2 found 1 forecast levels and 0 climatology
levels.
> >>>
> >>>
> >>>
> >>> Processing TMP/Z2 versus TMP/Z2, for observation type APDSFC,
over
> region
> >>> FULL, for interpolation method NEAREST(1), using 0 pairs.
> >>> DEBUG 3: Number of matched pairs = 0
> >>> DEBUG 3: Observations processed = 210
> >>> DEBUG 3: Rejected: SID exclusion = 0
> >>> DEBUG 3: Rejected: GRIB code = 168
> >>> DEBUG 3: Rejected: valid time = 42
> >>> DEBUG 3: Rejected: bad obs value = 0
> >>> DEBUG 3: Rejected: off the grid = 0
> >>> DEBUG 3: Rejected: level mismatch = 0
> >>> DEBUG 3: Rejected: quality marker = 0
> >>> DEBUG 3: Rejected: message type = 0
> >>> DEBUG 3: Rejected: masking region = 0
> >>> DEBUG 3: Rejected: bad fcst value = 0
> >>> DEBUG 3: Rejected: duplicates = 0
> >>> DEBUG 2:
> >>>
> >>>
> >>> Config file:
> >>>
> >>> /
> >>> // Verification grid
> >>> //
> >>> regrid = {
> >>> to_grid = NONE;
> >>> method = NEAREST;
> >>> width = 1;
> >>> vld_thresh = 0.5;
> >>> }
> >>>
> >>>
> >>> ////////////////////////////////////////////////////////////
> >> ////////////////////
> >>> cat_thresh = [ NA ];
> >>> cnt_thresh = [ NA ];
> >>> cnt_logic = UNION;
> >>> wind_thresh = [ NA ];
> >>> wind_logic = UNION;
> >>>
> >>> //
> >>> // Forecast and observation fields to be verified
> >>> //
> >>>
> >>> // Gust height unclear assumed 10 m like wind
> >>> fcst = {
> >>> field = [
> >>>
> >>> {
> >>> name = "GUST";
> >>> level = [ "Z10" ];
> >>> cat_thresh = [ >5.0 ];
> >>> },
> >>>
> >>>
> >>>
> >>> {
> >>> name = "DPT";
> >>> level = [ "Z2" ];
> >>> cat_thresh = [ >-100.0 ];
> >>> },
> >>>
> >>> {
> >>> name = "TMP";
> >>> level = [ "Z2" ];
> >>> cat_thresh = [ >-100.0 ];
> >>> },
> >>> {
> >>> name = "WIND";
> >>> level = [ "Z10" ];
> >>> cat_thresh = [ >0.0 ];
> >>> }
> >>>
> >>> obs = fcst;
> >>>
> >>>
> >>> ////////////////////////////////////////////////////////////
> >> ////////////////////
> >>> //
> >>> // Point observation filtering options
> >>> // May be set separately in each "obs.field" entry
> >>> //
> >>> message_type = ["APDSFC"];
> >>> sid_exc = [];
> >>> obs_quality = [];
> >>> duplicate_flag = NONE;
> >>> obs_summary = NONE;
> >>> obs_perc_value = 50;
> >>>
> >>>
> >>> ////////////////////////////////////////////////////////////
> >> ////////////////////
> >>> //
> >>> // Climatology mean data
> >>> //
> >>> climo_mean = {
> >>>
> >>> file_name = [];
> >>> field = [];
> >>>
> >>> regrid = {
> >>> method = NEAREST;
> >>> width = 1;
> >>> vld_thresh = 0.5;
> >>> }
> >>>
> >>> time_interp_method = DW_MEAN;
> >>> match_day = FALSE;
> >>> time_step = 21600;
> >>> }
> >>>
> >>>
> >>> ////////////////////////////////////////////////////////////
> >> ////////////////////
> >>> //
> >>> // Point observation time window
> >>> //
> >>> obs_window = {
> >>> beg = -54000;
> >>> end = 54000;
> >>>
> >>> // Verification masking regions
> >>> //
> >>> mask = {
> >>> grid = [ "FULL" ];
> >>> poly = [];
> >>> sid = [];
> >>> }
> >>>
> >>>
> >>> ////////////////////////////////////////////////////////////
> >> ////////////////////
> >>> //
> >>> // Confidence interval settings
> >>> //
> >>> ci_alpha = [ 0.05 ];
> >>>
> >>> boot = {
> >>> interval = PCTILE;
> >>> rep_prop = 1.0;
> >>> n_rep = 0;
> >>> rng = "mt19937";
> >>> seed = "";
> >>> }
> >>>
> >>>
> >>
>
>
>
------------------------------------------------
Subject: Re: [rt.rap.ucar.edu #83072] Point-Stats Error
From: Howard Soh
Time: Wed Nov 22 09:12:37 2017
"APDSFC" VS. "ADPSFC"
Would you change the message type at nPointStatConfig_default.txt to
"ADPSFC"? The message type in the config file is "APDSFC" and the
message type in ascii2nc output All_outpl7.nc is "ADPSFC".
I got these numbers with 1732021000000.grb1 and All_outpl7.nc:
DEBUG 2: Processing DPT/Z2 versus DPT/Z2, for observation type ADPSFC,
over region FULL, for interpolation method NEAREST(1), using 0 pairs.
DEBUG 2: Processing TMP/Z2 versus TMP/Z2, for observation type ADPSFC,
over region FULL, for interpolation method NEAREST(1), using 225
pairs.
DEBUG 2: Processing WIND/Z10 versus WIND/Z10, for observation type
ADPSFC, over region FULL, for interpolation method NEAREST(1), using
56
pairs.
Cheers,
Howard
FYI:
At the All_outpl7.nc:
- there are 6 variables with 336 observations: 2016 observations
(
336 * 6)
Processing WIND/Z10 versus WIND/Z10, for observation type APDSFC,
over
region FULL, for interpolation method NEAREST(1), using 0 pairs.
DEBUG 3: Observations processed = 2016
DEBUG 3: Rejected: GRIB code = 1680
DEBUG 3: Rejected: bad obs value = 256
DEBUG 3: Rejected: message type = 80
Get variable, WIND: 2016 - 336 = 1680
==> 1680 are rejected because they are not WIND
Filter by missing value or bad value: 256
==> valid WIND obs. is 80 (= 336 - 256)
The 80 data was rejected by message type (not "ADPSFC")
Variable names from the config files:
fcst: GUST, DPT, TMP, WIND
Variable count from 1732021000000.grb1:
- GUST: 1
- DPT: 1
- TMP:2
- UGRD nd VGRD: 2
- Obs time: 17111621 ==> 1 matching obs time ("20171116_030000")
from
All_outpl7.nc
- location: Lat1 41.612000 Long1 185.117000 Orient 225.000000
Variable count from akurma.t04z.2dvarges_ndfd_3p0.grb11
- GUST: 1
- DPT: 1
- TMP: 1
- UGRD nd VGRD: 1
- Obs time: 17111603 ==> 1 matching obs time ("20171116_030000") from
All_outpl7.nc
- location: Lat1 40.530000 Long1 -178.571000
Varibales and count from All_outpl7.nc
- message type:"ADPSFC"
- 336 observations for each variables: PRES, TMP, RH, ,WDIR, WIND, and
GUST
- Obs time: 20170111_000130 to "20171116_225000" (1 or 2 obs for each
time)
- Locations:
61.17, -149.99, 46 : 303 headers,
61.32, -150.09, 109 : 33 headers
On 11/21/2017 5:48 PM, emily niebuhr via RT wrote:
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=83072 >
>
> Thank you for the help Howard- I have shared my files! I even double
> checked my g2lib errors and none of them are any of the variables
that I
> use for Point_Stat - i.e. none of them are TMP etc. So I have run
out of
> ideas since I have similar Point Stat errors for BUFR. Thank you for
your
> help!
>
> Just in case, I receive the following error for HRRR files but not
for URMA
> when I run cnvgrib, which varifies to me that these errors are not
the
> variables I am interested in and I am looking at grib tables
correctly.
>
>
>
> param_g2_to_g1:GRIB2 param 0 16 3
not found.
> param_g2_to_g1:GRIB2 param 0 16 201
not found.
> param_g2_to_g1:GRIB2 param 0 1 74
not found.
> param_g2_to_g1:GRIB2 param 0 17 1
not found.
> param_g2_to_g1:GRIB2 param 0 17 1
not found.
> param_g2_to_g1:GRIB2 param 10 191 0
not found.
> param_g2_to_g1:GRIB2 param 10 191 0
not found.
> param_g2_to_g1:GRIB2 param 10 191 0
not found.
> param_g2_to_g1:GRIB2 param 10 191 0
not found.
> param_g2_to_g1:GRIB2 param 10 191 0
not found.
> param_g2_to_g1:GRIB2 param 10 191 0
not found.
> param_g2_to_g1:GRIB2 param 2 0 13
not found.
> param_g2_to_g1:GRIB2 param 0 1 42
not found.
> param_g2_to_g1:GRIB2 param 1 0 6
not found.
> param_g2_to_g1:GRIB2 param 1 0 5
not found.
> param_g2_to_g1:GRIB2 param 0 1 36
not found.
> param_g2_to_g1:GRIB2 param 0 1 35
not found.
> param_g2_to_g1:GRIB2 param 0 1 34
not found.
> param_g2_to_g1:GRIB2 param 0 1 33
not found.
> param_g2_to_g1:GRIB2 param 0 2 30
not found.
> param_g2_to_g1:GRIB2 param 2 0 10
not found.
> param_g2_to_g1:GRIB2 param 0 7 10
not found.
> param_g2_to_g1:GRIB2 param 0 5 4
not found.
> param_g2_to_g1:GRIB2 param 0 4 7
not found.
> param_g2_to_g1:GRIB2 param 0 5 3
not found.
> param_g2_to_g1:GRIB2 param 0 4 8
not found.
> param_g2_to_g1:GRIB2 param 0 5 4
not found.
> param_g2_to_g1:GRIB2 param 0 2 27
not found.
> param_g2_to_g1:GRIB2 param 0 2 28
not found.
> param_g2_to_g1:GRIB2 param 0 3 18
not found.
>
>
> On 20 November 2017 at 09:59, Howard Soh via RT <met_help at ucar.edu>
wrote:
>
>> Hi Emily,
>>
>> John is out of office this week.
>>
>> The main issues are GRIB code and messgae type. The pair was not
>> rejected by QC value.
>>
>> DEBUG 3: Rejected: quality marker = 0
>>
>>
>> I'm sorry if you already did this but I would check
>> 1. MET version
>> 2. the GRIB names at the configuration file
>> 3. the existence of GRIB variables at the forecast file and the
>> observation.
>>
>> It would probably be easiest to have you send us the files. You
>> can post it to our anonymous ftp site following these instructions:
>>
>> http://www.dtcenter.org/met/users/support/met_help.php#ftp
>>
>> Three files: the forecast file, observation file, and configuration
file
>>
>> Please write back once you have posted it, and I'll grab it.
>>
>> Cheers,
>> Howard
>>
>> FYI:
>> The text file (observation data) shows following GRIB codes exist:
>> - code 01: PRES
>> - code 11: TMP
>> - code 52: RH
>> - code 31: WDIR
>> - code 32: WIND
>> - code 180: GUST
>> ==> DPT (code 17 from point_stat config file below) is missing
>>
>>
>> On 11/20/2017 11:02 AM, emily niebuhr via RT wrote:
>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=83072 >
>>>
>>> John,
>>>
>>> Thank you for the fast reply and suggestion, but unfortunately it
did not
>>> work. Taking a fresh Monday look at things, I noticed that many
of the
>>> observations were rejected for GRIB Code or message type. I have
included
>>> my input observations. Do you see something incorrect here? I
put QC
>> as 9
>>> as the tutorial indicated, but maybe this is not appropriate for
this
>> case.
>>> ADPSFC 702730 20171116_000000 61.17 -149.99 46 11 1007.0 46 9
268.15
>>> ADPSFC 702730 20171116_000000 61.17 -149.99 46 52 1007.0 46
9 62.7
>>> ADPSFC 702730 20171116_000000 61.17 -149.99 46 31 1007.0 46
9 -9999
>>> ADPSFC 702730 20171116_000000 61.17 -149.99 46 01 1007.0 46
9
>> 1007.0
>>> ADPSFC 702730 20171116_000000 61.17 -149.99 46 32 1007.0 46
9 -9999
>>> ADPSFC 702730 20171116_000000 61.17 -149.99 46 180 1007.0
46 9
>> -9999
>>> ADPSFC 702730 20171116_000500 61.17 -149.99 46 11 1007.0 46
9
>> 267.15
>>> ADPSFC 702730 20171116_000500 61.17 -149.99 46 52 1007.0 46
9 73.25
>>> ADPSFC 702730 20171116_000500 61.17 -149.99 46 31 1007.0 46
9 -9999
>>>
>>> Processing WIND/Z10 versus WIND/Z10, for observation type
APDSFC, over
>>> region FULL, for interpolation method NEAREST(1), using 0 pairs.
>>> DEBUG 3: Number of matched pairs = 0
>>> DEBUG 3: Observations processed = 2016
>>> DEBUG 3: Rejected: SID exclusion = 0
>>> DEBUG 3: Rejected: GRIB code = 1680
>>> DEBUG 3: Rejected: valid time = 0
>>> DEBUG 3: Rejected: bad obs value = 256
>>> DEBUG 3: Rejected: off the grid = 0
>>> DEBUG 3: Rejected: level mismatch = 0
>>> DEBUG 3: Rejected: quality marker = 0
>>> DEBUG 3: Rejected: message type = 80
>>> DEBUG 3: Rejected: masking region = 0
>>> DEBUG 3: Rejected: bad fcst value = 0
>>> DEBUG 3: Rejected: duplicates = 0
>>>
>>> Processing TMP/Z2 versus TMP/Z2, for observation type APDSFC, over
region
>>> FULL, for interpolation method NEAREST(1), using 0 pairs.
>>> DEBUG 3: Number of matched pairs = 0
>>> DEBUG 3: Observations processed = 2016
>>> DEBUG 3: Rejected: SID exclusion = 0
>>> DEBUG 3: Rejected: GRIB code = 1680
>>> DEBUG 3: Rejected: valid time = 0
>>> DEBUG 3: Rejected: bad obs value = 0
>>> DEBUG 3: Rejected: off the grid = 0
>>> DEBUG 3: Rejected: level mismatch = 0
>>> DEBUG 3: Rejected: quality marker = 0
>>> DEBUG 3: Rejected: message type = 336
>>> DEBUG 3: Rejected: masking region = 0
>>> DEBUG 3: Rejected: bad fcst value = 0
>>> DEBUG 3: Rejected: duplicates = 0
>>>
>>>
>>> On 17 November 2017 at 17:19, John Halley Gotway via RT <
>> met_help at ucar.edu>
>>> wrote:
>>>
>>>> Hi Emily,
>>>>
>>>> That’s great that you ran Point-Stat at verbosity level 3 to dump
out
>> the
>>>> counts for the reasons why observations weren’t used for each
>> verification
>>>> task.
>>>>
>>>> Looking at those counts I see that 42 weren’t used because of
their
>> valid
>>>> time. Mid suggest starting there. Perhaps your observations
aren’t
>> close
>>>> enough in time to your forecast valid time?
>>>>
>>>> One way of testing this would be rerunning point_stat using these
>> command
>>>> line options:
>>>> -obs_valid_beg 20000101 -obs_valid_end 21000101
>>>>
>>>> That tells point-stat to use all obs between the years 2000 and
2100!
>> And
>>>> that should include all of yours.
>>>>
>>>> Once you get some matches pairs, you can decide how you’d really
like to
>>>> set the matching time window for the point obs.
>>>>
>>>> Hope that helps.
>>>>
>>>> Thanks,
>>>> John
>>>>
>>>> On Fri, Nov 17, 2017 at 7:00 PM emily niebuhr via RT
<met_help at ucar.edu
>>>> wrote:
>>>>
>>>>> Fri Nov 17 19:00:18 2017: Request 83072 was acted upon.
>>>>> Transaction: Ticket created by elniebuhr at gmail.com
>>>>> Queue: met_help
>>>>> Subject: Point-Stats Error
>>>>> Owner: Nobody
>>>>> Requestors: elniebuhr at gmail.com
>>>>> Status: new
>>>>> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=83072
>>>>>
>>>>> To whom it may concern,
>>>>>
>>>>> Hopefully this is a small user error that I am encountering, but
I
>> cannot
>>>>> seem to find matches after running point_Stat.Do you know why
the
>>>>> observations may not be matching? I get no errors when I run
ascii2nc
>>>> and
>>>>> I clearly define two points with correct stations and lat/lon.
>>>>>
>>>>>
>>>>> I was wondering if I am possibly having errors since it is polar
>>>> projection
>>>>> or grib2 data. Right away I receive an error about unrecognised
GRIB2
>>>>> field indexes. However I don't think this is the main problem
since I
>>>> still
>>>>> end up with no matching pairs even if I convert it to grib1. The
only
>>>> other
>>>>> thing I can think of is that I incorrectly defined the QC
variable.
>> What
>>>>> value do you suggest?
>>>>>
>>>>> I seem to get similar errors when I try prepbufr files, and if I
try to
>>>>> verify with HRRR or URMA files. Thanks!
>>>>>
>>>>>
>>>>>
>>>>> DEBUG 1: User Config File: nPointStatConfig_default
>>>>> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created
new
>>>>> Met2dDataFile object of type "FileType_Gb2".
>>>>> DEBUG 4: Switching the GRIB2 radius of the earth value of
6371.23 km to
>>>>> 6371.2 km for internal consistency.
>>>>> DEBUG 4:
>>>>> DEBUG 4: Stereographic Grid Data:
>>>>> DEBUG 4: hemisphere: N
>>>>> DEBUG 4: scale_lat: 60
>>>>> DEBUG 4: lat_pin: 41.6129
>>>>> DEBUG 4: lon_pin: 174.883
>>>>> DEBUG 4: x_pin: 0
>>>>> DEBUG 4: y_pin: 0
>>>>> DEBUG 4: lon_orient: 135
>>>>> DEBUG 4: d_km: 3
>>>>> DEBUG 4: r_km: 6371.2
>>>>> DEBUG 4: nx: 1299
>>>>> DEBUG 4: ny: 919
>>>>> DEBUG 4:
>>>>> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
>> GRIB2
>>>>> field indexes - disc: 0, master table: 2, center: 59, local
table: 1,
>>>>> parm_cat: 16, parm: 196
>>>>> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
>> GRIB2
>>>>> field indexes - disc: 0, master table: 2, center: 59, local
table: 1,
>>>>> parm_cat: 16, parm: 201
>>>>> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
>> GRIB2
>>>>> field indexes - disc: 0, master table: 2, center: 59, local
table: 1,
>>>>> parm_cat: 16, parm: 195
>>>>> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
>> GRIB2
>>>>> field indexes - disc: 0, master table: 2, center: 59, local
table: 1,
>>>>> parm_cat: 16, parm: 195
>>>>> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
>> GRIB2
>>>>> field indexes - disc: 0, master table: 2, center: 59, local
table: 1,
>>>>> parm_cat: 16, parm: 195
>>>>>
>>>>>
>>>>> ARNING: Multiple GRIB2 table entries match lookup criteria
(parm_name =
>>>>> GUST):
>>>>> WARNING: parm_name: GUST, index_a = 0, grib2_mtab = 1,
grib2_cntr =
>> 0,
>>>>> grib2_ltab = 0, index_b = 2, index_c = 22
>>>>> WARNING: parm_name: GUST, index_a = 0, grib2_mtab = 14,
grib2_cntr =
>>>> 57,
>>>>> grib2_ltab = 0, index_b = 2, index_c = 22
>>>>> WARNING: Using: parm_name: GUST, index_a = 0, grib2_mtab = 1,
>>>> grib2_cntr
>>>>> = 0, grib2_ltab = 0, index_b = 2, index_c = 22
>>>>>
>>>>>
>>>>> Reading data for TMP/Z2.
>>>>> DEBUG 3: MetGrib2DataFile::data_plane_array() - Found exact
match for
>>>>> "TMP/Z2" in GRIB2 record 59 field 1 of GRIB2 file
"1732021000000.grb2"
>>>>> DEBUG 4:
>>>>> DEBUG 4: Data plane information:
>>>>> DEBUG 4: plane min: 234.527
>>>>> DEBUG 4: plane max: 286.34
>>>>> DEBUG 4: scan mode: 64
>>>>> DEBUG 4: valid time: 20171116_210000
>>>>> DEBUG 4: lead time: 000000
>>>>> DEBUG 4: init time: 20171116_210000
>>>>> DEBUG 4: bitmap flag: 255
>>>>> DEBUG 4:
>>>>> DEBUG 2: For TMP/Z2 found 1 forecast levels and 0 climatology
levels.
>>>>>
>>>>>
>>>>>
>>>>> Processing TMP/Z2 versus TMP/Z2, for observation type APDSFC,
over
>> region
>>>>> FULL, for interpolation method NEAREST(1), using 0 pairs.
>>>>> DEBUG 3: Number of matched pairs = 0
>>>>> DEBUG 3: Observations processed = 210
>>>>> DEBUG 3: Rejected: SID exclusion = 0
>>>>> DEBUG 3: Rejected: GRIB code = 168
>>>>> DEBUG 3: Rejected: valid time = 42
>>>>> DEBUG 3: Rejected: bad obs value = 0
>>>>> DEBUG 3: Rejected: off the grid = 0
>>>>> DEBUG 3: Rejected: level mismatch = 0
>>>>> DEBUG 3: Rejected: quality marker = 0
>>>>> DEBUG 3: Rejected: message type = 0
>>>>> DEBUG 3: Rejected: masking region = 0
>>>>> DEBUG 3: Rejected: bad fcst value = 0
>>>>> DEBUG 3: Rejected: duplicates = 0
>>>>> DEBUG 2:
>>>>>
>>>>>
>>>>> Config file:
>>>>>
>>>>> /
>>>>> // Verification grid
>>>>> //
>>>>> regrid = {
>>>>> to_grid = NONE;
>>>>> method = NEAREST;
>>>>> width = 1;
>>>>> vld_thresh = 0.5;
>>>>> }
>>>>>
>>>>>
>>>>> ////////////////////////////////////////////////////////////
>>>> ////////////////////
>>>>> cat_thresh = [ NA ];
>>>>> cnt_thresh = [ NA ];
>>>>> cnt_logic = UNION;
>>>>> wind_thresh = [ NA ];
>>>>> wind_logic = UNION;
>>>>>
>>>>> //
>>>>> // Forecast and observation fields to be verified
>>>>> //
>>>>>
>>>>> // Gust height unclear assumed 10 m like wind
>>>>> fcst = {
>>>>> field = [
>>>>>
>>>>> {
>>>>> name = "GUST";
>>>>> level = [ "Z10" ];
>>>>> cat_thresh = [ >5.0 ];
>>>>> },
>>>>>
>>>>>
>>>>>
>>>>> {
>>>>> name = "DPT";
>>>>> level = [ "Z2" ];
>>>>> cat_thresh = [ >-100.0 ];
>>>>> },
>>>>>
>>>>> {
>>>>> name = "TMP";
>>>>> level = [ "Z2" ];
>>>>> cat_thresh = [ >-100.0 ];
>>>>> },
>>>>> {
>>>>> name = "WIND";
>>>>> level = [ "Z10" ];
>>>>> cat_thresh = [ >0.0 ];
>>>>> }
>>>>>
>>>>> obs = fcst;
>>>>>
>>>>>
>>>>> ////////////////////////////////////////////////////////////
>>>> ////////////////////
>>>>> //
>>>>> // Point observation filtering options
>>>>> // May be set separately in each "obs.field" entry
>>>>> //
>>>>> message_type = ["APDSFC"];
>>>>> sid_exc = [];
>>>>> obs_quality = [];
>>>>> duplicate_flag = NONE;
>>>>> obs_summary = NONE;
>>>>> obs_perc_value = 50;
>>>>>
>>>>>
>>>>> ////////////////////////////////////////////////////////////
>>>> ////////////////////
>>>>> //
>>>>> // Climatology mean data
>>>>> //
>>>>> climo_mean = {
>>>>>
>>>>> file_name = [];
>>>>> field = [];
>>>>>
>>>>> regrid = {
>>>>> method = NEAREST;
>>>>> width = 1;
>>>>> vld_thresh = 0.5;
>>>>> }
>>>>>
>>>>> time_interp_method = DW_MEAN;
>>>>> match_day = FALSE;
>>>>> time_step = 21600;
>>>>> }
>>>>>
>>>>>
>>>>> ////////////////////////////////////////////////////////////
>>>> ////////////////////
>>>>> //
>>>>> // Point observation time window
>>>>> //
>>>>> obs_window = {
>>>>> beg = -54000;
>>>>> end = 54000;
>>>>>
>>>>> // Verification masking regions
>>>>> //
>>>>> mask = {
>>>>> grid = [ "FULL" ];
>>>>> poly = [];
>>>>> sid = [];
>>>>> }
>>>>>
>>>>>
>>>>> ////////////////////////////////////////////////////////////
>>>> ////////////////////
>>>>> //
>>>>> // Confidence interval settings
>>>>> //
>>>>> ci_alpha = [ 0.05 ];
>>>>>
>>>>> boot = {
>>>>> interval = PCTILE;
>>>>> rep_prop = 1.0;
>>>>> n_rep = 0;
>>>>> rng = "mt19937";
>>>>> seed = "";
>>>>> }
>>>>>
>>>>>
>>
>>
------------------------------------------------
Subject: Point-Stats Error
From: emily niebuhr
Time: Wed Nov 22 16:18:22 2017
Oh no all that work for a typo! Thank you for all your help!
Sincerely,
Emily
On 22 November 2017 at 07:12, Howard Soh via RT <met_help at ucar.edu>
wrote:
>
> "APDSFC" VS. "ADPSFC"
>
> Would you change the message type at nPointStatConfig_default.txt to
> "ADPSFC"? The message type in the config file is "APDSFC" and the
> message type in ascii2nc output All_outpl7.nc is "ADPSFC".
>
> I got these numbers with 1732021000000.grb1 and All_outpl7.nc:
>
> DEBUG 2: Processing DPT/Z2 versus DPT/Z2, for observation type
ADPSFC,
> over region FULL, for interpolation method NEAREST(1), using 0
pairs.
> DEBUG 2: Processing TMP/Z2 versus TMP/Z2, for observation type
ADPSFC,
> over region FULL, for interpolation method NEAREST(1), using 225
pairs.
> DEBUG 2: Processing WIND/Z10 versus WIND/Z10, for observation type
> ADPSFC, over region FULL, for interpolation method NEAREST(1), using
56
> pairs.
>
> Cheers,
> Howard
>
> FYI:
>
> At the All_outpl7.nc:
> - there are 6 variables with 336 observations: 2016
observations (
> 336 * 6)
>
> Processing WIND/Z10 versus WIND/Z10, for observation type APDSFC,
over
> region FULL, for interpolation method NEAREST(1), using 0 pairs.
>
> DEBUG 3: Observations processed = 2016
> DEBUG 3: Rejected: GRIB code = 1680
> DEBUG 3: Rejected: bad obs value = 256
> DEBUG 3: Rejected: message type = 80
>
> Get variable, WIND: 2016 - 336 = 1680
> ==> 1680 are rejected because they are not WIND
> Filter by missing value or bad value: 256
> ==> valid WIND obs. is 80 (= 336 - 256)
> The 80 data was rejected by message type (not "ADPSFC")
>
>
> Variable names from the config files:
> fcst: GUST, DPT, TMP, WIND
>
> Variable count from 1732021000000.grb1:
> - GUST: 1
> - DPT: 1
> - TMP:2
> - UGRD nd VGRD: 2
> - Obs time: 17111621 ==> 1 matching obs time ("20171116_030000")
from
> All_outpl7.nc
> - location: Lat1 41.612000 Long1 185.117000 Orient 225.000000
>
> Variable count from akurma.t04z.2dvarges_ndfd_3p0.grb11
> - GUST: 1
> - DPT: 1
> - TMP: 1
> - UGRD nd VGRD: 1
> - Obs time: 17111603 ==> 1 matching obs time ("20171116_030000")
from
> All_outpl7.nc
> - location: Lat1 40.530000 Long1 -178.571000
>
> Varibales and count from All_outpl7.nc
> - message type:"ADPSFC"
> - 336 observations for each variables: PRES, TMP, RH, ,WDIR, WIND,
and GUST
> - Obs time: 20170111_000130 to "20171116_225000" (1 or 2 obs for
each time)
> - Locations:
> 61.17, -149.99, 46 : 303 headers,
> 61.32, -150.09, 109 : 33 headers
>
>
> On 11/21/2017 5:48 PM, emily niebuhr via RT wrote:
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=83072 >
> >
> > Thank you for the help Howard- I have shared my files! I even
double
> > checked my g2lib errors and none of them are any of the variables
that I
> > use for Point_Stat - i.e. none of them are TMP etc. So I have run
out of
> > ideas since I have similar Point Stat errors for BUFR. Thank you
for your
> > help!
> >
> > Just in case, I receive the following error for HRRR files but not
for
> URMA
> > when I run cnvgrib, which varifies to me that these errors are not
the
> > variables I am interested in and I am looking at grib tables
correctly.
> >
> >
> >
> > param_g2_to_g1:GRIB2 param 0 16 3
not
> found.
> > param_g2_to_g1:GRIB2 param 0 16 201
not
> found.
> > param_g2_to_g1:GRIB2 param 0 1 74
not
> found.
> > param_g2_to_g1:GRIB2 param 0 17 1
not
> found.
> > param_g2_to_g1:GRIB2 param 0 17 1
not
> found.
> > param_g2_to_g1:GRIB2 param 10 191 0
not
> found.
> > param_g2_to_g1:GRIB2 param 10 191 0
not
> found.
> > param_g2_to_g1:GRIB2 param 10 191 0
not
> found.
> > param_g2_to_g1:GRIB2 param 10 191 0
not
> found.
> > param_g2_to_g1:GRIB2 param 10 191 0
not
> found.
> > param_g2_to_g1:GRIB2 param 10 191 0
not
> found.
> > param_g2_to_g1:GRIB2 param 2 0 13
not
> found.
> > param_g2_to_g1:GRIB2 param 0 1 42
not
> found.
> > param_g2_to_g1:GRIB2 param 1 0 6
not
> found.
> > param_g2_to_g1:GRIB2 param 1 0 5
not
> found.
> > param_g2_to_g1:GRIB2 param 0 1 36
not
> found.
> > param_g2_to_g1:GRIB2 param 0 1 35
not
> found.
> > param_g2_to_g1:GRIB2 param 0 1 34
not
> found.
> > param_g2_to_g1:GRIB2 param 0 1 33
not
> found.
> > param_g2_to_g1:GRIB2 param 0 2 30
not
> found.
> > param_g2_to_g1:GRIB2 param 2 0 10
not
> found.
> > param_g2_to_g1:GRIB2 param 0 7 10
not
> found.
> > param_g2_to_g1:GRIB2 param 0 5 4
not
> found.
> > param_g2_to_g1:GRIB2 param 0 4 7
not
> found.
> > param_g2_to_g1:GRIB2 param 0 5 3
not
> found.
> > param_g2_to_g1:GRIB2 param 0 4 8
not
> found.
> > param_g2_to_g1:GRIB2 param 0 5 4
not
> found.
> > param_g2_to_g1:GRIB2 param 0 2 27
not
> found.
> > param_g2_to_g1:GRIB2 param 0 2 28
not
> found.
> > param_g2_to_g1:GRIB2 param 0 3 18
not
> found.
> >
> >
> > On 20 November 2017 at 09:59, Howard Soh via RT
<met_help at ucar.edu>
> wrote:
> >
> >> Hi Emily,
> >>
> >> John is out of office this week.
> >>
> >> The main issues are GRIB code and messgae type. The pair was not
> >> rejected by QC value.
> >>
> >> DEBUG 3: Rejected: quality marker = 0
> >>
> >>
> >> I'm sorry if you already did this but I would check
> >> 1. MET version
> >> 2. the GRIB names at the configuration file
> >> 3. the existence of GRIB variables at the forecast file and the
> >> observation.
> >>
> >> It would probably be easiest to have you send us the files. You
> >> can post it to our anonymous ftp site following these
instructions:
> >>
> >> http://www.dtcenter.org/met/users/support/met_help.php#ftp
> >>
> >> Three files: the forecast file, observation file, and
configuration file
> >>
> >> Please write back once you have posted it, and I'll grab it.
> >>
> >> Cheers,
> >> Howard
> >>
> >> FYI:
> >> The text file (observation data) shows following GRIB codes
exist:
> >> - code 01: PRES
> >> - code 11: TMP
> >> - code 52: RH
> >> - code 31: WDIR
> >> - code 32: WIND
> >> - code 180: GUST
> >> ==> DPT (code 17 from point_stat config file below) is missing
> >>
> >>
> >> On 11/20/2017 11:02 AM, emily niebuhr via RT wrote:
> >>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=83072 >
> >>>
> >>> John,
> >>>
> >>> Thank you for the fast reply and suggestion, but unfortunately
it did
> not
> >>> work. Taking a fresh Monday look at things, I noticed that many
of the
> >>> observations were rejected for GRIB Code or message type. I have
> included
> >>> my input observations. Do you see something incorrect here? I
put QC
> >> as 9
> >>> as the tutorial indicated, but maybe this is not appropriate for
this
> >> case.
> >>> ADPSFC 702730 20171116_000000 61.17 -149.99 46 11 1007.0 46
9
> 268.15
> >>> ADPSFC 702730 20171116_000000 61.17 -149.99 46 52 1007.0
46 9
> 62.7
> >>> ADPSFC 702730 20171116_000000 61.17 -149.99 46 31 1007.0
46 9
> -9999
> >>> ADPSFC 702730 20171116_000000 61.17 -149.99 46 01 1007.0
46 9
> >> 1007.0
> >>> ADPSFC 702730 20171116_000000 61.17 -149.99 46 32 1007.0
46 9
> -9999
> >>> ADPSFC 702730 20171116_000000 61.17 -149.99 46 180 1007.0
46 9
> >> -9999
> >>> ADPSFC 702730 20171116_000500 61.17 -149.99 46 11 1007.0
46 9
> >> 267.15
> >>> ADPSFC 702730 20171116_000500 61.17 -149.99 46 52 1007.0
46 9
> 73.25
> >>> ADPSFC 702730 20171116_000500 61.17 -149.99 46 31 1007.0
46 9
> -9999
> >>>
> >>> Processing WIND/Z10 versus WIND/Z10, for observation type
APDSFC,
> over
> >>> region FULL, for interpolation method NEAREST(1), using 0 pairs.
> >>> DEBUG 3: Number of matched pairs = 0
> >>> DEBUG 3: Observations processed = 2016
> >>> DEBUG 3: Rejected: SID exclusion = 0
> >>> DEBUG 3: Rejected: GRIB code = 1680
> >>> DEBUG 3: Rejected: valid time = 0
> >>> DEBUG 3: Rejected: bad obs value = 256
> >>> DEBUG 3: Rejected: off the grid = 0
> >>> DEBUG 3: Rejected: level mismatch = 0
> >>> DEBUG 3: Rejected: quality marker = 0
> >>> DEBUG 3: Rejected: message type = 80
> >>> DEBUG 3: Rejected: masking region = 0
> >>> DEBUG 3: Rejected: bad fcst value = 0
> >>> DEBUG 3: Rejected: duplicates = 0
> >>>
> >>> Processing TMP/Z2 versus TMP/Z2, for observation type APDSFC,
over
> region
> >>> FULL, for interpolation method NEAREST(1), using 0 pairs.
> >>> DEBUG 3: Number of matched pairs = 0
> >>> DEBUG 3: Observations processed = 2016
> >>> DEBUG 3: Rejected: SID exclusion = 0
> >>> DEBUG 3: Rejected: GRIB code = 1680
> >>> DEBUG 3: Rejected: valid time = 0
> >>> DEBUG 3: Rejected: bad obs value = 0
> >>> DEBUG 3: Rejected: off the grid = 0
> >>> DEBUG 3: Rejected: level mismatch = 0
> >>> DEBUG 3: Rejected: quality marker = 0
> >>> DEBUG 3: Rejected: message type = 336
> >>> DEBUG 3: Rejected: masking region = 0
> >>> DEBUG 3: Rejected: bad fcst value = 0
> >>> DEBUG 3: Rejected: duplicates = 0
> >>>
> >>>
> >>> On 17 November 2017 at 17:19, John Halley Gotway via RT <
> >> met_help at ucar.edu>
> >>> wrote:
> >>>
> >>>> Hi Emily,
> >>>>
> >>>> That’s great that you ran Point-Stat at verbosity level 3 to
dump out
> >> the
> >>>> counts for the reasons why observations weren’t used for each
> >> verification
> >>>> task.
> >>>>
> >>>> Looking at those counts I see that 42 weren’t used because of
their
> >> valid
> >>>> time. Mid suggest starting there. Perhaps your observations
aren’t
> >> close
> >>>> enough in time to your forecast valid time?
> >>>>
> >>>> One way of testing this would be rerunning point_stat using
these
> >> command
> >>>> line options:
> >>>> -obs_valid_beg 20000101 -obs_valid_end 21000101
> >>>>
> >>>> That tells point-stat to use all obs between the years 2000 and
2100!
> >> And
> >>>> that should include all of yours.
> >>>>
> >>>> Once you get some matches pairs, you can decide how you’d
really like
> to
> >>>> set the matching time window for the point obs.
> >>>>
> >>>> Hope that helps.
> >>>>
> >>>> Thanks,
> >>>> John
> >>>>
> >>>> On Fri, Nov 17, 2017 at 7:00 PM emily niebuhr via RT <
> met_help at ucar.edu
> >>>> wrote:
> >>>>
> >>>>> Fri Nov 17 19:00:18 2017: Request 83072 was acted upon.
> >>>>> Transaction: Ticket created by elniebuhr at gmail.com
> >>>>> Queue: met_help
> >>>>> Subject: Point-Stats Error
> >>>>> Owner: Nobody
> >>>>> Requestors: elniebuhr at gmail.com
> >>>>> Status: new
> >>>>> Ticket <URL: https://rt.rap.ucar.edu/rt/
> Ticket/Display.html?id=83072
> >>>>>
> >>>>> To whom it may concern,
> >>>>>
> >>>>> Hopefully this is a small user error that I am encountering,
but I
> >> cannot
> >>>>> seem to find matches after running point_Stat.Do you know why
the
> >>>>> observations may not be matching? I get no errors when I run
> ascii2nc
> >>>> and
> >>>>> I clearly define two points with correct stations and lat/lon.
> >>>>>
> >>>>>
> >>>>> I was wondering if I am possibly having errors since it is
polar
> >>>> projection
> >>>>> or grib2 data. Right away I receive an error about
unrecognised
> GRIB2
> >>>>> field indexes. However I don't think this is the main problem
since I
> >>>> still
> >>>>> end up with no matching pairs even if I convert it to grib1.
The only
> >>>> other
> >>>>> thing I can think of is that I incorrectly defined the QC
variable.
> >> What
> >>>>> value do you suggest?
> >>>>>
> >>>>> I seem to get similar errors when I try prepbufr files, and if
I try
> to
> >>>>> verify with HRRR or URMA files. Thanks!
> >>>>>
> >>>>>
> >>>>>
> >>>>> DEBUG 1: User Config File: nPointStatConfig_default
> >>>>> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() ->
created new
> >>>>> Met2dDataFile object of type "FileType_Gb2".
> >>>>> DEBUG 4: Switching the GRIB2 radius of the earth value of
6371.23 km
> to
> >>>>> 6371.2 km for internal consistency.
> >>>>> DEBUG 4:
> >>>>> DEBUG 4: Stereographic Grid Data:
> >>>>> DEBUG 4: hemisphere: N
> >>>>> DEBUG 4: scale_lat: 60
> >>>>> DEBUG 4: lat_pin: 41.6129
> >>>>> DEBUG 4: lon_pin: 174.883
> >>>>> DEBUG 4: x_pin: 0
> >>>>> DEBUG 4: y_pin: 0
> >>>>> DEBUG 4: lon_orient: 135
> >>>>> DEBUG 4: d_km: 3
> >>>>> DEBUG 4: r_km: 6371.2
> >>>>> DEBUG 4: nx: 1299
> >>>>> DEBUG 4: ny: 919
> >>>>> DEBUG 4:
> >>>>> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> >> GRIB2
> >>>>> field indexes - disc: 0, master table: 2, center: 59, local
table: 1,
> >>>>> parm_cat: 16, parm: 196
> >>>>> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> >> GRIB2
> >>>>> field indexes - disc: 0, master table: 2, center: 59, local
table: 1,
> >>>>> parm_cat: 16, parm: 201
> >>>>> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> >> GRIB2
> >>>>> field indexes - disc: 0, master table: 2, center: 59, local
table: 1,
> >>>>> parm_cat: 16, parm: 195
> >>>>> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> >> GRIB2
> >>>>> field indexes - disc: 0, master table: 2, center: 59, local
table: 1,
> >>>>> parm_cat: 16, parm: 195
> >>>>> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
> >> GRIB2
> >>>>> field indexes - disc: 0, master table: 2, center: 59, local
table: 1,
> >>>>> parm_cat: 16, parm: 195
> >>>>>
> >>>>>
> >>>>> ARNING: Multiple GRIB2 table entries match lookup criteria
> (parm_name =
> >>>>> GUST):
> >>>>> WARNING: parm_name: GUST, index_a = 0, grib2_mtab = 1,
grib2_cntr =
> >> 0,
> >>>>> grib2_ltab = 0, index_b = 2, index_c = 22
> >>>>> WARNING: parm_name: GUST, index_a = 0, grib2_mtab = 14,
grib2_cntr
> =
> >>>> 57,
> >>>>> grib2_ltab = 0, index_b = 2, index_c = 22
> >>>>> WARNING: Using: parm_name: GUST, index_a = 0, grib2_mtab =
1,
> >>>> grib2_cntr
> >>>>> = 0, grib2_ltab = 0, index_b = 2, index_c = 22
> >>>>>
> >>>>>
> >>>>> Reading data for TMP/Z2.
> >>>>> DEBUG 3: MetGrib2DataFile::data_plane_array() - Found exact
match
> for
> >>>>> "TMP/Z2" in GRIB2 record 59 field 1 of GRIB2 file
> "1732021000000.grb2"
> >>>>> DEBUG 4:
> >>>>> DEBUG 4: Data plane information:
> >>>>> DEBUG 4: plane min: 234.527
> >>>>> DEBUG 4: plane max: 286.34
> >>>>> DEBUG 4: scan mode: 64
> >>>>> DEBUG 4: valid time: 20171116_210000
> >>>>> DEBUG 4: lead time: 000000
> >>>>> DEBUG 4: init time: 20171116_210000
> >>>>> DEBUG 4: bitmap flag: 255
> >>>>> DEBUG 4:
> >>>>> DEBUG 2: For TMP/Z2 found 1 forecast levels and 0 climatology
levels.
> >>>>>
> >>>>>
> >>>>>
> >>>>> Processing TMP/Z2 versus TMP/Z2, for observation type APDSFC,
over
> >> region
> >>>>> FULL, for interpolation method NEAREST(1), using 0 pairs.
> >>>>> DEBUG 3: Number of matched pairs = 0
> >>>>> DEBUG 3: Observations processed = 210
> >>>>> DEBUG 3: Rejected: SID exclusion = 0
> >>>>> DEBUG 3: Rejected: GRIB code = 168
> >>>>> DEBUG 3: Rejected: valid time = 42
> >>>>> DEBUG 3: Rejected: bad obs value = 0
> >>>>> DEBUG 3: Rejected: off the grid = 0
> >>>>> DEBUG 3: Rejected: level mismatch = 0
> >>>>> DEBUG 3: Rejected: quality marker = 0
> >>>>> DEBUG 3: Rejected: message type = 0
> >>>>> DEBUG 3: Rejected: masking region = 0
> >>>>> DEBUG 3: Rejected: bad fcst value = 0
> >>>>> DEBUG 3: Rejected: duplicates = 0
> >>>>> DEBUG 2:
> >>>>>
> >>>>>
> >>>>> Config file:
> >>>>>
> >>>>> /
> >>>>> // Verification grid
> >>>>> //
> >>>>> regrid = {
> >>>>> to_grid = NONE;
> >>>>> method = NEAREST;
> >>>>> width = 1;
> >>>>> vld_thresh = 0.5;
> >>>>> }
> >>>>>
> >>>>>
> >>>>> ////////////////////////////////////////////////////////////
> >>>> ////////////////////
> >>>>> cat_thresh = [ NA ];
> >>>>> cnt_thresh = [ NA ];
> >>>>> cnt_logic = UNION;
> >>>>> wind_thresh = [ NA ];
> >>>>> wind_logic = UNION;
> >>>>>
> >>>>> //
> >>>>> // Forecast and observation fields to be verified
> >>>>> //
> >>>>>
> >>>>> // Gust height unclear assumed 10 m like wind
> >>>>> fcst = {
> >>>>> field = [
> >>>>>
> >>>>> {
> >>>>> name = "GUST";
> >>>>> level = [ "Z10" ];
> >>>>> cat_thresh = [ >5.0 ];
> >>>>> },
> >>>>>
> >>>>>
> >>>>>
> >>>>> {
> >>>>> name = "DPT";
> >>>>> level = [ "Z2" ];
> >>>>> cat_thresh = [ >-100.0 ];
> >>>>> },
> >>>>>
> >>>>> {
> >>>>> name = "TMP";
> >>>>> level = [ "Z2" ];
> >>>>> cat_thresh = [ >-100.0 ];
> >>>>> },
> >>>>> {
> >>>>> name = "WIND";
> >>>>> level = [ "Z10" ];
> >>>>> cat_thresh = [ >0.0 ];
> >>>>> }
> >>>>>
> >>>>> obs = fcst;
> >>>>>
> >>>>>
> >>>>> ////////////////////////////////////////////////////////////
> >>>> ////////////////////
> >>>>> //
> >>>>> // Point observation filtering options
> >>>>> // May be set separately in each "obs.field" entry
> >>>>> //
> >>>>> message_type = ["APDSFC"];
> >>>>> sid_exc = [];
> >>>>> obs_quality = [];
> >>>>> duplicate_flag = NONE;
> >>>>> obs_summary = NONE;
> >>>>> obs_perc_value = 50;
> >>>>>
> >>>>>
> >>>>> ////////////////////////////////////////////////////////////
> >>>> ////////////////////
> >>>>> //
> >>>>> // Climatology mean data
> >>>>> //
> >>>>> climo_mean = {
> >>>>>
> >>>>> file_name = [];
> >>>>> field = [];
> >>>>>
> >>>>> regrid = {
> >>>>> method = NEAREST;
> >>>>> width = 1;
> >>>>> vld_thresh = 0.5;
> >>>>> }
> >>>>>
> >>>>> time_interp_method = DW_MEAN;
> >>>>> match_day = FALSE;
> >>>>> time_step = 21600;
> >>>>> }
> >>>>>
> >>>>>
> >>>>> ////////////////////////////////////////////////////////////
> >>>> ////////////////////
> >>>>> //
> >>>>> // Point observation time window
> >>>>> //
> >>>>> obs_window = {
> >>>>> beg = -54000;
> >>>>> end = 54000;
> >>>>>
> >>>>> // Verification masking regions
> >>>>> //
> >>>>> mask = {
> >>>>> grid = [ "FULL" ];
> >>>>> poly = [];
> >>>>> sid = [];
> >>>>> }
> >>>>>
> >>>>>
> >>>>> ////////////////////////////////////////////////////////////
> >>>> ////////////////////
> >>>>> //
> >>>>> // Confidence interval settings
> >>>>> //
> >>>>> ci_alpha = [ 0.05 ];
> >>>>>
> >>>>> boot = {
> >>>>> interval = PCTILE;
> >>>>> rep_prop = 1.0;
> >>>>> n_rep = 0;
> >>>>> rng = "mt19937";
> >>>>> seed = "";
> >>>>> }
> >>>>>
> >>>>>
> >>
> >>
>
>
>
------------------------------------------------
Subject: Re: [rt.rap.ucar.edu #83072] Point-Stats Error
From: Howard Soh
Time: Wed Nov 22 16:35:48 2017
I will close the ticket if no more issues.
Cheers,
Howard
On 11/22/2017 4:18 PM, emily niebuhr via RT wrote:
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=83072 >
>
> Oh no all that work for a typo! Thank you for all your help!
>
> Sincerely,
> Emily
>
> On 22 November 2017 at 07:12, Howard Soh via RT <met_help at ucar.edu>
wrote:
>
>> "APDSFC" VS. "ADPSFC"
>>
>> Would you change the message type at nPointStatConfig_default.txt
to
>> "ADPSFC"? The message type in the config file is "APDSFC" and the
>> message type in ascii2nc output All_outpl7.nc is "ADPSFC".
>>
>> I got these numbers with 1732021000000.grb1 and All_outpl7.nc:
>>
>> DEBUG 2: Processing DPT/Z2 versus DPT/Z2, for observation type
ADPSFC,
>> over region FULL, for interpolation method NEAREST(1), using 0
pairs.
>> DEBUG 2: Processing TMP/Z2 versus TMP/Z2, for observation type
ADPSFC,
>> over region FULL, for interpolation method NEAREST(1), using 225
pairs.
>> DEBUG 2: Processing WIND/Z10 versus WIND/Z10, for observation type
>> ADPSFC, over region FULL, for interpolation method NEAREST(1),
using 56
>> pairs.
>>
>> Cheers,
>> Howard
>>
>> FYI:
>>
>> At the All_outpl7.nc:
>> - there are 6 variables with 336 observations: 2016
observations (
>> 336 * 6)
>>
>> Processing WIND/Z10 versus WIND/Z10, for observation type
APDSFC, over
>> region FULL, for interpolation method NEAREST(1), using 0 pairs.
>>
>> DEBUG 3: Observations processed = 2016
>> DEBUG 3: Rejected: GRIB code = 1680
>> DEBUG 3: Rejected: bad obs value = 256
>> DEBUG 3: Rejected: message type = 80
>>
>> Get variable, WIND: 2016 - 336 = 1680
>> ==> 1680 are rejected because they are not WIND
>> Filter by missing value or bad value: 256
>> ==> valid WIND obs. is 80 (= 336 - 256)
>> The 80 data was rejected by message type (not "ADPSFC")
>>
>>
>> Variable names from the config files:
>> fcst: GUST, DPT, TMP, WIND
>>
>> Variable count from 1732021000000.grb1:
>> - GUST: 1
>> - DPT: 1
>> - TMP:2
>> - UGRD nd VGRD: 2
>> - Obs time: 17111621 ==> 1 matching obs time ("20171116_030000")
from
>> All_outpl7.nc
>> - location: Lat1 41.612000 Long1 185.117000 Orient 225.000000
>>
>> Variable count from akurma.t04z.2dvarges_ndfd_3p0.grb11
>> - GUST: 1
>> - DPT: 1
>> - TMP: 1
>> - UGRD nd VGRD: 1
>> - Obs time: 17111603 ==> 1 matching obs time ("20171116_030000")
from
>> All_outpl7.nc
>> - location: Lat1 40.530000 Long1 -178.571000
>>
>> Varibales and count from All_outpl7.nc
>> - message type:"ADPSFC"
>> - 336 observations for each variables: PRES, TMP, RH, ,WDIR, WIND,
and GUST
>> - Obs time: 20170111_000130 to "20171116_225000" (1 or 2 obs for
each time)
>> - Locations:
>> 61.17, -149.99, 46 : 303 headers,
>> 61.32, -150.09, 109 : 33 headers
>>
>>
>> On 11/21/2017 5:48 PM, emily niebuhr via RT wrote:
>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=83072 >
>>>
>>> Thank you for the help Howard- I have shared my files! I even
double
>>> checked my g2lib errors and none of them are any of the variables
that I
>>> use for Point_Stat - i.e. none of them are TMP etc. So I have run
out of
>>> ideas since I have similar Point Stat errors for BUFR. Thank you
for your
>>> help!
>>>
>>> Just in case, I receive the following error for HRRR files but not
for
>> URMA
>>> when I run cnvgrib, which varifies to me that these errors are not
the
>>> variables I am interested in and I am looking at grib tables
correctly.
>>>
>>>
>>>
>>> param_g2_to_g1:GRIB2 param 0 16 3
not
>> found.
>>> param_g2_to_g1:GRIB2 param 0 16 201
not
>> found.
>>> param_g2_to_g1:GRIB2 param 0 1 74
not
>> found.
>>> param_g2_to_g1:GRIB2 param 0 17 1
not
>> found.
>>> param_g2_to_g1:GRIB2 param 0 17 1
not
>> found.
>>> param_g2_to_g1:GRIB2 param 10 191 0
not
>> found.
>>> param_g2_to_g1:GRIB2 param 10 191 0
not
>> found.
>>> param_g2_to_g1:GRIB2 param 10 191 0
not
>> found.
>>> param_g2_to_g1:GRIB2 param 10 191 0
not
>> found.
>>> param_g2_to_g1:GRIB2 param 10 191 0
not
>> found.
>>> param_g2_to_g1:GRIB2 param 10 191 0
not
>> found.
>>> param_g2_to_g1:GRIB2 param 2 0 13
not
>> found.
>>> param_g2_to_g1:GRIB2 param 0 1 42
not
>> found.
>>> param_g2_to_g1:GRIB2 param 1 0 6
not
>> found.
>>> param_g2_to_g1:GRIB2 param 1 0 5
not
>> found.
>>> param_g2_to_g1:GRIB2 param 0 1 36
not
>> found.
>>> param_g2_to_g1:GRIB2 param 0 1 35
not
>> found.
>>> param_g2_to_g1:GRIB2 param 0 1 34
not
>> found.
>>> param_g2_to_g1:GRIB2 param 0 1 33
not
>> found.
>>> param_g2_to_g1:GRIB2 param 0 2 30
not
>> found.
>>> param_g2_to_g1:GRIB2 param 2 0 10
not
>> found.
>>> param_g2_to_g1:GRIB2 param 0 7 10
not
>> found.
>>> param_g2_to_g1:GRIB2 param 0 5 4
not
>> found.
>>> param_g2_to_g1:GRIB2 param 0 4 7
not
>> found.
>>> param_g2_to_g1:GRIB2 param 0 5 3
not
>> found.
>>> param_g2_to_g1:GRIB2 param 0 4 8
not
>> found.
>>> param_g2_to_g1:GRIB2 param 0 5 4
not
>> found.
>>> param_g2_to_g1:GRIB2 param 0 2 27
not
>> found.
>>> param_g2_to_g1:GRIB2 param 0 2 28
not
>> found.
>>> param_g2_to_g1:GRIB2 param 0 3 18
not
>> found.
>>>
>>> On 20 November 2017 at 09:59, Howard Soh via RT
<met_help at ucar.edu>
>> wrote:
>>>> Hi Emily,
>>>>
>>>> John is out of office this week.
>>>>
>>>> The main issues are GRIB code and messgae type. The pair was not
>>>> rejected by QC value.
>>>>
>>>> DEBUG 3: Rejected: quality marker = 0
>>>>
>>>>
>>>> I'm sorry if you already did this but I would check
>>>> 1. MET version
>>>> 2. the GRIB names at the configuration file
>>>> 3. the existence of GRIB variables at the forecast file and the
>>>> observation.
>>>>
>>>> It would probably be easiest to have you send us the files. You
>>>> can post it to our anonymous ftp site following these
instructions:
>>>>
>>>> http://www.dtcenter.org/met/users/support/met_help.php#ftp
>>>>
>>>> Three files: the forecast file, observation file, and
configuration file
>>>>
>>>> Please write back once you have posted it, and I'll grab it.
>>>>
>>>> Cheers,
>>>> Howard
>>>>
>>>> FYI:
>>>> The text file (observation data) shows following GRIB codes
exist:
>>>> - code 01: PRES
>>>> - code 11: TMP
>>>> - code 52: RH
>>>> - code 31: WDIR
>>>> - code 32: WIND
>>>> - code 180: GUST
>>>> ==> DPT (code 17 from point_stat config file below) is missing
>>>>
>>>>
>>>> On 11/20/2017 11:02 AM, emily niebuhr via RT wrote:
>>>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=83072 >
>>>>>
>>>>> John,
>>>>>
>>>>> Thank you for the fast reply and suggestion, but unfortunately
it did
>> not
>>>>> work. Taking a fresh Monday look at things, I noticed that many
of the
>>>>> observations were rejected for GRIB Code or message type. I have
>> included
>>>>> my input observations. Do you see something incorrect here? I
put QC
>>>> as 9
>>>>> as the tutorial indicated, but maybe this is not appropriate for
this
>>>> case.
>>>>> ADPSFC 702730 20171116_000000 61.17 -149.99 46 11 1007.0 46
9
>> 268.15
>>>>> ADPSFC 702730 20171116_000000 61.17 -149.99 46 52 1007.0
46 9
>> 62.7
>>>>> ADPSFC 702730 20171116_000000 61.17 -149.99 46 31 1007.0
46 9
>> -9999
>>>>> ADPSFC 702730 20171116_000000 61.17 -149.99 46 01 1007.0
46 9
>>>> 1007.0
>>>>> ADPSFC 702730 20171116_000000 61.17 -149.99 46 32 1007.0
46 9
>> -9999
>>>>> ADPSFC 702730 20171116_000000 61.17 -149.99 46 180
1007.0 46 9
>>>> -9999
>>>>> ADPSFC 702730 20171116_000500 61.17 -149.99 46 11 1007.0
46 9
>>>> 267.15
>>>>> ADPSFC 702730 20171116_000500 61.17 -149.99 46 52 1007.0
46 9
>> 73.25
>>>>> ADPSFC 702730 20171116_000500 61.17 -149.99 46 31 1007.0
46 9
>> -9999
>>>>> Processing WIND/Z10 versus WIND/Z10, for observation type
APDSFC,
>> over
>>>>> region FULL, for interpolation method NEAREST(1), using 0 pairs.
>>>>> DEBUG 3: Number of matched pairs = 0
>>>>> DEBUG 3: Observations processed = 2016
>>>>> DEBUG 3: Rejected: SID exclusion = 0
>>>>> DEBUG 3: Rejected: GRIB code = 1680
>>>>> DEBUG 3: Rejected: valid time = 0
>>>>> DEBUG 3: Rejected: bad obs value = 256
>>>>> DEBUG 3: Rejected: off the grid = 0
>>>>> DEBUG 3: Rejected: level mismatch = 0
>>>>> DEBUG 3: Rejected: quality marker = 0
>>>>> DEBUG 3: Rejected: message type = 80
>>>>> DEBUG 3: Rejected: masking region = 0
>>>>> DEBUG 3: Rejected: bad fcst value = 0
>>>>> DEBUG 3: Rejected: duplicates = 0
>>>>>
>>>>> Processing TMP/Z2 versus TMP/Z2, for observation type APDSFC,
over
>> region
>>>>> FULL, for interpolation method NEAREST(1), using 0 pairs.
>>>>> DEBUG 3: Number of matched pairs = 0
>>>>> DEBUG 3: Observations processed = 2016
>>>>> DEBUG 3: Rejected: SID exclusion = 0
>>>>> DEBUG 3: Rejected: GRIB code = 1680
>>>>> DEBUG 3: Rejected: valid time = 0
>>>>> DEBUG 3: Rejected: bad obs value = 0
>>>>> DEBUG 3: Rejected: off the grid = 0
>>>>> DEBUG 3: Rejected: level mismatch = 0
>>>>> DEBUG 3: Rejected: quality marker = 0
>>>>> DEBUG 3: Rejected: message type = 336
>>>>> DEBUG 3: Rejected: masking region = 0
>>>>> DEBUG 3: Rejected: bad fcst value = 0
>>>>> DEBUG 3: Rejected: duplicates = 0
>>>>>
>>>>>
>>>>> On 17 November 2017 at 17:19, John Halley Gotway via RT <
>>>> met_help at ucar.edu>
>>>>> wrote:
>>>>>
>>>>>> Hi Emily,
>>>>>>
>>>>>> That’s great that you ran Point-Stat at verbosity level 3 to
dump out
>>>> the
>>>>>> counts for the reasons why observations weren’t used for each
>>>> verification
>>>>>> task.
>>>>>>
>>>>>> Looking at those counts I see that 42 weren’t used because of
their
>>>> valid
>>>>>> time. Mid suggest starting there. Perhaps your observations
aren’t
>>>> close
>>>>>> enough in time to your forecast valid time?
>>>>>>
>>>>>> One way of testing this would be rerunning point_stat using
these
>>>> command
>>>>>> line options:
>>>>>> -obs_valid_beg 20000101 -obs_valid_end 21000101
>>>>>>
>>>>>> That tells point-stat to use all obs between the years 2000 and
2100!
>>>> And
>>>>>> that should include all of yours.
>>>>>>
>>>>>> Once you get some matches pairs, you can decide how you’d
really like
>> to
>>>>>> set the matching time window for the point obs.
>>>>>>
>>>>>> Hope that helps.
>>>>>>
>>>>>> Thanks,
>>>>>> John
>>>>>>
>>>>>> On Fri, Nov 17, 2017 at 7:00 PM emily niebuhr via RT <
>> met_help at ucar.edu
>>>>>> wrote:
>>>>>>
>>>>>>> Fri Nov 17 19:00:18 2017: Request 83072 was acted upon.
>>>>>>> Transaction: Ticket created by elniebuhr at gmail.com
>>>>>>> Queue: met_help
>>>>>>> Subject: Point-Stats Error
>>>>>>> Owner: Nobody
>>>>>>> Requestors: elniebuhr at gmail.com
>>>>>>> Status: new
>>>>>>> Ticket <URL: https://rt.rap.ucar.edu/rt/
>> Ticket/Display.html?id=83072
>>>>>>> To whom it may concern,
>>>>>>>
>>>>>>> Hopefully this is a small user error that I am encountering,
but I
>>>> cannot
>>>>>>> seem to find matches after running point_Stat.Do you know why
the
>>>>>>> observations may not be matching? I get no errors when I run
>> ascii2nc
>>>>>> and
>>>>>>> I clearly define two points with correct stations and lat/lon.
>>>>>>>
>>>>>>>
>>>>>>> I was wondering if I am possibly having errors since it is
polar
>>>>>> projection
>>>>>>> or grib2 data. Right away I receive an error about
unrecognised
>> GRIB2
>>>>>>> field indexes. However I don't think this is the main problem
since I
>>>>>> still
>>>>>>> end up with no matching pairs even if I convert it to grib1.
The only
>>>>>> other
>>>>>>> thing I can think of is that I incorrectly defined the QC
variable.
>>>> What
>>>>>>> value do you suggest?
>>>>>>>
>>>>>>> I seem to get similar errors when I try prepbufr files, and if
I try
>> to
>>>>>>> verify with HRRR or URMA files. Thanks!
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> DEBUG 1: User Config File: nPointStatConfig_default
>>>>>>> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() ->
created new
>>>>>>> Met2dDataFile object of type "FileType_Gb2".
>>>>>>> DEBUG 4: Switching the GRIB2 radius of the earth value of
6371.23 km
>> to
>>>>>>> 6371.2 km for internal consistency.
>>>>>>> DEBUG 4:
>>>>>>> DEBUG 4: Stereographic Grid Data:
>>>>>>> DEBUG 4: hemisphere: N
>>>>>>> DEBUG 4: scale_lat: 60
>>>>>>> DEBUG 4: lat_pin: 41.6129
>>>>>>> DEBUG 4: lon_pin: 174.883
>>>>>>> DEBUG 4: x_pin: 0
>>>>>>> DEBUG 4: y_pin: 0
>>>>>>> DEBUG 4: lon_orient: 135
>>>>>>> DEBUG 4: d_km: 3
>>>>>>> DEBUG 4: r_km: 6371.2
>>>>>>> DEBUG 4: nx: 1299
>>>>>>> DEBUG 4: ny: 919
>>>>>>> DEBUG 4:
>>>>>>> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
>>>> GRIB2
>>>>>>> field indexes - disc: 0, master table: 2, center: 59, local
table: 1,
>>>>>>> parm_cat: 16, parm: 196
>>>>>>> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
>>>> GRIB2
>>>>>>> field indexes - disc: 0, master table: 2, center: 59, local
table: 1,
>>>>>>> parm_cat: 16, parm: 201
>>>>>>> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
>>>> GRIB2
>>>>>>> field indexes - disc: 0, master table: 2, center: 59, local
table: 1,
>>>>>>> parm_cat: 16, parm: 195
>>>>>>> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
>>>> GRIB2
>>>>>>> field indexes - disc: 0, master table: 2, center: 59, local
table: 1,
>>>>>>> parm_cat: 16, parm: 195
>>>>>>> DEBUG 4: MetGrib2DataFile::read_grib2_record_list() -
unrecognized
>>>> GRIB2
>>>>>>> field indexes - disc: 0, master table: 2, center: 59, local
table: 1,
>>>>>>> parm_cat: 16, parm: 195
>>>>>>>
>>>>>>>
>>>>>>> ARNING: Multiple GRIB2 table entries match lookup criteria
>> (parm_name =
>>>>>>> GUST):
>>>>>>> WARNING: parm_name: GUST, index_a = 0, grib2_mtab = 1,
grib2_cntr =
>>>> 0,
>>>>>>> grib2_ltab = 0, index_b = 2, index_c = 22
>>>>>>> WARNING: parm_name: GUST, index_a = 0, grib2_mtab = 14,
grib2_cntr
>> =
>>>>>> 57,
>>>>>>> grib2_ltab = 0, index_b = 2, index_c = 22
>>>>>>> WARNING: Using: parm_name: GUST, index_a = 0, grib2_mtab =
1,
>>>>>> grib2_cntr
>>>>>>> = 0, grib2_ltab = 0, index_b = 2, index_c = 22
>>>>>>>
>>>>>>>
>>>>>>> Reading data for TMP/Z2.
>>>>>>> DEBUG 3: MetGrib2DataFile::data_plane_array() - Found exact
match
>> for
>>>>>>> "TMP/Z2" in GRIB2 record 59 field 1 of GRIB2 file
>> "1732021000000.grb2"
>>>>>>> DEBUG 4:
>>>>>>> DEBUG 4: Data plane information:
>>>>>>> DEBUG 4: plane min: 234.527
>>>>>>> DEBUG 4: plane max: 286.34
>>>>>>> DEBUG 4: scan mode: 64
>>>>>>> DEBUG 4: valid time: 20171116_210000
>>>>>>> DEBUG 4: lead time: 000000
>>>>>>> DEBUG 4: init time: 20171116_210000
>>>>>>> DEBUG 4: bitmap flag: 255
>>>>>>> DEBUG 4:
>>>>>>> DEBUG 2: For TMP/Z2 found 1 forecast levels and 0 climatology
levels.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Processing TMP/Z2 versus TMP/Z2, for observation type APDSFC,
over
>>>> region
>>>>>>> FULL, for interpolation method NEAREST(1), using 0 pairs.
>>>>>>> DEBUG 3: Number of matched pairs = 0
>>>>>>> DEBUG 3: Observations processed = 210
>>>>>>> DEBUG 3: Rejected: SID exclusion = 0
>>>>>>> DEBUG 3: Rejected: GRIB code = 168
>>>>>>> DEBUG 3: Rejected: valid time = 42
>>>>>>> DEBUG 3: Rejected: bad obs value = 0
>>>>>>> DEBUG 3: Rejected: off the grid = 0
>>>>>>> DEBUG 3: Rejected: level mismatch = 0
>>>>>>> DEBUG 3: Rejected: quality marker = 0
>>>>>>> DEBUG 3: Rejected: message type = 0
>>>>>>> DEBUG 3: Rejected: masking region = 0
>>>>>>> DEBUG 3: Rejected: bad fcst value = 0
>>>>>>> DEBUG 3: Rejected: duplicates = 0
>>>>>>> DEBUG 2:
>>>>>>>
>>>>>>>
>>>>>>> Config file:
>>>>>>>
>>>>>>> /
>>>>>>> // Verification grid
>>>>>>> //
>>>>>>> regrid = {
>>>>>>> to_grid = NONE;
>>>>>>> method = NEAREST;
>>>>>>> width = 1;
>>>>>>> vld_thresh = 0.5;
>>>>>>> }
>>>>>>>
>>>>>>>
>>>>>>> ////////////////////////////////////////////////////////////
>>>>>> ////////////////////
>>>>>>> cat_thresh = [ NA ];
>>>>>>> cnt_thresh = [ NA ];
>>>>>>> cnt_logic = UNION;
>>>>>>> wind_thresh = [ NA ];
>>>>>>> wind_logic = UNION;
>>>>>>>
>>>>>>> //
>>>>>>> // Forecast and observation fields to be verified
>>>>>>> //
>>>>>>>
>>>>>>> // Gust height unclear assumed 10 m like wind
>>>>>>> fcst = {
>>>>>>> field = [
>>>>>>>
>>>>>>> {
>>>>>>> name = "GUST";
>>>>>>> level = [ "Z10" ];
>>>>>>> cat_thresh = [ >5.0 ];
>>>>>>> },
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> {
>>>>>>> name = "DPT";
>>>>>>> level = [ "Z2" ];
>>>>>>> cat_thresh = [ >-100.0 ];
>>>>>>> },
>>>>>>>
>>>>>>> {
>>>>>>> name = "TMP";
>>>>>>> level = [ "Z2" ];
>>>>>>> cat_thresh = [ >-100.0 ];
>>>>>>> },
>>>>>>> {
>>>>>>> name = "WIND";
>>>>>>> level = [ "Z10" ];
>>>>>>> cat_thresh = [ >0.0 ];
>>>>>>> }
>>>>>>>
>>>>>>> obs = fcst;
>>>>>>>
>>>>>>>
>>>>>>> ////////////////////////////////////////////////////////////
>>>>>> ////////////////////
>>>>>>> //
>>>>>>> // Point observation filtering options
>>>>>>> // May be set separately in each "obs.field" entry
>>>>>>> //
>>>>>>> message_type = ["APDSFC"];
>>>>>>> sid_exc = [];
>>>>>>> obs_quality = [];
>>>>>>> duplicate_flag = NONE;
>>>>>>> obs_summary = NONE;
>>>>>>> obs_perc_value = 50;
>>>>>>>
>>>>>>>
>>>>>>> ////////////////////////////////////////////////////////////
>>>>>> ////////////////////
>>>>>>> //
>>>>>>> // Climatology mean data
>>>>>>> //
>>>>>>> climo_mean = {
>>>>>>>
>>>>>>> file_name = [];
>>>>>>> field = [];
>>>>>>>
>>>>>>> regrid = {
>>>>>>> method = NEAREST;
>>>>>>> width = 1;
>>>>>>> vld_thresh = 0.5;
>>>>>>> }
>>>>>>>
>>>>>>> time_interp_method = DW_MEAN;
>>>>>>> match_day = FALSE;
>>>>>>> time_step = 21600;
>>>>>>> }
>>>>>>>
>>>>>>>
>>>>>>> ////////////////////////////////////////////////////////////
>>>>>> ////////////////////
>>>>>>> //
>>>>>>> // Point observation time window
>>>>>>> //
>>>>>>> obs_window = {
>>>>>>> beg = -54000;
>>>>>>> end = 54000;
>>>>>>>
>>>>>>> // Verification masking regions
>>>>>>> //
>>>>>>> mask = {
>>>>>>> grid = [ "FULL" ];
>>>>>>> poly = [];
>>>>>>> sid = [];
>>>>>>> }
>>>>>>>
>>>>>>>
>>>>>>> ////////////////////////////////////////////////////////////
>>>>>> ////////////////////
>>>>>>> //
>>>>>>> // Confidence interval settings
>>>>>>> //
>>>>>>> ci_alpha = [ 0.05 ];
>>>>>>>
>>>>>>> boot = {
>>>>>>> interval = PCTILE;
>>>>>>> rep_prop = 1.0;
>>>>>>> n_rep = 0;
>>>>>>> rng = "mt19937";
>>>>>>> seed = "";
>>>>>>> }
>>>>>>>
>>>>>>>
>>>>
>>
>>
------------------------------------------------
More information about the Met_help
mailing list