You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Aug 13, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Aug 13, 2026. It is now read-only.
The QG notebook was completely busted by metpy 1.0rc1. Not sure if it's a simple update, or if there's something not-so-good in the rc. (heads up @jthielen )
I'll have to take a closer look once Unidata/MetPy#1304 / Unidata/MetPy#1325 are in, but my initial guess from a quick read through is that that notebook assumes mpcalc.smooth_n_point outputs pint Quantities when supplied xarray.DataArray, which changed to outputting xarray.DataArray with Unidata/MetPy#1223.
That makes sense, I can run with that and see what happens. This is the first time I've tried to use the RC in a workshop, and I did that because some combination of xarray and pint updates broke something in getting the longitude coords.
Activity
jthielen commentedon Mar 6, 2020
I'll have to take a closer look once Unidata/MetPy#1304 / Unidata/MetPy#1325 are in, but my initial guess from a quick read through is that that notebook assumes
mpcalc.smooth_n_pointoutputs pint Quantities when suppliedxarray.DataArray, which changed to outputtingxarray.DataArraywith Unidata/MetPy#1223.dopplershift commentedon Mar 6, 2020
That makes sense, I can run with that and see what happens. This is the first time I've tried to use the RC in a workshop, and I did that because some combination of xarray and pint updates broke something in getting the longitude coords.
dopplershift commentedon Mar 13, 2020
Fixed in 455ffa0.