[Met_help] [rt.rap.ucar.edu #90379] History for Bad Obs Value

John Halley Gotway via RT met_help at ucar.edu
Wed Jul 10 17:03:24 MDT 2019


----------------------------------------------------------------
  Initial Request
----------------------------------------------------------------

John, I am verifying forecast field of precip type against surface
observations of precip type.  The values are code values ranging from 0 - 6,
192.    Looking in my obs file, the obs_vals are either missing or 0 -6.  I
use censor thresh and value to make sure the obs code and model code refer
to the same precip type.  When I verify, MET throws away all the obs for
"bad obs value".   The run output is below.  Notice the censor values are
floats instead of integers - not sure if this is a problem.  My config file
and the observation files are attached.   Also, notice  the bold warning -
how do I use the information in my config file?   It says it used the first
entry and that one is the one hour precip type which should be correct.

 

Thanks

Bob

 

Processing 6hour

Using forecast file ->
/h/data/global/FSMT/data/GALWEM/RD/output/korea_1p5km_10_6/PS.557WW_SC.U_DI.
C_GP.GALWEM-RD-REGRID_GR.C1P5KM_AR.KOREA_DD.20180102_CY.00_FH.006_DF.GR2

Using observation file ->
/h/data/global/WXQC/data/met/nc_obs/ptype/2018010206.nc

Using climo file ->  []

Using config file ->
/h/data/global/WXQC/data/met/config/met_config/PointStatConfig_PT_korea_1p5_
10_6

Running MET command string ->  ['/h/WXQC/met-8.1/bin/point_stat',
'/h/data/global/FSMT/data/GALWEM/RD/output/korea_1p5km_10_6/PS.557WW_SC.U_DI
.C_GP.GALWEM-RD-REGRID_GR.C1P5KM_AR.KOREA_DD.20180102_CY.00_FH.006_DF.GR2',
'/h/data/global/WXQC/data/met/nc_obs/ptype/2018010206.nc',
'/h/data/global/WXQC/data/met/config/met_config/PointStatConfig_PT_korea_1p5
_10_6_updated', '-outdir',
'/h/data/global/WXQC/data/met/ptstat/mdlob_pairs/korea_1p5_10_6/PT', '-v',
'3']

DEBUG 1: Reading user-defined grib1 MET_GRIB_TABLES file:
/h/data/global/WXQC/data/met/config/grib2/grib1_af_131_57.txt

DEBUG 1: Reading user-defined grib2 MET_GRIB_TABLES file:
/h/data/global/WXQC/data/met/config/grib2/grib2_geps.txt

DEBUG 1: Default Config File:
/h/WXQC/met-8.1/share/met/config/PointStatConfig_default

DEBUG 1: User Config File:
/h/data/global/WXQC/data/met/config/met_config/PointStatConfig_PT_korea_1p5_
10_6_updated

GSL_RNG_TYPE=mt19937

GSL_RNG_SEED=1921903964

DEBUG 1: Forecast File:
/h/data/global/FSMT/data/GALWEM/RD/output/korea_1p5km_10_6/PS.557WW_SC.U_DI.
C_GP.GALWEM-RD-REGRID_GR.C1P5KM_AR.KOREA_DD.20180102_CY.00_FH.006_DF.GR2

DEBUG 1: Observation File:
/h/data/global/WXQC/data/met/nc_obs/ptype/2018010206.nc

WARNING: 

WARNING: MetGrib2DataFile::data_plane_array() -> Using the first of 2 exact
matching records for "PTYPE/L0":

WARNING: record 44 field 1: ipdtmpl[29] = 1, 19, 2, 255, 16, 0, 0, 1, 5, 1,
-127, 255, 255, -127, 255, 2018, 1, 2, 6, 0, 0, 1, 0, 0, 2, 1, 1, 255, 0

WARNING: record 45 field 1: ipdtmpl[29] = 1, 19, 2, 255, 16, 0, 0, 1, 3, 1,
-127, 255, 255, -127, 255, 2018, 1, 2, 6, 0, 0, 1, 0, 0, 2, 1, 3, 255, 0

WARNING: Try setting the 0-based "GRIB2_ipdtmpl_index" and
"GRIB2_ipdtmpl_val" config file options to select one.

WARNING: 

DEBUG 3: Applying censor thresholds "==0 ==6 ==192 ==4 ==3 ==7 ==8 ==9" and
replacing with values "-9999.00000 5.00000 2.00000 6.00000 6.00000 4.00000
3.00000 3.00000".

DEBUG 3: Censored values for 328926 of 336000 grid points.

DEBUG 2: 

DEBUG 2:
----------------------------------------------------------------------------
----

DEBUG 2: 

DEBUG 2: Reading data for PTYPE/L0.

DEBUG 3: Use the matching forecast and observation grids.

DEBUG 3: Grid Definition: Projection: Lambert Conformal Nx: 420 Ny: 800
Lat_LL: 32.758 Lon_LL: -123.644 Lon_orient: -127.000 Alpha: 8437.628 Cone:
0.618 Bx: 210.1230 By: 5797.8017

DEBUG 2: Processing masking regions.

DEBUG 3: Processing grid mask: FULL

DEBUG 2: Processing geography data.

DEBUG 2: For PTYPE/L0 found 1 forecast levels, 0 climatology mean levels,
and 0 climatology standard deviation levels.

DEBUG 2: 

DEBUG 2:
----------------------------------------------------------------------------
----

DEBUG 2: 

DEBUG 2: Searching 12375 observations from 12375 messages.

DEBUG 2: 

DEBUG 2:
----------------------------------------------------------------------------
----

DEBUG 2: 

DEBUG 2: Processing PTYPE/L0 versus PTYPE/L0, for observation type ADPSFC,
over region FULL, for interpolation method NEAREST(1), using 0 pairs.

DEBUG 3: Number of matched pairs  = 0

DEBUG 3: Observations processed   = 12375

DEBUG 3: Rejected: SID exclusion  = 0

DEBUG 3: Rejected: obs type       = 0

DEBUG 3: Rejected: valid time     = 0

DEBUG 3: Rejected: bad obs value  = 10563

DEBUG 3: Rejected: off the grid   = 1810

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 = 2

DEBUG 3: Rejected: duplicates     = 0

DEBUG 2:



----------------------------------------------------------------
  Complete Ticket History
----------------------------------------------------------------

Subject: Bad Obs Value
From: Tara Jensen
Time: Wed May 29 07:29:52 2019

Hi Bob,

John is out for the week.  METviewer does plot Roebber diagrams.  I
believe
METviewer has been approved for install at your facility but will need
to
follow-up on that.  In the meantime, if you'd like to try out the
interface, we can host some of your data here at NCAR if you'd like.

Cheers, Tara

On Tue, May 28, 2019 at 1:53 PM robert.craig.2 at us.af.mil via RT <
met_help at ucar.edu> wrote:

>
> Tue May 28 13:53:26 2019: Request 90379 was acted upon.
> Transaction: Ticket created by robert.craig.2 at us.af.mil
>        Queue: met_help
>      Subject: Bad Obs Value
>        Owner: Nobody
>   Requestors: robert.craig.2 at us.af.mil
>       Status: new
>  Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=90379 >
>
>
> John, I am verifying forecast field of precip type against surface
> observations of precip type.  The values are code values ranging
from 0 -
> 6,
> 192.    Looking in my obs file, the obs_vals are either missing or 0
-6.  I
> use censor thresh and value to make sure the obs code and model code
refer
> to the same precip type.  When I verify, MET throws away all the obs
for
> "bad obs value".   The run output is below.  Notice the censor
values are
> floats instead of integers - not sure if this is a problem.  My
config file
> and the observation files are attached.   Also, notice  the bold
warning -
> how do I use the information in my config file?   It says it used
the first
> entry and that one is the one hour precip type which should be
correct.
>
>
>
> Thanks
>
> Bob
>
>
>
> Processing 6hour
>
> Using forecast file ->
>
>
/h/data/global/FSMT/data/GALWEM/RD/output/korea_1p5km_10_6/PS.557WW_SC.U_DI.
> C_GP.GALWEM-RD-
REGRID_GR.C1P5KM_AR.KOREA_DD.20180102_CY.00_FH.006_DF.GR2
>
> Using observation file ->
> /h/data/global/WXQC/data/met/nc_obs/ptype/2018010206.nc
>
> Using climo file ->  []
>
> Using config file ->
>
>
/h/data/global/WXQC/data/met/config/met_config/PointStatConfig_PT_korea_1p5_
> 10_6
>
> Running MET command string ->  ['/h/WXQC/met-8.1/bin/point_stat',
>
>
'/h/data/global/FSMT/data/GALWEM/RD/output/korea_1p5km_10_6/PS.557WW_SC.U_DI
> .C_GP.GALWEM-RD-
REGRID_GR.C1P5KM_AR.KOREA_DD.20180102_CY.00_FH.006_DF.GR2',
> '/h/data/global/WXQC/data/met/nc_obs/ptype/2018010206.nc',
>
>
'/h/data/global/WXQC/data/met/config/met_config/PointStatConfig_PT_korea_1p5
> _10_6_updated', '-outdir',
> '/h/data/global/WXQC/data/met/ptstat/mdlob_pairs/korea_1p5_10_6/PT',
'-v',
> '3']
>
> DEBUG 1: Reading user-defined grib1 MET_GRIB_TABLES file:
> /h/data/global/WXQC/data/met/config/grib2/grib1_af_131_57.txt
>
> DEBUG 1: Reading user-defined grib2 MET_GRIB_TABLES file:
> /h/data/global/WXQC/data/met/config/grib2/grib2_geps.txt
>
> DEBUG 1: Default Config File:
> /h/WXQC/met-8.1/share/met/config/PointStatConfig_default
>
> DEBUG 1: User Config File:
>
>
/h/data/global/WXQC/data/met/config/met_config/PointStatConfig_PT_korea_1p5_
> 10_6_updated
>
> GSL_RNG_TYPE=mt19937
>
> GSL_RNG_SEED=1921903964
>
> DEBUG 1: Forecast File:
>
>
/h/data/global/FSMT/data/GALWEM/RD/output/korea_1p5km_10_6/PS.557WW_SC.U_DI.
> C_GP.GALWEM-RD-
REGRID_GR.C1P5KM_AR.KOREA_DD.20180102_CY.00_FH.006_DF.GR2
>
> DEBUG 1: Observation File:
> /h/data/global/WXQC/data/met/nc_obs/ptype/2018010206.nc
>
> WARNING:
>
> WARNING: MetGrib2DataFile::data_plane_array() -> Using the first of
2 exact
> matching records for "PTYPE/L0":
>
> WARNING: record 44 field 1: ipdtmpl[29] = 1, 19, 2, 255, 16, 0, 0,
1, 5, 1,
> -127, 255, 255, -127, 255, 2018, 1, 2, 6, 0, 0, 1, 0, 0, 2, 1, 1,
255, 0
>
> WARNING: record 45 field 1: ipdtmpl[29] = 1, 19, 2, 255, 16, 0, 0,
1, 3, 1,
> -127, 255, 255, -127, 255, 2018, 1, 2, 6, 0, 0, 1, 0, 0, 2, 1, 3,
255, 0
>
> WARNING: Try setting the 0-based "GRIB2_ipdtmpl_index" and
> "GRIB2_ipdtmpl_val" config file options to select one.
>
> WARNING:
>
> DEBUG 3: Applying censor thresholds "==0 ==6 ==192 ==4 ==3 ==7 ==8
==9" and
> replacing with values "-9999.00000 5.00000 2.00000 6.00000 6.00000
4.00000
> 3.00000 3.00000".
>
> DEBUG 3: Censored values for 328926 of 336000 grid points.
>
> DEBUG 2:
>
> DEBUG 2:
>
>
----------------------------------------------------------------------------
> ----
>
> DEBUG 2:
>
> DEBUG 2: Reading data for PTYPE/L0.
>
> DEBUG 3: Use the matching forecast and observation grids.
>
> DEBUG 3: Grid Definition: Projection: Lambert Conformal Nx: 420 Ny:
800
> Lat_LL: 32.758 Lon_LL: -123.644 Lon_orient: -127.000 Alpha: 8437.628
Cone:
> 0.618 Bx: 210.1230 By: 5797.8017
>
> DEBUG 2: Processing masking regions.
>
> DEBUG 3: Processing grid mask: FULL
>
> DEBUG 2: Processing geography data.
>
> DEBUG 2: For PTYPE/L0 found 1 forecast levels, 0 climatology mean
levels,
> and 0 climatology standard deviation levels.
>
> DEBUG 2:
>
> DEBUG 2:
>
>
----------------------------------------------------------------------------
> ----
>
> DEBUG 2:
>
> DEBUG 2: Searching 12375 observations from 12375 messages.
>
> DEBUG 2:
>
> DEBUG 2:
>
>
----------------------------------------------------------------------------
> ----
>
> DEBUG 2:
>
> DEBUG 2: Processing PTYPE/L0 versus PTYPE/L0, for observation type
ADPSFC,
> over region FULL, for interpolation method NEAREST(1), using 0
pairs.
>
> DEBUG 3: Number of matched pairs  = 0
>
> DEBUG 3: Observations processed   = 12375
>
> DEBUG 3: Rejected: SID exclusion  = 0
>
> DEBUG 3: Rejected: obs type       = 0
>
> DEBUG 3: Rejected: valid time     = 0
>
> DEBUG 3: Rejected: bad obs value  = 10563
>
> DEBUG 3: Rejected: off the grid   = 1810
>
> 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 = 2
>
> DEBUG 3: Rejected: duplicates     = 0
>
> DEBUG 2:
>
>
>

--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Tara Jensen
Project Manager II
NCAR RAL and DTC
PO Box 3000, Boulder, Colorado 80307 USA
+1 303-497-8479          jensen at ucar.edu

------------------------------------------------
Subject: RE: [Non-DoD Source] Re: [rt.rap.ucar.edu #90379] Bad Obs Value
From: robert.craig.2 at us.af.mil
Time: Wed May 29 07:44:07 2019

Hi Tara, I figured John must have been out.  I have a couple tickets
open currently - one is using the GO Index.  The manual is vague on
how to select the model and it reference in the configuration file.
If someone is familiar with that or could send me one of your
configuration files you used for this, any help would be appreciated.

We have placed MET 8.1 on our Dev system.  We should be able to
install MET Viewer on our development system as well - I believe I
have the proper permissions.   How do you deploy MET Viewer - do you
have to install it?

Thanks

-----Original Message-----
From: Tara Jensen via RT <met_help at ucar.edu>
Sent: Wednesday, May 29, 2019 8:30 AM
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 #90379] Bad Obs Value

Hi Bob,

John is out for the week.  METviewer does plot Roebber diagrams.  I
believe METviewer has been approved for install at your facility but
will need to follow-up on that.  In the meantime, if you'd like to try
out the interface, we can host some of your data here at NCAR if you'd
like.

Cheers, Tara

On Tue, May 28, 2019 at 1:53 PM robert.craig.2 at us.af.mil via RT <
met_help at ucar.edu> wrote:

>
> Tue May 28 13:53:26 2019: Request 90379 was acted upon.
> Transaction: Ticket created by robert.craig.2 at us.af.mil
>        Queue: met_help
>      Subject: Bad Obs Value
>        Owner: Nobody
>   Requestors: robert.craig.2 at us.af.mil
>       Status: new
>  Ticket <URL:
>
https://usg01.safelinks.protection.office365.us/?url=https%3A%2F%2Frt.
>
rap.ucar.edu%2Frt%2FTicket%2FDisplay.html%3Fid%3D90379&data=02%7C0
>
1%7Crobert.craig.2%40us.af.mil%7Ce6a9be97fcbb4389f1af08d6e439df07%7C83
>
31b18d2d8748efa35fac8818ebf9b4%7C1%7C1%7C636947334571481633&sdata=
> Z0SQbQIov4RWEKfiwVL2gf97gJgM7iiKdbI2NbMJiM4%3D&reserved=0 >
>
>
> John, I am verifying forecast field of precip type against surface
> observations of precip type.  The values are code values ranging
from
> 0 - 6,
> 192.    Looking in my obs file, the obs_vals are either missing or 0
-6.  I
> use censor thresh and value to make sure the obs code and model code
> refer to the same precip type.  When I verify, MET throws away all
the obs for
> "bad obs value".   The run output is below.  Notice the censor
values are
> floats instead of integers - not sure if this is a problem.  My
config file
> and the observation files are attached.   Also, notice  the bold
warning -
> how do I use the information in my config file?   It says it used
the first
> entry and that one is the one hour precip type which should be
correct.
>
>
>
> Thanks
>
> Bob
>
>
>
> Processing 6hour
>
> Using forecast file ->
>
>
/h/data/global/FSMT/data/GALWEM/RD/output/korea_1p5km_10_6/PS.557WW_SC.U_DI.
> C_GP.GALWEM-RD-
REGRID_GR.C1P5KM_AR.KOREA_DD.20180102_CY.00_FH.006_DF.G
> R2
>
> Using observation file ->
> /h/data/global/WXQC/data/met/nc_obs/ptype/2018010206.nc
>
> Using climo file ->  []
>
> Using config file ->
>
>
/h/data/global/WXQC/data/met/config/met_config/PointStatConfig_PT_kore
> a_1p5_
> 10_6
>
> Running MET command string ->  ['/h/WXQC/met-8.1/bin/point_stat',
>
>
'/h/data/global/FSMT/data/GALWEM/RD/output/korea_1p5km_10_6/PS.557WW_S
> C.U_DI
> .C_GP.GALWEM-RD-
REGRID_GR.C1P5KM_AR.KOREA_DD.20180102_CY.00_FH.006_DF.
> GR2', '/h/data/global/WXQC/data/met/nc_obs/ptype/2018010206.nc',
>
>
'/h/data/global/WXQC/data/met/config/met_config/PointStatConfig_PT_kor
> ea_1p5
> _10_6_updated', '-outdir',
> '/h/data/global/WXQC/data/met/ptstat/mdlob_pairs/korea_1p5_10_6/PT',
> '-v', '3']
>
> DEBUG 1: Reading user-defined grib1 MET_GRIB_TABLES file:
> /h/data/global/WXQC/data/met/config/grib2/grib1_af_131_57.txt
>
> DEBUG 1: Reading user-defined grib2 MET_GRIB_TABLES file:
> /h/data/global/WXQC/data/met/config/grib2/grib2_geps.txt
>
> DEBUG 1: Default Config File:
> /h/WXQC/met-8.1/share/met/config/PointStatConfig_default
>
> DEBUG 1: User Config File:
>
>
/h/data/global/WXQC/data/met/config/met_config/PointStatConfig_PT_kore
> a_1p5_
> 10_6_updated
>
> GSL_RNG_TYPE=mt19937
>
> GSL_RNG_SEED=1921903964
>
> DEBUG 1: Forecast File:
>
>
/h/data/global/FSMT/data/GALWEM/RD/output/korea_1p5km_10_6/PS.557WW_SC.U_DI.
> C_GP.GALWEM-RD-
REGRID_GR.C1P5KM_AR.KOREA_DD.20180102_CY.00_FH.006_DF.G
> R2
>
> DEBUG 1: Observation File:
> /h/data/global/WXQC/data/met/nc_obs/ptype/2018010206.nc
>
> WARNING:
>
> WARNING: MetGrib2DataFile::data_plane_array() -> Using the first of
2
> exact matching records for "PTYPE/L0":
>
> WARNING: record 44 field 1: ipdtmpl[29] = 1, 19, 2, 255, 16, 0, 0,
1,
> 5, 1, -127, 255, 255, -127, 255, 2018, 1, 2, 6, 0, 0, 1, 0, 0, 2, 1,
> 1, 255, 0
>
> WARNING: record 45 field 1: ipdtmpl[29] = 1, 19, 2, 255, 16, 0, 0,
1,
> 3, 1, -127, 255, 255, -127, 255, 2018, 1, 2, 6, 0, 0, 1, 0, 0, 2, 1,
> 3, 255, 0
>
> WARNING: Try setting the 0-based "GRIB2_ipdtmpl_index" and
> "GRIB2_ipdtmpl_val" config file options to select one.
>
> WARNING:
>
> DEBUG 3: Applying censor thresholds "==0 ==6 ==192 ==4 ==3 ==7 ==8
> ==9" and replacing with values "-9999.00000 5.00000 2.00000 6.00000
> 6.00000 4.00000
> 3.00000 3.00000".
>
> DEBUG 3: Censored values for 328926 of 336000 grid points.
>
> DEBUG 2:
>
> DEBUG 2:
>
>
----------------------------------------------------------------------
> ------
> ----
>
> DEBUG 2:
>
> DEBUG 2: Reading data for PTYPE/L0.
>
> DEBUG 3: Use the matching forecast and observation grids.
>
> DEBUG 3: Grid Definition: Projection: Lambert Conformal Nx: 420 Ny:
> 800
> Lat_LL: 32.758 Lon_LL: -123.644 Lon_orient: -127.000 Alpha: 8437.628
Cone:
> 0.618 Bx: 210.1230 By: 5797.8017
>
> DEBUG 2: Processing masking regions.
>
> DEBUG 3: Processing grid mask: FULL
>
> DEBUG 2: Processing geography data.
>
> DEBUG 2: For PTYPE/L0 found 1 forecast levels, 0 climatology mean
> levels, and 0 climatology standard deviation levels.
>
> DEBUG 2:
>
> DEBUG 2:
>
>
----------------------------------------------------------------------
> ------
> ----
>
> DEBUG 2:
>
> DEBUG 2: Searching 12375 observations from 12375 messages.
>
> DEBUG 2:
>
> DEBUG 2:
>
>
----------------------------------------------------------------------
> ------
> ----
>
> DEBUG 2:
>
> DEBUG 2: Processing PTYPE/L0 versus PTYPE/L0, for observation type
> ADPSFC, over region FULL, for interpolation method NEAREST(1), using
0 pairs.
>
> DEBUG 3: Number of matched pairs  = 0
>
> DEBUG 3: Observations processed   = 12375
>
> DEBUG 3: Rejected: SID exclusion  = 0
>
> DEBUG 3: Rejected: obs type       = 0
>
> DEBUG 3: Rejected: valid time     = 0
>
> DEBUG 3: Rejected: bad obs value  = 10563
>
> DEBUG 3: Rejected: off the grid   = 1810
>
> 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 = 2
>
> DEBUG 3: Rejected: duplicates     = 0
>
> DEBUG 2:
>
>
>

--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Tara Jensen
Project Manager II
NCAR RAL and DTC
PO Box 3000, Boulder, Colorado 80307 USA
+1 303-497-8479          jensen at ucar.edu



------------------------------------------------
Subject: Bad Obs Value
From: John Halley Gotway
Time: Wed May 29 10:43:25 2019

Bob,

Yes, I'm out of the office this week but do have some limited access
to
email.  Tatiana would really be the best person to help with the
installation of METviewer.  Are you the person at the AF responsible
for
doing this?

I agree with Tara that it may be useful to have you send us MET output
to
host in our instance of METviewer.  I think there are two underlying
questions here...
- How do you get METviewer installed and administer it well?
- How do you make good use of METviewer?

To answer the second question, it'd be useful to put some sample data
in
the NCAR METviewer instance that we can use to work up examples.

Thanks,
John

On Wed, May 29, 2019 at 7:44 AM robert.craig.2 at us.af.mil via RT <
met_help at ucar.edu> wrote:

>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=90379 >
>
> Hi Tara, I figured John must have been out.  I have a couple tickets
open
> currently - one is using the GO Index.  The manual is vague on how
to
> select the model and it reference in the configuration file.  If
someone is
> familiar with that or could send me one of your configuration files
you
> used for this, any help would be appreciated.
>
> We have placed MET 8.1 on our Dev system.  We should be able to
install
> MET Viewer on our development system as well - I believe I have the
proper
> permissions.   How do you deploy MET Viewer - do you have to install
it?
>
> Thanks
>
> -----Original Message-----
> From: Tara Jensen via RT <met_help at ucar.edu>
> Sent: Wednesday, May 29, 2019 8:30 AM
> 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 #90379] Bad Obs Value
>
> Hi Bob,
>
> John is out for the week.  METviewer does plot Roebber diagrams.  I
> believe METviewer has been approved for install at your facility but
will
> need to follow-up on that.  In the meantime, if you'd like to try
out the
> interface, we can host some of your data here at NCAR if you'd like.
>
> Cheers, Tara
>
> On Tue, May 28, 2019 at 1:53 PM robert.craig.2 at us.af.mil via RT <
> met_help at ucar.edu> wrote:
>
> >
> > Tue May 28 13:53:26 2019: Request 90379 was acted upon.
> > Transaction: Ticket created by robert.craig.2 at us.af.mil
> >        Queue: met_help
> >      Subject: Bad Obs Value
> >        Owner: Nobody
> >   Requestors: robert.craig.2 at us.af.mil
> >       Status: new
> >  Ticket <URL:
> >
https://usg01.safelinks.protection.office365.us/?url=https%3A%2F%2Frt.
> >
rap.ucar.edu%2Frt%2FTicket%2FDisplay.html%3Fid%3D90379&data=02%7C0
> >
1%7Crobert.craig.2%40us.af.mil%7Ce6a9be97fcbb4389f1af08d6e439df07%7C83
> >
31b18d2d8748efa35fac8818ebf9b4%7C1%7C1%7C636947334571481633&sdata=
> > Z0SQbQIov4RWEKfiwVL2gf97gJgM7iiKdbI2NbMJiM4%3D&reserved=0 >
> >
> >
> > John, I am verifying forecast field of precip type against surface
> > observations of precip type.  The values are code values ranging
from
> > 0 - 6,
> > 192.    Looking in my obs file, the obs_vals are either missing or
0
> -6.  I
> > use censor thresh and value to make sure the obs code and model
code
> > refer to the same precip type.  When I verify, MET throws away all
the
> obs for
> > "bad obs value".   The run output is below.  Notice the censor
values are
> > floats instead of integers - not sure if this is a problem.  My
config
> file
> > and the observation files are attached.   Also, notice  the bold
warning
> -
> > how do I use the information in my config file?   It says it used
the
> first
> > entry and that one is the one hour precip type which should be
correct.
> >
> >
> >
> > Thanks
> >
> > Bob
> >
> >
> >
> > Processing 6hour
> >
> > Using forecast file ->
> >
> >
>
/h/data/global/FSMT/data/GALWEM/RD/output/korea_1p5km_10_6/PS.557WW_SC.U_DI.
> > C_GP.GALWEM-RD-
REGRID_GR.C1P5KM_AR.KOREA_DD.20180102_CY.00_FH.006_DF.G
> > R2
> >
> > Using observation file ->
> > /h/data/global/WXQC/data/met/nc_obs/ptype/2018010206.nc
> >
> > Using climo file ->  []
> >
> > Using config file ->
> >
> >
/h/data/global/WXQC/data/met/config/met_config/PointStatConfig_PT_kore
> > a_1p5_
> > 10_6
> >
> > Running MET command string ->  ['/h/WXQC/met-8.1/bin/point_stat',
> >
> >
'/h/data/global/FSMT/data/GALWEM/RD/output/korea_1p5km_10_6/PS.557WW_S
> > C.U_DI
> > .C_GP.GALWEM-RD-
REGRID_GR.C1P5KM_AR.KOREA_DD.20180102_CY.00_FH.006_DF.
> > GR2', '/h/data/global/WXQC/data/met/nc_obs/ptype/2018010206.nc',
> >
> >
'/h/data/global/WXQC/data/met/config/met_config/PointStatConfig_PT_kor
> > ea_1p5
> > _10_6_updated', '-outdir',
> >
'/h/data/global/WXQC/data/met/ptstat/mdlob_pairs/korea_1p5_10_6/PT',
> > '-v', '3']
> >
> > DEBUG 1: Reading user-defined grib1 MET_GRIB_TABLES file:
> > /h/data/global/WXQC/data/met/config/grib2/grib1_af_131_57.txt
> >
> > DEBUG 1: Reading user-defined grib2 MET_GRIB_TABLES file:
> > /h/data/global/WXQC/data/met/config/grib2/grib2_geps.txt
> >
> > DEBUG 1: Default Config File:
> > /h/WXQC/met-8.1/share/met/config/PointStatConfig_default
> >
> > DEBUG 1: User Config File:
> >
> >
/h/data/global/WXQC/data/met/config/met_config/PointStatConfig_PT_kore
> > a_1p5_
> > 10_6_updated
> >
> > GSL_RNG_TYPE=mt19937
> >
> > GSL_RNG_SEED=1921903964
> >
> > DEBUG 1: Forecast File:
> >
> >
>
/h/data/global/FSMT/data/GALWEM/RD/output/korea_1p5km_10_6/PS.557WW_SC.U_DI.
> > C_GP.GALWEM-RD-
REGRID_GR.C1P5KM_AR.KOREA_DD.20180102_CY.00_FH.006_DF.G
> > R2
> >
> > DEBUG 1: Observation File:
> > /h/data/global/WXQC/data/met/nc_obs/ptype/2018010206.nc
> >
> > WARNING:
> >
> > WARNING: MetGrib2DataFile::data_plane_array() -> Using the first
of 2
> > exact matching records for "PTYPE/L0":
> >
> > WARNING: record 44 field 1: ipdtmpl[29] = 1, 19, 2, 255, 16, 0, 0,
1,
> > 5, 1, -127, 255, 255, -127, 255, 2018, 1, 2, 6, 0, 0, 1, 0, 0, 2,
1,
> > 1, 255, 0
> >
> > WARNING: record 45 field 1: ipdtmpl[29] = 1, 19, 2, 255, 16, 0, 0,
1,
> > 3, 1, -127, 255, 255, -127, 255, 2018, 1, 2, 6, 0, 0, 1, 0, 0, 2,
1,
> > 3, 255, 0
> >
> > WARNING: Try setting the 0-based "GRIB2_ipdtmpl_index" and
> > "GRIB2_ipdtmpl_val" config file options to select one.
> >
> > WARNING:
> >
> > DEBUG 3: Applying censor thresholds "==0 ==6 ==192 ==4 ==3 ==7 ==8
> > ==9" and replacing with values "-9999.00000 5.00000 2.00000
6.00000
> > 6.00000 4.00000
> > 3.00000 3.00000".
> >
> > DEBUG 3: Censored values for 328926 of 336000 grid points.
> >
> > DEBUG 2:
> >
> > DEBUG 2:
> >
> >
----------------------------------------------------------------------
> > ------
> > ----
> >
> > DEBUG 2:
> >
> > DEBUG 2: Reading data for PTYPE/L0.
> >
> > DEBUG 3: Use the matching forecast and observation grids.
> >
> > DEBUG 3: Grid Definition: Projection: Lambert Conformal Nx: 420
Ny:
> > 800
> > Lat_LL: 32.758 Lon_LL: -123.644 Lon_orient: -127.000 Alpha:
8437.628
> Cone:
> > 0.618 Bx: 210.1230 By: 5797.8017
> >
> > DEBUG 2: Processing masking regions.
> >
> > DEBUG 3: Processing grid mask: FULL
> >
> > DEBUG 2: Processing geography data.
> >
> > DEBUG 2: For PTYPE/L0 found 1 forecast levels, 0 climatology mean
> > levels, and 0 climatology standard deviation levels.
> >
> > DEBUG 2:
> >
> > DEBUG 2:
> >
> >
----------------------------------------------------------------------
> > ------
> > ----
> >
> > DEBUG 2:
> >
> > DEBUG 2: Searching 12375 observations from 12375 messages.
> >
> > DEBUG 2:
> >
> > DEBUG 2:
> >
> >
----------------------------------------------------------------------
> > ------
> > ----
> >
> > DEBUG 2:
> >
> > DEBUG 2: Processing PTYPE/L0 versus PTYPE/L0, for observation type
> > ADPSFC, over region FULL, for interpolation method NEAREST(1),
using 0
> pairs.
> >
> > DEBUG 3: Number of matched pairs  = 0
> >
> > DEBUG 3: Observations processed   = 12375
> >
> > DEBUG 3: Rejected: SID exclusion  = 0
> >
> > DEBUG 3: Rejected: obs type       = 0
> >
> > DEBUG 3: Rejected: valid time     = 0
> >
> > DEBUG 3: Rejected: bad obs value  = 10563
> >
> > DEBUG 3: Rejected: off the grid   = 1810
> >
> > 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 = 2
> >
> > DEBUG 3: Rejected: duplicates     = 0
> >
> > DEBUG 2:
> >
> >
> >
>
> --
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Tara Jensen
> Project Manager II
> NCAR RAL and DTC
> PO Box 3000, Boulder, Colorado 80307 USA
> +1 303-497-8479          jensen at ucar.edu
>
>
>
>

------------------------------------------------
Subject: RE: [Non-DoD Source] Re: [rt.rap.ucar.edu #90379] Bad Obs Value
From: robert.craig.2 at us.af.mil
Time: Wed May 29 10:54:58 2019

John, I would be the guy to install it on Dev 9 if it is relatively
straight forward like the MET 8.1 code.  If it is more complicated
than that, we would have to discuss with Tatiana the best way forward.
We currently have our data in model specific and variable specific
directories.  So in the case of GALWEM, we would have the .stat files
in GALWEM/TT for temperature or GALWEM/TP for precip.  How does MET
viewer expect the files to be organized?  Once we know this, I will
send you our data for testing as you suggested.

Thanks
Bob

-----Original Message-----
From: John Halley Gotway via RT <met_help at ucar.edu>
Sent: Wednesday, May 29, 2019 11:43 AM
To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
<robert.craig.2 at us.af.mil>
Subject: Re: [Non-DoD Source] Re: [rt.rap.ucar.edu #90379] Bad Obs
Value

Bob,

Yes, I'm out of the office this week but do have some limited access
to email.  Tatiana would really be the best person to help with the
installation of METviewer.  Are you the person at the AF responsible
for doing this?

I agree with Tara that it may be useful to have you send us MET output
to host in our instance of METviewer.  I think there are two
underlying questions here...
- How do you get METviewer installed and administer it well?
- How do you make good use of METviewer?

To answer the second question, it'd be useful to put some sample data
in the NCAR METviewer instance that we can use to work up examples.

Thanks,
John

On Wed, May 29, 2019 at 7:44 AM robert.craig.2 at us.af.mil via RT <
met_help at ucar.edu> wrote:

>
> <URL:
>
https://usg01.safelinks.protection.office365.us/?url=https%3A%2F%2Frt.
>
rap.ucar.edu%2Frt%2FTicket%2FDisplay.html%3Fid%3D90379&data=02%7C0
>
1%7Crobert.craig.2%40us.af.mil%7Cf902e763a511472ca49108d6e454e4e5%7C83
>
31b18d2d8748efa35fac8818ebf9b4%7C1%7C1%7C636947450630658177&sdata=
> 6Gnyb1zXxQxd%2BGLG6Az2%2Fpz4bcPQKTT6bvEbutmgbgU%3D&reserved=0 >
>
> Hi Tara, I figured John must have been out.  I have a couple tickets
> open currently - one is using the GO Index.  The manual is vague on
> how to select the model and it reference in the configuration file.
> If someone is familiar with that or could send me one of your
> configuration files you used for this, any help would be
appreciated.
>
> We have placed MET 8.1 on our Dev system.  We should be able to
> install MET Viewer on our development system as well - I believe I
have the proper
> permissions.   How do you deploy MET Viewer - do you have to install
it?
>
> Thanks
>
> -----Original Message-----
> From: Tara Jensen via RT <met_help at ucar.edu>
> Sent: Wednesday, May 29, 2019 8:30 AM
> 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 #90379] Bad Obs Value
>
> Hi Bob,
>
> John is out for the week.  METviewer does plot Roebber diagrams.  I
> believe METviewer has been approved for install at your facility but
> will need to follow-up on that.  In the meantime, if you'd like to
try
> out the interface, we can host some of your data here at NCAR if
you'd like.
>
> Cheers, Tara
>
> On Tue, May 28, 2019 at 1:53 PM robert.craig.2 at us.af.mil via RT <
> met_help at ucar.edu> wrote:
>
> >
> > Tue May 28 13:53:26 2019: Request 90379 was acted upon.
> > Transaction: Ticket created by robert.craig.2 at us.af.mil
> >        Queue: met_help
> >      Subject: Bad Obs Value
> >        Owner: Nobody
> >   Requestors: robert.craig.2 at us.af.mil
> >       Status: new
> >  Ticket <URL:
> >
https://usg01.safelinks.protection.office365.us/?url=https%3A%2F%2Frt.
> >
rap.ucar.edu%2Frt%2FTicket%2FDisplay.html%3Fid%3D90379&data=02%7
> > C0
> >
1%7Crobert.craig.2%40us.af.mil%7Ce6a9be97fcbb4389f1af08d6e439df07%7C
> > 83
> >
31b18d2d8748efa35fac8818ebf9b4%7C1%7C1%7C636947334571481633&sdat
> > a=
> > Z0SQbQIov4RWEKfiwVL2gf97gJgM7iiKdbI2NbMJiM4%3D&reserved=0 >
> >
> >
> > John, I am verifying forecast field of precip type against surface
> > observations of precip type.  The values are code values ranging
> > from
> > 0 - 6,
> > 192.    Looking in my obs file, the obs_vals are either missing or
0
> -6.  I
> > use censor thresh and value to make sure the obs code and model
code
> > refer to the same precip type.  When I verify, MET throws away all
> > the
> obs for
> > "bad obs value".   The run output is below.  Notice the censor
values are
> > floats instead of integers - not sure if this is a problem.  My
> > config
> file
> > and the observation files are attached.   Also, notice  the bold
warning
> -
> > how do I use the information in my config file?   It says it used
the
> first
> > entry and that one is the one hour precip type which should be
correct.
> >
> >
> >
> > Thanks
> >
> > Bob
> >
> >
> >
> > Processing 6hour
> >
> > Using forecast file ->
> >
> >
>
/h/data/global/FSMT/data/GALWEM/RD/output/korea_1p5km_10_6/PS.557WW_SC.U_DI.
> > C_GP.GALWEM-RD-
REGRID_GR.C1P5KM_AR.KOREA_DD.20180102_CY.00_FH.006_DF
> > .G
> > R2
> >
> > Using observation file ->
> > /h/data/global/WXQC/data/met/nc_obs/ptype/2018010206.nc
> >
> > Using climo file ->  []
> >
> > Using config file ->
> >
> >
/h/data/global/WXQC/data/met/config/met_config/PointStatConfig_PT_ko
> > re
> > a_1p5_
> > 10_6
> >
> > Running MET command string ->  ['/h/WXQC/met-8.1/bin/point_stat',
> >
> >
'/h/data/global/FSMT/data/GALWEM/RD/output/korea_1p5km_10_6/PS.557WW
> > _S
> > C.U_DI
> > .C_GP.GALWEM-RD-
REGRID_GR.C1P5KM_AR.KOREA_DD.20180102_CY.00_FH.006_DF.
> > GR2', '/h/data/global/WXQC/data/met/nc_obs/ptype/2018010206.nc',
> >
> >
'/h/data/global/WXQC/data/met/config/met_config/PointStatConfig_PT_k
> > or
> > ea_1p5
> > _10_6_updated', '-outdir',
> >
'/h/data/global/WXQC/data/met/ptstat/mdlob_pairs/korea_1p5_10_6/PT',
> > '-v', '3']
> >
> > DEBUG 1: Reading user-defined grib1 MET_GRIB_TABLES file:
> > /h/data/global/WXQC/data/met/config/grib2/grib1_af_131_57.txt
> >
> > DEBUG 1: Reading user-defined grib2 MET_GRIB_TABLES file:
> > /h/data/global/WXQC/data/met/config/grib2/grib2_geps.txt
> >
> > DEBUG 1: Default Config File:
> > /h/WXQC/met-8.1/share/met/config/PointStatConfig_default
> >
> > DEBUG 1: User Config File:
> >
> >
/h/data/global/WXQC/data/met/config/met_config/PointStatConfig_PT_ko
> > re
> > a_1p5_
> > 10_6_updated
> >
> > GSL_RNG_TYPE=mt19937
> >
> > GSL_RNG_SEED=1921903964
> >
> > DEBUG 1: Forecast File:
> >
> >
>
/h/data/global/FSMT/data/GALWEM/RD/output/korea_1p5km_10_6/PS.557WW_SC.U_DI.
> > C_GP.GALWEM-RD-
REGRID_GR.C1P5KM_AR.KOREA_DD.20180102_CY.00_FH.006_DF
> > .G
> > R2
> >
> > DEBUG 1: Observation File:
> > /h/data/global/WXQC/data/met/nc_obs/ptype/2018010206.nc
> >
> > WARNING:
> >
> > WARNING: MetGrib2DataFile::data_plane_array() -> Using the first
of
> > 2 exact matching records for "PTYPE/L0":
> >
> > WARNING: record 44 field 1: ipdtmpl[29] = 1, 19, 2, 255, 16, 0, 0,
> > 1, 5, 1, -127, 255, 255, -127, 255, 2018, 1, 2, 6, 0, 0, 1, 0, 0,
2,
> > 1, 1, 255, 0
> >
> > WARNING: record 45 field 1: ipdtmpl[29] = 1, 19, 2, 255, 16, 0, 0,
> > 1, 3, 1, -127, 255, 255, -127, 255, 2018, 1, 2, 6, 0, 0, 1, 0, 0,
2,
> > 1, 3, 255, 0
> >
> > WARNING: Try setting the 0-based "GRIB2_ipdtmpl_index" and
> > "GRIB2_ipdtmpl_val" config file options to select one.
> >
> > WARNING:
> >
> > DEBUG 3: Applying censor thresholds "==0 ==6 ==192 ==4 ==3 ==7 ==8
> > ==9" and replacing with values "-9999.00000 5.00000 2.00000
6.00000
> > 6.00000 4.00000
> > 3.00000 3.00000".
> >
> > DEBUG 3: Censored values for 328926 of 336000 grid points.
> >
> > DEBUG 2:
> >
> > DEBUG 2:
> >
> >
--------------------------------------------------------------------
> > --
> > ------
> > ----
> >
> > DEBUG 2:
> >
> > DEBUG 2: Reading data for PTYPE/L0.
> >
> > DEBUG 3: Use the matching forecast and observation grids.
> >
> > DEBUG 3: Grid Definition: Projection: Lambert Conformal Nx: 420
Ny:
> > 800
> > Lat_LL: 32.758 Lon_LL: -123.644 Lon_orient: -127.000 Alpha:
8437.628
> Cone:
> > 0.618 Bx: 210.1230 By: 5797.8017
> >
> > DEBUG 2: Processing masking regions.
> >
> > DEBUG 3: Processing grid mask: FULL
> >
> > DEBUG 2: Processing geography data.
> >
> > DEBUG 2: For PTYPE/L0 found 1 forecast levels, 0 climatology mean
> > levels, and 0 climatology standard deviation levels.
> >
> > DEBUG 2:
> >
> > DEBUG 2:
> >
> >
--------------------------------------------------------------------
> > --
> > ------
> > ----
> >
> > DEBUG 2:
> >
> > DEBUG 2: Searching 12375 observations from 12375 messages.
> >
> > DEBUG 2:
> >
> > DEBUG 2:
> >
> >
--------------------------------------------------------------------
> > --
> > ------
> > ----
> >
> > DEBUG 2:
> >
> > DEBUG 2: Processing PTYPE/L0 versus PTYPE/L0, for observation type
> > ADPSFC, over region FULL, for interpolation method NEAREST(1),
using
> > 0
> pairs.
> >
> > DEBUG 3: Number of matched pairs  = 0
> >
> > DEBUG 3: Observations processed   = 12375
> >
> > DEBUG 3: Rejected: SID exclusion  = 0
> >
> > DEBUG 3: Rejected: obs type       = 0
> >
> > DEBUG 3: Rejected: valid time     = 0
> >
> > DEBUG 3: Rejected: bad obs value  = 10563
> >
> > DEBUG 3: Rejected: off the grid   = 1810
> >
> > 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 = 2
> >
> > DEBUG 3: Rejected: duplicates     = 0
> >
> > DEBUG 2:
> >
> >
> >
>
> --
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Tara Jensen
> Project Manager II
> NCAR RAL and DTC
> PO Box 3000, Boulder, Colorado 80307 USA
> +1 303-497-8479          jensen at ucar.edu
>
>
>
>



------------------------------------------------
Subject: Bad Obs Value
From: John Halley Gotway
Time: Wed May 29 11:04:26 2019

Bob,

There really are no requirements for how you organize your MET output
files
for METviewer.  Instead, you can organize it into whatever directory
structure makes sense for your organization.  But when you want to
load
data into a METviewer database, you setup an XML file to *describe*
how the
directory structure.

The tags used in the Load XML are described here:
http://www.dtcenter.org/met/metviewer/doc/load.html

In particular, the <folder_tmpl> tag defines the directory structure.

But we should start by getting METviewer installed first.

John

On Wed, May 29, 2019 at 10:55 AM robert.craig.2 at us.af.mil via RT <
met_help at ucar.edu> wrote:

>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=90379 >
>
> John, I would be the guy to install it on Dev 9 if it is relatively
> straight forward like the MET 8.1 code.  If it is more complicated
than
> that, we would have to discuss with Tatiana the best way forward.
We
> currently have our data in model specific and variable specific
> directories.  So in the case of GALWEM, we would have the .stat
files in
> GALWEM/TT for temperature or GALWEM/TP for precip.  How does MET
viewer
> expect the files to be organized?  Once we know this, I will send
you our
> data for testing as you suggested.
>
> Thanks
> Bob
>
> -----Original Message-----
> From: John Halley Gotway via RT <met_help at ucar.edu>
> Sent: Wednesday, May 29, 2019 11:43 AM
> To: CRAIG, ROBERT J GS-12 USAF ACC 16 WS/WXN
<robert.craig.2 at us.af.mil>
> Subject: Re: [Non-DoD Source] Re: [rt.rap.ucar.edu #90379] Bad Obs
Value
>
> Bob,
>
> Yes, I'm out of the office this week but do have some limited access
to
> email.  Tatiana would really be the best person to help with the
> installation of METviewer.  Are you the person at the AF responsible
for
> doing this?
>
> I agree with Tara that it may be useful to have you send us MET
output to
> host in our instance of METviewer.  I think there are two underlying
> questions here...
> - How do you get METviewer installed and administer it well?
> - How do you make good use of METviewer?
>
> To answer the second question, it'd be useful to put some sample
data in
> the NCAR METviewer instance that we can use to work up examples.
>
> Thanks,
> John
>
> On Wed, May 29, 2019 at 7:44 AM robert.craig.2 at us.af.mil via RT <
> met_help at ucar.edu> wrote:
>
> >
> > <URL:
> >
https://usg01.safelinks.protection.office365.us/?url=https%3A%2F%2Frt.
> >
rap.ucar.edu%2Frt%2FTicket%2FDisplay.html%3Fid%3D90379&data=02%7C0
> >
1%7Crobert.craig.2%40us.af.mil%7Cf902e763a511472ca49108d6e454e4e5%7C83
> >
31b18d2d8748efa35fac8818ebf9b4%7C1%7C1%7C636947450630658177&sdata=
> > 6Gnyb1zXxQxd%2BGLG6Az2%2Fpz4bcPQKTT6bvEbutmgbgU%3D&reserved=0
>
> >
> > Hi Tara, I figured John must have been out.  I have a couple
tickets
> > open currently - one is using the GO Index.  The manual is vague
on
> > how to select the model and it reference in the configuration
file.
> > If someone is familiar with that or could send me one of your
> > configuration files you used for this, any help would be
appreciated.
> >
> > We have placed MET 8.1 on our Dev system.  We should be able to
> > install MET Viewer on our development system as well - I believe I
have
> the proper
> > permissions.   How do you deploy MET Viewer - do you have to
install it?
> >
> > Thanks
> >
> > -----Original Message-----
> > From: Tara Jensen via RT <met_help at ucar.edu>
> > Sent: Wednesday, May 29, 2019 8:30 AM
> > 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 #90379] Bad Obs
Value
> >
> > Hi Bob,
> >
> > John is out for the week.  METviewer does plot Roebber diagrams.
I
> > believe METviewer has been approved for install at your facility
but
> > will need to follow-up on that.  In the meantime, if you'd like to
try
> > out the interface, we can host some of your data here at NCAR if
you'd
> like.
> >
> > Cheers, Tara
> >
> > On Tue, May 28, 2019 at 1:53 PM robert.craig.2 at us.af.mil via RT <
> > met_help at ucar.edu> wrote:
> >
> > >
> > > Tue May 28 13:53:26 2019: Request 90379 was acted upon.
> > > Transaction: Ticket created by robert.craig.2 at us.af.mil
> > >        Queue: met_help
> > >      Subject: Bad Obs Value
> > >        Owner: Nobody
> > >   Requestors: robert.craig.2 at us.af.mil
> > >       Status: new
> > >  Ticket <URL:
> > >
https://usg01.safelinks.protection.office365.us/?url=https%3A%2F%2Frt.
> > >
rap.ucar.edu%2Frt%2FTicket%2FDisplay.html%3Fid%3D90379&data=02%7
> > > C0
> > >
1%7Crobert.craig.2%40us.af.mil%7Ce6a9be97fcbb4389f1af08d6e439df07%7C
> > > 83
> > >
31b18d2d8748efa35fac8818ebf9b4%7C1%7C1%7C636947334571481633&sdat
> > > a=
> > > Z0SQbQIov4RWEKfiwVL2gf97gJgM7iiKdbI2NbMJiM4%3D&reserved=0 >
> > >
> > >
> > > John, I am verifying forecast field of precip type against
surface
> > > observations of precip type.  The values are code values ranging
> > > from
> > > 0 - 6,
> > > 192.    Looking in my obs file, the obs_vals are either missing
or 0
> > -6.  I
> > > use censor thresh and value to make sure the obs code and model
code
> > > refer to the same precip type.  When I verify, MET throws away
all
> > > the
> > obs for
> > > "bad obs value".   The run output is below.  Notice the censor
values
> are
> > > floats instead of integers - not sure if this is a problem.  My
> > > config
> > file
> > > and the observation files are attached.   Also, notice  the bold
> warning
> > -
> > > how do I use the information in my config file?   It says it
used the
> > first
> > > entry and that one is the one hour precip type which should be
correct.
> > >
> > >
> > >
> > > Thanks
> > >
> > > Bob
> > >
> > >
> > >
> > > Processing 6hour
> > >
> > > Using forecast file ->
> > >
> > >
> >
>
/h/data/global/FSMT/data/GALWEM/RD/output/korea_1p5km_10_6/PS.557WW_SC.U_DI.
> > > C_GP.GALWEM-RD-
REGRID_GR.C1P5KM_AR.KOREA_DD.20180102_CY.00_FH.006_DF
> > > .G
> > > R2
> > >
> > > Using observation file ->
> > > /h/data/global/WXQC/data/met/nc_obs/ptype/2018010206.nc
> > >
> > > Using climo file ->  []
> > >
> > > Using config file ->
> > >
> > >
/h/data/global/WXQC/data/met/config/met_config/PointStatConfig_PT_ko
> > > re
> > > a_1p5_
> > > 10_6
> > >
> > > Running MET command string ->  ['/h/WXQC/met-
8.1/bin/point_stat',
> > >
> > >
'/h/data/global/FSMT/data/GALWEM/RD/output/korea_1p5km_10_6/PS.557WW
> > > _S
> > > C.U_DI
> > > .C_GP.GALWEM-RD-
REGRID_GR.C1P5KM_AR.KOREA_DD.20180102_CY.00_FH.006_DF.
> > > GR2', '/h/data/global/WXQC/data/met/nc_obs/ptype/2018010206.nc',
> > >
> > >
'/h/data/global/WXQC/data/met/config/met_config/PointStatConfig_PT_k
> > > or
> > > ea_1p5
> > > _10_6_updated', '-outdir',
> > >
'/h/data/global/WXQC/data/met/ptstat/mdlob_pairs/korea_1p5_10_6/PT',
> > > '-v', '3']
> > >
> > > DEBUG 1: Reading user-defined grib1 MET_GRIB_TABLES file:
> > > /h/data/global/WXQC/data/met/config/grib2/grib1_af_131_57.txt
> > >
> > > DEBUG 1: Reading user-defined grib2 MET_GRIB_TABLES file:
> > > /h/data/global/WXQC/data/met/config/grib2/grib2_geps.txt
> > >
> > > DEBUG 1: Default Config File:
> > > /h/WXQC/met-8.1/share/met/config/PointStatConfig_default
> > >
> > > DEBUG 1: User Config File:
> > >
> > >
/h/data/global/WXQC/data/met/config/met_config/PointStatConfig_PT_ko
> > > re
> > > a_1p5_
> > > 10_6_updated
> > >
> > > GSL_RNG_TYPE=mt19937
> > >
> > > GSL_RNG_SEED=1921903964
> > >
> > > DEBUG 1: Forecast File:
> > >
> > >
> >
>
/h/data/global/FSMT/data/GALWEM/RD/output/korea_1p5km_10_6/PS.557WW_SC.U_DI.
> > > C_GP.GALWEM-RD-
REGRID_GR.C1P5KM_AR.KOREA_DD.20180102_CY.00_FH.006_DF
> > > .G
> > > R2
> > >
> > > DEBUG 1: Observation File:
> > > /h/data/global/WXQC/data/met/nc_obs/ptype/2018010206.nc
> > >
> > > WARNING:
> > >
> > > WARNING: MetGrib2DataFile::data_plane_array() -> Using the first
of
> > > 2 exact matching records for "PTYPE/L0":
> > >
> > > WARNING: record 44 field 1: ipdtmpl[29] = 1, 19, 2, 255, 16, 0,
0,
> > > 1, 5, 1, -127, 255, 255, -127, 255, 2018, 1, 2, 6, 0, 0, 1, 0,
0, 2,
> > > 1, 1, 255, 0
> > >
> > > WARNING: record 45 field 1: ipdtmpl[29] = 1, 19, 2, 255, 16, 0,
0,
> > > 1, 3, 1, -127, 255, 255, -127, 255, 2018, 1, 2, 6, 0, 0, 1, 0,
0, 2,
> > > 1, 3, 255, 0
> > >
> > > WARNING: Try setting the 0-based "GRIB2_ipdtmpl_index" and
> > > "GRIB2_ipdtmpl_val" config file options to select one.
> > >
> > > WARNING:
> > >
> > > DEBUG 3: Applying censor thresholds "==0 ==6 ==192 ==4 ==3 ==7
==8
> > > ==9" and replacing with values "-9999.00000 5.00000 2.00000
6.00000
> > > 6.00000 4.00000
> > > 3.00000 3.00000".
> > >
> > > DEBUG 3: Censored values for 328926 of 336000 grid points.
> > >
> > > DEBUG 2:
> > >
> > > DEBUG 2:
> > >
> > >
--------------------------------------------------------------------
> > > --
> > > ------
> > > ----
> > >
> > > DEBUG 2:
> > >
> > > DEBUG 2: Reading data for PTYPE/L0.
> > >
> > > DEBUG 3: Use the matching forecast and observation grids.
> > >
> > > DEBUG 3: Grid Definition: Projection: Lambert Conformal Nx: 420
Ny:
> > > 800
> > > Lat_LL: 32.758 Lon_LL: -123.644 Lon_orient: -127.000 Alpha:
8437.628
> > Cone:
> > > 0.618 Bx: 210.1230 By: 5797.8017
> > >
> > > DEBUG 2: Processing masking regions.
> > >
> > > DEBUG 3: Processing grid mask: FULL
> > >
> > > DEBUG 2: Processing geography data.
> > >
> > > DEBUG 2: For PTYPE/L0 found 1 forecast levels, 0 climatology
mean
> > > levels, and 0 climatology standard deviation levels.
> > >
> > > DEBUG 2:
> > >
> > > DEBUG 2:
> > >
> > >
--------------------------------------------------------------------
> > > --
> > > ------
> > > ----
> > >
> > > DEBUG 2:
> > >
> > > DEBUG 2: Searching 12375 observations from 12375 messages.
> > >
> > > DEBUG 2:
> > >
> > > DEBUG 2:
> > >
> > >
--------------------------------------------------------------------
> > > --
> > > ------
> > > ----
> > >
> > > DEBUG 2:
> > >
> > > DEBUG 2: Processing PTYPE/L0 versus PTYPE/L0, for observation
type
> > > ADPSFC, over region FULL, for interpolation method NEAREST(1),
using
> > > 0
> > pairs.
> > >
> > > DEBUG 3: Number of matched pairs  = 0
> > >
> > > DEBUG 3: Observations processed   = 12375
> > >
> > > DEBUG 3: Rejected: SID exclusion  = 0
> > >
> > > DEBUG 3: Rejected: obs type       = 0
> > >
> > > DEBUG 3: Rejected: valid time     = 0
> > >
> > > DEBUG 3: Rejected: bad obs value  = 10563
> > >
> > > DEBUG 3: Rejected: off the grid   = 1810
> > >
> > > 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 = 2
> > >
> > > DEBUG 3: Rejected: duplicates     = 0
> > >
> > > DEBUG 2:
> > >
> > >
> > >
> >
> > --
> > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> > Tara Jensen
> > Project Manager II
> > NCAR RAL and DTC
> > PO Box 3000, Boulder, Colorado 80307 USA
> > +1 303-497-8479          jensen at ucar.edu
> >
> >
> >
> >
>
>
>
>

------------------------------------------------


More information about the Met_help mailing list