Re: [python-users] Metpy height being read in incorrectly

• To: "Larkin, Grant, P" <grant.larkin490@xxxxxxxxxxxxxx>
• Subject: Re: [python-users] Metpy height being read in incorrectly
• From: Ryan May <rmay@xxxxxxxx>
• Date: Wed, 28 Mar 2018 13:54:49 -0600

Pierce,

Thanks for your interest and the report. It turns out there's a bug in the
get_layer_heights() function (which is used by storm_relative_helicity)
that modifies heights in-place.

You can follow progress on this issue here:
https://github.com/Unidata/MetPy/issues/789

I anticipate that this will be resolved in the 0.8 release of MetPy, which
will be released in mid-to-late April.

Ryan

On Tue, Mar 27, 2018 at 6:35 PM, Larkin, Grant, P <
grant.larkin490@xxxxxxxxxxxxxx> wrote:

> Hi,
>
>
> I am working on creating custom soundings using the Metpy programs. I am
> running into some issues, though (discovered today). The main one being
> that the height is initially read into the code correctly, but several
> blocks of Jupyter code later and the height reverts back to 0 m as the
> surface height. To combat this, I reread in the height in the block that I
> was working with, and printed the height at the beginning and end of the
> block of code. The height was read in correctly at the beginning of the
> block, but incorrectly at the end of the code. I have attached two images.
> One is of the block of code, and the other is of the output. This is
> throwing off some of my wind shear calculations, as well as my ability to
> plot the LCL in meters accurately (I have it in hPa currently, which isn't
> as effective at conveying the information). This issue isn't *as* big a
> deal in the eastern US, but on the high plains, it makes a big difference
> (example: my LCL was at 1670 m where it should be around 880m)! If you
> could be of any help, that would be awesome!
>
>
> Sincerely,
>
>
> Pierce Larkin
>
>
>
> _______________________________________________
> NOTE: All exchanges posted to Unidata maintained email lists are
> recorded in the Unidata inquiry tracking system and made publicly
> available through the web.  Users who post to any of the lists we
> maintain are reminded to remove any personal information that they
> do not want to be made public.
>
>
> python-users mailing list
> python-users@xxxxxxxxxxxxxxxxxxxxxxxx
> For list information, to unsubscribe, or change your membership options,
> visit: http://www.unidata.ucar.edu/mailing_lists/
>



-- 
Ryan May, Ph.D.
Software Engineer
UCAR/Unidata
Boulder, CO

• References:
  • [python-users] Metpy height being read in incorrectly
    • From: Larkin, Grant, P