anemoi-datasets 0.5.20__tar.gz → 0.5.21__tar.gz

anemoi_datasets-0.5.21/.release-please-manifest.json

@@ -0,0 +1,3 @@
+{
+    ".": "0.5.21"
+}

{anemoi_datasets-0.5.20 → anemoi_datasets-0.5.21}/CHANGELOG.md

@@ -8,6 +8,27 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 Please add your functional changes to the appropriate section in the PR.
 Keep it human-readable, your future self will thank you!
 
+## [0.5.21](https://github.com/ecmwf/anemoi-datasets/compare/0.5.20...0.5.21) (2025-04-08)
+
+
+### Features
+
+* more tests ([#277](https://github.com/ecmwf/anemoi-datasets/issues/277)) ([0ea7d46](https://github.com/ecmwf/anemoi-datasets/commit/0ea7d46a61aaa4381f8eb75b2623033bd404da5b))
+
+
+### Bug Fixes
+
+* grib-index command default ([#275](https://github.com/ecmwf/anemoi-datasets/issues/275)) ([04a37d8](https://github.com/ecmwf/anemoi-datasets/commit/04a37d8a046dc6b314e9f2376c69f1824cbfa43d))
+* pin version of numcodecs ([#285](https://github.com/ecmwf/anemoi-datasets/issues/285)) ([d86f317](https://github.com/ecmwf/anemoi-datasets/commit/d86f317981a312438a19323d5d67e1b31f80cf23))
+* update version of transform ([#284](https://github.com/ecmwf/anemoi-datasets/issues/284)) ([e72cdde](https://github.com/ecmwf/anemoi-datasets/commit/e72cddedd8160a27a9e63e2581f4fcc1a91cd8b6))
+
+
+### Documentation
+
+* some cleanup ([#276](https://github.com/ecmwf/anemoi-datasets/issues/276)) ([496b82a](https://github.com/ecmwf/anemoi-datasets/commit/496b82a5e10119c1fd27a58a85d5964fcad3c7bb))
+* time interpolation example ([#274](https://github.com/ecmwf/anemoi-datasets/issues/274)) ([9d19bd6](https://github.com/ecmwf/anemoi-datasets/commit/9d19bd6bc3c8e0c25718a05d670357936ec99a8b))
+* update documentation ([#271](https://github.com/ecmwf/anemoi-datasets/issues/271)) ([85ea386](https://github.com/ecmwf/anemoi-datasets/commit/85ea38690e7e8fab4dbac5c5b4d10eafdabde766))
+
 ## [0.5.20](https://github.com/ecmwf/anemoi-datasets/compare/0.5.19...0.5.20) (2025-03-31)
 
 

{anemoi_datasets-0.5.20 → anemoi_datasets-0.5.21}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: anemoi-datasets
-Version: 0.5.20
+Version: 0.5.21
 Summary: A package to hold various functions to support training of ML models on ECMWF data.
 Author-email: "European Centre for Medium-Range Weather Forecasts (ECMWF)" <software.support@ecmwf.int>
 License:                                  Apache License
@@ -225,9 +225,10 @@ Classifier: Programming Language :: Python :: Implementation :: CPython
 Classifier: Programming Language :: Python :: Implementation :: PyPy
 Requires-Python: >=3.9
 License-File: LICENSE
-Requires-Dist: anemoi-transform>=0.1.6
-Requires-Dist: anemoi-utils[provenance]>=0.4.18
+Requires-Dist: anemoi-transform>=0.1.9
+Requires-Dist: anemoi-utils[provenance]>=0.4.19
 Requires-Dist: cfunits
+Requires-Dist: numcodecs<0.16
 Requires-Dist: numpy
 Requires-Dist: pyyaml
 Requires-Dist: semantic-version

{anemoi_datasets-0.5.20 → anemoi_datasets-0.5.21}/docs/datasets/building/filters/orog_to_z.rst

@@ -2,7 +2,7 @@
  orog_to_z
 ###########
 
-The ``orog_to_z`` filter converts orography (in meters) to surface
+The ``orog_to_z`` filter converts orography (in metres) to surface
 geopotential height (m^2/s^2) using the equation:
 
 .. math::
@@ -10,7 +10,7 @@ geopotential height (m^2/s^2) using the equation:
    z &= g \cdot \textrm{orog}\\
    g &= 9.80665\ m \cdot s^{-1}
 
-This filter needs to follow a source that provides orography, which is
+This filter must follow a source that provides orography, which is
 replaced by surface geopotential height.
 
 .. literalinclude:: yaml/orog_to_z.yaml

{anemoi_datasets-0.5.20 → anemoi_datasets-0.5.21}/docs/datasets/building/filters/regrid.rst

@@ -3,23 +3,22 @@
 ########
 
 When building a dataset for a specific model, it is possible that the
-source grid or resolution doesn't fit the needs. In that case, it is
+source grid or resolution does not fit the needs. In that case, it is
 possible to add a filter to interpolate the data to a target grid. The
 filter is part of the ``anemoi-transform`` package. It will call the
 ``interpolate`` function from `earthkit-regrid
 <https://earthkit-regrid.readthedocs.io/en/latest/interpolate.html>`_ if
-the keys ``method``, ``in_grid`` and ``out_grid`` are provide and if a
+the keys ``method``, ``in_grid`` and ``out_grid`` are provided and if a
 `pre-generated matrix
 <https://earthkit-regrid.readthedocs.io/en/latest/inventory/index.html>`_
-exist for this tranformation. Otherwise it is possible to provide a
-``regrid matrix`` previously generate with ``anemoi-transform
-make-regrid-matrix``. The generated matrix is a NPZ file containing the
-input/output coordinates, the indices and the weights of the
+exists for this transformation. Otherwise, it is possible to provide a
+``regrid matrix`` previously generated with ``anemoi-transform
+make-regrid-matrix``. The generated matrix is an NPZ file containing the
+input/output coordinates, the indices, and the weights of the
 interpolation.
 
-``regrid`` is a :ref:`filter <filters>` that needs to follow a
-:ref:`source <sources>` or another filter in a :ref:`building-pipe`
-operation.
+``regrid`` is a :ref:`filter <filters>` that must follow a :ref:`source
+<sources>` or another filter in a :ref:`building-pipe` operation.
 
 .. literalinclude:: yaml/regrid1.yaml
    :language: yaml

{anemoi_datasets-0.5.20 → anemoi_datasets-0.5.21}/docs/datasets/building/filters/rename.rst

@@ -3,10 +3,10 @@
 ########
 
 When combining several sources, it is common to have different values
-for a given attribute to represents the same concept. For example,
+for a given attribute to represent the same concept. For example,
 ``temperature_850hPa`` and ``t_850`` are two different ways to represent
-the temperature at 850 hPa. The ``rename`` filter allows to rename a key
-to another key. It is a :ref:`filter <filters>` that needs to follow a
+the temperature at 850 hPa. The ``rename`` filter allows renaming a key
+to another key. It is a :ref:`filter <filters>` that must follow a
 :ref:`source <sources>` or another filter in a :ref:`building-pipe`
 operation.
 
@@ -15,6 +15,6 @@ operation.
 
 .. note::
 
-   The ``rename`` filter was mostly designed to rename the ``param``
+   The ``rename`` filter was primarily designed to rename the ``param``
    attribute, but any key can be renamed. The ``rename`` filter can take
    several renaming keys.

anemoi_datasets-0.5.21/docs/datasets/building/filters/sum.rst

@@ -0,0 +1,13 @@
+#####
+ sum
+#####
+
+The ``sum`` filter computes the sum over multiple variables. This can be
+useful for computing total precipitation from its components (snow,
+rain) or summing the components of total column-integrated water. This
+filter must follow a source that provides the list of variables to be
+summed up. These variables are removed by the filter and replaced by a
+single summed variable.
+
+.. literalinclude:: yaml/sum.yaml
+   :language: yaml

{anemoi_datasets-0.5.20 → anemoi_datasets-0.5.21}/docs/datasets/building/filters/wz_to_w.rst

@@ -4,8 +4,8 @@
 
 The ``wz_to_w`` filter converts geometric vertical velocity (provided in
 m/s) to vertical velocity in pressure coordinates (Pa/s). This filter
-needs to follow a source that provides geometric vertical velocity.
-Geometric vertical velocity is removed by the filter and pressure
+must follow a source that provides geometric vertical velocity.
+Geometric vertical velocity is removed by the filter, and pressure
 vertical velocity is added.
 
 .. literalinclude:: yaml/wz_to_w.yaml

{anemoi_datasets-0.5.20 → anemoi_datasets-0.5.21}/docs/datasets/building/filters.rst

@@ -6,7 +6,7 @@
 
 .. warning::
 
-   This is still a work in progress. Some of the filters may be renamed
+   This is still a work-in-progress. Some of the filters may be renamed
    later.
 
 Filters are used to modify the data or metadata in a dataset.

{anemoi_datasets-0.5.20 → anemoi_datasets-0.5.21}/docs/datasets/building/handling-missing-dates.rst

@@ -6,7 +6,8 @@ By default, the package will raise an error if there are missing dates.
 
 Missing dates can be handled by specifying a list of dates in the
 configuration file. The dates should be in the same format as the dates
-in the time series. The missing dates will be filled ``np.nan`` values.
+in the time series. The missing dates will be filled with ``np.nan``
+values.
 
 .. literalinclude:: ../yaml/missing_dates.yaml
    :language: yaml

{anemoi_datasets-0.5.20 → anemoi_datasets-0.5.21}/docs/datasets/building/handling-missing-values.rst

@@ -9,8 +9,8 @@ complete data in all fields.
 
 However, there are scenarios where `NaNs` naturally occur, such as with
 variables only relevant on land or at sea. This happens for sea surface
-temperature (`sst`), for example. In such cases, the default behavior is
-to reject data with `NaNs` as invalid. To accommodate `NaNs` and
+temperature (`sst`), for example. In such cases, the default behaviour
+is to reject data with `NaNs` as invalid. To accommodate `NaNs` and
 accurately compute statistics based on them, you can include the
 ``allow_nans`` key in the configuration.
 

{anemoi_datasets-0.5.20 → anemoi_datasets-0.5.21}/docs/datasets/building/incremental.rst

@@ -54,7 +54,7 @@ concurrent writes.
 
 Once you have loaded all the parts, you can finalise the dataset with
 the `finalise` command. This will write the metadata and the attributes
-to the dataset, and consolidate the statistics and cleanup some
+to the dataset, and consolidate the statistics and clean up some
 temporary files.
 
 .. code:: bash

{anemoi_datasets-0.5.20 → anemoi_datasets-0.5.21}/docs/datasets/building/introduction.rst

@@ -11,7 +11,7 @@ fields as well as the operations to perform on them, before they are
 written to a zarr file. The input of the process is a range of dates and
 some options to control the layout of the output. Statistics will be
 computed as the dataset is built, and stored in the metadata, with other
-information such as the the locations of the grid points, the list of
+information such as the locations of the grid points, the list of
 variables, etc.
 
 .. figure:: ../../_static/schemas/recipe.png
@@ -27,7 +27,7 @@ date
    not just a date. A training dataset covers a continuous range of
    dates with a given frequency. Missing dates are still part of the
    dataset, but missing data are marked as such using NaNs. Dates are
-   always in UTC, and refer to date at which the data is valid. For
+   always in UTC, and refer to the date at which the data is valid. For
    accumulations and fluxes, that would be the end of the accumulation
    period.
 
@@ -44,9 +44,9 @@ field
 
 source
    The `source` is a software component that, given a list of dates and
-   variables will return the corresponding fields. An example of source
-   is ECMWF's MARS archive, a collection of GRIB or NetCDF files, a
-   database, etc. See :ref:`sources` for more information.
+   variables, will return the corresponding fields. An example of a
+   source is ECMWF's MARS archive, a collection of GRIB or NetCDF files,
+   a database, etc. See :ref:`sources` for more information.
 
 filter
    A `filter` is a software component that takes as input the output of
@@ -69,13 +69,13 @@ join
 pipe
    The pipe is the process of transforming fields using filters. The
    first step of a pipe is typically a source, a join, or another pipe.
-   This can subsequently followed by more filters.
+   This can subsequently be followed by more filters.
 
 concat
    The concatenation is the process of combining different sets of
    operations that handle different dates. This is typically used to
    build a dataset that spans several years, when several sources are
-   involved, each providing data for different period.
+   involved, each providing data for a different period.
 
 Each operation is considered as a :ref:`source <sources>`, therefore
 operations can be combined to build complex datasets.

{anemoi_datasets-0.5.20 → anemoi_datasets-0.5.21}/docs/datasets/building/naming-conventions.rst

@@ -5,17 +5,17 @@
 ############################
 
 A dataset name is a string used to identify a dataset. It is designed to
-be human readable and is *not* designed to be parsed and splitted into
+be human-readable and is *not* designed to be parsed and split into
 parts.
 
 To ensure consistency, a dataset name should follow the following rules:
 
    -  All lower case.
-   -  Only letters and numbers and dashes ``-`` are allowed.
-   -  No underscore ``_`` and no dot ``.`` and no upper case letter and
-      no other special character (``@``, ``#``, ``*`` etc.).
+   -  Only letters, numbers, and dashes ``-`` are allowed.
+   -  No underscores ``_``, no dots ``.``, no uppercase letters, and no
+      other special characters (``@``, ``#``, ``*``, etc.).
 
-Additionlly, a dataset name is built from different parts joined with
+Additionally, a dataset name is built from different parts joined with
 ``-`` as follows (each part can contain additional ``-``):
 
 .. code::
@@ -24,12 +24,12 @@ Additionlly, a dataset name is built from different parts joined with
 
 .. note::
 
-   This is the current naming conventions for datasets in the Anemoi
+   This is the current naming convention for datasets in the Anemoi
    registry. It will need to be updated and adapted as more datasets are
    added. The part **purpose** is especially difficult to define for
    some datasets and may be revisited.
 
-The tables below provides more details and some examples.
+The tables below provide more details and some examples.
 
 .. list-table:: Dataset naming conventions
    :widths: 20 80
@@ -41,7 +41,7 @@ The tables below provides more details and some examples.
    -  -  **purpose**
 
       -  Can be `aifs` because the data is used to train the AIFS model.
-         Is also sometime `metno` for data from the Norwegian
+         It is also sometimes `metno` for data from the Norwegian
          Meteorological Institute. This definition may need to be
          revisited.
 
@@ -69,7 +69,7 @@ The tables below provides more details and some examples.
    -  -  **end-year**
 
       -  2020 if the first validity time is in 2020. Notice that if the
-         dataset is from 18.04.2020 to 19.07.2020, the star-year and
+         dataset is from 18.04.2020 to 19.07.2020, the start-year and
          end-year are both 2020. For instance in
          aifs-od-an-oper-0001-mars-o96-2020-2020-6h-v5
 
@@ -88,7 +88,7 @@ The tables below provides more details and some examples.
 
       -  Experimental datasets can have additional text in the name.
          This extra string can contain additional `-`. It provides
-         additional information about the content of dataset.
+         additional information about the content of the dataset.
 
 .. list-table:: Examples
    :widths: 100

{anemoi_datasets-0.5.20 → anemoi_datasets-0.5.21}/docs/datasets/building/naming-variables.rst

@@ -1,11 +1,11 @@
 .. _naming-variables:
 
 ##################
- Naming variables
+ Naming Variables
 ##################
 
 ***************
- rename filter
+ Rename Filter
 ***************
 
 The rename filter is used to rename variables in a dataset.
@@ -13,7 +13,7 @@ The rename filter is used to rename variables in a dataset.
 .. _remapping_option:
 
 ******************
- remapping option
+ Remapping Option
 ******************
 
 TODO.

{anemoi_datasets-0.5.20 → anemoi_datasets-0.5.21}/docs/datasets/building/operations.rst

@@ -4,7 +4,7 @@
  Operations
 ############
 
-Operations are blocks of YAML code that translates a list of dates into
+Operations are blocks of YAML code that translate a list of dates into
 fields.
 
 .. _building-join:
@@ -13,8 +13,8 @@ fields.
  join
 ******
 
-The join is the process of combining several sources data. Each source
-is expected to provide different variables at the same dates.
+The join is the process of combining data from several sources. Each
+source is expected to provide different variables for the same dates.
 
 .. literalinclude:: ../yaml/input.yaml
    :language: yaml
@@ -25,10 +25,10 @@ is expected to provide different variables at the same dates.
  concat
 ********
 
-The concatenation is the process of combining different sets of
-operation that handle different dates. This is typically used to build a
-dataset that spans several years, when the several sources are involved,
-each providing a different period.
+Concatenation is the process of combining different sets of operations
+that handle different dates. This is typically used to build a dataset
+that spans several years, when several sources are involved, each
+providing a different period.
 
 .. literalinclude:: ../yaml/concat.yaml
    :language: yaml
@@ -40,7 +40,7 @@ each providing a different period.
 ******
 
 The pipe is the process of transforming fields using :ref:`filters
-<filters>`. The first step of a pipe is typically a source, a join or
+<filters>`. The first step of a pipe is typically a source, a join, or
 another pipe. The following steps are filters.
 
 .. literalinclude:: ../yaml/pipe.yaml

{anemoi_datasets-0.5.20 → anemoi_datasets-0.5.21}/docs/datasets/building/sources/accumulations.rst

@@ -7,13 +7,13 @@
    The `accumulations` source is currently using the `mars` source
    internally. This will be changed in the future.
 
-Accumulations and fluxes variables, such as precipitations, are often
-forecast fields, which are archived for a given a base date (or
-reference time) and a forecast time (or step). These fields are valid at
-the forecast time, and are accumulated over a given period of time, with
-the relation: :math:`valid\_date = base\_date + step`.
+Accumulations and flux variables, such as precipitation, are often
+forecast fields, which are archived for a given base date (or reference
+time) and a forecast time (or step). These fields are valid at the
+forecast time and are accumulated over a given period of time, with the
+relation: :math:`valid\_date = base\_date + step`.
 
-Because the package build datasets according to the valid date of the
+Because the package builds datasets according to the valid date of the
 fields, it must be able to compute the base date and the forecast time
 from the valid date. Furthermore, some fields are accumulated since the
 beginning of the forecast (e.g. ECMWF operational forecast), while
@@ -37,19 +37,18 @@ used:
 
 -  For ERA5, the data is accumulated since the last time step, and steps
    are hourly, and only available at 06Z and 18Z. So, a 6h accumulation
-   for the date for the date 2020-01-01 13:00 the source will use the
-   forecast of 2020-01-01 06:00 and the step 1-2h, 2-3h, 3-4h, 4-5h,
-   5-6h and 6-7h.
+   for the date 2020-01-01 13:00, the source will use the forecast of
+   2020-01-01 06:00 and the step 1-2h, 2-3h, 3-4h, 4-5h, 5-6h and 6-7h.
 
-If the of ``accumulation_period`` value is a pair of integers `[step1,
+If the ``accumulation_period`` value is a pair of integers `[step1,
 step2]`, the algorithm is different. The source will compute the
-accumulation between the `step1` and `step2` previous forecast that
+accumulation between the `step1` and `step2` previous forecasts that
 validate at the given date at `step2`. For example, if the accumulation
 period is `[6, 12]`, and the valid date is 2020-10-10 18:00, the source
 will use the forecast of 2020-10-10 06:00 and the steps 6h and 12h.
 
 Please note that ``accumulation_period=6`` and ``accumulation_period=[0,
-6]`` are not equivalent. In the first case, the source can use return an
+6]`` are not equivalent. In the first case, the source can return an
 accumulation between step 1h and step 7h if it is the most appropriate
 data available, while in the second case, the source will always return
 the accumulation between step 0h and step 6h, if available.

{anemoi_datasets-0.5.20 → anemoi_datasets-0.5.21}/docs/datasets/building/sources/anemoi-dataset.rst

@@ -14,6 +14,6 @@ An anemoi-dataset can be a source for a dataset:
 .. literalinclude:: yaml/anemoi-dataset.yaml
    :language: yaml
 
-The parameters are the same as the ones used in the ``open_dataset``
+The parameters are the same as those used in the ``open_dataset``
 function, which allows you to subset and combine datasets. See
 :ref:`opening-datasets` for more information.

{anemoi_datasets-0.5.20 → anemoi_datasets-0.5.21}/docs/datasets/building/sources/cds.rst

@@ -4,10 +4,10 @@
  cds
 #####
 
-For users outside of ECMWF organisation, it is possible to access ERA5
-data through the Copernicus Climate Data Store ``cdsapi`` instead.
+For users outside of the ECMWF organisation, it is possible to access
+ERA5 data through the Copernicus Climate Data Store ``cdsapi`` instead.
 
-The steps to setup a CDS API account are detailed `here
+The steps to set up a CDS API account are detailed `here
 <https://cds.climate.copernicus.eu/how-to-api>`_.
 
 The only difference with the previous MARS recipes is the addition of

{anemoi_datasets-0.5.20 → anemoi_datasets-0.5.21}/docs/datasets/building/sources/eccc-fstd.rst

@@ -12,7 +12,7 @@ The recipe will build a dataset from a standard file using the
 ``fstd2nc`` xarray plugin.
 
 The ``fstd2nc`` dependency is not part of the default anemoi-datasets
-installation and has to be install following the `fstd2nc project
+installation and has to be installed following the `fstd2nc project
 description <https://github.com/neishm/fstd2nc>`_.
 
 See :ref:`create-cf-data` for more information.

{anemoi_datasets-0.5.20 → anemoi_datasets-0.5.21}/docs/datasets/building/sources/forcings.rst

@@ -8,8 +8,8 @@ The purpose of `forcings` is to provide fields with values that only
 depend on the grid cell and/or the time.
 
 Because the source needs to generate fields on the same grids as the
-other, it requires a template field. This is provided in the recipe with
-the ``template`` keyword:
+others, it requires a template field. This is provided in the recipe
+with the ``template`` keyword:
 
 .. literalinclude:: yaml/forcings.yaml
    :language: yaml
@@ -17,19 +17,19 @@ the ``template`` keyword:
 .. _yaml-reference:
 
 The value ``${input.join.0.source1}`` is the "path" to the first source,
-starting from the root of the recipe. The path is composed of the of the
-nodes in the recipe, separated by dots. If a node contains a list, the
-index of the next node is added after the node name, starting from 0.
-This is called a `reference`.
+starting from the root of the recipe. The path is composed of the nodes
+in the recipe, separated by dots. If a node contains a list, the index
+of the next node is added after the node name, starting from 0. This is
+called a `reference`.
 
 .. warning::
 
-   If you use the :ref:`concat <building-concat>` contruct to have
-   different inputs for different time ranges, the template field point
+   If you use the :ref:`concat <building-concat>` construct to have
+   different inputs for different time ranges, the template field points
    to a source in the same block of the concat where the `forcing` is
    mentioned.
 
-The is a mean to provide the model with with space and time information
+This is a means to provide the model with space and time information
 during training and inference.
 
 The following fields are available:
@@ -53,8 +53,8 @@ sin_latitude
 
 longitude
    Each grid point has the value of its longitude in degrees. Currently,
-   the longitude are not normalised and the values are the ones provided
-   by the source used as template.
+   the longitude is not normalised, and the values are the ones provided
+   by the source used as a template.
 
    Range of values: :math:`[-180, 360)`
 
@@ -72,29 +72,29 @@ sin_longitude
 
 ecef_x
    Each grid point has the value of the **x** coordinate of the
-   `Earth-Centered, Earth-Fixed (ECEF) coordinate system <ECEF>`_. The
+   `Earth-Centred, Earth-Fixed (ECEF) coordinate system <ECEF>`_. The
    Earth is assumed to be a perfect sphere with a radius of 1.
 
    Range of values: :math:`[-1, 1]`
 
 ecef_y
    Each grid point has the value of the **y** coordinate of the
-   `Earth-Centered, Earth-Fixed (ECEF) coordinate system <ECEF>`_. The
+   `Earth-Centred, Earth-Fixed (ECEF) coordinate system <ECEF>`_. The
    Earth is assumed to be a perfect sphere with a radius of 1.
 
    Range of values: :math:`[-1, 1]`
 
 ecef_z
    Each grid point has the value of the **z** coordinate of the
-   `Earth-Centered, Earth-Fixed (ECEF) coordinate system <ECEF>`_. The
+   `Earth-Centred, Earth-Fixed (ECEF) coordinate system <ECEF>`_. The
    Earth is assumed to be a perfect sphere with a radius of 1.
 
    Range of values: :math:`[-1, 1]`
 
 julian_day
-   The Julian day is the fractional number of days since the 1st or
+   The Julian day is the fractional number of days since the 1st of
    January at 00:00 of the current year. For example, the Julian day of
-   1st or January at 12:00 is 0.5. Every grid point has the same value
+   1st of January at 12:00 is 0.5. Every grid point has the same value
    of the Julian day at the given date.
 
    Range of values: :math:`[0, 365)` on a non-leap year and :math:`[0,
@@ -155,4 +155,4 @@ toa_incident_solar_radiation
 
 .. _earthkit.meteo: https://github.com/ecmwf/earthkit-meteo/blob/74654e0b188e5a201d8268e93376246c925e3172/earthkit/meteo/solar/__init__.py#L49C4-L49C27
 
-.. _ecef: https://en.wikipedia.org/wiki/Earth-centered,_Earth-fixed_coordinate_system
+.. _ecef: https://en.wikipedia.org/wiki/Earth-centred,_Earth-fixed_coordinate_system

{anemoi_datasets-0.5.20 → anemoi_datasets-0.5.21}/docs/datasets/building/sources/grib.rst

@@ -10,22 +10,22 @@ To read all the GRIB from a file, use the following:
    :language: yaml
 
 You can also read specific GRIB messages by specifying them using the
-MARS language (excluding the keywords `date`, `time` and `step`, as well
-as any post-processing options, such as `grid` or `area`):
+MARS language (excluding the keywords `date`, `time`, and `step`, as
+well as any post-processing options, such as `grid` or `area`):
 
 .. literalinclude:: yaml/grib2.yaml
    :language: yaml
 
-You can also read a collection of GRIB files, using Unix' shell
+You can also read a collection of GRIB files, using Unix shell
 wildcards_:
 
 .. literalinclude:: yaml/grib3.yaml
    :language: yaml
 
 You can also use the requested `date` to build the filenames. For
-example It the GRIB files containing the requested data are named
+example, if the GRIB files containing the requested data are named
 according to the following pattern: ``/path/to/YYYY/MM/YYYYMMDDHH.grib``
-with `YYYY` being the year, `MM` the month, `DD` the day and `HH` the
+with `YYYY` being the year, `MM` the month, `DD` the day, and `HH` the
 hour, you can use the following configuration:
 
 .. literalinclude:: yaml/grib4.yaml
@@ -39,7 +39,7 @@ See :ref:`create-grib-data` for more information.
 .. note::
 
    You can combine all the above options when selecting GRIB messages
-   from file.
+   from a file.
 
 .. _strftime: https://python.readthedocs.io/en/latest/library/datetime.html#strftime-and-strptime-behavior
 

{anemoi_datasets-0.5.20 → anemoi_datasets-0.5.21}/docs/datasets/building/sources/hindcasts.rst

@@ -8,7 +8,7 @@
    internally. This will be changed in the future.
 
 Hindcasts data, also known as reforecasts, are unique because they are
-run for a specific day of year (such as 1 January or 11 June) for
+run for a specific day of the year (such as 1 January or 11 June) for
 multiple years. So, for a given reference date like 2022-05-12, we can
 have hindcasts for 2001-05-12, 2002-05-12, 2003-05-12, and so on. This
 is useful in many cases. For more details, please refer to this ECMWF
@@ -17,7 +17,7 @@ documentation.
 The `hindcasts` source has a special argument called `reference_year`,
 which represents the year of the reference date. Based on the requested
 valid datetime and on the `reference_year`, the `hindcasts` source will
-calculate the `hdate` and `date` and `time` appropriately.
+calculate the `hdate`, `date`, and `time` appropriately.
 
 For example, if the `reference_year` is 2022, then the data for
 2002-05-12 will use data with `hdate=2002-05-12` and `date=2022-05-12`.

{anemoi_datasets-0.5.20 → anemoi_datasets-0.5.21}/docs/datasets/building/sources/mars.rst

@@ -6,8 +6,8 @@ The ``mars`` source will retrieve the data from the ECMWF MARS archive.
 For that, you need to have an ECMWF account and build your dataset on
 one of the Centre's computers, or use the ``ecmwfapi`` Python package.
 
-The `yaml` block can contain any keys that following the `MARS language
-specification`_, with the exception of the ``date``, ``time``` and
+The `yaml` block can contain any keys that follow the `MARS language
+specification`_, with the exception of the ``date``, ``time``, and
 ``step``.
 
 The missing keys will be filled with the default values, as defined in
@@ -16,13 +16,13 @@ the MARS language specification.
 .. literalinclude:: yaml/mars1.yaml
    :language: yaml
 
-Data from several levels types must be requested in separate requests,
+Data from several level types must be requested in separate requests,
 with the ``join`` command.
 
 .. literalinclude:: yaml/mars2.yaml
    :language: yaml
 
 See :ref:`naming-variables` for information on how to name the variables
-when mixing single level and multi-levels variables in the same dataset.
+when mixing single-level and multi-level variables in the same dataset.
 
 .. _mars language specification: https://confluence.ecmwf.int/display/UDOC/MARS+user+documentation

{anemoi_datasets-0.5.20 → anemoi_datasets-0.5.21}/docs/datasets/building/sources/netcdf.rst

@@ -2,7 +2,7 @@
  netcdf
 ########
 
-In the examples below we explain how to create an anemoi dataset from
+In the examples below, we explain how to create an anemoi dataset from
 one or more netCDF files.
 
 .. literalinclude:: yaml/netcdf.yaml