[Met_help] [rt.rap.ucar.edu #79364] History for MSLP verification issue
John Halley Gotway via RT
met_help at ucar.edu
Thu Feb 9 10:14:41 MST 2017
----------------------------------------------------------------
Initial Request
----------------------------------------------------------------
Dear MetHelp,
I'm trying to extract MSLP for verification, but MET finds no matches. Can you help me in figuring out how to extract it? PREPBUFR data is RAP
Thanks,
Jose M. Garcia-Rivera, PhD
IMSG
fcst = {
message_type = [ "ADPSFC" ];
sid_exc = [];
field = [
{
name = "TMP";
level = [ "Z2" ];
cat_thresh = [ >=293 ];
},
{
name = "RH";
level = [ "Z2" ];
cat_thresh = [ >=70 ];
},
{
name = "WIND";
level = [ "Z10" ];
cat_thresh = [ >=5 ];
},
{
name = "PRMSL";
level = [ "Z0" ];
cat_thresh = [ >=1000 ];
}
];
}
obs = {
message_type = [ "ADPSFC" ];
sid_exc = [];
field = [
{
name = "TMP";
level = [ "Z2" ];
cat_thresh = [ >=293 ];
},
{
name = "RH";
level = [ "Z2" ];
cat_thresh = [ >=70 ];
},
{
name = "WIND";
level = [ "Z10" ];
cat_thresh = [ >=5 ];
},
{
name = "PRMSL";
level = [ "R002" ];
cat_thresh = [ >=1000 ];
GRIB1_ptv = 388;
}
];
}
This e-mail, including attachments, may include confidential and/or proprietary information, and may be used only by the person or entity to which it is addressed. If the reader of this e-mail is not the intended recipient or his or her authorized agent, the reader is hereby notified that any dissemination, distribution or copying of this e-mail is prohibited. If you have received this e-mail in error, please notify the sender by replying to this message and delete this e-mail immediately.
----------------------------------------------------------------
Complete Ticket History
----------------------------------------------------------------
Subject: MSLP verification issue
From: John Halley Gotway
Time: Mon Feb 06 14:58:36 2017
Hello Jose,
I see you're having trouble verifying MSLP using the MET point_stat
tool.
By saying "MET finds no matches", I assume you mean that you're
getting 0
matched pairs for MSLP. Here's what I'd suggest. Please try
rerunning
point_stat but increase the verbosity level to at least 3 (-v 3) and
also
write a log file (-log run_ps.log). Running point_stat at that
verbosity
level will print out log messages that look like this:
DEBUG 2: Processing TMP/P900-750 versus TMP/P900-750, for observation
type
ADPUPA, over region DTC165, for interpolation method MEDIAN(9), using
155
pairs.
DEBUG 3: Number of matched pairs = 155
DEBUG 3: Observations processed = 89893
DEBUG 3: Rejected: SID exclusion = 0
DEBUG 3: Rejected: GRIB code = 79360
DEBUG 3: Rejected: valid time = 0
DEBUG 3: Rejected: bad obs value = 0
DEBUG 3: Rejected: off the grid = 5
DEBUG 3: Rejected: level mismatch = 9607
DEBUG 3: Rejected: quality marker = 0
DEBUG 3: Rejected: message type = 344
DEBUG 3: Rejected: masking region = 422
DEBUG 3: Rejected: bad fcst value = 0
DEBUG 3: Rejected: duplicates = 0
In this example of verifying upper air temperature, point_stat
considered
89893 observation values but only used 155 of them in the computation
of
statistics. The other counts list why the observations were discarded
(79360 for the observation type, 5 for being off the grid, 9607 for
the
vertical level, and so on).
In your case, you'll see that MSLP has 0 matched pairs, but the
rejection
counts will give you more information as to *why* they were all
discarded.
If the problem isn't obvious, please send me the "run_ps.log" file,
and
I'll see if anything jumps out at me. And if we still can't figure it
out,
I'll have you send me a sample forecast file, point observation file,
and
point_stat config file. Hopefully I'd be able to diagnose the problem
from
there.
Thanks,
John Halley Gotway
On Mon, Feb 6, 2017 at 2:35 PM, Jose Garcia-Rivera via RT
<met_help at ucar.edu
> wrote:
>
> Mon Feb 06 14:35:22 2017: Request 79364 was acted upon.
> Transaction: Ticket created by GarciaJ at imsg.com
> Queue: met_help
> Subject: MSLP verification issue
> Owner: Nobody
> Requestors: GarciaJ at imsg.com
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=79364 >
>
>
> Dear MetHelp,
>
> I'm trying to extract MSLP for verification, but MET finds no
matches. Can
> you help me in figuring out how to extract it? PREPBUFR data is RAP
>
> Thanks,
> Jose M. Garcia-Rivera, PhD
> IMSG
>
>
> fcst = {
> message_type = [ "ADPSFC" ];
> sid_exc = [];
>
> field = [
> {
> name = "TMP";
> level = [ "Z2" ];
> cat_thresh = [ >=293 ];
> },
> {
> name = "RH";
> level = [ "Z2" ];
> cat_thresh = [ >=70 ];
> },
> {
> name = "WIND";
> level = [ "Z10" ];
> cat_thresh = [ >=5 ];
> },
> {
> name = "PRMSL";
> level = [ "Z0" ];
> cat_thresh = [ >=1000 ];
> }
> ];
>
> }
> obs = {
> message_type = [ "ADPSFC" ];
> sid_exc = [];
>
> field = [
> {
> name = "TMP";
> level = [ "Z2" ];
> cat_thresh = [ >=293 ];
> },
> {
> name = "RH";
> level = [ "Z2" ];
> cat_thresh = [ >=70 ];
> },
> {
> name = "WIND";
> level = [ "Z10" ];
> cat_thresh = [ >=5 ];
> },
> {
> name = "PRMSL";
> level = [ "R002" ];
> cat_thresh = [ >=1000 ];
> GRIB1_ptv = 388;
> }
> ];
> }
> This e-mail, including attachments, may include confidential and/or
> proprietary information, and may be used only by the person or
entity to
> which it is addressed. If the reader of this e-mail is not the
intended
> recipient or his or her authorized agent, the reader is hereby
notified
> that any dissemination, distribution or copying of this e-mail is
> prohibited. If you have received this e-mail in error, please notify
the
> sender by replying to this message and delete this e-mail
immediately.
>
>
------------------------------------------------
Subject: MSLP verification issue
From: Jose Garcia-Rivera
Time: Mon Feb 06 15:47:23 2017
Dear John,
Thanks for the quick reply. It seems not to be reading PRMSL from OBS
file. Here's the log file.
Best Regards,
Jose
-----Original Message-----
From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
Sent: Monday, February 06, 2017 4:59 PM
To: Jose Garcia-Rivera <GarciaJ at imsg.com>
Subject: Re: [rt.rap.ucar.edu #79364] MSLP verification issue
Hello Jose,
I see you're having trouble verifying MSLP using the MET point_stat
tool.
By saying "MET finds no matches", I assume you mean that you're
getting 0 matched pairs for MSLP. Here's what I'd suggest. Please
try rerunning point_stat but increase the verbosity level to at least
3 (-v 3) and also write a log file (-log run_ps.log). Running
point_stat at that verbosity level will print out log messages that
look like this:
DEBUG 2: Processing TMP/P900-750 versus TMP/P900-750, for observation
type ADPUPA, over region DTC165, for interpolation method MEDIAN(9),
using 155 pairs.
DEBUG 3: Number of matched pairs = 155
DEBUG 3: Observations processed = 89893
DEBUG 3: Rejected: SID exclusion = 0
DEBUG 3: Rejected: GRIB code = 79360
DEBUG 3: Rejected: valid time = 0
DEBUG 3: Rejected: bad obs value = 0
DEBUG 3: Rejected: off the grid = 5
DEBUG 3: Rejected: level mismatch = 9607 DEBUG 3: Rejected: quality
marker = 0
DEBUG 3: Rejected: message type = 344
DEBUG 3: Rejected: masking region = 422
DEBUG 3: Rejected: bad fcst value = 0
DEBUG 3: Rejected: duplicates = 0
In this example of verifying upper air temperature, point_stat
considered
89893 observation values but only used 155 of them in the computation
of statistics. The other counts list why the observations were
discarded
(79360 for the observation type, 5 for being off the grid, 9607 for
the vertical level, and so on).
In your case, you'll see that MSLP has 0 matched pairs, but the
rejection counts will give you more information as to *why* they were
all discarded.
If the problem isn't obvious, please send me the "run_ps.log" file,
and I'll see if anything jumps out at me. And if we still can't
figure it out, I'll have you send me a sample forecast file, point
observation file, and point_stat config file. Hopefully I'd be able
to diagnose the problem from there.
Thanks,
John Halley Gotway
On Mon, Feb 6, 2017 at 2:35 PM, Jose Garcia-Rivera via RT
<met_help at ucar.edu
> wrote:
>
> Mon Feb 06 14:35:22 2017: Request 79364 was acted upon.
> Transaction: Ticket created by GarciaJ at imsg.com
> Queue: met_help
> Subject: MSLP verification issue
> Owner: Nobody
> Requestors: GarciaJ at imsg.com
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=79364
> >
>
>
> Dear MetHelp,
>
> I'm trying to extract MSLP for verification, but MET finds no
matches.
> Can you help me in figuring out how to extract it? PREPBUFR data is
> RAP
>
> Thanks,
> Jose M. Garcia-Rivera, PhD
> IMSG
>
>
> fcst = {
> message_type = [ "ADPSFC" ];
> sid_exc = [];
>
> field = [
> {
> name = "TMP";
> level = [ "Z2" ];
> cat_thresh = [ >=293 ];
> },
> {
> name = "RH";
> level = [ "Z2" ];
> cat_thresh = [ >=70 ];
> },
> {
> name = "WIND";
> level = [ "Z10" ];
> cat_thresh = [ >=5 ];
> },
> {
> name = "PRMSL";
> level = [ "Z0" ];
> cat_thresh = [ >=1000 ];
> }
> ];
>
> }
> obs = {
> message_type = [ "ADPSFC" ];
> sid_exc = [];
>
> field = [
> {
> name = "TMP";
> level = [ "Z2" ];
> cat_thresh = [ >=293 ];
> },
> {
> name = "RH";
> level = [ "Z2" ];
> cat_thresh = [ >=70 ];
> },
> {
> name = "WIND";
> level = [ "Z10" ];
> cat_thresh = [ >=5 ];
> },
> {
> name = "PRMSL";
> level = [ "R002" ];
> cat_thresh = [ >=1000 ];
> GRIB1_ptv = 388;
> }
> ];
> }
> This e-mail, including attachments, may include confidential and/or
> proprietary information, and may be used only by the person or
entity
> to which it is addressed. If the reader of this e-mail is not the
> intended recipient or his or her authorized agent, the reader is
> hereby notified that any dissemination, distribution or copying of
> this e-mail is prohibited. If you have received this e-mail in
error,
> please notify the sender by replying to this message and delete this
e-mail immediately.
>
>
This e-mail, including attachments, may include confidential and/or
proprietary information, and may be used only by the person or entity
to which it is addressed. If the reader of this e-mail is not the
intended recipient or his or her authorized agent, the reader is
hereby notified that any dissemination, distribution or copying of
this e-mail is prohibited. If you have received this e-mail in error,
please notify the sender by replying to this message and delete this
e-mail immediately.
------------------------------------------------
Subject: MSLP verification issue
From: Jose Garcia-Rivera
Time: Mon Feb 06 15:47:23 2017
DEBUG 1: Default Config File:
/work/apps/intel_2016/met/5.2/share/met/config/PointStatConfig_default
DEBUG 1: User Config File: PointStatConfig
DEBUG 1: Forecast File: nmbprs_d01.08_3km
DEBUG 1: Observation File: 2016100812_rap_prepbufr_f08.nc
DEBUG 2:
DEBUG 2:
--------------------------------------------------------------------------------
DEBUG 2:
DEBUG 2: Reading data for TMP/Z2.
DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found range match for
VarInfo "TMP/Z2" in GRIB record 2 of GRIB file "nmbprs_d01.08_3km".
DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found range match for
VarInfo "TMP/Z2" in GRIB record 11 of GRIB file "nmbprs_d01.08_3km".
DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found 2 GRIB records
matching VarInfo "TMP/Z2" in GRIB file "nmbprs_d01.08_3km".
DEBUG 3: Use the matching forecast and observation grids.
DEBUG 3: Grid Definition: Projection: Lambert Conformal Nx: 400 Ny:
400 Lat_LL: 33.302 Lon_LL: 84.951 Lon_orient: 77.459 Alpha: 4181.434
Cone: 0.629 Bx: 232.9380 By: 2827.5508
DEBUG 2: For TMP/Z2 found 2 forecast levels and 0 climatology levels.
DEBUG 2:
DEBUG 2:
--------------------------------------------------------------------------------
DEBUG 2:
DEBUG 2: Reading data for RH/Z2.
DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found range match for
VarInfo "RH/Z2" in GRIB record 4 of GRIB file "nmbprs_d01.08_3km".
DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found range match for
VarInfo "RH/Z2" in GRIB record 13 of GRIB file "nmbprs_d01.08_3km".
DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found 2 GRIB records
matching VarInfo "RH/Z2" in GRIB file "nmbprs_d01.08_3km".
DEBUG 2: For RH/Z2 found 2 forecast levels and 0 climatology levels.
DEBUG 2:
DEBUG 2:
--------------------------------------------------------------------------------
DEBUG 2:
DEBUG 2: Reading data for WIND/Z10.
DEBUG 3: MetGrib1DataFile::data_plane_array() -> Attempt to derive
winds from U and V components.
DEBUG 3: MetGrib1DataFile::data_plane_array() -> Reading U-wind
records.
DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found range match for
VarInfo "WIND/Z10" in GRIB record 7 of GRIB file "nmbprs_d01.08_3km".
DEBUG 3: MetGrib1DataFile::rotate_winds() -> Have U-wind record,
reading V-wind record.
DEBUG 3: MetGrib1DataFile::data_plane_scalar() -> Found exact match
for VarInfo "WIND/Z10" in GRIB record 8 of GRIB file
"nmbprs_d01.08_3km".
DEBUG 3: Rotating U and V wind components from grid-relative to earth-
relative.
DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found range match for
VarInfo "WIND/Z10" in GRIB record 16 of GRIB file "nmbprs_d01.08_3km".
DEBUG 3: MetGrib1DataFile::rotate_winds() -> Have U-wind record,
reading V-wind record.
DEBUG 3: MetGrib1DataFile::data_plane_scalar() -> Found exact match
for VarInfo "WIND/Z10" in GRIB record 8 of GRIB file
"nmbprs_d01.08_3km".
DEBUG 3: Rotating U and V wind components from grid-relative to earth-
relative.
DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found 2 GRIB records
matching VarInfo "WIND/Z10" in GRIB file "nmbprs_d01.08_3km".
DEBUG 3: MetGrib1DataFile::data_plane_array() -> Reading V-wind
records.
DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found range match for
VarInfo "WIND/Z10" in GRIB record 8 of GRIB file "nmbprs_d01.08_3km".
DEBUG 3: MetGrib1DataFile::rotate_winds() -> Have V-wind record,
reading U-wind record.
DEBUG 3: MetGrib1DataFile::data_plane_scalar() -> Found exact match
for VarInfo "WIND/Z10" in GRIB record 7 of GRIB file
"nmbprs_d01.08_3km".
DEBUG 3: Rotating U and V wind components from grid-relative to earth-
relative.
DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found range match for
VarInfo "WIND/Z10" in GRIB record 17 of GRIB file "nmbprs_d01.08_3km".
DEBUG 3: MetGrib1DataFile::rotate_winds() -> Have V-wind record,
reading U-wind record.
DEBUG 3: MetGrib1DataFile::data_plane_scalar() -> Found exact match
for VarInfo "WIND/Z10" in GRIB record 7 of GRIB file
"nmbprs_d01.08_3km".
DEBUG 3: Rotating U and V wind components from grid-relative to earth-
relative.
DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found 2 GRIB records
matching VarInfo "WIND/Z10" in GRIB file "nmbprs_d01.08_3km".
DEBUG 3: Deriving wind speed from U and V wind components.
DEBUG 3: Deriving wind speed from U and V wind components.
DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found 2 GRIB records
matching VarInfo "WIND/Z10" in GRIB file "nmbprs_d01.08_3km".
DEBUG 2: For WIND/Z10 found 2 forecast levels and 0 climatology
levels.
DEBUG 2:
DEBUG 2:
--------------------------------------------------------------------------------
DEBUG 2:
DEBUG 2: Reading data for PRMSL/L0.
DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found range match for
VarInfo "PRMSL/L0" in GRIB record 19 of GRIB file "nmbprs_d01.08_3km".
DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found 1 GRIB records
matching VarInfo "PRMSL/L0" in GRIB file "nmbprs_d01.08_3km".
DEBUG 2: For PRMSL/L0 found 1 forecast levels and 0 climatology
levels.
DEBUG 2:
DEBUG 2:
--------------------------------------------------------------------------------
DEBUG 2:
DEBUG 2: Searching 66723 observations from 5783 messages.
DEBUG 2:
DEBUG 2:
--------------------------------------------------------------------------------
DEBUG 2:
DEBUG 2: Processing TMP/Z2 versus TMP/Z2, for observation type ADPSFC,
over region FULL, for interpolation method BILIN(4), using 990 pairs.
DEBUG 3: Number of matched pairs = 990
DEBUG 3: Observations processed = 66723
DEBUG 3: Rejected: SID exclusion = 0
DEBUG 3: Rejected: GRIB code = 64243
DEBUG 3: Rejected: valid time = 0
DEBUG 3: Rejected: bad obs value = 0
DEBUG 3: Rejected: off the grid = 1102
DEBUG 3: Rejected: level mismatch = 221
DEBUG 3: Rejected: quality marker = 0
DEBUG 3: Rejected: message type = 161
DEBUG 3: Rejected: masking region = 0
DEBUG 3: Rejected: bad fcst value = 6
DEBUG 3: Rejected: duplicates = 0
DEBUG 2: Computing Categorical Statistics.
DEBUG 2: Computing Continuous Statistics.
DEBUG 3: Using 990 of 990 pairs for forecast filtering threshold NA,
observation filtering threshold NA, and field logic UNION.
DEBUG 2: Computing Scalar Partial Sums.
DEBUG 3: Using 990 of 990 pairs for forecast filtering threshold NA,
observation filtering threshold NA, and field logic UNION.
DEBUG 2:
DEBUG 2:
--------------------------------------------------------------------------------
DEBUG 2:
DEBUG 2: Processing RH/Z2 versus RH/Z2, for observation type ADPSFC,
over region FULL, for interpolation method BILIN(4), using 954 pairs.
DEBUG 3: Number of matched pairs = 954
DEBUG 3: Observations processed = 66723
DEBUG 3: Rejected: SID exclusion = 0
DEBUG 3: Rejected: GRIB code = 64947
DEBUG 3: Rejected: valid time = 0
DEBUG 3: Rejected: bad obs value = 0
DEBUG 3: Rejected: off the grid = 802
DEBUG 3: Rejected: level mismatch = 0
DEBUG 3: Rejected: quality marker = 0
DEBUG 3: Rejected: message type = 14
DEBUG 3: Rejected: masking region = 0
DEBUG 3: Rejected: bad fcst value = 6
DEBUG 3: Rejected: duplicates = 0
DEBUG 2: Computing Categorical Statistics.
DEBUG 2: Computing Continuous Statistics.
DEBUG 3: Using 954 of 954 pairs for forecast filtering threshold NA,
observation filtering threshold NA, and field logic UNION.
DEBUG 2: Computing Scalar Partial Sums.
DEBUG 3: Using 954 of 954 pairs for forecast filtering threshold NA,
observation filtering threshold NA, and field logic UNION.
DEBUG 2:
DEBUG 2:
--------------------------------------------------------------------------------
DEBUG 2:
DEBUG 2: Processing WIND/Z10 versus WIND/Z10, for observation type
ADPSFC, over region FULL, for interpolation method BILIN(4), using 989
pairs.
DEBUG 3: Number of matched pairs = 989
DEBUG 3: Observations processed = 66723
DEBUG 3: Rejected: SID exclusion = 0
DEBUG 3: Rejected: GRIB code = 38188
DEBUG 3: Rejected: valid time = 11043
DEBUG 3: Rejected: bad obs value = 0
DEBUG 3: Rejected: off the grid = 8937
DEBUG 3: Rejected: level mismatch = 7394
DEBUG 3: Rejected: quality marker = 0
DEBUG 3: Rejected: message type = 166
DEBUG 3: Rejected: masking region = 0
DEBUG 3: Rejected: bad fcst value = 6
DEBUG 3: Rejected: duplicates = 0
DEBUG 2: Computing Categorical Statistics.
DEBUG 2: Computing Continuous Statistics.
DEBUG 3: Using 989 of 989 pairs for forecast filtering threshold NA,
observation filtering threshold NA, and field logic UNION.
DEBUG 2: Computing Scalar Partial Sums.
DEBUG 3: Using 989 of 989 pairs for forecast filtering threshold NA,
observation filtering threshold NA, and field logic UNION.
DEBUG 2:
DEBUG 2:
--------------------------------------------------------------------------------
DEBUG 2:
DEBUG 2: Processing PRMSL/L0 versus PRMSL/L0, for observation type
ADPSFC, over region FULL, for interpolation method BILIN(4), using 0
pairs.
DEBUG 3: Number of matched pairs = 0
DEBUG 3: Observations processed = 66723
DEBUG 3: Rejected: SID exclusion = 0
DEBUG 3: Rejected: GRIB code = 66723
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 = 0
DEBUG 3: Rejected: masking region = 0
DEBUG 3: Rejected: bad fcst value = 0
DEBUG 3: Rejected: duplicates = 0
DEBUG 2:
DEBUG 2:
--------------------------------------------------------------------------------
DEBUG 2:
DEBUG 1: Output file:
./point_stat_2016100812_09hr_080000L_20161008_200000V.stat
DEBUG 1: Output file:
./point_stat_2016100812_09hr_080000L_20161008_200000V_cts.txt
DEBUG 1: Output file:
./point_stat_2016100812_09hr_080000L_20161008_200000V_cnt.txt
DEBUG 1: Output file:
./point_stat_2016100812_09hr_080000L_20161008_200000V_sl1l2.txt
DEBUG 1: Output file:
./point_stat_2016100812_09hr_080000L_20161008_200000V_vl1l2.txt
------------------------------------------------
Subject: MSLP verification issue
From: John Halley Gotway
Time: Mon Feb 06 16:39:47 2017
Jose,
So here's the relevant output from your log file:
DEBUG 2: Processing PRMSL/L0 versus PRMSL/L0, for observation type
ADPSFC, over region FULL, for interpolation method BILIN(4), using 0
pairs.
DEBUG 3: Number of matched pairs = 0
DEBUG 3: Observations processed = 66723
DEBUG 3: Rejected: SID exclusion = 0
DEBUG 3: Rejected: GRIB code = 66723
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 = 0
DEBUG 3: Rejected: masking region = 0
DEBUG 3: Rejected: bad fcst value = 0
DEBUG 3: Rejected: duplicates = 0
We need to look at your observation files and see how the PRMSL
observation
is being encoded.
Perhaps it'd be easiest to have you send me your sample forecast,
observation, and point_stat config file, by posting them to our
anonymous
ftp site:
http://www.dtcenter.org/met/users/support/met_help.php#ftp
Please email me once you've posted the sample data, and I'll go grab
it.
Thanks,
John
On Mon, Feb 6, 2017 at 3:47 PM, Jose Garcia-Rivera via RT
<met_help at ucar.edu
> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=79364 >
>
> Dear John,
>
> Thanks for the quick reply. It seems not to be reading PRMSL from
OBS
> file. Here's the log file.
>
> Best Regards,
> Jose
>
> -----Original Message-----
> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> Sent: Monday, February 06, 2017 4:59 PM
> To: Jose Garcia-Rivera <GarciaJ at imsg.com>
> Subject: Re: [rt.rap.ucar.edu #79364] MSLP verification issue
>
> Hello Jose,
>
> I see you're having trouble verifying MSLP using the MET point_stat
tool.
> By saying "MET finds no matches", I assume you mean that you're
getting 0
> matched pairs for MSLP. Here's what I'd suggest. Please try
rerunning
> point_stat but increase the verbosity level to at least 3 (-v 3) and
also
> write a log file (-log run_ps.log). Running point_stat at that
verbosity
> level will print out log messages that look like this:
>
> DEBUG 2: Processing TMP/P900-750 versus TMP/P900-750, for
observation type
> ADPUPA, over region DTC165, for interpolation method MEDIAN(9),
using 155
> pairs.
> DEBUG 3: Number of matched pairs = 155
> DEBUG 3: Observations processed = 89893
> DEBUG 3: Rejected: SID exclusion = 0
> DEBUG 3: Rejected: GRIB code = 79360
> DEBUG 3: Rejected: valid time = 0
> DEBUG 3: Rejected: bad obs value = 0
> DEBUG 3: Rejected: off the grid = 5
> DEBUG 3: Rejected: level mismatch = 9607 DEBUG 3: Rejected: quality
marker
> = 0
> DEBUG 3: Rejected: message type = 344
> DEBUG 3: Rejected: masking region = 422
> DEBUG 3: Rejected: bad fcst value = 0
> DEBUG 3: Rejected: duplicates = 0
>
> In this example of verifying upper air temperature, point_stat
considered
> 89893 observation values but only used 155 of them in the
computation of
> statistics. The other counts list why the observations were
discarded
> (79360 for the observation type, 5 for being off the grid, 9607 for
the
> vertical level, and so on).
>
> In your case, you'll see that MSLP has 0 matched pairs, but the
rejection
> counts will give you more information as to *why* they were all
discarded.
>
> If the problem isn't obvious, please send me the "run_ps.log" file,
and
> I'll see if anything jumps out at me. And if we still can't figure
it out,
> I'll have you send me a sample forecast file, point observation
file, and
> point_stat config file. Hopefully I'd be able to diagnose the
problem from
> there.
>
> Thanks,
> John Halley Gotway
>
>
> On Mon, Feb 6, 2017 at 2:35 PM, Jose Garcia-Rivera via RT <
> met_help at ucar.edu
> > wrote:
>
> >
> > Mon Feb 06 14:35:22 2017: Request 79364 was acted upon.
> > Transaction: Ticket created by GarciaJ at imsg.com
> > Queue: met_help
> > Subject: MSLP verification issue
> > Owner: Nobody
> > Requestors: GarciaJ at imsg.com
> > Status: new
> > Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=79364
> > >
> >
> >
> > Dear MetHelp,
> >
> > I'm trying to extract MSLP for verification, but MET finds no
matches.
> > Can you help me in figuring out how to extract it? PREPBUFR data
is
> > RAP
> >
> > Thanks,
> > Jose M. Garcia-Rivera, PhD
> > IMSG
> >
> >
> > fcst = {
> > message_type = [ "ADPSFC" ];
> > sid_exc = [];
> >
> > field = [
> > {
> > name = "TMP";
> > level = [ "Z2" ];
> > cat_thresh = [ >=293 ];
> > },
> > {
> > name = "RH";
> > level = [ "Z2" ];
> > cat_thresh = [ >=70 ];
> > },
> > {
> > name = "WIND";
> > level = [ "Z10" ];
> > cat_thresh = [ >=5 ];
> > },
> > {
> > name = "PRMSL";
> > level = [ "Z0" ];
> > cat_thresh = [ >=1000 ];
> > }
> > ];
> >
> > }
> > obs = {
> > message_type = [ "ADPSFC" ];
> > sid_exc = [];
> >
> > field = [
> > {
> > name = "TMP";
> > level = [ "Z2" ];
> > cat_thresh = [ >=293 ];
> > },
> > {
> > name = "RH";
> > level = [ "Z2" ];
> > cat_thresh = [ >=70 ];
> > },
> > {
> > name = "WIND";
> > level = [ "Z10" ];
> > cat_thresh = [ >=5 ];
> > },
> > {
> > name = "PRMSL";
> > level = [ "R002" ];
> > cat_thresh = [ >=1000 ];
> > GRIB1_ptv = 388;
> > }
> > ];
> > }
> > This e-mail, including attachments, may include confidential
and/or
> > proprietary information, and may be used only by the person or
entity
> > to which it is addressed. If the reader of this e-mail is not the
> > intended recipient or his or her authorized agent, the reader is
> > hereby notified that any dissemination, distribution or copying of
> > this e-mail is prohibited. If you have received this e-mail in
error,
> > please notify the sender by replying to this message and delete
this
> e-mail immediately.
> >
> >
>
> This e-mail, including attachments, may include confidential and/or
> proprietary information, and may be used only by the person or
entity to
> which it is addressed. If the reader of this e-mail is not the
intended
> recipient or his or her authorized agent, the reader is hereby
notified
> that any dissemination, distribution or copying of this e-mail is
> prohibited. If you have received this e-mail in error, please notify
the
> sender by replying to this message and delete this e-mail
immediately.
>
>
------------------------------------------------
Subject: Re: [rt.rap.ucar.edu #79364] MSLP verification issue
From: Jose Garcia-Rivera
Time: Wed Feb 08 09:26:55 2017
Hi John,
Thanks for the help. Unfortunately I'm having trouble doing FTP from
work computer (restricted).
Do you have an example configure file in which PRMSL is called from
either GDAS or RAP prepbufr files?
Best Regards,
Jose
________________________________________
From: John Halley Gotway via RT <met_help at ucar.edu>
Sent: Monday, February 6, 2017 6:39 PM
To: Jose Garcia-Rivera
Subject: Re: [rt.rap.ucar.edu #79364] MSLP verification issue
Jose,
So here's the relevant output from your log file:
DEBUG 2: Processing PRMSL/L0 versus PRMSL/L0, for observation type
ADPSFC, over region FULL, for interpolation method BILIN(4), using 0
pairs.
DEBUG 3: Number of matched pairs = 0
DEBUG 3: Observations processed = 66723
DEBUG 3: Rejected: SID exclusion = 0
DEBUG 3: Rejected: GRIB code = 66723
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 = 0
DEBUG 3: Rejected: masking region = 0
DEBUG 3: Rejected: bad fcst value = 0
DEBUG 3: Rejected: duplicates = 0
We need to look at your observation files and see how the PRMSL
observation
is being encoded.
Perhaps it'd be easiest to have you send me your sample forecast,
observation, and point_stat config file, by posting them to our
anonymous
ftp site:
http://www.dtcenter.org/met/users/support/met_help.php#ftp
Please email me once you've posted the sample data, and I'll go grab
it.
Thanks,
John
On Mon, Feb 6, 2017 at 3:47 PM, Jose Garcia-Rivera via RT
<met_help at ucar.edu
> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=79364 >
>
> Dear John,
>
> Thanks for the quick reply. It seems not to be reading PRMSL from
OBS
> file. Here's the log file.
>
> Best Regards,
> Jose
>
> -----Original Message-----
> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> Sent: Monday, February 06, 2017 4:59 PM
> To: Jose Garcia-Rivera <GarciaJ at imsg.com>
> Subject: Re: [rt.rap.ucar.edu #79364] MSLP verification issue
>
> Hello Jose,
>
> I see you're having trouble verifying MSLP using the MET point_stat
tool.
> By saying "MET finds no matches", I assume you mean that you're
getting 0
> matched pairs for MSLP. Here's what I'd suggest. Please try
rerunning
> point_stat but increase the verbosity level to at least 3 (-v 3) and
also
> write a log file (-log run_ps.log). Running point_stat at that
verbosity
> level will print out log messages that look like this:
>
> DEBUG 2: Processing TMP/P900-750 versus TMP/P900-750, for
observation type
> ADPUPA, over region DTC165, for interpolation method MEDIAN(9),
using 155
> pairs.
> DEBUG 3: Number of matched pairs = 155
> DEBUG 3: Observations processed = 89893
> DEBUG 3: Rejected: SID exclusion = 0
> DEBUG 3: Rejected: GRIB code = 79360
> DEBUG 3: Rejected: valid time = 0
> DEBUG 3: Rejected: bad obs value = 0
> DEBUG 3: Rejected: off the grid = 5
> DEBUG 3: Rejected: level mismatch = 9607 DEBUG 3: Rejected: quality
marker
> = 0
> DEBUG 3: Rejected: message type = 344
> DEBUG 3: Rejected: masking region = 422
> DEBUG 3: Rejected: bad fcst value = 0
> DEBUG 3: Rejected: duplicates = 0
>
> In this example of verifying upper air temperature, point_stat
considered
> 89893 observation values but only used 155 of them in the
computation of
> statistics. The other counts list why the observations were
discarded
> (79360 for the observation type, 5 for being off the grid, 9607 for
the
> vertical level, and so on).
>
> In your case, you'll see that MSLP has 0 matched pairs, but the
rejection
> counts will give you more information as to *why* they were all
discarded.
>
> If the problem isn't obvious, please send me the "run_ps.log" file,
and
> I'll see if anything jumps out at me. And if we still can't figure
it out,
> I'll have you send me a sample forecast file, point observation
file, and
> point_stat config file. Hopefully I'd be able to diagnose the
problem from
> there.
>
> Thanks,
> John Halley Gotway
>
>
> On Mon, Feb 6, 2017 at 2:35 PM, Jose Garcia-Rivera via RT <
> met_help at ucar.edu
> > wrote:
>
> >
> > Mon Feb 06 14:35:22 2017: Request 79364 was acted upon.
> > Transaction: Ticket created by GarciaJ at imsg.com
> > Queue: met_help
> > Subject: MSLP verification issue
> > Owner: Nobody
> > Requestors: GarciaJ at imsg.com
> > Status: new
> > Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=79364
> > >
> >
> >
> > Dear MetHelp,
> >
> > I'm trying to extract MSLP for verification, but MET finds no
matches.
> > Can you help me in figuring out how to extract it? PREPBUFR data
is
> > RAP
> >
> > Thanks,
> > Jose M. Garcia-Rivera, PhD
> > IMSG
> >
> >
> > fcst = {
> > message_type = [ "ADPSFC" ];
> > sid_exc = [];
> >
> > field = [
> > {
> > name = "TMP";
> > level = [ "Z2" ];
> > cat_thresh = [ >=293 ];
> > },
> > {
> > name = "RH";
> > level = [ "Z2" ];
> > cat_thresh = [ >=70 ];
> > },
> > {
> > name = "WIND";
> > level = [ "Z10" ];
> > cat_thresh = [ >=5 ];
> > },
> > {
> > name = "PRMSL";
> > level = [ "Z0" ];
> > cat_thresh = [ >=1000 ];
> > }
> > ];
> >
> > }
> > obs = {
> > message_type = [ "ADPSFC" ];
> > sid_exc = [];
> >
> > field = [
> > {
> > name = "TMP";
> > level = [ "Z2" ];
> > cat_thresh = [ >=293 ];
> > },
> > {
> > name = "RH";
> > level = [ "Z2" ];
> > cat_thresh = [ >=70 ];
> > },
> > {
> > name = "WIND";
> > level = [ "Z10" ];
> > cat_thresh = [ >=5 ];
> > },
> > {
> > name = "PRMSL";
> > level = [ "R002" ];
> > cat_thresh = [ >=1000 ];
> > GRIB1_ptv = 388;
> > }
> > ];
> > }
> > This e-mail, including attachments, may include confidential
and/or
> > proprietary information, and may be used only by the person or
entity
> > to which it is addressed. If the reader of this e-mail is not the
> > intended recipient or his or her authorized agent, the reader is
> > hereby notified that any dissemination, distribution or copying of
> > this e-mail is prohibited. If you have received this e-mail in
error,
> > please notify the sender by replying to this message and delete
this
> e-mail immediately.
> >
> >
>
> This e-mail, including attachments, may include confidential and/or
> proprietary information, and may be used only by the person or
entity to
> which it is addressed. If the reader of this e-mail is not the
intended
> recipient or his or her authorized agent, the reader is hereby
notified
> that any dissemination, distribution or copying of this e-mail is
> prohibited. If you have received this e-mail in error, please notify
the
> sender by replying to this message and delete this e-mail
immediately.
>
>
This e-mail, including attachments, may include confidential and/or
proprietary information, and may be used only by the person or entity
to which it is addressed. If the reader of this e-mail is not the
intended recipient or his or her authorized agent, the reader is
hereby notified that any dissemination, distribution or copying of
this e-mail is prohibited. If you have received this e-mail in error,
please notify the sender by replying to this message and delete this
e-mail immediately.
------------------------------------------------
Subject: MSLP verification issue
From: John Halley Gotway
Time: Wed Feb 08 15:43:05 2017
Jose,
I think you're likely running into a problem with the quality marker
used
for surface data in these PREPBUFR files. Please see the *NOTE* about
surface data at the bottom of this page:
http://www.dtcenter.org/met/users/downloads/observation_data.php
Surface observations with message type ADPSFC are set to a quality
marker
value of 9. By default, PB2NC discards any observations whose quality
marker is > 2. So PB2NC is tossing out all of the ADPSFC observations
of
PRMSL.
I grabbed a recent GDAS PREPBUFR file:
http://www.nco.ncep.noaa.gov/pmb/docs/on388/table2.html
I configured PB2NC to retain the PRMSL observation type by adding it
to the
"obs_grib_code" array. Then I ran PB2NC twice... once with the
default
quality mark threshold of 2 and a second time with it set to 9:
quality_mark_thresh = 9;
Then I ran the plot_point_obs command on both output files, plotting
only
PRMSL for the ADPSFC message type:
/usr/local/met-5.2/bin/plot_point_obs gdas.20170205.t12z_qm2.nc
gdas.20170205.t12z_qm2.ps -gc 2 -msg_typ ADPSFC
/usr/local/met-5.2/bin/plot_point_obs gdas.20170205.t12z_qm9.nc
gdas.20170205.t12z_qm9.ps -gc 2 -msg_typ ADPSFC
The first one plotted 0 locations while the second one plotted 34462
locations. The resulting plot quality marker 9 plot is attached.
It's unfortunate that they set the quality maker for the data in this
way.
By setting quality_mark_thresh = 9 in PB2NC, you'll end up with
observations with quality markers ranging from 0 to 9. However, in
the
Point-Stat config file, you could set the following:
obs_quality = [ "0", "1", "2", "9" ];
That would tell Point-Stat to only use observations who's quality flag
is
0, 1, 2, or 9... so we can skip over the 3 - 8 quality marks there.
Hope that helps explain the behavior you're seeing.
Thanks,
John
On Wed, Feb 8, 2017 at 9:26 AM, Jose Garcia-Rivera via RT
<met_help at ucar.edu
> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=79364 >
>
> Hi John,
>
> Thanks for the help. Unfortunately I'm having trouble doing FTP from
work
> computer (restricted).
>
> Do you have an example configure file in which PRMSL is called from
either
> GDAS or RAP prepbufr files?
>
> Best Regards,
> Jose
> ________________________________________
> From: John Halley Gotway via RT <met_help at ucar.edu>
> Sent: Monday, February 6, 2017 6:39 PM
> To: Jose Garcia-Rivera
> Subject: Re: [rt.rap.ucar.edu #79364] MSLP verification issue
>
> Jose,
>
> So here's the relevant output from your log file:
>
> DEBUG 2: Processing PRMSL/L0 versus PRMSL/L0, for observation type
> ADPSFC, over region FULL, for interpolation method BILIN(4), using 0
> pairs.
> DEBUG 3: Number of matched pairs = 0
> DEBUG 3: Observations processed = 66723
> DEBUG 3: Rejected: SID exclusion = 0
> DEBUG 3: Rejected: GRIB code = 66723
> 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 = 0
> DEBUG 3: Rejected: masking region = 0
> DEBUG 3: Rejected: bad fcst value = 0
> DEBUG 3: Rejected: duplicates = 0
>
> We need to look at your observation files and see how the PRMSL
observation
> is being encoded.
>
> Perhaps it'd be easiest to have you send me your sample forecast,
> observation, and point_stat config file, by posting them to our
anonymous
> ftp site:
> http://www.dtcenter.org/met/users/support/met_help.php#ftp
>
> Please email me once you've posted the sample data, and I'll go grab
it.
>
> Thanks,
> John
>
>
> On Mon, Feb 6, 2017 at 3:47 PM, Jose Garcia-Rivera via RT <
> met_help at ucar.edu
> > wrote:
>
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=79364 >
> >
> > Dear John,
> >
> > Thanks for the quick reply. It seems not to be reading PRMSL from
OBS
> > file. Here's the log file.
> >
> > Best Regards,
> > Jose
> >
> > -----Original Message-----
> > From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> > Sent: Monday, February 06, 2017 4:59 PM
> > To: Jose Garcia-Rivera <GarciaJ at imsg.com>
> > Subject: Re: [rt.rap.ucar.edu #79364] MSLP verification issue
> >
> > Hello Jose,
> >
> > I see you're having trouble verifying MSLP using the MET
point_stat tool.
> > By saying "MET finds no matches", I assume you mean that you're
getting 0
> > matched pairs for MSLP. Here's what I'd suggest. Please try
rerunning
> > point_stat but increase the verbosity level to at least 3 (-v 3)
and also
> > write a log file (-log run_ps.log). Running point_stat at that
verbosity
> > level will print out log messages that look like this:
> >
> > DEBUG 2: Processing TMP/P900-750 versus TMP/P900-750, for
observation
> type
> > ADPUPA, over region DTC165, for interpolation method MEDIAN(9),
using 155
> > pairs.
> > DEBUG 3: Number of matched pairs = 155
> > DEBUG 3: Observations processed = 89893
> > DEBUG 3: Rejected: SID exclusion = 0
> > DEBUG 3: Rejected: GRIB code = 79360
> > DEBUG 3: Rejected: valid time = 0
> > DEBUG 3: Rejected: bad obs value = 0
> > DEBUG 3: Rejected: off the grid = 5
> > DEBUG 3: Rejected: level mismatch = 9607 DEBUG 3: Rejected:
quality
> marker
> > = 0
> > DEBUG 3: Rejected: message type = 344
> > DEBUG 3: Rejected: masking region = 422
> > DEBUG 3: Rejected: bad fcst value = 0
> > DEBUG 3: Rejected: duplicates = 0
> >
> > In this example of verifying upper air temperature, point_stat
considered
> > 89893 observation values but only used 155 of them in the
computation of
> > statistics. The other counts list why the observations were
discarded
> > (79360 for the observation type, 5 for being off the grid, 9607
for the
> > vertical level, and so on).
> >
> > In your case, you'll see that MSLP has 0 matched pairs, but the
rejection
> > counts will give you more information as to *why* they were all
> discarded.
> >
> > If the problem isn't obvious, please send me the "run_ps.log"
file, and
> > I'll see if anything jumps out at me. And if we still can't
figure it
> out,
> > I'll have you send me a sample forecast file, point observation
file, and
> > point_stat config file. Hopefully I'd be able to diagnose the
problem
> from
> > there.
> >
> > Thanks,
> > John Halley Gotway
> >
> >
> > On Mon, Feb 6, 2017 at 2:35 PM, Jose Garcia-Rivera via RT <
> > met_help at ucar.edu
> > > wrote:
> >
> > >
> > > Mon Feb 06 14:35:22 2017: Request 79364 was acted upon.
> > > Transaction: Ticket created by GarciaJ at imsg.com
> > > Queue: met_help
> > > Subject: MSLP verification issue
> > > Owner: Nobody
> > > Requestors: GarciaJ at imsg.com
> > > Status: new
> > > Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=79364
> > > >
> > >
> > >
> > > Dear MetHelp,
> > >
> > > I'm trying to extract MSLP for verification, but MET finds no
matches.
> > > Can you help me in figuring out how to extract it? PREPBUFR
data is
> > > RAP
> > >
> > > Thanks,
> > > Jose M. Garcia-Rivera, PhD
> > > IMSG
> > >
> > >
> > > fcst = {
> > > message_type = [ "ADPSFC" ];
> > > sid_exc = [];
> > >
> > > field = [
> > > {
> > > name = "TMP";
> > > level = [ "Z2" ];
> > > cat_thresh = [ >=293 ];
> > > },
> > > {
> > > name = "RH";
> > > level = [ "Z2" ];
> > > cat_thresh = [ >=70 ];
> > > },
> > > {
> > > name = "WIND";
> > > level = [ "Z10" ];
> > > cat_thresh = [ >=5 ];
> > > },
> > > {
> > > name = "PRMSL";
> > > level = [ "Z0" ];
> > > cat_thresh = [ >=1000 ];
> > > }
> > > ];
> > >
> > > }
> > > obs = {
> > > message_type = [ "ADPSFC" ];
> > > sid_exc = [];
> > >
> > > field = [
> > > {
> > > name = "TMP";
> > > level = [ "Z2" ];
> > > cat_thresh = [ >=293 ];
> > > },
> > > {
> > > name = "RH";
> > > level = [ "Z2" ];
> > > cat_thresh = [ >=70 ];
> > > },
> > > {
> > > name = "WIND";
> > > level = [ "Z10" ];
> > > cat_thresh = [ >=5 ];
> > > },
> > > {
> > > name = "PRMSL";
> > > level = [ "R002" ];
> > > cat_thresh = [ >=1000 ];
> > > GRIB1_ptv = 388;
> > > }
> > > ];
> > > }
> > > This e-mail, including attachments, may include confidential
and/or
> > > proprietary information, and may be used only by the person or
entity
> > > to which it is addressed. If the reader of this e-mail is not
the
> > > intended recipient or his or her authorized agent, the reader is
> > > hereby notified that any dissemination, distribution or copying
of
> > > this e-mail is prohibited. If you have received this e-mail in
error,
> > > please notify the sender by replying to this message and delete
this
> > e-mail immediately.
> > >
> > >
> >
> > This e-mail, including attachments, may include confidential
and/or
> > proprietary information, and may be used only by the person or
entity to
> > which it is addressed. If the reader of this e-mail is not the
intended
> > recipient or his or her authorized agent, the reader is hereby
notified
> > that any dissemination, distribution or copying of this e-mail is
> > prohibited. If you have received this e-mail in error, please
notify the
> > sender by replying to this message and delete this e-mail
immediately.
> >
> >
>
> This e-mail, including attachments, may include confidential and/or
> proprietary information, and may be used only by the person or
entity to
> which it is addressed. If the reader of this e-mail is not the
intended
> recipient or his or her authorized agent, the reader is hereby
notified
> that any dissemination, distribution or copying of this e-mail is
> prohibited. If you have received this e-mail in error, please notify
the
> sender by replying to this message and delete this e-mail
immediately.
>
>
>
------------------------------------------------
Subject: Re: [rt.rap.ucar.edu #79364] MSLP verification issue
From: Jose Garcia-Rivera
Time: Thu Feb 09 09:09:18 2017
Dear John,
I got it working. I forgot about that little but important detail!
Thanks so much for the support.
Best Regards,
Jose
________________________________________
From: John Halley Gotway via RT <met_help at ucar.edu>
Sent: Wednesday, February 8, 2017 5:43 PM
To: Jose Garcia-Rivera
Subject: Re: [rt.rap.ucar.edu #79364] MSLP verification issue
Jose,
I think you're likely running into a problem with the quality marker
used
for surface data in these PREPBUFR files. Please see the *NOTE* about
surface data at the bottom of this page:
http://www.dtcenter.org/met/users/downloads/observation_data.php
Surface observations with message type ADPSFC are set to a quality
marker
value of 9. By default, PB2NC discards any observations whose quality
marker is > 2. So PB2NC is tossing out all of the ADPSFC observations
of
PRMSL.
I grabbed a recent GDAS PREPBUFR file:
http://www.nco.ncep.noaa.gov/pmb/docs/on388/table2.html
I configured PB2NC to retain the PRMSL observation type by adding it
to the
"obs_grib_code" array. Then I ran PB2NC twice... once with the
default
quality mark threshold of 2 and a second time with it set to 9:
quality_mark_thresh = 9;
Then I ran the plot_point_obs command on both output files, plotting
only
PRMSL for the ADPSFC message type:
/usr/local/met-5.2/bin/plot_point_obs gdas.20170205.t12z_qm2.nc
gdas.20170205.t12z_qm2.ps -gc 2 -msg_typ ADPSFC
/usr/local/met-5.2/bin/plot_point_obs gdas.20170205.t12z_qm9.nc
gdas.20170205.t12z_qm9.ps -gc 2 -msg_typ ADPSFC
The first one plotted 0 locations while the second one plotted 34462
locations. The resulting plot quality marker 9 plot is attached.
It's unfortunate that they set the quality maker for the data in this
way.
By setting quality_mark_thresh = 9 in PB2NC, you'll end up with
observations with quality markers ranging from 0 to 9. However, in
the
Point-Stat config file, you could set the following:
obs_quality = [ "0", "1", "2", "9" ];
That would tell Point-Stat to only use observations who's quality flag
is
0, 1, 2, or 9... so we can skip over the 3 - 8 quality marks there.
Hope that helps explain the behavior you're seeing.
Thanks,
John
On Wed, Feb 8, 2017 at 9:26 AM, Jose Garcia-Rivera via RT
<met_help at ucar.edu
> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=79364 >
>
> Hi John,
>
> Thanks for the help. Unfortunately I'm having trouble doing FTP from
work
> computer (restricted).
>
> Do you have an example configure file in which PRMSL is called from
either
> GDAS or RAP prepbufr files?
>
> Best Regards,
> Jose
> ________________________________________
> From: John Halley Gotway via RT <met_help at ucar.edu>
> Sent: Monday, February 6, 2017 6:39 PM
> To: Jose Garcia-Rivera
> Subject: Re: [rt.rap.ucar.edu #79364] MSLP verification issue
>
> Jose,
>
> So here's the relevant output from your log file:
>
> DEBUG 2: Processing PRMSL/L0 versus PRMSL/L0, for observation type
> ADPSFC, over region FULL, for interpolation method BILIN(4), using 0
> pairs.
> DEBUG 3: Number of matched pairs = 0
> DEBUG 3: Observations processed = 66723
> DEBUG 3: Rejected: SID exclusion = 0
> DEBUG 3: Rejected: GRIB code = 66723
> 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 = 0
> DEBUG 3: Rejected: masking region = 0
> DEBUG 3: Rejected: bad fcst value = 0
> DEBUG 3: Rejected: duplicates = 0
>
> We need to look at your observation files and see how the PRMSL
observation
> is being encoded.
>
> Perhaps it'd be easiest to have you send me your sample forecast,
> observation, and point_stat config file, by posting them to our
anonymous
> ftp site:
> http://www.dtcenter.org/met/users/support/met_help.php#ftp
>
> Please email me once you've posted the sample data, and I'll go grab
it.
>
> Thanks,
> John
>
>
> On Mon, Feb 6, 2017 at 3:47 PM, Jose Garcia-Rivera via RT <
> met_help at ucar.edu
> > wrote:
>
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=79364 >
> >
> > Dear John,
> >
> > Thanks for the quick reply. It seems not to be reading PRMSL from
OBS
> > file. Here's the log file.
> >
> > Best Regards,
> > Jose
> >
> > -----Original Message-----
> > From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> > Sent: Monday, February 06, 2017 4:59 PM
> > To: Jose Garcia-Rivera <GarciaJ at imsg.com>
> > Subject: Re: [rt.rap.ucar.edu #79364] MSLP verification issue
> >
> > Hello Jose,
> >
> > I see you're having trouble verifying MSLP using the MET
point_stat tool.
> > By saying "MET finds no matches", I assume you mean that you're
getting 0
> > matched pairs for MSLP. Here's what I'd suggest. Please try
rerunning
> > point_stat but increase the verbosity level to at least 3 (-v 3)
and also
> > write a log file (-log run_ps.log). Running point_stat at that
verbosity
> > level will print out log messages that look like this:
> >
> > DEBUG 2: Processing TMP/P900-750 versus TMP/P900-750, for
observation
> type
> > ADPUPA, over region DTC165, for interpolation method MEDIAN(9),
using 155
> > pairs.
> > DEBUG 3: Number of matched pairs = 155
> > DEBUG 3: Observations processed = 89893
> > DEBUG 3: Rejected: SID exclusion = 0
> > DEBUG 3: Rejected: GRIB code = 79360
> > DEBUG 3: Rejected: valid time = 0
> > DEBUG 3: Rejected: bad obs value = 0
> > DEBUG 3: Rejected: off the grid = 5
> > DEBUG 3: Rejected: level mismatch = 9607 DEBUG 3: Rejected:
quality
> marker
> > = 0
> > DEBUG 3: Rejected: message type = 344
> > DEBUG 3: Rejected: masking region = 422
> > DEBUG 3: Rejected: bad fcst value = 0
> > DEBUG 3: Rejected: duplicates = 0
> >
> > In this example of verifying upper air temperature, point_stat
considered
> > 89893 observation values but only used 155 of them in the
computation of
> > statistics. The other counts list why the observations were
discarded
> > (79360 for the observation type, 5 for being off the grid, 9607
for the
> > vertical level, and so on).
> >
> > In your case, you'll see that MSLP has 0 matched pairs, but the
rejection
> > counts will give you more information as to *why* they were all
> discarded.
> >
> > If the problem isn't obvious, please send me the "run_ps.log"
file, and
> > I'll see if anything jumps out at me. And if we still can't
figure it
> out,
> > I'll have you send me a sample forecast file, point observation
file, and
> > point_stat config file. Hopefully I'd be able to diagnose the
problem
> from
> > there.
> >
> > Thanks,
> > John Halley Gotway
> >
> >
> > On Mon, Feb 6, 2017 at 2:35 PM, Jose Garcia-Rivera via RT <
> > met_help at ucar.edu
> > > wrote:
> >
> > >
> > > Mon Feb 06 14:35:22 2017: Request 79364 was acted upon.
> > > Transaction: Ticket created by GarciaJ at imsg.com
> > > Queue: met_help
> > > Subject: MSLP verification issue
> > > Owner: Nobody
> > > Requestors: GarciaJ at imsg.com
> > > Status: new
> > > Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=79364
> > > >
> > >
> > >
> > > Dear MetHelp,
> > >
> > > I'm trying to extract MSLP for verification, but MET finds no
matches.
> > > Can you help me in figuring out how to extract it? PREPBUFR
data is
> > > RAP
> > >
> > > Thanks,
> > > Jose M. Garcia-Rivera, PhD
> > > IMSG
> > >
> > >
> > > fcst = {
> > > message_type = [ "ADPSFC" ];
> > > sid_exc = [];
> > >
> > > field = [
> > > {
> > > name = "TMP";
> > > level = [ "Z2" ];
> > > cat_thresh = [ >=293 ];
> > > },
> > > {
> > > name = "RH";
> > > level = [ "Z2" ];
> > > cat_thresh = [ >=70 ];
> > > },
> > > {
> > > name = "WIND";
> > > level = [ "Z10" ];
> > > cat_thresh = [ >=5 ];
> > > },
> > > {
> > > name = "PRMSL";
> > > level = [ "Z0" ];
> > > cat_thresh = [ >=1000 ];
> > > }
> > > ];
> > >
> > > }
> > > obs = {
> > > message_type = [ "ADPSFC" ];
> > > sid_exc = [];
> > >
> > > field = [
> > > {
> > > name = "TMP";
> > > level = [ "Z2" ];
> > > cat_thresh = [ >=293 ];
> > > },
> > > {
> > > name = "RH";
> > > level = [ "Z2" ];
> > > cat_thresh = [ >=70 ];
> > > },
> > > {
> > > name = "WIND";
> > > level = [ "Z10" ];
> > > cat_thresh = [ >=5 ];
> > > },
> > > {
> > > name = "PRMSL";
> > > level = [ "R002" ];
> > > cat_thresh = [ >=1000 ];
> > > GRIB1_ptv = 388;
> > > }
> > > ];
> > > }
> > > This e-mail, including attachments, may include confidential
and/or
> > > proprietary information, and may be used only by the person or
entity
> > > to which it is addressed. If the reader of this e-mail is not
the
> > > intended recipient or his or her authorized agent, the reader is
> > > hereby notified that any dissemination, distribution or copying
of
> > > this e-mail is prohibited. If you have received this e-mail in
error,
> > > please notify the sender by replying to this message and delete
this
> > e-mail immediately.
> > >
> > >
> >
> > This e-mail, including attachments, may include confidential
and/or
> > proprietary information, and may be used only by the person or
entity to
> > which it is addressed. If the reader of this e-mail is not the
intended
> > recipient or his or her authorized agent, the reader is hereby
notified
> > that any dissemination, distribution or copying of this e-mail is
> > prohibited. If you have received this e-mail in error, please
notify the
> > sender by replying to this message and delete this e-mail
immediately.
> >
> >
>
> This e-mail, including attachments, may include confidential and/or
> proprietary information, and may be used only by the person or
entity to
> which it is addressed. If the reader of this e-mail is not the
intended
> recipient or his or her authorized agent, the reader is hereby
notified
> that any dissemination, distribution or copying of this e-mail is
> prohibited. If you have received this e-mail in error, please notify
the
> sender by replying to this message and delete this e-mail
immediately.
>
>
>
This e-mail, including attachments, may include confidential and/or
proprietary information, and may be used only by the person or entity
to which it is addressed. If the reader of this e-mail is not the
intended recipient or his or her authorized agent, the reader is
hereby notified that any dissemination, distribution or copying of
this e-mail is prohibited. If you have received this e-mail in error,
please notify the sender by replying to this message and delete this
e-mail immediately.
------------------------------------------------
More information about the Met_help
mailing list