xarray-binfile 0.1.0b1__tar.gz → 0.2.0__tar.gz

{xarray_binfile-0.1.0b1 → xarray_binfile-0.2.0}/.github/workflows/check-links.yaml

@@ -17,7 +17,7 @@ jobs:
   check-links:
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0
+      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
         with:
           persist-credentials: false
       - uses: gaurav-nelson/github-action-markdown-link-check@3c3b66f1f7d0900e37b71eca45b63ea9eedfce31 # 1.0.17

{xarray_binfile-0.1.0b1 → xarray_binfile-0.2.0}/.github/workflows/ci.yaml

@@ -38,18 +38,18 @@ jobs:
     # Python 3.15 is still a release candidate, so keep a single advisory job
     continue-on-error: ${{ matrix.python-version == '3.15' }}
     steps:
-      - uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0
+      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
         with:
           persist-credentials: false
 
       - name: Set up Python
-        uses: actions/setup-python@ece7cb06caefa5fff74198d8649806c4678c61a1 # v6.3.0
+        uses: actions/setup-python@5fda3b95a4ea91299a34e894583c3862153e4b97 # v7.0.0
         with:
           python-version: ${{ matrix.python-version }}
           allow-prereleases: true
 
       - name: Install Hatch
-        uses: pypa/hatch@257e27e51a6a5616ed08a39a408a21c35c9931bc
+        uses: pypa/hatch@f647ed70d49adb885f53a27d1c7f5bdaeacf2c60
 
       - name: Run tests
         run: |
@@ -65,14 +65,14 @@ jobs:
     needs: test
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0
+      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
         with:
           persist-credentials: false
-      - uses: actions/setup-python@ece7cb06caefa5fff74198d8649806c4678c61a1 # v6.3.0
+      - uses: actions/setup-python@5fda3b95a4ea91299a34e894583c3862153e4b97 # v7.0.0
         with:
           python-version: "3.12"
       - name: Install Hatch
-        uses: pypa/hatch@257e27e51a6a5616ed08a39a408a21c35c9931bc
+        uses: pypa/hatch@f647ed70d49adb885f53a27d1c7f5bdaeacf2c60
       - name: Build package
         run: hatch build
       - uses: actions/upload-artifact@043fb46d1a93c77aae656e7c1c64a875d1fc6a0a # v7.0.1
@@ -91,7 +91,7 @@ jobs:
     permissions:
       contents: read
     steps:
-      - uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0
+      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
         with:
           persist-credentials: false
           fetch-depth: 0 # Shallow clones should be disabled for a better relevancy of analysis
@@ -103,7 +103,7 @@ jobs:
           merge-multiple: true
 
       - name: SonarQube Scan
-        uses: SonarSource/sonarqube-scan-action@713881670b6b3676cda39549040e2d88c70d582e # v8.2.0
+        uses: SonarSource/sonarqube-scan-action@ba9859eae8dd6bd29e412f25ddbbef3d032000f4 # v8.2.2
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
           SONAR_TOKEN: ${{ secrets.SONAR_TOKEN }}
@@ -139,4 +139,4 @@ jobs:
           path: dist
 
       - name: Publish package distributions to PyPI
-        uses: pypa/gh-action-pypi-publish@cef221092ed1bacb1cc03d23a2d87d1d172e277b # v1.14.0
+        uses: pypa/gh-action-pypi-publish@dc37677b2e1c63e2034f94d8a5b11f265b73ba33 # v1.14.2

{xarray_binfile-0.1.0b1 → xarray_binfile-0.2.0}/.github/workflows/docs.yaml

@@ -24,17 +24,17 @@ jobs:
     permissions:
       contents: read
     steps:
-      - uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0
+      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
         with:
           persist-credentials: false
 
       - name: Set up Python
-        uses: actions/setup-python@ece7cb06caefa5fff74198d8649806c4678c61a1 # v6.3.0
+        uses: actions/setup-python@5fda3b95a4ea91299a34e894583c3862153e4b97 # v7.0.0
         with:
           python-version: "3.13"
 
       - name: Install Hatch
-        uses: pypa/hatch@257e27e51a6a5616ed08a39a408a21c35c9931bc
+        uses: pypa/hatch@f647ed70d49adb885f53a27d1c7f5bdaeacf2c60
 
       - name: Install Graphviz
         run: sudo apt-get update && sudo apt-get install --yes graphviz

{xarray_binfile-0.1.0b1 → xarray_binfile-0.2.0}/.pre-commit-config.yaml

@@ -17,7 +17,7 @@ repos:
       - id: mixed-line-ending
       - id: trailing-whitespace
   - repo: https://github.com/astral-sh/ruff-pre-commit
-    rev: v0.15.20
+    rev: v0.16.10
     hooks:
       # Run the linter.
       - id: ruff
@@ -27,12 +27,12 @@ repos:
       - id: ruff-format
         types_or: [python, pyi, jupyter]
   - repo: https://github.com/pre-commit/mirrors-mypy
-    rev: v2.1.0
+    rev: v2.4.0
     hooks:
       - id: mypy
         exclude: docs/conf.py
   - repo: https://github.com/codespell-project/codespell
-    rev: v2.4.2
+    rev: v2.4.3
     hooks:
       - id: codespell
         additional_dependencies:
@@ -48,7 +48,7 @@ repos:
     hooks:
       - id: nbstripout
   - repo: https://github.com/woodruffw/zizmor-pre-commit
-    rev: v1.26.1
+    rev: v1.30.1
     hooks:
       - id: zizmor
 

{xarray_binfile-0.1.0b1 → xarray_binfile-0.2.0}/.vscode/settings.json

@@ -24,11 +24,5 @@
     "cSpell.enabled": true,
     "cSpell.language": "en",
     "python.envFile": "${workspaceFolder}/.venv/xarray-binfile",
-    "python-envs.pythonProjects": [
-        {
-            "path": ".",
-            "envManager": "ms-python.python:venv",
-            "packageManager": "ms-python.python:pip"
-        }
-    ]
+    "python.testing.pytestPath": "${workspaceFolder}/.venv/xarray-binfile/bin/pytest"
 }

xarray_binfile-0.2.0/CITATION.cff

@@ -0,0 +1,21 @@
+cff-version: 1.2.0
+message: If you use this software, please cite it using the metadata from this file.
+type: software
+title: Xarray-binfile
+abstract: >-
+  Custom Xarray file engine to read and write raw binary files, with optional
+  lazy chunking through Dask.
+authors:
+  - family-names: Schuch
+    given-names: Felipe N.
+    email: me@fschuch.com
+    orcid: https://orcid.org/0000-0002-6140-0273
+license: MIT
+repository-code: https://github.com/fschuch/xarray-binfile
+url: https://docs.fschuch.com/xarray-binfile/
+keywords:
+  - xarray
+  - dask
+  - binary files
+  - xcompact3d
+  - 2decomp

xarray_binfile-0.2.0/CODE_OF_CONDUCT.md

@@ -0,0 +1,83 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, caste, color, religion, or sexual identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our community include:
+
+- Demonstrating empathy and kindness toward other people
+- Being respectful of differing opinions, viewpoints, and experiences
+- Giving and gracefully accepting constructive feedback
+- Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
+- Focusing on what is best not just for us as individuals, but for the overall community
+
+Examples of unacceptable behavior include:
+
+- The use of sexualized language or imagery, and sexual attention or advances of any kind
+- Trolling, insulting or derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or email address, without their explicit permission
+- Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at [contato@fschuch.com](mailto:contato@fschuch.com). All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.1, available at [https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder][mozilla coc].
+
+For answers to common questions about this code of conduct, see the FAQ at [https://www.contributor-covenant.org/faq][faq]. Translations are available at [https://www.contributor-covenant.org/translations][translations].
+
+[faq]: https://www.contributor-covenant.org/faq
+[homepage]: https://www.contributor-covenant.org
+[mozilla coc]: https://github.com/mozilla/diversity
+[translations]: https://www.contributor-covenant.org/translations
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html

xarray_binfile-0.2.0/CONTRIBUTING.md

@@ -0,0 +1,42 @@
+# Contributing to Xarray-binfile
+
+Thank you for your interest in contributing! Contributions of all kinds are welcome: bug reports, feature requests, documentation improvements, and code.
+
+## Reporting issues
+
+Open an issue at <https://github.com/fschuch/xarray-binfile/issues>. Please include the package version, Python version, operating system, and a minimal example that reproduces the problem.
+
+## Development setup
+
+The development workflow is powered by [Hatch](https://hatch.pypa.io). After installing Hatch, fork and clone the repository, then run:
+
+```bash
+hatch run qa
+```
+
+This runs the pre-commit checks (ruff, mypy, codespell, and others) and the full test suite with coverage. Useful individual commands:
+
+```bash
+hatch run check          # pre-commit hooks on all files
+hatch run test           # tests with coverage
+hatch run test-benchmark # benchmarks (pytest-benchmark and memray)
+hatch run docs:serve     # live preview of the documentation
+```
+
+## Pull requests
+
+1. Create a branch from `main`.
+1. Add or update tests for your change.
+1. Make sure `hatch run qa` passes locally.
+1. Open a pull request describing the motivation and the change.
+
+Continuous integration runs the same checks across all supported Python versions.
+
+## Code of conduct
+
+This project follows the [Contributor Covenant](CODE_OF_CONDUCT.md). By participating you agree to abide by its terms.
+
+## Full guide
+
+The complete contributor guide, including details on releases, versioning, and documentation, lives in the documentation:
+<https://docs.fschuch.com/xarray-binfile/references/how-to-contribute.html>

{xarray_binfile-0.1.0b1 → xarray_binfile-0.2.0}/PKG-INFO

@@ -1,6 +1,6 @@
-Metadata-Version: 2.4
+Metadata-Version: 2.5
 Name: xarray-binfile
-Version: 0.1.0b1
+Version: 0.2.0
 Summary: Read and write raw binary files using the familiar interface from the Xarray library
 Project-URL: Source, https://github.com/fschuch/xarray-binfile
 Project-URL: Tracker, https://github.com/fschuch/xarray-binfile/issues
@@ -41,8 +41,8 @@ Requires-Dist: pytest-benchmark>=5.1.0; extra == 'tests'
 Requires-Dist: pytest-cov>=5.0.0; extra == 'tests'
 Requires-Dist: pytest>=8.2.2; extra == 'tests'
 Provides-Extra: tests-extra
-Requires-Dist: pytest-randomly==4.1.0; extra == 'tests-extra'
-Requires-Dist: pytest-rerunfailures==16.3; extra == 'tests-extra'
+Requires-Dist: pytest-randomly==5.0.0; extra == 'tests-extra'
+Requires-Dist: pytest-rerunfailures==16.7; extra == 'tests-extra'
 Requires-Dist: pytest-xdist==3.8.0; extra == 'tests-extra'
 Description-Content-Type: text/markdown
 

{xarray_binfile-0.1.0b1 → xarray_binfile-0.2.0}/docs/_config.yml

@@ -49,6 +49,10 @@ sphinx:
     #https://github.com/executablebooks/jupyter-book/issues/1950#issuecomment-1454801479
     suppress_warnings: ["mystnb.unknown_mime_type"]
 
+    # allow_errors: false only reports failed cells as warnings; this makes
+    # a notebook execution error abort the build with a non-zero exit code
+    nb_execution_raise_on_error: true
+
     intersphinx_mapping:
       python:
         - "https://docs.python.org/3"

{xarray_binfile-0.1.0b1 → xarray_binfile-0.2.0}/docs/references/api-reference.rst

@@ -19,6 +19,15 @@ Write accessors
    :imported-members:
 
 
+Conventions
+-----------
+
+.. automodule:: xarray_binfile.conventions
+   :members:
+   :show-inheritance:
+   :imported-members:
+
+
 Tutorial helpers
 ----------------
 

{xarray_binfile-0.1.0b1 → xarray_binfile-0.2.0}/docs/tutorials/benchmarking.ipynb

@@ -41,7 +41,8 @@
     "import xarray as xr\n",
     "\n",
     "import xarray_binfile  # noqa: F401  (registers the .binary_engine accessors)\n",
-    "from xarray_binfile.tutorial import DatasetGenerator, FileSpecsGetter\n",
+    "from xarray_binfile.conventions import Layout, StepIndexedFiles\n",
+    "from xarray_binfile.tutorial import DatasetGenerator\n",
     "\n",
     "workdir_holder = tempfile.TemporaryDirectory()\n",
     "workdir = pathlib.Path(workdir_holder.name)\n",
@@ -98,10 +99,10 @@
     "        axis: np.linspace(0.0, 1.0, num=num_points, dtype=np.float32)\n",
     "        for axis in (\"x\", \"y\", \"z\")\n",
     "    }\n",
-    "    getter = FileSpecsGetter(base_coords=coords, dtype=dtype)\n",
+    "    getter = StepIndexedFiles(Layout(coords, dtype=dtype))\n",
     "    generator = DatasetGenerator(getter.reader)\n",
     "    filenames = (\n",
-    "        getter.filename_template.format(name=name, digits=step)\n",
+    "        getter.pattern.format(name=name, step=step)\n",
     "        for name in variables\n",
     "        for step in range(num_steps)\n",
     "    )\n",

{xarray_binfile-0.1.0b1 → xarray_binfile-0.2.0}/docs/tutorials/examples.ipynb

@@ -23,8 +23,8 @@
    "metadata": {},
    "source": [
     "```{note}\n",
-    "These recipes reuse the shipped `FileSpecsGetter` convention\n",
-    "(`{name}-{digits:04}.bin`). For a different on-disk layout, provide your own\n",
+    "These recipes reuse the shipped `StepIndexedFiles` convention\n",
+    "(`{name}-{step:04d}.bin`). For a different on-disk layout, provide your own\n",
     "read/write getters as shown in\n",
     "[Spec getter protocols](../usage/spec-getter-protocols.md).\n",
     "```"
@@ -46,7 +46,8 @@
     "import xarray as xr\n",
     "\n",
     "import xarray_binfile  # noqa: F401  (registers the .binary_engine accessors)\n",
-    "from xarray_binfile.tutorial import DatasetGenerator, FileSpecsGetter\n",
+    "from xarray_binfile.conventions import Layout, StepIndexedFiles\n",
+    "from xarray_binfile.tutorial import DatasetGenerator\n",
     "\n",
     "source_directory_holder = tempfile.TemporaryDirectory()\n",
     "float32_directory_holder = tempfile.TemporaryDirectory()\n",
@@ -80,10 +81,10 @@
     "    \"z\": np.linspace(0.0, 2.0, num=8, dtype=np.float32),\n",
     "}\n",
     "\n",
-    "reader_float64 = FileSpecsGetter(base_coords=base_coords, dtype=np.float64)\n",
+    "reader_float64 = StepIndexedFiles(Layout(base_coords, dtype=np.float64))\n",
     "dataset_generator = DatasetGenerator(reader_float64.reader)\n",
     "filenames = (\n",
-    "    reader_float64.filename_template.format(name=name, digits=step)\n",
+    "    reader_float64.pattern.format(name=name, step=step)\n",
     "    for name in (\"ux\", \"uy\", \"uz\")\n",
     "    for step in range(6)\n",
     ")\n",
@@ -109,7 +110,7 @@
    "metadata": {},
    "outputs": [],
    "source": [
-    "reader_float32 = FileSpecsGetter(base_coords=base_coords, dtype=np.float32)\n",
+    "reader_float32 = StepIndexedFiles(Layout(base_coords, dtype=np.float32))\n",
     "\n",
     "for path in sorted(source_directory.glob(\"*.bin\")):\n",
     "    single = xr.open_dataset(\n",

{xarray_binfile-0.1.0b1 → xarray_binfile-0.2.0}/docs/tutorials/parallel-and-larger-than-memory.ipynb

@@ -44,7 +44,8 @@
     "import xarray as xr\n",
     "\n",
     "import xarray_binfile  # noqa: F401  (registers the .binary_engine accessors)\n",
-    "from xarray_binfile.tutorial import DatasetGenerator, FileSpecsGetter\n",
+    "from xarray_binfile.conventions import Layout, StepIndexedFiles\n",
+    "from xarray_binfile.tutorial import DatasetGenerator\n",
     "\n",
     "source_directory_holder = tempfile.TemporaryDirectory()\n",
     "derived_directory_holder = tempfile.TemporaryDirectory()\n",
@@ -76,10 +77,10 @@
     "    \"z\": np.linspace(0.0, 2.0, num=16, dtype=np.float32),\n",
     "}\n",
     "\n",
-    "getter = FileSpecsGetter(base_coords=base_coords, dtype=np.float32)\n",
+    "getter = StepIndexedFiles(Layout(base_coords, dtype=np.float32))\n",
     "dataset_generator = DatasetGenerator(getter.reader)\n",
     "filenames = (\n",
-    "    getter.filename_template.format(name=name, digits=step)\n",
+    "    getter.pattern.format(name=name, step=step)\n",
     "    for name in (\"ux\", \"uy\", \"uz\")\n",
     "    for step in range(12)\n",
     ")\n",

{xarray_binfile-0.1.0b1 → xarray_binfile-0.2.0}/docs/tutorials/read.ipynb

@@ -9,7 +9,7 @@
     "\n",
     "This notebook shows the main xarray-binfile workflow:\n",
     "\n",
-    "- describe a binary-file convention with `FileSpecsGetter`\n",
+    "- describe a binary-file convention with `StepIndexedFiles`\n",
     "- open individual files or a whole collection with `engine=\"binfile\"`\n",
     "- keep the resulting arrays lazy and Dask-backed\n",
     "- inspect the task graph before executing a calculation\n",
@@ -24,7 +24,6 @@
    "outputs": [],
    "source": [
     "import pathlib\n",
-    "import re\n",
     "import tempfile\n",
     "from shutil import which\n",
     "\n",
@@ -33,7 +32,8 @@
     "from IPython.display import Markdown, display\n",
     "\n",
     "import xarray_binfile  # noqa: F401  (registers the .binary_engine accessors)\n",
-    "from xarray_binfile.tutorial import DatasetGenerator, FileSpecsGetter\n",
+    "from xarray_binfile.conventions import Layout, StepIndexedFiles\n",
+    "from xarray_binfile.tutorial import DatasetGenerator\n",
     "\n",
     "temporary_directory = tempfile.TemporaryDirectory()\n",
     "data_directory = pathlib.Path(temporary_directory.name)\n",
@@ -53,16 +53,14 @@
     "    \"z\": np.linspace(0.0, 2.0, num=8, dtype=np.float32),\n",
     "}\n",
     "\n",
-    "file_specs_getter = FileSpecsGetter(\n",
-    "    base_coords=base_coords,\n",
-    "    dtype=np.float32,\n",
-    "    filename_template=\"{name}-{digits:04}.bin\",\n",
-    "    filename_regex=re.compile(r\"(?P<name>\\w+)-(?P<digits>\\d{4})\\.bin\"),\n",
+    "file_specs_getter = StepIndexedFiles(\n",
+    "    layout=Layout(base_coords, dtype=np.float32),\n",
+    "    pattern=\"{name}-{step:04d}.bin\",\n",
     ")\n",
     "\n",
     "dataset_generator = DatasetGenerator(file_specs_getter.reader)\n",
     "filenames = (\n",
-    "    file_specs_getter.filename_template.format(name=name, digits=step)\n",
+    "    file_specs_getter.pattern.format(name=name, step=step)\n",
     "    for name in (\"ux\", \"uy\", \"uz\")\n",
     "    for step in range(2)\n",
     ")\n",
@@ -89,7 +87,7 @@
    "outputs": [],
    "source": [
     "single_dataset = xr.open_dataset(\n",
-    "    sorted(data_directory.glob(\"ux-*.bin\"))[0],\n",
+    "    min(data_directory.glob(\"ux-*.bin\")),\n",
     "    engine=\"binfile\",\n",
     "    read_specs_getter=file_specs_getter.reader,\n",
     ")\n",

{xarray_binfile-0.1.0b1 → xarray_binfile-0.2.0}/docs/tutorials/write.ipynb

@@ -34,15 +34,13 @@
    "outputs": [],
    "source": [
     "import pathlib\n",
-    "import re\n",
     "import tempfile\n",
-    "from dataclasses import dataclass\n",
     "\n",
     "import numpy as np\n",
     "import xarray as xr\n",
     "\n",
-    "from xarray_binfile import WriteSpecs\n",
-    "from xarray_binfile.tutorial import DatasetGenerator, FileSpecsGetter\n",
+    "from xarray_binfile.conventions import Layout, StepIndexedFiles\n",
+    "from xarray_binfile.tutorial import DatasetGenerator\n",
     "\n",
     "input_directory_holder = tempfile.TemporaryDirectory()\n",
     "output_directory_holder = tempfile.TemporaryDirectory()\n",
@@ -64,16 +62,14 @@
     "    \"z\": np.linspace(0.0, 1.5, num=12, dtype=np.float32),\n",
     "}\n",
     "\n",
-    "input_specs_getter = FileSpecsGetter(\n",
-    "    base_coords=base_coords,\n",
-    "    dtype=np.float32,\n",
-    "    filename_template=\"{name}-{digits:04}.bin\",\n",
-    "    filename_regex=re.compile(r\"(?P<name>\\w+)-(?P<digits>\\d{4})\\.bin\"),\n",
+    "input_specs_getter = StepIndexedFiles(\n",
+    "    layout=Layout(base_coords, dtype=np.float32),\n",
+    "    pattern=\"{name}-{step:04d}.bin\",\n",
     ")\n",
     "\n",
     "dataset_generator = DatasetGenerator(input_specs_getter.reader)\n",
     "filenames = (\n",
-    "    input_specs_getter.filename_template.format(name=name, digits=step)\n",
+    "    input_specs_getter.pattern.format(name=name, step=step)\n",
     "    for name in (\"ux\", \"uy\", \"uz\")\n",
     "    for step in range(8)\n",
     ")\n",
@@ -138,9 +134,9 @@
    "source": [
     "## Custom write specifications\n",
     "\n",
-    "`FileSpecsGetter.writer` is useful when your output convention matches the tutorial helper. If you need a different layout, implement a callable compatible with `WriteSpecsGetterProtocol`.\n",
+    "The derived array has the same layout as the inputs; only the filename differs. Declaring a second `StepIndexedFiles` with another `pattern` is enough, and because the regex used for reading is derived from that same pattern, the files can be read back without repeating the convention. When the shipped conventions do not fit, implement a callable compatible with `WriteSpecsGetterProtocol` as described in [Spec getter protocols](../usage/spec-getter-protocols.md).\n",
     "\n",
-    "Setting `dtype` on each `WriteSpecs` pins the on-disk data type (including byte order): the values are cast right before serialization, so the files always match what the corresponding read getter declares. When `dtype` is omitted, the in-memory dtype and native byte order are written as-is."
+    "The `dtype` of the `Layout` pins the on-disk data type (including byte order): the values are cast right before serialization, so the files always match what the corresponding reader declares.\n"
    ]
   },
   {
@@ -150,26 +146,11 @@
    "metadata": {},
    "outputs": [],
    "source": [
-    "@dataclass(frozen=True)\n",
-    "class DerivedWriteSpecsGetter:\n",
-    "    prefix: str = \"derived\"\n",
-    "    base_dims: tuple[str, ...] = (\"x\", \"y\", \"z\")\n",
-    "    dtype: np.dtype = np.float32\n",
-    "\n",
-    "    def __call__(self, data_array: xr.DataArray):\n",
-    "        for time_value in data_array.coords[\"time\"].values:\n",
-    "            timestep = int(time_value)\n",
-    "            yield WriteSpecs(\n",
-    "                filename=f\"{self.prefix}-{data_array.name}-{timestep:04}.bin\",\n",
-    "                sub_array=data_array.sel(time=timestep).transpose(\n",
-    "                    *self.base_dims, missing_dims=\"raise\"\n",
-    "                ),\n",
-    "                dtype=self.dtype,\n",
-    "            )\n",
-    "\n",
-    "\n",
-    "derived_write_specs_getter = DerivedWriteSpecsGetter()\n",
-    "derived_write_specs_getter"
+    "output_specs_getter = StepIndexedFiles(\n",
+    "    layout=Layout(base_coords, dtype=np.float32),\n",
+    "    pattern=\"derived-{name}-{step:04d}.bin\",\n",
+    ")\n",
+    "output_specs_getter"
    ]
   },
   {
@@ -179,7 +160,7 @@
    "metadata": {},
    "outputs": [],
    "source": [
-    "speed.binary_engine.to_file(derived_write_specs_getter, output_directory)\n",
+    "speed.binary_engine.to_file(output_specs_getter.writer, output_directory)\n",
     "sorted(path.name for path in output_directory.glob(\"*.bin\"))[:6]"
    ]
   },
@@ -191,7 +172,7 @@
     "Writing triggers the actual per-file materialization of each selected slice. That is often exactly what you want when handing data back to an external solver or post-processing pipeline.\n",
     "\n",
     "```{warning}\n",
-    "`.binary_engine.to_file(...)` never writes a file partially. Each `sub_array` is fully loaded into memory (a Dask compute for lazy data) and the whole file is written in a single pass — there is no appending, patching, or resuming. Each file is also written atomically: the bytes go to a unique temporary directory inside the destination and are moved into place with `os.replace` only when complete, so an interrupted write never leaves a truncated file behind. This keeps the on-disk files consistent instead of risking partially-updated, corrupted content, but it means every individual output file must fit in memory. Plan your chunks and the number of output files accordingly, for example one file per time step. If you need streaming or partial writes, use one of the other xarray-supported formats such as NetCDF or Zarr.\n",
+    "`.binary_engine.to_file(...)` never writes a file partially. Each `sub_array` is fully loaded into memory (a Dask compute for lazy data) and the whole file is written in a single pass — there is no appending, patching, or resuming. Each file is also written atomically: the bytes go to a temporary file next to the destination and are moved into place with `os.replace` only when complete, so an interrupted write never leaves a truncated file behind. This keeps the on-disk files consistent instead of risking partially-updated, corrupted content, but it means every individual output file must fit in memory. Plan your chunks and the number of output files accordingly, for example one file per time step. If you need streaming or partial writes, use one of the other xarray-supported formats such as NetCDF or Zarr.\n",
     "```"
    ]
   },
@@ -202,13 +183,6 @@
    "metadata": {},
    "outputs": [],
    "source": [
-    "output_specs_getter = FileSpecsGetter(\n",
-    "    base_coords=base_coords,\n",
-    "    dtype=np.float32,\n",
-    "    filename_template=\"derived-{name}-{digits:04}.bin\",\n",
-    "    filename_regex=re.compile(r\"derived-(?P<name>\\w+)-(?P<digits>\\d{4})\\.bin\"),\n",
-    ")\n",
-    "\n",
     "roundtrip_dataset = xr.open_mfdataset(\n",
     "    sorted(output_directory.glob(\"derived-*.bin\")),\n",
     "    engine=\"binfile\",\n",