[Met_help] [rt.rap.ucar.edu #70486] History for Applying grid_stat to field on height-relative layer
John Halley Gotway via RT
met_help at ucar.edu
Mon Feb 2 10:12:03 MST 2015
----------------------------------------------------------------
Initial Request
----------------------------------------------------------------
Hello again John,
I was hoping that you again might be able to quickly point me to the
correct syntax to run grid_stat on the updraft helicity field:
rotor[265]> wgrib2 obs_d2_2013053106_1345.grib2 -v2
...
3:198203:06Z31may2013:MXUPHL Hourly Maximum of Updraft Helicity over Layer
2km to 5 km AGL [m^2/s^2]:lvl1=(103,5000) lvl2=(103,2000):5000-2000 m
above ground:810-825 min max fcst:
...
10:518511:06Z31may2013:VUCSH Vertical U-Component Shear [1/s]:lvl1=(103,0)
lvl2=(103,6000):0-6000 m above ground:825 min fcst:
Š
I¹ve been able to successfully run all other fields, including record 10
above using
name = "VUCSH";
level = [ "Z0-6000" ];
but I¹d like to avoid using R3 for the helicity field in case the grib
file changes structure. The helicity field is the same as the one you
helped me with below but now in grib2 format. Attempts using the VUCSHR
field as a guide have not worked.
Any help would be much appreciated.
Thanks.
John Henderson
On 5/1/14, 4:21 PM, "John Halley Gotway via RT" <met_help at ucar.edu> wrote:
>...
>
>If you have a meaningful interpretation of this data, you could update
>that table file. Even if you don't, here's a way you can tell MET to use
>that record:
>
> METv4.1/bin/plot_data_plane d2_2013053106_1830-ACM2.grib
>d2_2013053106_1830-ACM2.ps 'name="var236"; level="Z50-20";
>GRIB1_ptv=129;' -v 3
> DEBUG 1: Opening data file: d2_2013053106_1830-ACM2.grib
> DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found range match
>for VarInfo "var236/Z20-50" in GRIB record 7 of GRIB file
>"d2_2013053106_1830-ACM2.grib".
> DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found 1 GRIB records
>matching VarInfo "var236/Z20-50" in GRIB file
>"d2_2013053106_1830-ACM2.grib".
> DEBUG 1: Creating postscript file: d2_2013053106_1830-ACM2.ps
>
>I used "GRIB1_ptv=129" to tell it to look at the table entries for
>parameter table version number 129. "var236" is the current abbreviation
>for that record. And the level value is "Z50-20". This
>can be seen in the wgrib output: levels=(50,20). The 'Z' tells MET to
>look for a vertical level, as opposed to a pressure level. And 50 to 20
>defines the lower and upper bounds for that vertical level.
>
>That should do the trick. I've attached a png version of the resulting
>image.
>
>Please give that a shot and let me know if it works for you. Feel free
>to update your version of nceptab_flat.txt to list a more meaningful
>abbreviation, long name, and units for this data type.
>
>Thanks,
>John
________________________________
This email is intended solely for the recipient. It may contain privileged, proprietary or confidential information or material. If you are not the intended recipient, please delete this email and any attachments and notify the sender of the error.
----------------------------------------------------------------
Complete Ticket History
----------------------------------------------------------------
Subject: Applying grid_stat to field on height-relative layer
From: John Halley Gotway
Time: Fri Jan 23 12:19:16 2015
John,
Would you be able to post a sample GRIB2 file on our anonymous ftp
site?
You can follow the instructions here:
http://www.dtcenter.org/met/users/support/met_help.php#ftp
John
On Fri, Jan 23, 2015 at 11:23 AM, jhenders at aer.com via RT
<met_help at ucar.edu
> wrote:
>
> Fri Jan 23 11:23:42 2015: Request 70486 was acted upon.
> Transaction: Ticket created by jhenders at aer.com
> Queue: met_help
> Subject: Applying grid_stat to field on height-relative layer
> Owner: Nobody
> Requestors: jhenders at aer.com
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=70486 >
>
>
> Hello again John,
>
> I was hoping that you again might be able to quickly point me to the
> correct syntax to run grid_stat on the updraft helicity field:
>
> rotor[265]> wgrib2 obs_d2_2013053106_1345.grib2 -v2
> ...
> 3:198203:06Z31may2013:MXUPHL Hourly Maximum of Updraft Helicity over
Layer
> 2km to 5 km AGL [m^2/s^2]:lvl1=(103,5000) lvl2=(103,2000):5000-2000
m
> above ground:810-825 min max fcst:
> ...
> 10:518511:06Z31may2013:VUCSH Vertical U-Component Shear
[1/s]:lvl1=(103,0)
> lvl2=(103,6000):0-6000 m above ground:825 min fcst:
> Š
>
> I¹ve been able to successfully run all other fields, including
record 10
> above using
>
> name = "VUCSH";
> level = [ "Z0-6000" ];
>
> but I¹d like to avoid using R3 for the helicity field in case the
grib
> file changes structure. The helicity field is the same as the one
you
> helped me with below but now in grib2 format. Attempts using the
VUCSHR
> field as a guide have not worked.
>
> Any help would be much appreciated.
>
> Thanks.
>
> John Henderson
>
> On 5/1/14, 4:21 PM, "John Halley Gotway via RT" <met_help at ucar.edu>
wrote:
>
>
> >...
> >
> >If you have a meaningful interpretation of this data, you could
update
> >that table file. Even if you don't, here's a way you can tell MET
to use
> >that record:
> >
> > METv4.1/bin/plot_data_plane d2_2013053106_1830-ACM2.grib
> >d2_2013053106_1830-ACM2.ps 'name="var236"; level="Z50-20";
> >GRIB1_ptv=129;' -v 3
> > DEBUG 1: Opening data file: d2_2013053106_1830-ACM2.grib
> > DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found range
match
> >for VarInfo "var236/Z20-50" in GRIB record 7 of GRIB file
> >"d2_2013053106_1830-ACM2.grib".
> > DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found 1 GRIB
records
> >matching VarInfo "var236/Z20-50" in GRIB file
> >"d2_2013053106_1830-ACM2.grib".
> > DEBUG 1: Creating postscript file: d2_2013053106_1830-ACM2.ps
> >
> >I used "GRIB1_ptv=129" to tell it to look at the table entries for
> >parameter table version number 129. "var236" is the current
abbreviation
> >for that record. And the level value is "Z50-20". This
> >can be seen in the wgrib output: levels=(50,20). The 'Z' tells MET
to
> >look for a vertical level, as opposed to a pressure level. And 50
to 20
> >defines the lower and upper bounds for that vertical level.
> >
> >That should do the trick. I've attached a png version of the
resulting
> >image.
> >
> >Please give that a shot and let me know if it works for you. Feel
free
> >to update your version of nceptab_flat.txt to list a more
meaningful
> >abbreviation, long name, and units for this data type.
> >
> >Thanks,
> >John
>
>
> ________________________________
>
> This email is intended solely for the recipient. It may contain
> privileged, proprietary or confidential information or material. If
you are
> not the intended recipient, please delete this email and any
attachments
> and notify the sender of the error.
>
>
>
>
------------------------------------------------
Subject: Re: [rt.rap.ucar.edu #70486] Applying grid_stat to field on height-relative layer
From: jhenders at aer.com
Time: Fri Jan 23 12:22:59 2015
Hi John,
I just uploaded the grib2 file in question.
Thanks!
John
On 1/23/15, 2:19 PM, "John Halley Gotway via RT" <met_help at ucar.edu>
wrote:
>John,
>
>Would you be able to post a sample GRIB2 file on our anonymous ftp
site?
>You can follow the instructions here:
> http://www.dtcenter.org/met/users/support/met_help.php#ftp
>
>John
>
>
>On Fri, Jan 23, 2015 at 11:23 AM, jhenders at aer.com via RT
><met_help at ucar.edu
>> wrote:
>
>>
>> Fri Jan 23 11:23:42 2015: Request 70486 was acted upon.
>> Transaction: Ticket created by jhenders at aer.com
>> Queue: met_help
>> Subject: Applying grid_stat to field on height-relative layer
>> Owner: Nobody
>> Requestors: jhenders at aer.com
>> Status: new
>> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=70486 >
>>
>>
>> Hello again John,
>>
>> I was hoping that you again might be able to quickly point me to
the
>> correct syntax to run grid_stat on the updraft helicity field:
>>
>> rotor[265]> wgrib2 obs_d2_2013053106_1345.grib2 -v2
>> ...
>> 3:198203:06Z31may2013:MXUPHL Hourly Maximum of Updraft Helicity
over
>>Layer
>> 2km to 5 km AGL [m^2/s^2]:lvl1=(103,5000) lvl2=(103,2000):5000-2000
m
>> above ground:810-825 min max fcst:
>> ...
>> 10:518511:06Z31may2013:VUCSH Vertical U-Component Shear
>>[1/s]:lvl1=(103,0)
>> lvl2=(103,6000):0-6000 m above ground:825 min fcst:
>> Š
>>
>> I¹ve been able to successfully run all other fields, including
record 10
>> above using
>>
>> name = "VUCSH";
>> level = [ "Z0-6000" ];
>>
>> but I¹d like to avoid using R3 for the helicity field in case the
grib
>> file changes structure. The helicity field is the same as the one
you
>> helped me with below but now in grib2 format. Attempts using the
VUCSHR
>> field as a guide have not worked.
>>
>> Any help would be much appreciated.
>>
>> Thanks.
>>
>> John Henderson
>>
>> On 5/1/14, 4:21 PM, "John Halley Gotway via RT" <met_help at ucar.edu>
>>wrote:
>>
>>
>> >...
>> >
>> >If you have a meaningful interpretation of this data, you could
update
>> >that table file. Even if you don't, here's a way you can tell MET
to
>>use
>> >that record:
>> >
>> > METv4.1/bin/plot_data_plane d2_2013053106_1830-ACM2.grib
>> >d2_2013053106_1830-ACM2.ps 'name="var236"; level="Z50-20";
>> >GRIB1_ptv=129;' -v 3
>> > DEBUG 1: Opening data file: d2_2013053106_1830-ACM2.grib
>> > DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found range
match
>> >for VarInfo "var236/Z20-50" in GRIB record 7 of GRIB file
>> >"d2_2013053106_1830-ACM2.grib".
>> > DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found 1 GRIB
>>records
>> >matching VarInfo "var236/Z20-50" in GRIB file
>> >"d2_2013053106_1830-ACM2.grib".
>> > DEBUG 1: Creating postscript file: d2_2013053106_1830-ACM2.ps
>> >
>> >I used "GRIB1_ptv=129" to tell it to look at the table entries for
>> >parameter table version number 129. "var236" is the current
>>abbreviation
>> >for that record. And the level value is "Z50-20". This
>> >can be seen in the wgrib output: levels=(50,20). The 'Z' tells
MET to
>> >look for a vertical level, as opposed to a pressure level. And 50
to
>>20
>> >defines the lower and upper bounds for that vertical level.
>> >
>> >That should do the trick. I've attached a png version of the
resulting
>> >image.
>> >
>> >Please give that a shot and let me know if it works for you. Feel
free
>> >to update your version of nceptab_flat.txt to list a more
meaningful
>> >abbreviation, long name, and units for this data type.
>> >
>> >Thanks,
>> >John
>>
>>
>> ________________________________
>>
>> This email is intended solely for the recipient. It may contain
>> privileged, proprietary or confidential information or material. If
you
>>are
>> not the intended recipient, please delete this email and any
attachments
>> and notify the sender of the error.
>>
>>
>>
>>
>
________________________________
This email is intended solely for the recipient. It may contain
privileged, proprietary or confidential information or material. If
you are not the intended recipient, please delete this email and any
attachments and notify the sender of the error.
------------------------------------------------
Subject: Applying grid_stat to field on height-relative layer
From: John Halley Gotway
Time: Fri Jan 23 16:02:12 2015
John,
Thanks for sending the file. I ran this through the debugger and for
some
reason MET is interpreting the level type of this data as an
accumulation.
That's pretty odd.
I'll need to look at this more closely next week to see if there's a
bug
somewhere in our GRIB2 code.
Thanks,
John
On Fri, Jan 23, 2015 at 12:23 PM, jhenders at aer.com via RT
<met_help at ucar.edu
> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=70486 >
>
> Hi John,
>
> I just uploaded the grib2 file in question.
>
> Thanks!
>
> John
>
> On 1/23/15, 2:19 PM, "John Halley Gotway via RT" <met_help at ucar.edu>
> wrote:
>
> >John,
> >
> >Would you be able to post a sample GRIB2 file on our anonymous ftp
site?
> >You can follow the instructions here:
> > http://www.dtcenter.org/met/users/support/met_help.php#ftp
> >
> >John
> >
> >
> >On Fri, Jan 23, 2015 at 11:23 AM, jhenders at aer.com via RT
> ><met_help at ucar.edu
> >> wrote:
> >
> >>
> >> Fri Jan 23 11:23:42 2015: Request 70486 was acted upon.
> >> Transaction: Ticket created by jhenders at aer.com
> >> Queue: met_help
> >> Subject: Applying grid_stat to field on height-relative
layer
> >> Owner: Nobody
> >> Requestors: jhenders at aer.com
> >> Status: new
> >> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=70486 >
> >>
> >>
> >> Hello again John,
> >>
> >> I was hoping that you again might be able to quickly point me to
the
> >> correct syntax to run grid_stat on the updraft helicity field:
> >>
> >> rotor[265]> wgrib2 obs_d2_2013053106_1345.grib2 -v2
> >> ...
> >> 3:198203:06Z31may2013:MXUPHL Hourly Maximum of Updraft Helicity
over
> >>Layer
> >> 2km to 5 km AGL [m^2/s^2]:lvl1=(103,5000) lvl2=(103,2000):5000-
2000 m
> >> above ground:810-825 min max fcst:
> >> ...
> >> 10:518511:06Z31may2013:VUCSH Vertical U-Component Shear
> >>[1/s]:lvl1=(103,0)
> >> lvl2=(103,6000):0-6000 m above ground:825 min fcst:
> >> Š
> >>
> >> I¹ve been able to successfully run all other fields, including
record 10
> >> above using
> >>
> >> name = "VUCSH";
> >> level = [ "Z0-6000" ];
> >>
> >> but I¹d like to avoid using R3 for the helicity field in case the
grib
> >> file changes structure. The helicity field is the same as the one
you
> >> helped me with below but now in grib2 format. Attempts using the
VUCSHR
> >> field as a guide have not worked.
> >>
> >> Any help would be much appreciated.
> >>
> >> Thanks.
> >>
> >> John Henderson
> >>
> >> On 5/1/14, 4:21 PM, "John Halley Gotway via RT"
<met_help at ucar.edu>
> >>wrote:
> >>
> >>
> >> >...
> >> >
> >> >If you have a meaningful interpretation of this data, you could
update
> >> >that table file. Even if you don't, here's a way you can tell
MET to
> >>use
> >> >that record:
> >> >
> >> > METv4.1/bin/plot_data_plane d2_2013053106_1830-ACM2.grib
> >> >d2_2013053106_1830-ACM2.ps 'name="var236"; level="Z50-20";
> >> >GRIB1_ptv=129;' -v 3
> >> > DEBUG 1: Opening data file: d2_2013053106_1830-ACM2.grib
> >> > DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found range
match
> >> >for VarInfo "var236/Z20-50" in GRIB record 7 of GRIB file
> >> >"d2_2013053106_1830-ACM2.grib".
> >> > DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found 1
GRIB
> >>records
> >> >matching VarInfo "var236/Z20-50" in GRIB file
> >> >"d2_2013053106_1830-ACM2.grib".
> >> > DEBUG 1: Creating postscript file: d2_2013053106_1830-
ACM2.ps
> >> >
> >> >I used "GRIB1_ptv=129" to tell it to look at the table entries
for
> >> >parameter table version number 129. "var236" is the current
> >>abbreviation
> >> >for that record. And the level value is "Z50-20". This
> >> >can be seen in the wgrib output: levels=(50,20). The 'Z' tells
MET to
> >> >look for a vertical level, as opposed to a pressure level. And
50 to
> >>20
> >> >defines the lower and upper bounds for that vertical level.
> >> >
> >> >That should do the trick. I've attached a png version of the
resulting
> >> >image.
> >> >
> >> >Please give that a shot and let me know if it works for you.
Feel free
> >> >to update your version of nceptab_flat.txt to list a more
meaningful
> >> >abbreviation, long name, and units for this data type.
> >> >
> >> >Thanks,
> >> >John
> >>
> >>
> >> ________________________________
> >>
> >> This email is intended solely for the recipient. It may contain
> >> privileged, proprietary or confidential information or material.
If you
> >>are
> >> not the intended recipient, please delete this email and any
attachments
> >> and notify the sender of the error.
> >>
> >>
> >>
> >>
> >
>
>
> ________________________________
>
> This email is intended solely for the recipient. It may contain
> privileged, proprietary or confidential information or material. If
you are
> not the intended recipient, please delete this email and any
attachments
> and notify the sender of the error.
>
>
>
------------------------------------------------
Subject: Re: [rt.rap.ucar.edu #70486] Applying grid_stat to field on height-relative layer
From: jhenders at aer.com
Time: Fri Jan 23 16:11:03 2015
Thanks. Will the current code work if I put “A” for accumulation just
like
precip?
John
On 1/23/15, 6:02 PM, "John Halley Gotway via RT" <met_help at ucar.edu>
wrote:
>John,
>
>Thanks for sending the file. I ran this through the debugger and for
some
>reason MET is interpreting the level type of this data as an
accumulation.
>That's pretty odd.
>
>I'll need to look at this more closely next week to see if there's a
bug
>somewhere in our GRIB2 code.
>
>Thanks,
>John
>
>
>
>On Fri, Jan 23, 2015 at 12:23 PM, jhenders at aer.com via RT
><met_help at ucar.edu
>> wrote:
>
>>
>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=70486 >
>>
>> Hi John,
>>
>> I just uploaded the grib2 file in question.
>>
>> Thanks!
>>
>> John
>>
>> On 1/23/15, 2:19 PM, "John Halley Gotway via RT"
<met_help at ucar.edu>
>> wrote:
>>
>> >John,
>> >
>> >Would you be able to post a sample GRIB2 file on our anonymous ftp
>>site?
>> >You can follow the instructions here:
>> > http://www.dtcenter.org/met/users/support/met_help.php#ftp
>> >
>> >John
>> >
>> >
>> >On Fri, Jan 23, 2015 at 11:23 AM, jhenders at aer.com via RT
>> ><met_help at ucar.edu
>> >> wrote:
>> >
>> >>
>> >> Fri Jan 23 11:23:42 2015: Request 70486 was acted upon.
>> >> Transaction: Ticket created by jhenders at aer.com
>> >> Queue: met_help
>> >> Subject: Applying grid_stat to field on height-relative
layer
>> >> Owner: Nobody
>> >> Requestors: jhenders at aer.com
>> >> Status: new
>> >> Ticket <URL:
>>https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=70486 >
>> >>
>> >>
>> >> Hello again John,
>> >>
>> >> I was hoping that you again might be able to quickly point me to
the
>> >> correct syntax to run grid_stat on the updraft helicity field:
>> >>
>> >> rotor[265]> wgrib2 obs_d2_2013053106_1345.grib2 -v2
>> >> ...
>> >> 3:198203:06Z31may2013:MXUPHL Hourly Maximum of Updraft Helicity
over
>> >>Layer
>> >> 2km to 5 km AGL [m^2/s^2]:lvl1=(103,5000) lvl2=(103,2000):5000-
2000 m
>> >> above ground:810-825 min max fcst:
>> >> ...
>> >> 10:518511:06Z31may2013:VUCSH Vertical U-Component Shear
>> >>[1/s]:lvl1=(103,0)
>> >> lvl2=(103,6000):0-6000 m above ground:825 min fcst:
>> >> Š
>> >>
>> >> I¹ve been able to successfully run all other fields, including
>>record 10
>> >> above using
>> >>
>> >> name = "VUCSH";
>> >> level = [ "Z0-6000" ];
>> >>
>> >> but I¹d like to avoid using R3 for the helicity field in case
the
>>grib
>> >> file changes structure. The helicity field is the same as the
one you
>> >> helped me with below but now in grib2 format. Attempts using the
>>VUCSHR
>> >> field as a guide have not worked.
>> >>
>> >> Any help would be much appreciated.
>> >>
>> >> Thanks.
>> >>
>> >> John Henderson
>> >>
>> >> On 5/1/14, 4:21 PM, "John Halley Gotway via RT"
<met_help at ucar.edu>
>> >>wrote:
>> >>
>> >>
>> >> >...
>> >> >
>> >> >If you have a meaningful interpretation of this data, you could
>>update
>> >> >that table file. Even if you don't, here's a way you can tell
MET
>>to
>> >>use
>> >> >that record:
>> >> >
>> >> > METv4.1/bin/plot_data_plane d2_2013053106_1830-ACM2.grib
>> >> >d2_2013053106_1830-ACM2.ps 'name="var236"; level="Z50-20";
>> >> >GRIB1_ptv=129;' -v 3
>> >> > DEBUG 1: Opening data file: d2_2013053106_1830-ACM2.grib
>> >> > DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found
range
>>match
>> >> >for VarInfo "var236/Z20-50" in GRIB record 7 of GRIB file
>> >> >"d2_2013053106_1830-ACM2.grib".
>> >> > DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found 1
GRIB
>> >>records
>> >> >matching VarInfo "var236/Z20-50" in GRIB file
>> >> >"d2_2013053106_1830-ACM2.grib".
>> >> > DEBUG 1: Creating postscript file: d2_2013053106_1830-
ACM2.ps
>> >> >
>> >> >I used "GRIB1_ptv=129" to tell it to look at the table entries
for
>> >> >parameter table version number 129. "var236" is the current
>> >>abbreviation
>> >> >for that record. And the level value is "Z50-20". This
>> >> >can be seen in the wgrib output: levels=(50,20). The 'Z' tells
MET
>>to
>> >> >look for a vertical level, as opposed to a pressure level. And
50
>>to
>> >>20
>> >> >defines the lower and upper bounds for that vertical level.
>> >> >
>> >> >That should do the trick. I've attached a png version of the
>>resulting
>> >> >image.
>> >> >
>> >> >Please give that a shot and let me know if it works for you.
Feel
>>free
>> >> >to update your version of nceptab_flat.txt to list a more
meaningful
>> >> >abbreviation, long name, and units for this data type.
>> >> >
>> >> >Thanks,
>> >> >John
>> >>
>> >>
>> >> ________________________________
>> >>
>> >> This email is intended solely for the recipient. It may contain
>> >> privileged, proprietary or confidential information or material.
If
>>you
>> >>are
>> >> not the intended recipient, please delete this email and any
>>attachments
>> >> and notify the sender of the error.
>> >>
>> >>
>> >>
>> >>
>> >
>>
>>
>> ________________________________
>>
>> This email is intended solely for the recipient. It may contain
>> privileged, proprietary or confidential information or material. If
you
>>are
>> not the intended recipient, please delete this email and any
attachments
>> and notify the sender of the error.
>>
>>
>>
>
________________________________
This email is intended solely for the recipient. It may contain
privileged, proprietary or confidential information or material. If
you are not the intended recipient, please delete this email and any
attachments and notify the sender of the error.
------------------------------------------------
Subject: Applying grid_stat to field on height-relative layer
From: John Halley Gotway
Time: Sun Jan 25 08:23:48 2015
Nope, I tried that on Friday and it cplains about parsing those as a
timestring. I'll take a closer look on Monday.
John
On Friday, January 23, 2015, jhenders at aer.com via RT
<met_help at ucar.edu>
wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=70486 >
>
> Thanks. Will the current code work if I put “A” for accumulation
just like
> precip?
>
> John
>
>
> On 1/23/15, 6:02 PM, "John Halley Gotway via RT" <met_help at ucar.edu
> <javascript:;>> wrote:
>
> >John,
> >
> >Thanks for sending the file. I ran this through the debugger and
for some
> >reason MET is interpreting the level type of this data as an
accumulation.
> >That's pretty odd.
> >
> >I'll need to look at this more closely next week to see if there's
a bug
> >somewhere in our GRIB2 code.
> >
> >Thanks,
> >John
> >
> >
> >
> >On Fri, Jan 23, 2015 at 12:23 PM, jhenders at aer.com <javascript:;>
via RT
> ><met_help at ucar.edu <javascript:;>
> >> wrote:
> >
> >>
> >> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=70486 >
> >>
> >> Hi John,
> >>
> >> I just uploaded the grib2 file in question.
> >>
> >> Thanks!
> >>
> >> John
> >>
> >> On 1/23/15, 2:19 PM, "John Halley Gotway via RT"
<met_help at ucar.edu
> <javascript:;>>
> >> wrote:
> >>
> >> >John,
> >> >
> >> >Would you be able to post a sample GRIB2 file on our anonymous
ftp
> >>site?
> >> >You can follow the instructions here:
> >> > http://www.dtcenter.org/met/users/support/met_help.php#ftp
> >> >
> >> >John
> >> >
> >> >
> >> >On Fri, Jan 23, 2015 at 11:23 AM, jhenders at aer.com
<javascript:;> via
> RT
> >> ><met_help at ucar.edu <javascript:;>
> >> >> wrote:
> >> >
> >> >>
> >> >> Fri Jan 23 11:23:42 2015: Request 70486 was acted upon.
> >> >> Transaction: Ticket created by jhenders at aer.com <javascript:;>
> >> >> Queue: met_help
> >> >> Subject: Applying grid_stat to field on height-relative
layer
> >> >> Owner: Nobody
> >> >> Requestors: jhenders at aer.com <javascript:;>
> >> >> Status: new
> >> >> Ticket <URL:
> >>https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=70486 >
> >> >>
> >> >>
> >> >> Hello again John,
> >> >>
> >> >> I was hoping that you again might be able to quickly point me
to the
> >> >> correct syntax to run grid_stat on the updraft helicity field:
> >> >>
> >> >> rotor[265]> wgrib2 obs_d2_2013053106_1345.grib2 -v2
> >> >> ...
> >> >> 3:198203:06Z31may2013:MXUPHL Hourly Maximum of Updraft
Helicity over
> >> >>Layer
> >> >> 2km to 5 km AGL [m^2/s^2]:lvl1=(103,5000)
lvl2=(103,2000):5000-2000 m
> >> >> above ground:810-825 min max fcst:
> >> >> ...
> >> >> 10:518511:06Z31may2013:VUCSH Vertical U-Component Shear
> >> >>[1/s]:lvl1=(103,0)
> >> >> lvl2=(103,6000):0-6000 m above ground:825 min fcst:
> >> >> Š
> >> >>
> >> >> I¹ve been able to successfully run all other fields, including
> >>record 10
> >> >> above using
> >> >>
> >> >> name = "VUCSH";
> >> >> level = [ "Z0-6000" ];
> >> >>
> >> >> but I¹d like to avoid using R3 for the helicity field in case
the
> >>grib
> >> >> file changes structure. The helicity field is the same as the
one you
> >> >> helped me with below but now in grib2 format. Attempts using
the
> >>VUCSHR
> >> >> field as a guide have not worked.
> >> >>
> >> >> Any help would be much appreciated.
> >> >>
> >> >> Thanks.
> >> >>
> >> >> John Henderson
> >> >>
> >> >> On 5/1/14, 4:21 PM, "John Halley Gotway via RT"
<met_help at ucar.edu
> <javascript:;>>
> >> >>wrote:
> >> >>
> >> >>
> >> >> >...
> >> >> >
> >> >> >If you have a meaningful interpretation of this data, you
could
> >>update
> >> >> >that table file. Even if you don't, here's a way you can
tell MET
> >>to
> >> >>use
> >> >> >that record:
> >> >> >
> >> >> > METv4.1/bin/plot_data_plane d2_2013053106_1830-ACM2.grib
> >> >> >d2_2013053106_1830-ACM2.ps 'name="var236"; level="Z50-20";
> >> >> >GRIB1_ptv=129;' -v 3
> >> >> > DEBUG 1: Opening data file: d2_2013053106_1830-ACM2.grib
> >> >> > DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found
range
> >>match
> >> >> >for VarInfo "var236/Z20-50" in GRIB record 7 of GRIB file
> >> >> >"d2_2013053106_1830-ACM2.grib".
> >> >> > DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found 1
GRIB
> >> >>records
> >> >> >matching VarInfo "var236/Z20-50" in GRIB file
> >> >> >"d2_2013053106_1830-ACM2.grib".
> >> >> > DEBUG 1: Creating postscript file: d2_2013053106_1830-
ACM2.ps
> >> >> >
> >> >> >I used "GRIB1_ptv=129" to tell it to look at the table
entries for
> >> >> >parameter table version number 129. "var236" is the current
> >> >>abbreviation
> >> >> >for that record. And the level value is "Z50-20". This
> >> >> >can be seen in the wgrib output: levels=(50,20). The 'Z'
tells MET
> >>to
> >> >> >look for a vertical level, as opposed to a pressure level.
And 50
> >>to
> >> >>20
> >> >> >defines the lower and upper bounds for that vertical level.
> >> >> >
> >> >> >That should do the trick. I've attached a png version of the
> >>resulting
> >> >> >image.
> >> >> >
> >> >> >Please give that a shot and let me know if it works for you.
Feel
> >>free
> >> >> >to update your version of nceptab_flat.txt to list a more
meaningful
> >> >> >abbreviation, long name, and units for this data type.
> >> >> >
> >> >> >Thanks,
> >> >> >John
> >> >>
> >> >>
> >> >> ________________________________
> >> >>
> >> >> This email is intended solely for the recipient. It may
contain
> >> >> privileged, proprietary or confidential information or
material. If
> >>you
> >> >>are
> >> >> not the intended recipient, please delete this email and any
> >>attachments
> >> >> and notify the sender of the error.
> >> >>
> >> >>
> >> >>
> >> >>
> >> >
> >>
> >>
> >> ________________________________
> >>
> >> This email is intended solely for the recipient. It may contain
> >> privileged, proprietary or confidential information or material.
If you
> >>are
> >> not the intended recipient, please delete this email and any
attachments
> >> and notify the sender of the error.
> >>
> >>
> >>
> >
>
>
> ________________________________
>
> This email is intended solely for the recipient. It may contain
> privileged, proprietary or confidential information or material. If
you are
> not the intended recipient, please delete this email and any
attachments
> and notify the sender of the error.
>
>
>
------------------------------------------------
Subject: Applying grid_stat to field on height-relative layer
From: John Halley Gotway
Time: Mon Jan 26 17:31:00 2015
John,
OK, I just posted a new set of bugfixes to the MET website. Please
apply
the patches and try reading MXUPHL using level="L5000-2000";
I do think it's weird that it's being stored as an accumulation
interval.
But I checked HRRR and that's how its stored there too.
Please let me know if these changes enable you to read that field.
Thanks,
John
On Sun, Jan 25, 2015 at 8:23 AM, John Halley Gotway <johnhg at ucar.edu>
wrote:
> Nope, I tried that on Friday and it cplains about parsing those as a
> timestring. I'll take a closer look on Monday.
>
> John
>
>
> On Friday, January 23, 2015, jhenders at aer.com via RT
<met_help at ucar.edu>
> wrote:
>
>>
>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=70486 >
>>
>> Thanks. Will the current code work if I put “A” for accumulation
just like
>> precip?
>>
>> John
>>
>>
>> On 1/23/15, 6:02 PM, "John Halley Gotway via RT"
<met_help at ucar.edu>
>> wrote:
>>
>> >John,
>> >
>> >Thanks for sending the file. I ran this through the debugger and
for
>> some
>> >reason MET is interpreting the level type of this data as an
>> accumulation.
>> >That's pretty odd.
>> >
>> >I'll need to look at this more closely next week to see if there's
a bug
>> >somewhere in our GRIB2 code.
>> >
>> >Thanks,
>> >John
>> >
>> >
>> >
>> >On Fri, Jan 23, 2015 at 12:23 PM, jhenders at aer.com via RT
>> ><met_help at ucar.edu
>> >> wrote:
>> >
>> >>
>> >> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=70486 >
>> >>
>> >> Hi John,
>> >>
>> >> I just uploaded the grib2 file in question.
>> >>
>> >> Thanks!
>> >>
>> >> John
>> >>
>> >> On 1/23/15, 2:19 PM, "John Halley Gotway via RT"
<met_help at ucar.edu>
>> >> wrote:
>> >>
>> >> >John,
>> >> >
>> >> >Would you be able to post a sample GRIB2 file on our anonymous
ftp
>> >>site?
>> >> >You can follow the instructions here:
>> >> > http://www.dtcenter.org/met/users/support/met_help.php#ftp
>> >> >
>> >> >John
>> >> >
>> >> >
>> >> >On Fri, Jan 23, 2015 at 11:23 AM, jhenders at aer.com via RT
>> >> ><met_help at ucar.edu
>> >> >> wrote:
>> >> >
>> >> >>
>> >> >> Fri Jan 23 11:23:42 2015: Request 70486 was acted upon.
>> >> >> Transaction: Ticket created by jhenders at aer.com
>> >> >> Queue: met_help
>> >> >> Subject: Applying grid_stat to field on height-relative
layer
>> >> >> Owner: Nobody
>> >> >> Requestors: jhenders at aer.com
>> >> >> Status: new
>> >> >> Ticket <URL:
>> >>https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=70486 >
>> >> >>
>> >> >>
>> >> >> Hello again John,
>> >> >>
>> >> >> I was hoping that you again might be able to quickly point me
to the
>> >> >> correct syntax to run grid_stat on the updraft helicity
field:
>> >> >>
>> >> >> rotor[265]> wgrib2 obs_d2_2013053106_1345.grib2 -v2
>> >> >> ...
>> >> >> 3:198203:06Z31may2013:MXUPHL Hourly Maximum of Updraft
Helicity over
>> >> >>Layer
>> >> >> 2km to 5 km AGL [m^2/s^2]:lvl1=(103,5000)
lvl2=(103,2000):5000-2000
>> m
>> >> >> above ground:810-825 min max fcst:
>> >> >> ...
>> >> >> 10:518511:06Z31may2013:VUCSH Vertical U-Component Shear
>> >> >>[1/s]:lvl1=(103,0)
>> >> >> lvl2=(103,6000):0-6000 m above ground:825 min fcst:
>> >> >> Š
>> >> >>
>> >> >> I¹ve been able to successfully run all other fields,
including
>> >>record 10
>> >> >> above using
>> >> >>
>> >> >> name = "VUCSH";
>> >> >> level = [ "Z0-6000" ];
>> >> >>
>> >> >> but I¹d like to avoid using R3 for the helicity field in case
the
>> >>grib
>> >> >> file changes structure. The helicity field is the same as the
one
>> you
>> >> >> helped me with below but now in grib2 format. Attempts using
the
>> >>VUCSHR
>> >> >> field as a guide have not worked.
>> >> >>
>> >> >> Any help would be much appreciated.
>> >> >>
>> >> >> Thanks.
>> >> >>
>> >> >> John Henderson
>> >> >>
>> >> >> On 5/1/14, 4:21 PM, "John Halley Gotway via RT"
<met_help at ucar.edu>
>> >> >>wrote:
>> >> >>
>> >> >>
>> >> >> >...
>> >> >> >
>> >> >> >If you have a meaningful interpretation of this data, you
could
>> >>update
>> >> >> >that table file. Even if you don't, here's a way you can
tell MET
>> >>to
>> >> >>use
>> >> >> >that record:
>> >> >> >
>> >> >> > METv4.1/bin/plot_data_plane d2_2013053106_1830-ACM2.grib
>> >> >> >d2_2013053106_1830-ACM2.ps 'name="var236"; level="Z50-20";
>> >> >> >GRIB1_ptv=129;' -v 3
>> >> >> > DEBUG 1: Opening data file: d2_2013053106_1830-ACM2.grib
>> >> >> > DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found
range
>> >>match
>> >> >> >for VarInfo "var236/Z20-50" in GRIB record 7 of GRIB file
>> >> >> >"d2_2013053106_1830-ACM2.grib".
>> >> >> > DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found 1
GRIB
>> >> >>records
>> >> >> >matching VarInfo "var236/Z20-50" in GRIB file
>> >> >> >"d2_2013053106_1830-ACM2.grib".
>> >> >> > DEBUG 1: Creating postscript file: d2_2013053106_1830-
ACM2.ps
>> >> >> >
>> >> >> >I used "GRIB1_ptv=129" to tell it to look at the table
entries for
>> >> >> >parameter table version number 129. "var236" is the current
>> >> >>abbreviation
>> >> >> >for that record. And the level value is "Z50-20". This
>> >> >> >can be seen in the wgrib output: levels=(50,20). The 'Z'
tells MET
>> >>to
>> >> >> >look for a vertical level, as opposed to a pressure level.
And 50
>> >>to
>> >> >>20
>> >> >> >defines the lower and upper bounds for that vertical level.
>> >> >> >
>> >> >> >That should do the trick. I've attached a png version of
the
>> >>resulting
>> >> >> >image.
>> >> >> >
>> >> >> >Please give that a shot and let me know if it works for you.
Feel
>> >>free
>> >> >> >to update your version of nceptab_flat.txt to list a more
>> meaningful
>> >> >> >abbreviation, long name, and units for this data type.
>> >> >> >
>> >> >> >Thanks,
>> >> >> >John
>> >> >>
>> >> >>
>> >> >> ________________________________
>> >> >>
>> >> >> This email is intended solely for the recipient. It may
contain
>> >> >> privileged, proprietary or confidential information or
material. If
>> >>you
>> >> >>are
>> >> >> not the intended recipient, please delete this email and any
>> >>attachments
>> >> >> and notify the sender of the error.
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >
>> >>
>> >>
>> >> ________________________________
>> >>
>> >> This email is intended solely for the recipient. It may contain
>> >> privileged, proprietary or confidential information or material.
If you
>> >>are
>> >> not the intended recipient, please delete this email and any
>> attachments
>> >> and notify the sender of the error.
>> >>
>> >>
>> >>
>> >
>>
>>
>> ________________________________
>>
>> This email is intended solely for the recipient. It may contain
>> privileged, proprietary or confidential information or material. If
you are
>> not the intended recipient, please delete this email and any
attachments
>> and notify the sender of the error.
>>
>>
>>
------------------------------------------------
Subject: Re: [rt.rap.ucar.edu #70486] Applying grid_stat to field on height-relative layer
From: jhenders at aer.com
Time: Thu Jan 29 14:06:59 2015
Hi John,
That seems to have done the trick. Thanks as always!
John
On 1/26/15, 7:31 PM, "John Halley Gotway via RT" <met_help at ucar.edu>
wrote:
>John,
>
>OK, I just posted a new set of bugfixes to the MET website. Please
apply
>the patches and try reading MXUPHL using level="L5000-2000";
>
>I do think it's weird that it's being stored as an accumulation
interval.
>But I checked HRRR and that's how its stored there too.
>
>Please let me know if these changes enable you to read that field.
>
>Thanks,
>John
>
>On Sun, Jan 25, 2015 at 8:23 AM, John Halley Gotway <johnhg at ucar.edu>
>wrote:
>
>> Nope, I tried that on Friday and it cplains about parsing those as
a
>> timestring. I'll take a closer look on Monday.
>>
>> John
>>
>>
>> On Friday, January 23, 2015, jhenders at aer.com via RT
<met_help at ucar.edu>
>> wrote:
>>
>>>
>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=70486 >
>>>
>>> Thanks. Will the current code work if I put “A” for accumulation
just
>>>like
>>> precip?
>>>
>>> John
>>>
>>>
>>> On 1/23/15, 6:02 PM, "John Halley Gotway via RT"
<met_help at ucar.edu>
>>> wrote:
>>>
>>> >John,
>>> >
>>> >Thanks for sending the file. I ran this through the debugger and
for
>>> some
>>> >reason MET is interpreting the level type of this data as an
>>> accumulation.
>>> >That's pretty odd.
>>> >
>>> >I'll need to look at this more closely next week to see if
there's a
>>>bug
>>> >somewhere in our GRIB2 code.
>>> >
>>> >Thanks,
>>> >John
>>> >
>>> >
>>> >
>>> >On Fri, Jan 23, 2015 at 12:23 PM, jhenders at aer.com via RT
>>> ><met_help at ucar.edu
>>> >> wrote:
>>> >
>>> >>
>>> >> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=70486 >
>>> >>
>>> >> Hi John,
>>> >>
>>> >> I just uploaded the grib2 file in question.
>>> >>
>>> >> Thanks!
>>> >>
>>> >> John
>>> >>
>>> >> On 1/23/15, 2:19 PM, "John Halley Gotway via RT"
<met_help at ucar.edu>
>>> >> wrote:
>>> >>
>>> >> >John,
>>> >> >
>>> >> >Would you be able to post a sample GRIB2 file on our anonymous
ftp
>>> >>site?
>>> >> >You can follow the instructions here:
>>> >> > http://www.dtcenter.org/met/users/support/met_help.php#ftp
>>> >> >
>>> >> >John
>>> >> >
>>> >> >
>>> >> >On Fri, Jan 23, 2015 at 11:23 AM, jhenders at aer.com via RT
>>> >> ><met_help at ucar.edu
>>> >> >> wrote:
>>> >> >
>>> >> >>
>>> >> >> Fri Jan 23 11:23:42 2015: Request 70486 was acted upon.
>>> >> >> Transaction: Ticket created by jhenders at aer.com
>>> >> >> Queue: met_help
>>> >> >> Subject: Applying grid_stat to field on height-relative
>>>layer
>>> >> >> Owner: Nobody
>>> >> >> Requestors: jhenders at aer.com
>>> >> >> Status: new
>>> >> >> Ticket <URL:
>>> >>https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=70486 >
>>> >> >>
>>> >> >>
>>> >> >> Hello again John,
>>> >> >>
>>> >> >> I was hoping that you again might be able to quickly point
me to
>>>the
>>> >> >> correct syntax to run grid_stat on the updraft helicity
field:
>>> >> >>
>>> >> >> rotor[265]> wgrib2 obs_d2_2013053106_1345.grib2 -v2
>>> >> >> ...
>>> >> >> 3:198203:06Z31may2013:MXUPHL Hourly Maximum of Updraft
Helicity
>>>over
>>> >> >>Layer
>>> >> >> 2km to 5 km AGL [m^2/s^2]:lvl1=(103,5000)
>>>lvl2=(103,2000):5000-2000
>>> m
>>> >> >> above ground:810-825 min max fcst:
>>> >> >> ...
>>> >> >> 10:518511:06Z31may2013:VUCSH Vertical U-Component Shear
>>> >> >>[1/s]:lvl1=(103,0)
>>> >> >> lvl2=(103,6000):0-6000 m above ground:825 min fcst:
>>> >> >> Š
>>> >> >>
>>> >> >> I¹ve been able to successfully run all other fields,
including
>>> >>record 10
>>> >> >> above using
>>> >> >>
>>> >> >> name = "VUCSH";
>>> >> >> level = [ "Z0-6000" ];
>>> >> >>
>>> >> >> but I¹d like to avoid using R3 for the helicity field in
case the
>>> >>grib
>>> >> >> file changes structure. The helicity field is the same as
the one
>>> you
>>> >> >> helped me with below but now in grib2 format. Attempts using
the
>>> >>VUCSHR
>>> >> >> field as a guide have not worked.
>>> >> >>
>>> >> >> Any help would be much appreciated.
>>> >> >>
>>> >> >> Thanks.
>>> >> >>
>>> >> >> John Henderson
>>> >> >>
>>> >> >> On 5/1/14, 4:21 PM, "John Halley Gotway via RT"
>>><met_help at ucar.edu>
>>> >> >>wrote:
>>> >> >>
>>> >> >>
>>> >> >> >...
>>> >> >> >
>>> >> >> >If you have a meaningful interpretation of this data, you
could
>>> >>update
>>> >> >> >that table file. Even if you don't, here's a way you can
tell
>>>MET
>>> >>to
>>> >> >>use
>>> >> >> >that record:
>>> >> >> >
>>> >> >> > METv4.1/bin/plot_data_plane d2_2013053106_1830-
ACM2.grib
>>> >> >> >d2_2013053106_1830-ACM2.ps 'name="var236"; level="Z50-20";
>>> >> >> >GRIB1_ptv=129;' -v 3
>>> >> >> > DEBUG 1: Opening data file: d2_2013053106_1830-
ACM2.grib
>>> >> >> > DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found
range
>>> >>match
>>> >> >> >for VarInfo "var236/Z20-50" in GRIB record 7 of GRIB file
>>> >> >> >"d2_2013053106_1830-ACM2.grib".
>>> >> >> > DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found
1
>>>GRIB
>>> >> >>records
>>> >> >> >matching VarInfo "var236/Z20-50" in GRIB file
>>> >> >> >"d2_2013053106_1830-ACM2.grib".
>>> >> >> > DEBUG 1: Creating postscript file:
>>>d2_2013053106_1830-ACM2.ps
>>> >> >> >
>>> >> >> >I used "GRIB1_ptv=129" to tell it to look at the table
entries
>>>for
>>> >> >> >parameter table version number 129. "var236" is the
current
>>> >> >>abbreviation
>>> >> >> >for that record. And the level value is "Z50-20". This
>>> >> >> >can be seen in the wgrib output: levels=(50,20). The 'Z'
tells
>>>MET
>>> >>to
>>> >> >> >look for a vertical level, as opposed to a pressure level.
And
>>>50
>>> >>to
>>> >> >>20
>>> >> >> >defines the lower and upper bounds for that vertical level.
>>> >> >> >
>>> >> >> >That should do the trick. I've attached a png version of
the
>>> >>resulting
>>> >> >> >image.
>>> >> >> >
>>> >> >> >Please give that a shot and let me know if it works for
you.
>>>Feel
>>> >>free
>>> >> >> >to update your version of nceptab_flat.txt to list a more
>>> meaningful
>>> >> >> >abbreviation, long name, and units for this data type.
>>> >> >> >
>>> >> >> >Thanks,
>>> >> >> >John
>>> >> >>
>>> >> >>
>>> >> >> ________________________________
>>> >> >>
>>> >> >> This email is intended solely for the recipient. It may
contain
>>> >> >> privileged, proprietary or confidential information or
material.
>>>If
>>> >>you
>>> >> >>are
>>> >> >> not the intended recipient, please delete this email and any
>>> >>attachments
>>> >> >> and notify the sender of the error.
>>> >> >>
>>> >> >>
>>> >> >>
>>> >> >>
>>> >> >
>>> >>
>>> >>
>>> >> ________________________________
>>> >>
>>> >> This email is intended solely for the recipient. It may contain
>>> >> privileged, proprietary or confidential information or
material. If
>>>you
>>> >>are
>>> >> not the intended recipient, please delete this email and any
>>> attachments
>>> >> and notify the sender of the error.
>>> >>
>>> >>
>>> >>
>>> >
>>>
>>>
>>> ________________________________
>>>
>>> This email is intended solely for the recipient. It may contain
>>> privileged, proprietary or confidential information or material.
If
>>>you are
>>> not the intended recipient, please delete this email and any
>>>attachments
>>> and notify the sender of the error.
>>>
>>>
>>>
>
________________________________
This email is intended solely for the recipient. It may contain
privileged, proprietary or confidential information or material. If
you are not the intended recipient, please delete this email and any
attachments and notify the sender of the error.
------------------------------------------------
Subject: Applying grid_stat to field on height-relative layer
From: John Halley Gotway
Time: Thu Jan 29 14:35:46 2015
Great! Thanks for letting me know. I'll go ahead and resolve the
ticket.
John
On Thu, Jan 29, 2015 at 2:06 PM, jhenders at aer.com via RT
<met_help at ucar.edu>
wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=70486 >
>
> Hi John,
>
> That seems to have done the trick. Thanks as always!
>
> John
>
> On 1/26/15, 7:31 PM, "John Halley Gotway via RT" <met_help at ucar.edu>
> wrote:
>
> >John,
> >
> >OK, I just posted a new set of bugfixes to the MET website. Please
apply
> >the patches and try reading MXUPHL using level="L5000-2000";
> >
> >I do think it's weird that it's being stored as an accumulation
interval.
> >But I checked HRRR and that's how its stored there too.
> >
> >Please let me know if these changes enable you to read that field.
> >
> >Thanks,
> >John
> >
> >On Sun, Jan 25, 2015 at 8:23 AM, John Halley Gotway
<johnhg at ucar.edu>
> >wrote:
> >
> >> Nope, I tried that on Friday and it cplains about parsing those
as a
> >> timestring. I'll take a closer look on Monday.
> >>
> >> John
> >>
> >>
> >> On Friday, January 23, 2015, jhenders at aer.com via RT
<met_help at ucar.edu
> >
> >> wrote:
> >>
> >>>
> >>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=70486 >
> >>>
> >>> Thanks. Will the current code work if I put “A” for accumulation
just
> >>>like
> >>> precip?
> >>>
> >>> John
> >>>
> >>>
> >>> On 1/23/15, 6:02 PM, "John Halley Gotway via RT"
<met_help at ucar.edu>
> >>> wrote:
> >>>
> >>> >John,
> >>> >
> >>> >Thanks for sending the file. I ran this through the debugger
and for
> >>> some
> >>> >reason MET is interpreting the level type of this data as an
> >>> accumulation.
> >>> >That's pretty odd.
> >>> >
> >>> >I'll need to look at this more closely next week to see if
there's a
> >>>bug
> >>> >somewhere in our GRIB2 code.
> >>> >
> >>> >Thanks,
> >>> >John
> >>> >
> >>> >
> >>> >
> >>> >On Fri, Jan 23, 2015 at 12:23 PM, jhenders at aer.com via RT
> >>> ><met_help at ucar.edu
> >>> >> wrote:
> >>> >
> >>> >>
> >>> >> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=70486
>
> >>> >>
> >>> >> Hi John,
> >>> >>
> >>> >> I just uploaded the grib2 file in question.
> >>> >>
> >>> >> Thanks!
> >>> >>
> >>> >> John
> >>> >>
> >>> >> On 1/23/15, 2:19 PM, "John Halley Gotway via RT"
<met_help at ucar.edu
> >
> >>> >> wrote:
> >>> >>
> >>> >> >John,
> >>> >> >
> >>> >> >Would you be able to post a sample GRIB2 file on our
anonymous ftp
> >>> >>site?
> >>> >> >You can follow the instructions here:
> >>> >> >
http://www.dtcenter.org/met/users/support/met_help.php#ftp
> >>> >> >
> >>> >> >John
> >>> >> >
> >>> >> >
> >>> >> >On Fri, Jan 23, 2015 at 11:23 AM, jhenders at aer.com via RT
> >>> >> ><met_help at ucar.edu
> >>> >> >> wrote:
> >>> >> >
> >>> >> >>
> >>> >> >> Fri Jan 23 11:23:42 2015: Request 70486 was acted upon.
> >>> >> >> Transaction: Ticket created by jhenders at aer.com
> >>> >> >> Queue: met_help
> >>> >> >> Subject: Applying grid_stat to field on height-
relative
> >>>layer
> >>> >> >> Owner: Nobody
> >>> >> >> Requestors: jhenders at aer.com
> >>> >> >> Status: new
> >>> >> >> Ticket <URL:
> >>> >>https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=70486 >
> >>> >> >>
> >>> >> >>
> >>> >> >> Hello again John,
> >>> >> >>
> >>> >> >> I was hoping that you again might be able to quickly point
me to
> >>>the
> >>> >> >> correct syntax to run grid_stat on the updraft helicity
field:
> >>> >> >>
> >>> >> >> rotor[265]> wgrib2 obs_d2_2013053106_1345.grib2 -v2
> >>> >> >> ...
> >>> >> >> 3:198203:06Z31may2013:MXUPHL Hourly Maximum of Updraft
Helicity
> >>>over
> >>> >> >>Layer
> >>> >> >> 2km to 5 km AGL [m^2/s^2]:lvl1=(103,5000)
> >>>lvl2=(103,2000):5000-2000
> >>> m
> >>> >> >> above ground:810-825 min max fcst:
> >>> >> >> ...
> >>> >> >> 10:518511:06Z31may2013:VUCSH Vertical U-Component Shear
> >>> >> >>[1/s]:lvl1=(103,0)
> >>> >> >> lvl2=(103,6000):0-6000 m above ground:825 min fcst:
> >>> >> >> Š
> >>> >> >>
> >>> >> >> I¹ve been able to successfully run all other fields,
including
> >>> >>record 10
> >>> >> >> above using
> >>> >> >>
> >>> >> >> name = "VUCSH";
> >>> >> >> level = [ "Z0-6000" ];
> >>> >> >>
> >>> >> >> but I¹d like to avoid using R3 for the helicity field in
case the
> >>> >>grib
> >>> >> >> file changes structure. The helicity field is the same as
the one
> >>> you
> >>> >> >> helped me with below but now in grib2 format. Attempts
using the
> >>> >>VUCSHR
> >>> >> >> field as a guide have not worked.
> >>> >> >>
> >>> >> >> Any help would be much appreciated.
> >>> >> >>
> >>> >> >> Thanks.
> >>> >> >>
> >>> >> >> John Henderson
> >>> >> >>
> >>> >> >> On 5/1/14, 4:21 PM, "John Halley Gotway via RT"
> >>><met_help at ucar.edu>
> >>> >> >>wrote:
> >>> >> >>
> >>> >> >>
> >>> >> >> >...
> >>> >> >> >
> >>> >> >> >If you have a meaningful interpretation of this data, you
could
> >>> >>update
> >>> >> >> >that table file. Even if you don't, here's a way you can
tell
> >>>MET
> >>> >>to
> >>> >> >>use
> >>> >> >> >that record:
> >>> >> >> >
> >>> >> >> > METv4.1/bin/plot_data_plane d2_2013053106_1830-
ACM2.grib
> >>> >> >> >d2_2013053106_1830-ACM2.ps 'name="var236"; level="Z50-
20";
> >>> >> >> >GRIB1_ptv=129;' -v 3
> >>> >> >> > DEBUG 1: Opening data file: d2_2013053106_1830-
ACM2.grib
> >>> >> >> > DEBUG 3: MetGrib1DataFile::data_plane_array() ->
Found range
> >>> >>match
> >>> >> >> >for VarInfo "var236/Z20-50" in GRIB record 7 of GRIB file
> >>> >> >> >"d2_2013053106_1830-ACM2.grib".
> >>> >> >> > DEBUG 3: MetGrib1DataFile::data_plane_array() ->
Found 1
> >>>GRIB
> >>> >> >>records
> >>> >> >> >matching VarInfo "var236/Z20-50" in GRIB file
> >>> >> >> >"d2_2013053106_1830-ACM2.grib".
> >>> >> >> > DEBUG 1: Creating postscript file:
> >>>d2_2013053106_1830-ACM2.ps
> >>> >> >> >
> >>> >> >> >I used "GRIB1_ptv=129" to tell it to look at the table
entries
> >>>for
> >>> >> >> >parameter table version number 129. "var236" is the
current
> >>> >> >>abbreviation
> >>> >> >> >for that record. And the level value is "Z50-20". This
> >>> >> >> >can be seen in the wgrib output: levels=(50,20). The 'Z'
tells
> >>>MET
> >>> >>to
> >>> >> >> >look for a vertical level, as opposed to a pressure
level. And
> >>>50
> >>> >>to
> >>> >> >>20
> >>> >> >> >defines the lower and upper bounds for that vertical
level.
> >>> >> >> >
> >>> >> >> >That should do the trick. I've attached a png version of
the
> >>> >>resulting
> >>> >> >> >image.
> >>> >> >> >
> >>> >> >> >Please give that a shot and let me know if it works for
you.
> >>>Feel
> >>> >>free
> >>> >> >> >to update your version of nceptab_flat.txt to list a more
> >>> meaningful
> >>> >> >> >abbreviation, long name, and units for this data type.
> >>> >> >> >
> >>> >> >> >Thanks,
> >>> >> >> >John
> >>> >> >>
> >>> >> >>
> >>> >> >> ________________________________
> >>> >> >>
> >>> >> >> This email is intended solely for the recipient. It may
contain
> >>> >> >> privileged, proprietary or confidential information or
material.
> >>>If
> >>> >>you
> >>> >> >>are
> >>> >> >> not the intended recipient, please delete this email and
any
> >>> >>attachments
> >>> >> >> and notify the sender of the error.
> >>> >> >>
> >>> >> >>
> >>> >> >>
> >>> >> >>
> >>> >> >
> >>> >>
> >>> >>
> >>> >> ________________________________
> >>> >>
> >>> >> This email is intended solely for the recipient. It may
contain
> >>> >> privileged, proprietary or confidential information or
material. If
> >>>you
> >>> >>are
> >>> >> not the intended recipient, please delete this email and any
> >>> attachments
> >>> >> and notify the sender of the error.
> >>> >>
> >>> >>
> >>> >>
> >>> >
> >>>
> >>>
> >>> ________________________________
> >>>
> >>> This email is intended solely for the recipient. It may contain
> >>> privileged, proprietary or confidential information or material.
If
> >>>you are
> >>> not the intended recipient, please delete this email and any
> >>>attachments
> >>> and notify the sender of the error.
> >>>
> >>>
> >>>
> >
>
>
> ________________________________
>
> This email is intended solely for the recipient. It may contain
> privileged, proprietary or confidential information or material. If
you are
> not the intended recipient, please delete this email and any
attachments
> and notify the sender of the error.
>
>
>
------------------------------------------------
More information about the Met_help
mailing list