[Met_help] [rt.rap.ucar.edu #92122] History for Obs being rejected based on Observation type
John Halley Gotway via RT
met_help at ucar.edu
Wed Sep 18 13:22:47 MDT 2019
----------------------------------------------------------------
Initial Request
----------------------------------------------------------------
John, I am trying to verify a model window over Taiwan. When I plot the
observations available there are plenty in the window. However, MET tells
me it has no matched pairs:
DEBUG 2:
DEBUG 2: Searching 85571 observations from 11951 messages.
DEBUG 2:
DEBUG 2:
----------------------------------------------------------------------------
----
DEBUG 2:
DEBUG 2: Processing TMP/Z2 versus TMP/Z2, for observation type ANYSFC, over
region FULL, for interpolation method BILIN(4), using 0 pairs.
DEBUG 3: Number of matched pairs = 0
DEBUG 3: Observations processed = 85571
DEBUG 3: Rejected: SID exclusion = 0
DEBUG 3: Rejected: obs type = 73522
DEBUG 3: Rejected: valid time = 143
DEBUG 3: Rejected: bad obs value = 0
DEBUG 3: Rejected: off the grid = 11855
DEBUG 3: Rejected: topography = 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 = 51
DEBUG 3: Rejected: duplicates = 0
DEBUG 2: Processing TMP/Z2 versus TMP/Z2, for observation type ANYSFC, over
region FULL, for interpolation method HiRA Ensemble NBRHD(169), using 0
pairs.
DEBUG 2: Processing TMP/Z2 versus TMP/Z2, for observation type ANYSFC, over
region FULL, for interpolation method HiRA Ensemble NBRHD(9), using 0 pairs.
DEBUG 2: Processing TMP/Z2NA versus TMP/Z2NA, for observation type ANYSFC,
over region FULL, for interpolation method HiRA Probability NBRHD(169),
using 0 pairs.
DEBUG 2: Processing TMP/Z2NA versus TMP/Z2NA, for observation type ANYSFC,
over region FULL, for interpolation method HiRA Probability NBRHD(9), using
0 pairs.
The config file is attached. I set obs_quality to everything, I am allowing
ADPSFC and LANDSF.
I sent a model file and ob files via AMRDEC.
Thanks
Bob Craig
----------------------------------------------------------------
Complete Ticket History
----------------------------------------------------------------
Subject: Obs being rejected based on Observation type
From: John Halley Gotway
Time: Tue Sep 17 11:36:26 2019
Bob,
OK, I grabbed the files you posted to ARMDEC and tested. First, I ran
plot_point_obs to illustrate how many stations fall on your model
domain:
*plot_point_obs 2018010306.nc <http://2018010306.nc> 2018010306.ps
<http://2018010306.ps> -data_file
PS.557WW_SC.U_DI.C_GP.GALWEM-RD-
REGRID_GR.C1P5KM_AR.TAIWAN_DD.20180103_CY.00_FH.006_DF.GR2*
*DEBUG 2: Retrieving grid from file:
PS.557WW_SC.U_DI.C_GP.GALWEM-RD-
REGRID_GR.C1P5KM_AR.TAIWAN_DD.20180103_CY.00_FH.006_DF.GR2
DEBUG 1: Opening netCDF file: 2018010306.nc <http://2018010306.nc>
DEBUG 2:
Processing 85571 observations at 11951 locations. DEBUG 2: Observation
var
names: ALL DEBUG 2: Observation message types: ALL DEBUG 1: Creating
postscript file: 2018010306.ps <http://2018010306.ps> DEBUG 2:
Finished
plotting 51 locations. DEBUG 2: Skipped 11900 locations off the grid.*
Looks like 51 stations fall in this domain. The resulting image is
attached. Coincidentally, I see that Point-Stat skipped exactly 51
points
where the forecast contains bad data:
*DEBUG 3: Rejected: bad fcst value = 51*
So next, let's plot 2-m temperature from your GRIB2 file to see what
the
values look like:
*plot_data_plane
PS.557WW_SC.U_DI.C_GP.GALWEM-RD-
REGRID_GR.C1P5KM_AR.TAIWAN_DD.20180103_CY.00_FH.006_DF.GR2
TMP_Z2.ps 'name="TMP"; level="Z2";'*
The resulting image is attached and shows a field of all gray, meaning
that
it's missing data values everywhere.
So you should have gotten 51 matched pairs for 2-m temperature, but
you got
0 because all of the forecast values are bad data.
I wanted to double-check this result so I used Unidata's IDV tool to
view
the 2-m temperature, and the result was the same... see attached
TMP_Z2_IDV.png.
Lastly, I ran wgrib2 on that file, and saw some suspicious output:
*wgrib2 -d 135
PS.557WW_SC.U_DI.C_GP.GALWEM-RD-
REGRID_GR.C1P5KM_AR.TAIWAN_DD.20180103_CY.00_FH.006_DF.GR2
Warning: g2lib/g2clib complex encode/decode may differ from WMO
standard,
use -g2clib 0 for WMO standard 135:9864803:d=2018010300:TMP:2 m above
ground:6 hour fcst:*
I've never seen this warning before. So maybe there's an issue in how
this
GRIB2 file was constructed.
Hope that helps point you in the right direction.
Thanks,
John
On Tue, Sep 17, 2019 at 10:01 AM robert.craig.2 at us.af.mil via RT <
met_help at ucar.edu> wrote:
>
> Tue Sep 17 10:01:20 2019: Request 92122 was acted upon.
> Transaction: Ticket created by robert.craig.2 at us.af.mil
> Queue: met_help
> Subject: Obs being rejected based on Observation type
> Owner: Nobody
> Requestors: robert.craig.2 at us.af.mil
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=92122 >
>
>
> John, I am trying to verify a model window over Taiwan. When I plot
the
> observations available there are plenty in the window. However, MET
tells
> me it has no matched pairs:
>
>
>
> DEBUG 2:
>
> DEBUG 2: Searching 85571 observations from 11951 messages.
>
> DEBUG 2:
>
> DEBUG 2:
>
>
----------------------------------------------------------------------------
> ----
>
> DEBUG 2:
>
> DEBUG 2: Processing TMP/Z2 versus TMP/Z2, for observation type
ANYSFC, over
> region FULL, for interpolation method BILIN(4), using 0 pairs.
>
> DEBUG 3: Number of matched pairs = 0
>
> DEBUG 3: Observations processed = 85571
>
> DEBUG 3: Rejected: SID exclusion = 0
>
> DEBUG 3: Rejected: obs type = 73522
>
> DEBUG 3: Rejected: valid time = 143
>
> DEBUG 3: Rejected: bad obs value = 0
>
> DEBUG 3: Rejected: off the grid = 11855
>
> DEBUG 3: Rejected: topography = 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 = 51
>
> DEBUG 3: Rejected: duplicates = 0
>
> DEBUG 2: Processing TMP/Z2 versus TMP/Z2, for observation type
ANYSFC, over
> region FULL, for interpolation method HiRA Ensemble NBRHD(169),
using 0
> pairs.
>
> DEBUG 2: Processing TMP/Z2 versus TMP/Z2, for observation type
ANYSFC, over
> region FULL, for interpolation method HiRA Ensemble NBRHD(9), using
0
> pairs.
>
> DEBUG 2: Processing TMP/Z2NA versus TMP/Z2NA, for observation type
ANYSFC,
> over region FULL, for interpolation method HiRA Probability
NBRHD(169),
> using 0 pairs.
>
> DEBUG 2: Processing TMP/Z2NA versus TMP/Z2NA, for observation type
ANYSFC,
> over region FULL, for interpolation method HiRA Probability
NBRHD(9), using
> 0 pairs.
>
>
>
> The config file is attached. I set obs_quality to everything, I am
> allowing
> ADPSFC and LANDSF.
>
>
>
> I sent a model file and ob files via AMRDEC.
>
>
>
> Thanks
>
> Bob Craig
>
>
>
------------------------------------------------
Subject: RE: [Non-DoD Source] Re: [rt.rap.ucar.edu #92122] Obs being rejected based on Observation type
From: robert.craig.2 at us.af.mil
Time: Tue Sep 17 12:38:18 2019
John, on quick question I forgot to ask in my last email. In the
manual, the instructions for plot_point_ob_usage says you can enter a
grib code to see a specific variable to be displayed. When I tried
"TMP" on the NETCDF file I sent you, it tells me it is ignoring the
-gc field. So, should I be able to display a specific variable type
in plot_point_ob_usage?
Thanks
Bob
-----Original Message-----
From: John Halley Gotway via RT <met_help at ucar.edu>
Sent: Tuesday, September 17, 2019 12:36 PM
To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
<robert.craig.2 at us.af.mil>
Subject: [Non-DoD Source] Re: [rt.rap.ucar.edu #92122] Obs being
rejected based on Observation type
Bob,
OK, I grabbed the files you posted to ARMDEC and tested. First, I ran
plot_point_obs to illustrate how many stations fall on your model
domain:
*plot_point_obs 2018010306.nc <http://2018010306.nc> 2018010306.ps
<http://2018010306.ps> -data_file
PS.557WW_SC.U_DI.C_GP.GALWEM-RD-
REGRID_GR.C1P5KM_AR.TAIWAN_DD.20180103_CY.00_FH.006_DF.GR2*
*DEBUG 2: Retrieving grid from file:
PS.557WW_SC.U_DI.C_GP.GALWEM-RD-
REGRID_GR.C1P5KM_AR.TAIWAN_DD.20180103_CY.00_FH.006_DF.GR2
DEBUG 1: Opening netCDF file: 2018010306.nc <http://2018010306.nc>
DEBUG 2:
Processing 85571 observations at 11951 locations. DEBUG 2: Observation
var
names: ALL DEBUG 2: Observation message types: ALL DEBUG 1: Creating
postscript file: 2018010306.ps <http://2018010306.ps> DEBUG 2:
Finished plotting 51 locations. DEBUG 2: Skipped 11900 locations off
the grid.*
Looks like 51 stations fall in this domain. The resulting image is
attached. Coincidentally, I see that Point-Stat skipped exactly 51
points where the forecast contains bad data:
*DEBUG 3: Rejected: bad fcst value = 51*
So next, let's plot 2-m temperature from your GRIB2 file to see what
the values look like:
*plot_data_plane
PS.557WW_SC.U_DI.C_GP.GALWEM-RD-
REGRID_GR.C1P5KM_AR.TAIWAN_DD.20180103_CY.00_FH.006_DF.GR2
TMP_Z2.ps 'name="TMP"; level="Z2";'*
The resulting image is attached and shows a field of all gray, meaning
that it's missing data values everywhere.
So you should have gotten 51 matched pairs for 2-m temperature, but
you got
0 because all of the forecast values are bad data.
I wanted to double-check this result so I used Unidata's IDV tool to
view the 2-m temperature, and the result was the same... see attached
TMP_Z2_IDV.png.
Lastly, I ran wgrib2 on that file, and saw some suspicious output:
*wgrib2 -d 135
PS.557WW_SC.U_DI.C_GP.GALWEM-RD-
REGRID_GR.C1P5KM_AR.TAIWAN_DD.20180103_CY.00_FH.006_DF.GR2
Warning: g2lib/g2clib complex encode/decode may differ from WMO
standard, use -g2clib 0 for WMO standard
135:9864803:d=2018010300:TMP:2 m above
ground:6 hour fcst:*
I've never seen this warning before. So maybe there's an issue in how
this
GRIB2 file was constructed.
Hope that helps point you in the right direction.
Thanks,
John
On Tue, Sep 17, 2019 at 10:01 AM robert.craig.2 at us.af.mil via RT <
met_help at ucar.edu> wrote:
>
> Tue Sep 17 10:01:20 2019: Request 92122 was acted upon.
> Transaction: Ticket created by robert.craig.2 at us.af.mil
> Queue: met_help
> Subject: Obs being rejected based on Observation type
> Owner: Nobody
> Requestors: robert.craig.2 at us.af.mil
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=92122
> >
>
>
> John, I am trying to verify a model window over Taiwan. When I plot
> the observations available there are plenty in the window. However,
> MET tells me it has no matched pairs:
>
>
>
> DEBUG 2:
>
> DEBUG 2: Searching 85571 observations from 11951 messages.
>
> DEBUG 2:
>
> DEBUG 2:
>
>
----------------------------------------------------------------------
> ------
> ----
>
> DEBUG 2:
>
> DEBUG 2: Processing TMP/Z2 versus TMP/Z2, for observation type
ANYSFC,
> over region FULL, for interpolation method BILIN(4), using 0 pairs.
>
> DEBUG 3: Number of matched pairs = 0
>
> DEBUG 3: Observations processed = 85571
>
> DEBUG 3: Rejected: SID exclusion = 0
>
> DEBUG 3: Rejected: obs type = 73522
>
> DEBUG 3: Rejected: valid time = 143
>
> DEBUG 3: Rejected: bad obs value = 0
>
> DEBUG 3: Rejected: off the grid = 11855
>
> DEBUG 3: Rejected: topography = 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 = 51
>
> DEBUG 3: Rejected: duplicates = 0
>
> DEBUG 2: Processing TMP/Z2 versus TMP/Z2, for observation type
ANYSFC,
> over region FULL, for interpolation method HiRA Ensemble NBRHD(169),
> using 0 pairs.
>
> DEBUG 2: Processing TMP/Z2 versus TMP/Z2, for observation type
ANYSFC,
> over region FULL, for interpolation method HiRA Ensemble NBRHD(9),
> using 0 pairs.
>
> DEBUG 2: Processing TMP/Z2NA versus TMP/Z2NA, for observation type
> ANYSFC, over region FULL, for interpolation method HiRA Probability
> NBRHD(169), using 0 pairs.
>
> DEBUG 2: Processing TMP/Z2NA versus TMP/Z2NA, for observation type
> ANYSFC, over region FULL, for interpolation method HiRA Probability
> NBRHD(9), using
> 0 pairs.
>
>
>
> The config file is attached. I set obs_quality to everything, I am
> allowing ADPSFC and LANDSF.
>
>
>
> I sent a model file and ob files via AMRDEC.
>
>
>
> Thanks
>
> Bob Craig
>
>
>
------------------------------------------------
Subject: RE: [Non-DoD Source] Re: [rt.rap.ucar.edu #92122] Obs being rejected based on Observation type
From: robert.craig.2 at us.af.mil
Time: Tue Sep 17 18:22:08 2019
Thanks John, I see what you are seeing. I usually assume the model
data is correct - but not in this case. I will be less trusting in
the future.
Bob
-----Original Message-----
From: John Halley Gotway via RT <met_help at ucar.edu>
Sent: Tuesday, September 17, 2019 12:36 PM
To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
<robert.craig.2 at us.af.mil>
Subject: [Non-DoD Source] Re: [rt.rap.ucar.edu #92122] Obs being
rejected based on Observation type
Bob,
OK, I grabbed the files you posted to ARMDEC and tested. First, I ran
plot_point_obs to illustrate how many stations fall on your model
domain:
*plot_point_obs 2018010306.nc <http://2018010306.nc> 2018010306.ps
<http://2018010306.ps> -data_file
PS.557WW_SC.U_DI.C_GP.GALWEM-RD-
REGRID_GR.C1P5KM_AR.TAIWAN_DD.20180103_CY.00_FH.006_DF.GR2*
*DEBUG 2: Retrieving grid from file:
PS.557WW_SC.U_DI.C_GP.GALWEM-RD-
REGRID_GR.C1P5KM_AR.TAIWAN_DD.20180103_CY.00_FH.006_DF.GR2
DEBUG 1: Opening netCDF file: 2018010306.nc <http://2018010306.nc>
DEBUG 2:
Processing 85571 observations at 11951 locations. DEBUG 2: Observation
var
names: ALL DEBUG 2: Observation message types: ALL DEBUG 1: Creating
postscript file: 2018010306.ps <http://2018010306.ps> DEBUG 2:
Finished plotting 51 locations. DEBUG 2: Skipped 11900 locations off
the grid.*
Looks like 51 stations fall in this domain. The resulting image is
attached. Coincidentally, I see that Point-Stat skipped exactly 51
points where the forecast contains bad data:
*DEBUG 3: Rejected: bad fcst value = 51*
So next, let's plot 2-m temperature from your GRIB2 file to see what
the values look like:
*plot_data_plane
PS.557WW_SC.U_DI.C_GP.GALWEM-RD-
REGRID_GR.C1P5KM_AR.TAIWAN_DD.20180103_CY.00_FH.006_DF.GR2
TMP_Z2.ps 'name="TMP"; level="Z2";'*
The resulting image is attached and shows a field of all gray, meaning
that it's missing data values everywhere.
So you should have gotten 51 matched pairs for 2-m temperature, but
you got
0 because all of the forecast values are bad data.
I wanted to double-check this result so I used Unidata's IDV tool to
view the 2-m temperature, and the result was the same... see attached
TMP_Z2_IDV.png.
Lastly, I ran wgrib2 on that file, and saw some suspicious output:
*wgrib2 -d 135
PS.557WW_SC.U_DI.C_GP.GALWEM-RD-
REGRID_GR.C1P5KM_AR.TAIWAN_DD.20180103_CY.00_FH.006_DF.GR2
Warning: g2lib/g2clib complex encode/decode may differ from WMO
standard, use -g2clib 0 for WMO standard
135:9864803:d=2018010300:TMP:2 m above
ground:6 hour fcst:*
I've never seen this warning before. So maybe there's an issue in how
this
GRIB2 file was constructed.
Hope that helps point you in the right direction.
Thanks,
John
On Tue, Sep 17, 2019 at 10:01 AM robert.craig.2 at us.af.mil via RT <
met_help at ucar.edu> wrote:
>
> Tue Sep 17 10:01:20 2019: Request 92122 was acted upon.
> Transaction: Ticket created by robert.craig.2 at us.af.mil
> Queue: met_help
> Subject: Obs being rejected based on Observation type
> Owner: Nobody
> Requestors: robert.craig.2 at us.af.mil
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=92122
> >
>
>
> John, I am trying to verify a model window over Taiwan. When I plot
> the observations available there are plenty in the window. However,
> MET tells me it has no matched pairs:
>
>
>
> DEBUG 2:
>
> DEBUG 2: Searching 85571 observations from 11951 messages.
>
> DEBUG 2:
>
> DEBUG 2:
>
>
----------------------------------------------------------------------
> ------
> ----
>
> DEBUG 2:
>
> DEBUG 2: Processing TMP/Z2 versus TMP/Z2, for observation type
ANYSFC,
> over region FULL, for interpolation method BILIN(4), using 0 pairs.
>
> DEBUG 3: Number of matched pairs = 0
>
> DEBUG 3: Observations processed = 85571
>
> DEBUG 3: Rejected: SID exclusion = 0
>
> DEBUG 3: Rejected: obs type = 73522
>
> DEBUG 3: Rejected: valid time = 143
>
> DEBUG 3: Rejected: bad obs value = 0
>
> DEBUG 3: Rejected: off the grid = 11855
>
> DEBUG 3: Rejected: topography = 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 = 51
>
> DEBUG 3: Rejected: duplicates = 0
>
> DEBUG 2: Processing TMP/Z2 versus TMP/Z2, for observation type
ANYSFC,
> over region FULL, for interpolation method HiRA Ensemble NBRHD(169),
> using 0 pairs.
>
> DEBUG 2: Processing TMP/Z2 versus TMP/Z2, for observation type
ANYSFC,
> over region FULL, for interpolation method HiRA Ensemble NBRHD(9),
> using 0 pairs.
>
> DEBUG 2: Processing TMP/Z2NA versus TMP/Z2NA, for observation type
> ANYSFC, over region FULL, for interpolation method HiRA Probability
> NBRHD(169), using 0 pairs.
>
> DEBUG 2: Processing TMP/Z2NA versus TMP/Z2NA, for observation type
> ANYSFC, over region FULL, for interpolation method HiRA Probability
> NBRHD(9), using
> 0 pairs.
>
>
>
> The config file is attached. I set obs_quality to everything, I am
> allowing ADPSFC and LANDSF.
>
>
>
> I sent a model file and ob files via AMRDEC.
>
>
>
> Thanks
>
> Bob Craig
>
>
>
------------------------------------------------
Subject: Obs being rejected based on Observation type
From: John Halley Gotway
Time: Tue Sep 17 21:45:20 2019
Agreed, I certainly haven’t seen this behavior much before. But
there’s
all sorts of things that can go wrong when creating GRIB output files.
Thanks,
John
On Tue, Sep 17, 2019 at 6:22 PM robert.craig.2 at us.af.mil via RT <
met_help at ucar.edu> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=92122 >
>
> Thanks John, I see what you are seeing. I usually assume the model
data
> is correct - but not in this case. I will be less trusting in the
future.
>
> Bob
>
> -----Original Message-----
> From: John Halley Gotway via RT <met_help at ucar.edu>
> Sent: Tuesday, September 17, 2019 12:36 PM
> To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
<robert.craig.2 at us.af.mil>
> Subject: [Non-DoD Source] Re: [rt.rap.ucar.edu #92122] Obs being
rejected
> based on Observation type
>
> Bob,
>
> OK, I grabbed the files you posted to ARMDEC and tested. First, I
ran
> plot_point_obs to illustrate how many stations fall on your model
domain:
>
>
> *plot_point_obs 2018010306.nc <http://2018010306.nc> 2018010306.ps <
> http://2018010306.ps> -data_file
>
> PS.557WW_SC.U_DI.C_GP.GALWEM-RD-
REGRID_GR.C1P5KM_AR.TAIWAN_DD.20180103_CY.00_FH.006_DF.GR2*
>
>
>
>
>
>
>
> *DEBUG 2: Retrieving grid from file:
>
> PS.557WW_SC.U_DI.C_GP.GALWEM-RD-
REGRID_GR.C1P5KM_AR.TAIWAN_DD.20180103_CY.00_FH.006_DF.GR2
> DEBUG 1: Opening netCDF file: 2018010306.nc <http://2018010306.nc>
DEBUG
> 2:
> Processing 85571 observations at 11951 locations. DEBUG 2:
Observation var
> names: ALL DEBUG 2: Observation message types: ALL DEBUG 1: Creating
> postscript file: 2018010306.ps <http://2018010306.ps> DEBUG 2:
Finished
> plotting 51 locations. DEBUG 2: Skipped 11900 locations off the
grid.*
>
> Looks like 51 stations fall in this domain. The resulting image is
> attached. Coincidentally, I see that Point-Stat skipped exactly 51
points
> where the forecast contains bad data:
>
> *DEBUG 3: Rejected: bad fcst value = 51*
>
> So next, let's plot 2-m temperature from your GRIB2 file to see what
the
> values look like:
>
> *plot_data_plane
>
> PS.557WW_SC.U_DI.C_GP.GALWEM-RD-
REGRID_GR.C1P5KM_AR.TAIWAN_DD.20180103_CY.00_FH.006_DF.GR2
> TMP_Z2.ps 'name="TMP"; level="Z2";'*
>
> The resulting image is attached and shows a field of all gray,
meaning
> that it's missing data values everywhere.
>
> So you should have gotten 51 matched pairs for 2-m temperature, but
you got
> 0 because all of the forecast values are bad data.
>
> I wanted to double-check this result so I used Unidata's IDV tool to
view
> the 2-m temperature, and the result was the same... see attached
> TMP_Z2_IDV.png.
>
> Lastly, I ran wgrib2 on that file, and saw some suspicious output:
>
>
>
> *wgrib2 -d 135
>
> PS.557WW_SC.U_DI.C_GP.GALWEM-RD-
REGRID_GR.C1P5KM_AR.TAIWAN_DD.20180103_CY.00_FH.006_DF.GR2
> Warning: g2lib/g2clib complex encode/decode may differ from WMO
standard,
> use -g2clib 0 for WMO standard 135:9864803:d=2018010300:TMP:2 m
above
> ground:6 hour fcst:*
>
> I've never seen this warning before. So maybe there's an issue in
how this
> GRIB2 file was constructed.
>
> Hope that helps point you in the right direction.
>
> Thanks,
> John
>
>
>
> On Tue, Sep 17, 2019 at 10:01 AM robert.craig.2 at us.af.mil via RT <
> met_help at ucar.edu> wrote:
>
> >
> > Tue Sep 17 10:01:20 2019: Request 92122 was acted upon.
> > Transaction: Ticket created by robert.craig.2 at us.af.mil
> > Queue: met_help
> > Subject: Obs being rejected based on Observation type
> > Owner: Nobody
> > Requestors: robert.craig.2 at us.af.mil
> > Status: new
> > Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=92122
> > >
> >
> >
> > John, I am trying to verify a model window over Taiwan. When I
plot
> > the observations available there are plenty in the window.
However,
> > MET tells me it has no matched pairs:
> >
> >
> >
> > DEBUG 2:
> >
> > DEBUG 2: Searching 85571 observations from 11951 messages.
> >
> > DEBUG 2:
> >
> > DEBUG 2:
> >
> >
----------------------------------------------------------------------
> > ------
> > ----
> >
> > DEBUG 2:
> >
> > DEBUG 2: Processing TMP/Z2 versus TMP/Z2, for observation type
ANYSFC,
> > over region FULL, for interpolation method BILIN(4), using 0
pairs.
> >
> > DEBUG 3: Number of matched pairs = 0
> >
> > DEBUG 3: Observations processed = 85571
> >
> > DEBUG 3: Rejected: SID exclusion = 0
> >
> > DEBUG 3: Rejected: obs type = 73522
> >
> > DEBUG 3: Rejected: valid time = 143
> >
> > DEBUG 3: Rejected: bad obs value = 0
> >
> > DEBUG 3: Rejected: off the grid = 11855
> >
> > DEBUG 3: Rejected: topography = 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 = 51
> >
> > DEBUG 3: Rejected: duplicates = 0
> >
> > DEBUG 2: Processing TMP/Z2 versus TMP/Z2, for observation type
ANYSFC,
> > over region FULL, for interpolation method HiRA Ensemble
NBRHD(169),
> > using 0 pairs.
> >
> > DEBUG 2: Processing TMP/Z2 versus TMP/Z2, for observation type
ANYSFC,
> > over region FULL, for interpolation method HiRA Ensemble NBRHD(9),
> > using 0 pairs.
> >
> > DEBUG 2: Processing TMP/Z2NA versus TMP/Z2NA, for observation type
> > ANYSFC, over region FULL, for interpolation method HiRA
Probability
> > NBRHD(169), using 0 pairs.
> >
> > DEBUG 2: Processing TMP/Z2NA versus TMP/Z2NA, for observation type
> > ANYSFC, over region FULL, for interpolation method HiRA
Probability
> > NBRHD(9), using
> > 0 pairs.
> >
> >
> >
> > The config file is attached. I set obs_quality to everything, I
am
> > allowing ADPSFC and LANDSF.
> >
> >
> >
> > I sent a model file and ob files via AMRDEC.
> >
> >
> >
> > Thanks
> >
> > Bob Craig
> >
> >
> >
>
>
>
>
------------------------------------------------
More information about the Met_help
mailing list