What’s New in Iris#
v3.13.0.dev78 (20 Jun 2025) [unreleased]#
This document explains the changes made to Iris for this release (View all changes.)
v3.13.0.dev78 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#
✨ Features#
@trexfeathers and @ukmo-ccbunney extended the
iris.loading.LOAD_PROBLEMS
capturing to _all_ NetCDF objects that are added to aCube
during loading, as well as a selection of other objects such asCoordSystem
. Note this includes an improvement to howDimCoord
is ‘gracefully’ converted toAuxCoord
if it is masked - the mask is now preserved when it was not previously.
🐛 Bugs Fixed#
@HGWright added a new warning to inform users that the boolean coordinate generated by
iris.coord_categorisation.add_season_membership()
is not saveable to netcdf. (PR #6305)@bouweandela changed the
convert_units
method on cubes and coordinates so it also converts the values of the attributes"actual_range"
,"valid_max"
,"valid_min"
, and"valid_range"
. (PR #6416)@ukmo-ccbunney fixed loading and merging of masked data in scalar
AuxCoords
. (Issue #3584, PR #6468)@stephenworsley fixed the html representation of cubes in Jupyter when coordinates share the same name. (PR #6476)
@schlunma fixed loading of netCDF files with coordinates that have non-string units. (Issue #6505, PR #6506)
@ukmo-ccbunney correctly set the
bplon
PP field parameter when saving a cube defined on Limited Area Model (LAM) grid to PP format. Activate this behaviour with the new Futures flagiris.FUTURE.lam_pole_offset=True
. (Issue #3560, PR #6520)@stephenworsley fixed incompatibilities with numpy v2.3 affecting arrays of dates and array printing. (PR #6518)
💣 Incompatible Changes#
N/A
🚀 Performance Enhancements#
N/A
🔥 Deprecations#
N/A
🔗 Dependencies#
N/A
📚 Documentation#
N/A
💼 Internal#
@pp-mo replaced the PR-based linkchecks with a daily scheduled link checker based on lychee. (Issue #4140, PR #6386)
@trexfeathers added a CI workflow to quickly validate that the benchmarking setup is still working. (PR #6496)
@trexfeathers improved the stack trace for errors that occur during benchmark data generation, showing developers the root problem at-a-glance without needing local replication. (PR #6524)