vine-reduce 2026.8.1__tar.gz

vine_reduce-2026.8.1/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the
+      purposes of this License, Derivative Works shall not include works
+      that remain separable from, or merely link (or bind by name) to the
+      interfaces of, the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 Ben Tovar
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

vine_reduce-2026.8.1/PKG-INFO

@@ -0,0 +1,226 @@
+Metadata-Version: 2.4
+Name: vine-reduce
+Version: 2026.8.1
+Summary: Dynamic MapReduce framework for data processing
+Author-email: Ben Tovar <btovar@nd.edu>
+Maintainer-email: Ben Tovar <btovar@nd.edu>
+License-Expression: Apache-2.0
+Project-URL: Homepage, https://github.com/cooperative-computing-lab/vine-reduce
+Project-URL: Repository, https://github.com/cooperative-computing-lab/vine-reduce.git
+Project-URL: Documentation, https://github.com/cooperative-computing-lab/vine-reduce#readme
+Project-URL: Bug Tracker, https://github.com/cooperative-computing-lab/vine-reduce/issues
+Keywords: dynamic-data-reduction,mapreduce,data-processing,distributed-computing
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Developers
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.13
+Requires-Python: >=3.13
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: awkward>=2.8.7
+Requires-Dist: coffea>=2025.7.3
+Requires-Dist: fsspec>=2026.7.0
+Requires-Dist: fsspec-xrootd>=0.5.1
+Requires-Dist: numpy>=2.4.6
+Requires-Dist: rich>=14.2.0
+Requires-Dist: uproot>=5.6.6
+Requires-Dist: xrootd>=5.8.4
+Requires-Dist: zstandard>=0.25.0
+Provides-Extra: dev
+Requires-Dist: pytest>=6.0; extra == "dev"
+Requires-Dist: pytest-cov>=2.0; extra == "dev"
+Requires-Dist: black>=21.0; extra == "dev"
+Requires-Dist: flake8>=3.8; extra == "dev"
+Provides-Extra: conda
+Requires-Dist: ndcctools>=7.17.1; extra == "conda"
+Dynamic: license-file
+
+# VineReduce
+
+A dynamic MapReduce framework for data processing, built on top of
+[TaskVine](https://cctools.readthedocs.io/en/latest/taskvine/).
+
+For each `(processor, dataset)` pair, `VineReduce` splits every file in the
+dataset into chunks, runs your processor over each chunk remotely (the "map"
+step), then repeatedly folds pooled processor outputs together with a
+reducer (the "reduce" step) until one final result covers the whole
+dataset. Progress is checkpointed along the way, so an interrupted run can
+resume without redoing finished work. See [PLAN.md](PLAN.md) for the full
+design.
+
+## Installation
+
+This project requires Python 3.13+ and is managed with
+[pixi](https://pixi.sh/).
+
+```bash
+# Clone the repository
+git clone https://github.com/cooperative-computing-lab/vine-reduce.git
+cd vine-reduce
+
+# Install the default environment (runtime dependencies only)
+pixi install
+
+# Or install the dev environment (adds pytest, black, flake8, pyright)
+pixi install -e dev
+```
+
+All commands should be run through pixi so they pick up the managed
+environment, e.g. `pixi run python your_script.py`.
+
+## Quick Start
+
+`examples/quick_start/quick_start.py` is a self-contained, runnable example:
+it generates some toy binary data, starts a `TaskVineDistributor` with a
+single local worker (no cluster or separate `vine_worker` process needed),
+runs three processors over two datasets, and checks the results for
+consistency.
+
+```bash
+cd examples/quick_start
+pixi run python quick_start.py
+```
+
+Reading through that file top-to-bottom (it's heavily commented) is the
+fastest way to see how the pieces fit together: `build_datasets` describes
+the input shape `VineReduce` expects, `numbers_chunk_to_args` turns a
+`Chunk` into processor arguments, and `main()` wires a `TaskVineDistributor`
+and `VineReduce` together and calls `compute()`.
+
+The shape of a minimal call looks like this:
+
+```python
+from vine_reduce import VineReduce
+
+vr = VineReduce(
+    processors={"my_processor": my_processor_fn},
+    input=datasets,  # {name: {"metadata": {...}, "files": {path: num_entries}}}
+    chunk_to_args=my_chunk_to_args,
+    chunksize=10_000,
+    results_dir="results",
+    # distributor defaults to a local ProcessPoolExecutor-backed
+    # LocalDistributor if omitted; pass a TaskVineDistributor to run on a
+    # real TaskVine cluster instead. Non-final checkpoints are the
+    # distributor's own concern (e.g. TaskVineDistributor(checkpoint_dir=...)),
+    # not VineReduce's.
+)
+vr.compute()
+```
+
+## Executors
+
+`chunk_to_args`'s output for a chunk becomes the argument each processor
+call runs remotely on. The `executor` argument to `VineReduce` controls how
+that call actually runs, at the execution site:
+
+- `simple_executor` (default) — calls `processor(args)` directly.
+- `cloudpickle_executor` — runs `processor(args)` in its own subprocess, so a
+  crash or memory leak in `processor` doesn't take down the worker task
+  itself. Supports closures and lambdas as `processor`, unlike the stdlib
+  `pickle` a plain `ProcessPoolExecutor` would require.
+- `dask_executor` — for a `processor` that returns a dask-delayed object (or
+  dask array/dataframe) rather than a plain value; computes it at the
+  execution site using one subprocess per core allocated to the task. `dask`
+  is not a `vine_reduce` dependency and must already be installed wherever
+  this executor runs.
+
+All three live in `src/vine_reduce/executor.py`.
+
+## Packaging an environment for remote workers
+
+`TaskVineDistributor` accepts an `environment=` argument — a path to a
+packed, relocatable [poncho package](https://cctools.readthedocs.io/en/stable/poncho)
+tarball — which it ships to every worker alongside each task, so worker
+nodes need nothing beyond TaskVine itself pre-installed.
+
+`vine_reduce.get_environment()` (`src/vine_reduce/remote_environment.py`)
+builds that tarball for you, via `poncho_package_create`:
+
+```python
+from vine_reduce import TaskVineDistributor, get_environment
+
+environment = get_environment()
+distributor = TaskVineDistributor(
+    port=0,
+    resources_processor={"cores": 1},
+    environment=environment,
+)
+```
+
+`get_environment()` packs whatever is currently installed in the calling
+conda environment (`$CONDA_PREFIX` by default, or pass `conda_env_path=`) -
+nothing more. Install whatever your workers need (conda install, pip
+install, a pixi dependency, ...) into that environment before calling it.
+Builds are cached on disk (keyed by a hash of the environment's installed
+packages) and reused across runs. Editable pip installs can't be packed
+as-is, so any package currently installed editable (`vine_reduce` itself,
+typically) is temporarily reinstalled non-editable for the pack step and
+reinstalled editable again immediately afterwards. If `vine_reduce` - or
+another package named via `pip_editable` - has uncommitted changes in its
+checkout, the next call rebuilds automatically rather than risk shipping
+stale code (pass `unstaged="fail"` to raise `UnstagedChanges` instead):
+
+```python
+environment = get_environment(
+    pip_editable={"my-analysis-repo": ["src", "pyproject.toml"]},
+)
+```
+
+`get_environment` is not TaskVine-specific: it just resolves a tarball
+path, so it works the same way regardless of which `Distributor`
+ultimately uses that path. Building requires `poncho_package_create` and
+`conda` on `PATH` - see the `conda` extra in `pyproject.toml`.
+
+## HEP / coffea workflows
+
+`vine_reduce.VineReduceCoffea` is a specialization for
+[coffea](https://coffeateam.github.io/coffea/)-based analyses: it supplies
+NanoEvents-reading, awkward-array materialization, and coffea-style
+accumulator merging, while chunking, checkpointing, and restart are
+inherited unchanged from `VineReduce`. See `src/vine_reduce/coffea.py`.
+
+`examples/cortado/vr_cortado.py` is a runnable example built on it,
+adapted from the ["cortado"
+example](https://github.com/cooperative-computing-lab/dynamic_data_reduction/tree/main/examples/cortado)
+in `dynamic_data_reduction`, the project this one's dynamic map-reduce loop
+descends from: it generates synthetic NanoAOD-like ROOT files for two
+datasets, skims each down to events with at least four leptons, and merges
+the surviving events per dataset with a custom awkward-array-concatenating
+reducer.
+
+```bash
+cd examples/cortado
+pixi run python vr_cortado.py
+```
+
+## Production use: ttbarEFT
+
+[`TopEFT/ttbarEFT`](https://github.com/TopEFT/ttbarEFT) is a CMS
+top-quark EFT search that runs its analysis stage through `vine_reduce`
+on top of TaskVine, distributing histogram-filling processors over an
+HTCondor pool.
+[`examples/ttBar/run_processor_with_vr.py`](examples/ttBar/run_processor_with_vr.py)
+shows how that integration looked in practice: driving a `ttbarEFT`
+`AnalysisProcessor` per lepton channel through `vine_reduce`. It predates
+the current `VineReduceCoffea`/`TaskVineDistributor` API described above
+(it was written against an earlier `vine_reduce` release), so treat it as
+a reference for how a full physics analysis wires up channels,
+Wilson-coefficient/histogram selection, and X509 proxy handling around
+`vine_reduce`, not as a runnable script against the current API.
+
+## Development
+
+```bash
+pixi run -e dev pytest tests/ -v   # run tests
+pixi run -e dev black .            # format
+pixi run -e dev flake8             # lint
+```
+
+CI (GitHub Actions and a mirrored GitLab CI pipeline) runs all three on
+every push and pull request.
+
+## License
+
+This project is licensed under the Apache License 2.0 - see the
+[LICENSE](LICENSE) file for details.

vine_reduce-2026.8.1/README.md

@@ -0,0 +1,188 @@
+# VineReduce
+
+A dynamic MapReduce framework for data processing, built on top of
+[TaskVine](https://cctools.readthedocs.io/en/latest/taskvine/).
+
+For each `(processor, dataset)` pair, `VineReduce` splits every file in the
+dataset into chunks, runs your processor over each chunk remotely (the "map"
+step), then repeatedly folds pooled processor outputs together with a
+reducer (the "reduce" step) until one final result covers the whole
+dataset. Progress is checkpointed along the way, so an interrupted run can
+resume without redoing finished work. See [PLAN.md](PLAN.md) for the full
+design.
+
+## Installation
+
+This project requires Python 3.13+ and is managed with
+[pixi](https://pixi.sh/).
+
+```bash
+# Clone the repository
+git clone https://github.com/cooperative-computing-lab/vine-reduce.git
+cd vine-reduce
+
+# Install the default environment (runtime dependencies only)
+pixi install
+
+# Or install the dev environment (adds pytest, black, flake8, pyright)
+pixi install -e dev
+```
+
+All commands should be run through pixi so they pick up the managed
+environment, e.g. `pixi run python your_script.py`.
+
+## Quick Start
+
+`examples/quick_start/quick_start.py` is a self-contained, runnable example:
+it generates some toy binary data, starts a `TaskVineDistributor` with a
+single local worker (no cluster or separate `vine_worker` process needed),
+runs three processors over two datasets, and checks the results for
+consistency.
+
+```bash
+cd examples/quick_start
+pixi run python quick_start.py
+```
+
+Reading through that file top-to-bottom (it's heavily commented) is the
+fastest way to see how the pieces fit together: `build_datasets` describes
+the input shape `VineReduce` expects, `numbers_chunk_to_args` turns a
+`Chunk` into processor arguments, and `main()` wires a `TaskVineDistributor`
+and `VineReduce` together and calls `compute()`.
+
+The shape of a minimal call looks like this:
+
+```python
+from vine_reduce import VineReduce
+
+vr = VineReduce(
+    processors={"my_processor": my_processor_fn},
+    input=datasets,  # {name: {"metadata": {...}, "files": {path: num_entries}}}
+    chunk_to_args=my_chunk_to_args,
+    chunksize=10_000,
+    results_dir="results",
+    # distributor defaults to a local ProcessPoolExecutor-backed
+    # LocalDistributor if omitted; pass a TaskVineDistributor to run on a
+    # real TaskVine cluster instead. Non-final checkpoints are the
+    # distributor's own concern (e.g. TaskVineDistributor(checkpoint_dir=...)),
+    # not VineReduce's.
+)
+vr.compute()
+```
+
+## Executors
+
+`chunk_to_args`'s output for a chunk becomes the argument each processor
+call runs remotely on. The `executor` argument to `VineReduce` controls how
+that call actually runs, at the execution site:
+
+- `simple_executor` (default) — calls `processor(args)` directly.
+- `cloudpickle_executor` — runs `processor(args)` in its own subprocess, so a
+  crash or memory leak in `processor` doesn't take down the worker task
+  itself. Supports closures and lambdas as `processor`, unlike the stdlib
+  `pickle` a plain `ProcessPoolExecutor` would require.
+- `dask_executor` — for a `processor` that returns a dask-delayed object (or
+  dask array/dataframe) rather than a plain value; computes it at the
+  execution site using one subprocess per core allocated to the task. `dask`
+  is not a `vine_reduce` dependency and must already be installed wherever
+  this executor runs.
+
+All three live in `src/vine_reduce/executor.py`.
+
+## Packaging an environment for remote workers
+
+`TaskVineDistributor` accepts an `environment=` argument — a path to a
+packed, relocatable [poncho package](https://cctools.readthedocs.io/en/stable/poncho)
+tarball — which it ships to every worker alongside each task, so worker
+nodes need nothing beyond TaskVine itself pre-installed.
+
+`vine_reduce.get_environment()` (`src/vine_reduce/remote_environment.py`)
+builds that tarball for you, via `poncho_package_create`:
+
+```python
+from vine_reduce import TaskVineDistributor, get_environment
+
+environment = get_environment()
+distributor = TaskVineDistributor(
+    port=0,
+    resources_processor={"cores": 1},
+    environment=environment,
+)
+```
+
+`get_environment()` packs whatever is currently installed in the calling
+conda environment (`$CONDA_PREFIX` by default, or pass `conda_env_path=`) -
+nothing more. Install whatever your workers need (conda install, pip
+install, a pixi dependency, ...) into that environment before calling it.
+Builds are cached on disk (keyed by a hash of the environment's installed
+packages) and reused across runs. Editable pip installs can't be packed
+as-is, so any package currently installed editable (`vine_reduce` itself,
+typically) is temporarily reinstalled non-editable for the pack step and
+reinstalled editable again immediately afterwards. If `vine_reduce` - or
+another package named via `pip_editable` - has uncommitted changes in its
+checkout, the next call rebuilds automatically rather than risk shipping
+stale code (pass `unstaged="fail"` to raise `UnstagedChanges` instead):
+
+```python
+environment = get_environment(
+    pip_editable={"my-analysis-repo": ["src", "pyproject.toml"]},
+)
+```
+
+`get_environment` is not TaskVine-specific: it just resolves a tarball
+path, so it works the same way regardless of which `Distributor`
+ultimately uses that path. Building requires `poncho_package_create` and
+`conda` on `PATH` - see the `conda` extra in `pyproject.toml`.
+
+## HEP / coffea workflows
+
+`vine_reduce.VineReduceCoffea` is a specialization for
+[coffea](https://coffeateam.github.io/coffea/)-based analyses: it supplies
+NanoEvents-reading, awkward-array materialization, and coffea-style
+accumulator merging, while chunking, checkpointing, and restart are
+inherited unchanged from `VineReduce`. See `src/vine_reduce/coffea.py`.
+
+`examples/cortado/vr_cortado.py` is a runnable example built on it,
+adapted from the ["cortado"
+example](https://github.com/cooperative-computing-lab/dynamic_data_reduction/tree/main/examples/cortado)
+in `dynamic_data_reduction`, the project this one's dynamic map-reduce loop
+descends from: it generates synthetic NanoAOD-like ROOT files for two
+datasets, skims each down to events with at least four leptons, and merges
+the surviving events per dataset with a custom awkward-array-concatenating
+reducer.
+
+```bash
+cd examples/cortado
+pixi run python vr_cortado.py
+```
+
+## Production use: ttbarEFT
+
+[`TopEFT/ttbarEFT`](https://github.com/TopEFT/ttbarEFT) is a CMS
+top-quark EFT search that runs its analysis stage through `vine_reduce`
+on top of TaskVine, distributing histogram-filling processors over an
+HTCondor pool.
+[`examples/ttBar/run_processor_with_vr.py`](examples/ttBar/run_processor_with_vr.py)
+shows how that integration looked in practice: driving a `ttbarEFT`
+`AnalysisProcessor` per lepton channel through `vine_reduce`. It predates
+the current `VineReduceCoffea`/`TaskVineDistributor` API described above
+(it was written against an earlier `vine_reduce` release), so treat it as
+a reference for how a full physics analysis wires up channels,
+Wilson-coefficient/histogram selection, and X509 proxy handling around
+`vine_reduce`, not as a runnable script against the current API.
+
+## Development
+
+```bash
+pixi run -e dev pytest tests/ -v   # run tests
+pixi run -e dev black .            # format
+pixi run -e dev flake8             # lint
+```
+
+CI (GitHub Actions and a mirrored GitLab CI pipeline) runs all three on
+every push and pull request.
+
+## License
+
+This project is licensed under the Apache License 2.0 - see the
+[LICENSE](LICENSE) file for details.