[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[python #ISB-316714]: Help with metpy skew t

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: [python #ISB-316714]: Help with metpy skew t
  • Date: Sun, 20 Aug 2023 17:12:26 -0600
Greetings!

Your problem is caused by having your x/y indices flipped. According to the 
docs for `ll_to_xy` 
(https://wrf-python.readthedocs.io/en/latest/user_api/generated/wrf.ll_to_xy.html):

* "return_val[0] will contain the X (west_east) values"
* "return_val[1] will contain the Y (south_north) values"

When you use get_var, the all of the data fields have a dimension ordering of 
(bottom_top: 44, south_north: 318, west_east: 327). However, when you index 
into them you are currently doing:

    p = p1[:, x_y[0], x_y[1]]

which means you are using the "west_east" index with the "south_north" 
dimension. If I flip those, I get the expect low-level location for BRO.

Cheers,

Ryan

> Also the winds as you said are very off
> 
> On Tue, Aug 1, 2023 at 7:14?PM Will H <address@hidden> wrote:
> 
> > Good afternoon Ryan,
> >
> > If you take a look at each image you can see that the thermodynamics start
> > aloft and not near the surface.  Specifically KBRO, KCRP, KDRT, KSHV, KAMA
> >
> >
> >
> > address@hidden> wrote:
> >
> >> Greetings!
> >>
> >> Thanks for the complete package to try to replicate, it makes debugging
> >> so much easier.
> >>
> >> Can you be more specific what you consider wrong in the images you sent?
> >> A cursory examination shows "ok" agreement for the thermodynamics, though
> >> the winds do seem pretty different.
> >>
> >> Cheers!
> >>
> >> Ryan
> >>
> >> > Good afternoon Unidata,
> >> >
> >> > I am having problems with the Skew-T python code off of unidata's
> >> example
> >> > page.  I have modified it to fit my data types and not sure why the
> >> > graphics are coming out the way they are.
> >> >
> >> > I have included the python code, wrf output file to be read into it, and
> >> > the real observation sounding, and the model observation sounding.
> >> >
> >> > Could you please take a look at my python code and see if you see what
> >> I am
> >> > doing wrong?
> >> >
> >>
> >>
> >> Ticket Details
> >> ===================
> >> Ticket ID: ISB-316714
> >> Department: Support Python
> >> Priority: Low
> >> Status: Closed
> >> ===================
> >> NOTE: All email exchanges with Unidata User Support are recorded in the
> >> Unidata inquiry tracking system and then made publicly available through
> >> the web.  If you do not want to have your interactions made available in
> >> this way, you must let us know in each email you send to us.
> >>
> >>
> >>
> 
> 


Ticket Details
===================
Ticket ID: ISB-316714
Department: Support Python
Priority: Low
Status: Closed
===================
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata 
inquiry tracking system and then made publicly available through the web.  If 
you do not want to have your interactions made available in this way, you must 
let us know in each email you send to us.