Skip to content

Commit

Permalink
Whats new updates for v3.6.0 (#5323)
Browse files Browse the repository at this point in the history
  • Loading branch information
bjlittle authored May 18, 2023
1 parent 79bc09e commit 9bb0a9d
Showing 1 changed file with 7 additions and 7 deletions.
14 changes: 7 additions & 7 deletions docs/src/whatsnew/3.6.rst
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
.. include:: ../common_links.inc

v3.6 (03 May 2023) [release candidate]
**************************************
v3.6 (18 May 2023)
******************

This document explains the changes made to Iris for this release
(:doc:`View all changes <index>`.)
Expand All @@ -17,11 +17,11 @@ This document explains the changes made to Iris for this release
to netCDF** (:pull:`5191`) that we're celebrating this important step change
in behavour with its very own dedicated release 🥳

By using ``iris.save(..., compute=False)`` you can now save to multiple netcdf files
By using ``iris.save(..., compute=False)`` you can now save to multiple NetCDF files
in parallel. See the new ``compute`` keyword in :func:`iris.fileformats.netcdf.save`.
This can share and re-use any common (lazy) result computations, and it makes much
better use of resources during any file-system waiting (i.e. it can use such periods to
progress the *other* saves).
better use of resources during any file-system waiting (i.e., it can use such periods
to progress the *other* saves).

Usage example::

Expand All @@ -33,11 +33,11 @@ This document explains the changes made to Iris for this release
# Complete saves in parallel.
dask.compute(*delayeds)

This advance also includes **another substantial benefit**, because netcdf saves can
This advance also includes **another substantial benefit**, because NetCDF saves can
now use a
`Dask.distributed scheduler <https://docs.dask.org/en/stable/scheduling.html>`_.
With `Distributed <https://distributed.dask.org/en/stable/>`_ you can parallelise the
saves across a whole cluster. Whereas previously, the netcdf saving *only* worked with
saves across a whole cluster. Whereas previously, the NetCDF saving *only* worked with
a "threaded" scheduler, limiting it to a single CPU.

We're so super keen for the community to leverage the benefit of this new
Expand Down

0 comments on commit 9bb0a9d

Please sign in to comment.