You are viewing the latest unreleased documentation v0.1.0.dev5407. You may prefer a stable version.

What’s New in Iris#

v0.1.0.dev5407 (03 Oct 2022) [unreleased]#

This document explains the changes made to Iris for this release (View all changes.)

v0.1.0.dev5407 Release Highlights

The highlights for this major/minor release of Iris include:

  • N/A

And finally, get in touch with us on GitHub if you have any issues or feature requests for improving Iris. Enjoy!

📢 Announcements#

  1. Welcome to @ESadek-MO and @TTV-Intrepid who made their first contributions to Iris 🎉

✨ Features#

  1. @ESadek-MO edited expand_filespecs() to allow expansion of non-existing paths, and added expansion functionality to save(). (Issue #4772, PR #4913)

🐛 Bugs Fixed#

  1. @rcomer and @pp-mo (reviewer) factored masking into the returned sum-of-weights calculation from SUM. (PR #4905)

  2. @schlunma fixed a bug which prevented using iris.cube.Cube.collapsed() on coordinates whose number of bounds differs from 0 or 2. This enables the use of this method on mesh coordinates. (Issue #4672, PR #4870)

  3. @bjlittle and @lbdreyer (reviewer) fixed the building of the CF Standard Names module iris.std_names for the setup.py commands develop and std_names. (Issue #4951, PR #4952)

  4. @lbdreyer and @pp-mo (reviewer) fixed the cube print out such that scalar ancillary variables are displayed in a dedicated section rather than being added to the vector ancillary variables section. Further, ancillary variables and cell measures that map to a cube dimension of length 1 are now included in the respective vector sections. (PR #4945)

💣 Incompatible Changes#

  1. N/A

🚀 Performance Enhancements#

  1. @rcomer and @pp-mo (reviewer) increased aggregation speed for SUM, COUNT and PROPORTION on real data. (PR #4905)

  2. @bouweandela made iris.coords.Coord.cells() faster for time coordinates. This also affects iris.cube.Cube.extract(), iris.cube.Cube.subset(), and iris.coords.Coord.intersect(). (PR #4969)

🔥 Deprecations#

  1. N/A

🔗 Dependencies#

  1. @rcomer introduced the dask >=2.26 minimum pin, so that Iris can benefit from Dask’s support for NEP13 and NEP18. (PR #4905)

  2. @trexfeathers advanced the Cartopy pin to >=0.21, as Cartopy’s change to default Transverse Mercator projection affects an Iris test. See SciTools/cartopy@fcb784d and SciTools/cartopy@8860a81 for more details. (PR #4968)

  3. @trexfeathers introduced the netcdf4!=1.6.1 pin to avoid a problem with segfaults. (PR #4968)

  4. @trexfeathers updated the Matplotlib colormap registration in iris.palette in response to a deprecation warning. Using the new Matplotlib API also means a matplotlib>=3.5 pin. (PR #4998)

📚 Documentation#

  1. @ESadek-MO, @TTV-Intrepid and @trexfeathers added a gallery example for zonal means plotted parallel to a cartographic plot. (PR #4871)

  2. @Esadek-MO added a key-terms Glossary page into the user guide. (PR #4902)

💼 Internal#

  1. @rcomer removed the obsolete setUpClass method from Iris testing. (PR #4927)

  2. @bjlittle and @lbdreyer (reviewer) removed support for python setup.py test, which is a deprecated approach to executing package tests, see pypa/setuptools#1684. Also performed assorted setup.py script hygiene. (PR #4948, PR #4949, PR #4950)

  3. @pp-mo split the module iris.fileformats.netcdf into separate loader and saver submodules, just to make the code easier to handle.

  4. @trexfeathers adapted the benchmark for importing iris.palette to cope with new colormap behaviour in Matplotlib v3.6. (PR #4998)

  5. @rcomer removed a now redundant workaround for an old matplotlib bug, highlighted by Issue #4090. (PR #4999)

previous

iris.util

next

v0.1.0.dev5407 (03 Oct 2022) [unreleased]