[Met_help] [rt.rap.ucar.edu #68672] History for Level type
John Halley Gotway via RT
met_help at ucar.edu
Fri Oct 3 12:26:54 MDT 2014
----------------------------------------------------------------
Initial Request
----------------------------------------------------------------
Hi,
I just have a quick question.
I want to include this specific grib record (below) in my verification.
565:15053278:d=08122912:HGT:kpds5=7:kpds6=215:kpds7=0:TR=0:P1=84:P2=0:TimeU=1:cloud
ceiling:84hr fcst:NAve=0
If I define...
{
name = "HGT";
level = [ "R565" ];
cat_thresh = [];
}
in the field area, it will work just fine. I want to avoid using the
grib code record because that can change.
In the METv4.1/data/config/ README file it looks like I can define
GRIB_lvl_typ but everything I have tried has failed. What is the best
way to define this forecast field?
Thanks,
Travis
----------------------------------------------------------------
Complete Ticket History
----------------------------------------------------------------
Subject: Level type
From: John Halley Gotway
Time: Tue Aug 19 14:31:11 2014
Travis,
After playing around with this for a while, unfortunately, the answer
is
no. There is no easy way to extract that single record. When you use
the
"L0" level, you end up with 9 matching GRIB records:
METv4.1/bin/plot_data_plane WRFPRS_d02.068 img.ps 'name="HGT";
level="L0";'
-v 3
DEBUG 1: Opening data file: WRFPRS_d02.068
DEBUG 3: MetGrib1DataFile::data_plane_
array() -> Found range match for VarInfo "HGT/L0" in GRIB record 497
of
GRIB file "WRFPRS_d02.068".
DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found range match for
VarInfo "HGT/L0" in GRIB record 563 of GRIB file "WRFPRS_d02.068".
DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found range match for
VarInfo "HGT/L0" in GRIB record 564 of GRIB file "WRFPRS_d02.068".
DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found range match for
VarInfo "HGT/L0" in GRIB record 565 of GRIB file "WRFPRS_d02.068".
DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found range match for
VarInfo "HGT/L0" in GRIB record 567 of GRIB file "WRFPRS_d02.068".
DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found range match for
VarInfo "HGT/L0" in GRIB record 568 of GRIB file "WRFPRS_d02.068".
DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found range match for
VarInfo "HGT/L0" in GRIB record 577 of GRIB file "WRFPRS_d02.068".
DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found range match for
VarInfo "HGT/L0" in GRIB record 610 of GRIB file "WRFPRS_d02.068".
DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found range match for
VarInfo "HGT/L0" in GRIB record 611 of GRIB file "WRFPRS_d02.068".
DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found 9 GRIB records
matching VarInfo "HGT/L0" in GRIB file "WRFPRS_d02.068".
WARNING:
WARNING: MetGrib1DataFile::data_plane() -> Found 9 matches for VarInfo
"HGT/L0" in GRIB file "WRFPRS_d02.068". Using the first match found.
WARNING:
DEBUG 1: Creating postscript file: img.ps
I tried using the GRIB_lvl_typ and GRIB_lvl_val1 configuration options
to
select out record 565 that has a level type value of 215 (for cloud
ceiling), but that dind't do the trick.
As people have applied MET to a wider range of data types, our initial
design of specifying level information has proven insufficient. I'll
talk
to folks here and see if/how we can refine this logic. In your case,
the
following setting would be pretty straight-forward, right?
name="HGT"; level="L0"; GRIB_lvl_typ = 215;
Thanks,
John
On Fri, Aug 15, 2014 at 1:57 PM, Travis Wilson via RT
<met_help at ucar.edu>
wrote:
>
> Fri Aug 15 13:57:05 2014: Request 68672 was acted upon.
> Transaction: Ticket created by twilson at atmos.ucla.edu
> Queue: met_help
> Subject: Level type
> Owner: Nobody
> Requestors: twilson at atmos.ucla.edu
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=68672 >
>
>
> Hi,
>
> I just have a quick question.
>
> I want to include this specific grib record (below) in my
verification.
>
>
565:15053278:d=08122912:HGT:kpds5=7:kpds6=215:kpds7=0:TR=0:P1=84:P2=0:TimeU=1:cloud
> ceiling:84hr fcst:NAve=0
>
> If I define...
> {
> name = "HGT";
> level = [ "R565" ];
> cat_thresh = [];
> }
> in the field area, it will work just fine. I want to avoid using
the
> grib code record because that can change.
>
> In the METv4.1/data/config/ README file it looks like I can define
> GRIB_lvl_typ but everything I have tried has failed. What is the
best
> way to define this forecast field?
>
> Thanks,
> Travis
>
>
>
>
>
------------------------------------------------
Subject: Level type
From: John Halley Gotway
Time: Tue Aug 19 15:26:17 2014
Travis,
I made several little changes to METv4.1 to enable the use of the
following:
name="HGT"; level="L0"; GRIB_lvl_typ = 215;
And have it select that single record number 565. Please try applying
the
latest set of patches here:
http://www.dtcenter.org/met/users/support/known_issues/METv4.1/index.php
And then see if the following command matches just record number 565:
METv4.1/bin/plot_data_plane WRFPRS_d02.068 img.ps 'name="HGT";
level="L0"; GRIB_lvl_typ=215;' -v 3
Thanks,
John
On Tue, Aug 19, 2014 at 2:31 PM, The RT System itself via RT <
met_help at ucar.edu> wrote:
>
> Tue Aug 19 14:31:11 2014: Request 68672 was acted upon.
> Transaction: Given to johnhg by RT_System
> Queue: met_help
> Subject: Level type
> Owner: johnhg
> Requestors: twilson at atmos.ucla.edu
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=68672 >
>
>
> This transaction appears to have no content
>
------------------------------------------------
Subject: Re: [rt.rap.ucar.edu #68672] Level type
From: Travis Wilson
Time: Tue Aug 19 21:43:18 2014
John,
You are the man! This new logic seems reasonable.
I am in San Diego for a conference this week so I'll have to try this
out next week. I'll probably send you a full report on Monday.
Thanks
for doing this!
-Travis
On 08/19/2014 02:26 PM, John Halley Gotway via RT wrote:
> Travis,
>
> I made several little changes to METv4.1 to enable the use of the
following:
> name="HGT"; level="L0"; GRIB_lvl_typ = 215;
>
> And have it select that single record number 565. Please try
applying the
> latest set of patches here:
>
http://www.dtcenter.org/met/users/support/known_issues/METv4.1/index.php
>
> And then see if the following command matches just record number
565:
> METv4.1/bin/plot_data_plane WRFPRS_d02.068 img.ps 'name="HGT";
> level="L0"; GRIB_lvl_typ=215;' -v 3
>
>
> Thanks,
> John
>
>
> On Tue, Aug 19, 2014 at 2:31 PM, The RT System itself via RT <
> met_help at ucar.edu> wrote:
>
>> Tue Aug 19 14:31:11 2014: Request 68672 was acted upon.
>> Transaction: Given to johnhg by RT_System
>> Queue: met_help
>> Subject: Level type
>> Owner: johnhg
>> Requestors: twilson at atmos.ucla.edu
>> Status: new
>> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=68672 >
>>
>>
>> This transaction appears to have no content
>>
------------------------------------------------
Subject: Re: [rt.rap.ucar.edu #68672] Level type
From: Travis Wilson
Time: Mon Aug 25 16:58:42 2014
Hi John,
So i gave it a shot, and I was able to produce the same image with the
commands
/extended/METv4.1/bin/plot_data_plane WRFPRS_d02.068 Limg.ps
'name="HGT"; level="L0"; GRIB_lvl_typ=215;' -v 3
/extended/METv4.1/bin/plot_data_plane WRFPRS_d02.068 Rimg.ps
'name="HGT"; level="R565";' -v 3
see ftp://ftp.rap.ucar.edu/incoming/irap/met_help/wilson_data/MET_HELP
for ps images.
However, when i run point stat, I cannot get the output to be the same
(see subdirectory lvlTYP and rTYP for point stat output). Any idea on
what is going on?
On 08/19/2014 02:26 PM, John Halley Gotway via RT wrote:
> Travis,
>
> I made several little changes to METv4.1 to enable the use of the
following:
> name="HGT"; level="L0"; GRIB_lvl_typ = 215;
>
> And have it select that single record number 565. Please try
applying the
> latest set of patches here:
>
http://www.dtcenter.org/met/users/support/known_issues/METv4.1/index.php
>
> And then see if the following command matches just record number
565:
> METv4.1/bin/plot_data_plane WRFPRS_d02.068 img.ps 'name="HGT";
> level="L0"; GRIB_lvl_typ=215;' -v 3
>
>
> Thanks,
> John
>
>
> On Tue, Aug 19, 2014 at 2:31 PM, The RT System itself via RT <
> met_help at ucar.edu> wrote:
>
>> Tue Aug 19 14:31:11 2014: Request 68672 was acted upon.
>> Transaction: Given to johnhg by RT_System
>> Queue: met_help
>> Subject: Level type
>> Owner: johnhg
>> Requestors: twilson at atmos.ucla.edu
>> Status: new
>> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=68672 >
>>
>>
>> This transaction appears to have no content
>>
------------------------------------------------
Subject: Level type
From: John Halley Gotway
Time: Tue Aug 26 15:47:13 2014
Travis,
When I try to run your sample data, I get a bunch of GRIB table
errors. I
suspect you've made local modification to your GRIB tables to handle
this
data.
Anyway, I have a suggestion. Looking in point_conf_lvlTYP, I see the
following:
{
name = "HGT";
level = ["L1"];
cat_thresh = ["215"];
}
But you really should use the same setting you used in that call to
plot_data_plane:
{
name = "HGT";
level = ["L0"];
GRIB_lvl_typ = 215;
}
This configuration file stuff all gets passed to the same library code
to
parse it. Whatever, field specification setting you pass to
plot_data_plane, you can pass to point_stat in the config file.
Also, when you rerun your test case, do so with a higher verbosity
level
(like -v 4). Then inspect the information that gets printed to screen
which should include the GRIB record number(s) being used for each
verification task.
Thanks,
John
On Mon, Aug 25, 2014 at 4:58 PM, Travis Wilson via RT
<met_help at ucar.edu>
wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=68672 >
>
> Hi John,
>
> So i gave it a shot, and I was able to produce the same image with
the
> commands
>
> /extended/METv4.1/bin/plot_data_plane WRFPRS_d02.068 Limg.ps
> 'name="HGT"; level="L0"; GRIB_lvl_typ=215;' -v 3
> /extended/METv4.1/bin/plot_data_plane WRFPRS_d02.068 Rimg.ps
> 'name="HGT"; level="R565";' -v 3
>
> see
ftp://ftp.rap.ucar.edu/incoming/irap/met_help/wilson_data/MET_HELP
> for ps images.
>
> However, when i run point stat, I cannot get the output to be the
same
> (see subdirectory lvlTYP and rTYP for point stat output). Any idea
on
> what is going on?
>
> On 08/19/2014 02:26 PM, John Halley Gotway via RT wrote:
> > Travis,
> >
> > I made several little changes to METv4.1 to enable the use of the
> following:
> > name="HGT"; level="L0"; GRIB_lvl_typ = 215;
> >
> > And have it select that single record number 565. Please try
applying
> the
> > latest set of patches here:
> >
>
http://www.dtcenter.org/met/users/support/known_issues/METv4.1/index.php
> >
> > And then see if the following command matches just record number
565:
> > METv4.1/bin/plot_data_plane WRFPRS_d02.068 img.ps 'name="HGT";
> > level="L0"; GRIB_lvl_typ=215;' -v 3
> >
> >
> > Thanks,
> > John
> >
> >
> > On Tue, Aug 19, 2014 at 2:31 PM, The RT System itself via RT <
> > met_help at ucar.edu> wrote:
> >
> >> Tue Aug 19 14:31:11 2014: Request 68672 was acted upon.
> >> Transaction: Given to johnhg by RT_System
> >> Queue: met_help
> >> Subject: Level type
> >> Owner: johnhg
> >> Requestors: twilson at atmos.ucla.edu
> >> Status: new
> >> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=68672
> >
> >>
> >>
> >> This transaction appears to have no content
> >>
>
>
>
------------------------------------------------
Subject: Re: [rt.rap.ucar.edu #68672] Level type
From: Travis Wilson
Time: Tue Aug 26 16:04:11 2014
Wow, sorry. Can't believe I didn't see I had it listed under
cat_thresh
and not GRIB_lvl_typ.
Everything is working properly now!
And yes, I do use a modified GRIB table since grib1 does not have
ceiling height. Sorry again for the troubles.
-Travis
On 08/26/2014 02:47 PM, John Halley Gotway via RT wrote:
> Travis,
>
> When I try to run your sample data, I get a bunch of GRIB table
errors. I
> suspect you've made local modification to your GRIB tables to handle
this
> data.
>
> Anyway, I have a suggestion. Looking in point_conf_lvlTYP, I see
the
> following:
> {
> name = "HGT";
> level = ["L1"];
> cat_thresh = ["215"];
> }
>
> But you really should use the same setting you used in that call to
> plot_data_plane:
> {
> name = "HGT";
> level = ["L0"];
> GRIB_lvl_typ = 215;
> }
>
> This configuration file stuff all gets passed to the same library
code to
> parse it. Whatever, field specification setting you pass to
> plot_data_plane, you can pass to point_stat in the config file.
>
> Also, when you rerun your test case, do so with a higher verbosity
level
> (like -v 4). Then inspect the information that gets printed to
screen
> which should include the GRIB record number(s) being used for each
> verification task.
>
> Thanks,
> John
>
>
>
> On Mon, Aug 25, 2014 at 4:58 PM, Travis Wilson via RT
<met_help at ucar.edu>
> wrote:
>
>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=68672 >
>>
>> Hi John,
>>
>> So i gave it a shot, and I was able to produce the same image with
the
>> commands
>>
>> /extended/METv4.1/bin/plot_data_plane WRFPRS_d02.068 Limg.ps
>> 'name="HGT"; level="L0"; GRIB_lvl_typ=215;' -v 3
>> /extended/METv4.1/bin/plot_data_plane WRFPRS_d02.068 Rimg.ps
>> 'name="HGT"; level="R565";' -v 3
>>
>> see
ftp://ftp.rap.ucar.edu/incoming/irap/met_help/wilson_data/MET_HELP
>> for ps images.
>>
>> However, when i run point stat, I cannot get the output to be the
same
>> (see subdirectory lvlTYP and rTYP for point stat output). Any idea
on
>> what is going on?
>>
>> On 08/19/2014 02:26 PM, John Halley Gotway via RT wrote:
>>> Travis,
>>>
>>> I made several little changes to METv4.1 to enable the use of the
>> following:
>>> name="HGT"; level="L0"; GRIB_lvl_typ = 215;
>>>
>>> And have it select that single record number 565. Please try
applying
>> the
>>> latest set of patches here:
>>>
>>
http://www.dtcenter.org/met/users/support/known_issues/METv4.1/index.php
>>> And then see if the following command matches just record number
565:
>>> METv4.1/bin/plot_data_plane WRFPRS_d02.068 img.ps
'name="HGT";
>>> level="L0"; GRIB_lvl_typ=215;' -v 3
>>>
>>>
>>> Thanks,
>>> John
>>>
>>>
>>> On Tue, Aug 19, 2014 at 2:31 PM, The RT System itself via RT <
>>> met_help at ucar.edu> wrote:
>>>
>>>> Tue Aug 19 14:31:11 2014: Request 68672 was acted upon.
>>>> Transaction: Given to johnhg by RT_System
>>>> Queue: met_help
>>>> Subject: Level type
>>>> Owner: johnhg
>>>> Requestors: twilson at atmos.ucla.edu
>>>> Status: new
>>>> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=68672
>>>>
>>>> This transaction appears to have no content
>>>>
>>
>>
------------------------------------------------
Subject: Level type
From: John Halley Gotway
Time: Tue Aug 26 16:21:00 2014
Great! Glad to hear it's working as expected. I'll resolve this one.
Thanks,
John
On Tue, Aug 26, 2014 at 4:04 PM, Travis Wilson via RT
<met_help at ucar.edu>
wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=68672 >
>
> Wow, sorry. Can't believe I didn't see I had it listed under
cat_thresh
> and not GRIB_lvl_typ.
>
> Everything is working properly now!
>
> And yes, I do use a modified GRIB table since grib1 does not have
> ceiling height. Sorry again for the troubles.
>
> -Travis
>
>
> On 08/26/2014 02:47 PM, John Halley Gotway via RT wrote:
> > Travis,
> >
> > When I try to run your sample data, I get a bunch of GRIB table
errors.
> I
> > suspect you've made local modification to your GRIB tables to
handle this
> > data.
> >
> > Anyway, I have a suggestion. Looking in point_conf_lvlTYP, I see
the
> > following:
> > {
> > name = "HGT";
> > level = ["L1"];
> > cat_thresh = ["215"];
> > }
> >
> > But you really should use the same setting you used in that call
to
> > plot_data_plane:
> > {
> > name = "HGT";
> > level = ["L0"];
> > GRIB_lvl_typ = 215;
> > }
> >
> > This configuration file stuff all gets passed to the same library
code to
> > parse it. Whatever, field specification setting you pass to
> > plot_data_plane, you can pass to point_stat in the config file.
> >
> > Also, when you rerun your test case, do so with a higher verbosity
level
> > (like -v 4). Then inspect the information that gets printed to
screen
> > which should include the GRIB record number(s) being used for each
> > verification task.
> >
> > Thanks,
> > John
> >
> >
> >
> > On Mon, Aug 25, 2014 at 4:58 PM, Travis Wilson via RT
<met_help at ucar.edu
> >
> > wrote:
> >
> >> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=68672 >
> >>
> >> Hi John,
> >>
> >> So i gave it a shot, and I was able to produce the same image
with the
> >> commands
> >>
> >> /extended/METv4.1/bin/plot_data_plane WRFPRS_d02.068 Limg.ps
> >> 'name="HGT"; level="L0"; GRIB_lvl_typ=215;' -v 3
> >> /extended/METv4.1/bin/plot_data_plane WRFPRS_d02.068 Rimg.ps
> >> 'name="HGT"; level="R565";' -v 3
> >>
> >> see
ftp://ftp.rap.ucar.edu/incoming/irap/met_help/wilson_data/MET_HELP
> >> for ps images.
> >>
> >> However, when i run point stat, I cannot get the output to be the
same
> >> (see subdirectory lvlTYP and rTYP for point stat output). Any
idea on
> >> what is going on?
> >>
> >> On 08/19/2014 02:26 PM, John Halley Gotway via RT wrote:
> >>> Travis,
> >>>
> >>> I made several little changes to METv4.1 to enable the use of
the
> >> following:
> >>> name="HGT"; level="L0"; GRIB_lvl_typ = 215;
> >>>
> >>> And have it select that single record number 565. Please try
applying
> >> the
> >>> latest set of patches here:
> >>>
> >>
>
http://www.dtcenter.org/met/users/support/known_issues/METv4.1/index.php
> >>> And then see if the following command matches just record number
565:
> >>> METv4.1/bin/plot_data_plane WRFPRS_d02.068 img.ps
'name="HGT";
> >>> level="L0"; GRIB_lvl_typ=215;' -v 3
> >>>
> >>>
> >>> Thanks,
> >>> John
> >>>
> >>>
> >>> On Tue, Aug 19, 2014 at 2:31 PM, The RT System itself via RT <
> >>> met_help at ucar.edu> wrote:
> >>>
> >>>> Tue Aug 19 14:31:11 2014: Request 68672 was acted upon.
> >>>> Transaction: Given to johnhg by RT_System
> >>>> Queue: met_help
> >>>> Subject: Level type
> >>>> Owner: johnhg
> >>>> Requestors: twilson at atmos.ucla.edu
> >>>> Status: new
> >>>> Ticket <URL:
> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=68672
> >>>>
> >>>> This transaction appears to have no content
> >>>>
> >>
> >>
>
>
>
------------------------------------------------
More information about the Met_help
mailing list