trnsci 0.1.0__tar.gz

trnsci-0.1.0/.github/workflows/docs.yml

@@ -0,0 +1,54 @@
+name: Deploy docs
+
+on:
+  push:
+    branches: [main]
+  workflow_dispatch:
+  # Rebuild daily to pick up sub-project changes.
+  schedule:
+    - cron: "0 6 * * *"
+  # External trigger so sub-project CIs can kick off an umbrella rebuild.
+  repository_dispatch:
+    types: [subproject-updated]
+
+permissions:
+  contents: write
+
+jobs:
+  deploy:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v6
+        with:
+          fetch-depth: 0
+
+      - uses: actions/setup-python@v6
+        with:
+          python-version: "3.11"
+
+      - name: Clone sub-projects
+        run: |
+          set -euo pipefail
+          # Each sub-project's own mkdocs.yml is composed into the umbrella site
+          # via mkdocs-monorepo-plugin. The trnsolver repo lives at the
+          # "trnsolve" directory name inside the umbrella layout.
+          declare -A REPOS=(
+            [trnfft]=trnfft
+            [trnblas]=trnblas
+            [trnrand]=trnrand
+            [trnsolve]=trnsolver
+            [trnsparse]=trnsparse
+            [trntensor]=trntensor
+          )
+          for dir in "${!REPOS[@]}"; do
+            repo="${REPOS[$dir]}"
+            git clone --depth 1 "https://github.com/trnsci/${repo}.git" "$dir"
+          done
+
+      - name: Install docs dependencies
+        run: |
+          pip install --upgrade pip
+          pip install mkdocs-material mkdocs-monorepo-plugin
+
+      - name: Build and deploy to gh-pages
+        run: mkdocs gh-deploy --force --clean

trnsci-0.1.0/.github/workflows/publish.yml

@@ -0,0 +1,56 @@
+name: Publish to PyPI
+
+on:
+  release:
+    types: [published]
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v6
+      - uses: actions/setup-python@v6
+        with:
+          python-version: "3.12"
+      - run: pip install build
+      - run: python -m build
+      - uses: actions/upload-artifact@v4
+        with:
+          name: dist
+          path: dist/
+
+  publish-pypi:
+    needs: build
+    runs-on: ubuntu-latest
+    # Only publish stable releases (v1.2.3), not pre-releases (v1.2.3-rc1)
+    if: ${{ !contains(github.event.release.tag_name, '-') }}
+    environment:
+      name: pypi
+      url: https://pypi.org/project/trnsci/
+    permissions:
+      id-token: write
+    steps:
+      - uses: actions/download-artifact@v4
+        with:
+          name: dist
+          path: dist/
+      - uses: pypa/gh-action-pypi-publish@release/v1
+
+  publish-testpypi:
+    needs: build
+    runs-on: ubuntu-latest
+    # Only publish pre-releases to TestPyPI
+    if: ${{ contains(github.event.release.tag_name, '-') }}
+    environment:
+      name: testpypi
+      url: https://test.pypi.org/project/trnsci/
+    permissions:
+      id-token: write
+    steps:
+      - uses: actions/download-artifact@v4
+        with:
+          name: dist
+          path: dist/
+      - uses: pypa/gh-action-pypi-publish@release/v1
+        with:
+          repository-url: https://test.pypi.org/legacy/

trnsci-0.1.0/.github/workflows/test.yml

@@ -0,0 +1,45 @@
+name: CI
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+
+# The sub-project libraries each have their own CI. The umbrella repo's
+# CI only verifies that the cross-library integration test works when
+# all six libraries are installed from their current upstream locations.
+#
+# Sub-project repos currently live under scttfrdmn/. After transfer to
+# the trnsci/ org, update the git URLs below.
+
+env:
+  SUBPROJECT_OWNER: scttfrdmn
+
+jobs:
+  integration:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v6
+      - uses: actions/setup-python@v6
+        with:
+          python-version: "3.11"
+
+      - name: Install sub-projects from git
+        run: |
+          set -euo pipefail
+          for pkg in trnfft trnblas trnrand trnsolver trnsparse trntensor; do
+            echo "==> $pkg"
+            if ! pip install "git+https://github.com/${SUBPROJECT_OWNER}/${pkg}.git#egg=${pkg}[dev]" ; then
+              echo "    skipping $pkg — repo not found under ${SUBPROJECT_OWNER}/ yet"
+            fi
+          done
+
+      - name: Install umbrella
+        run: pip install -e ".[dev]"
+
+      - name: Run integration tests
+        run: pytest tests/ -v -x --tb=short -m "not neuron"
+
+      - name: Run DF-MP2 demo
+        run: python examples/quantum_chemistry/df_mp2_synthetic.py --demo
+        continue-on-error: true

trnsci-0.1.0/.gitignore

@@ -0,0 +1,33 @@
+__pycache__/
+*.py[cod]
+*$py.class
+*.egg-info/
+dist/
+build/
+.eggs/
+*.egg
+.pytest_cache/
+.tox/
+.venv/
+venv/
+*.so
+.idea/
+.vscode/
+*.swp
+*.swo
+*~
+site/
+.benchmarks/
+.terraform/
+*.tfstate
+*.tfstate.backup
+.terraform.lock.hcl
+
+# Sub-projects live here as sibling directories but each has its own .git
+# and its own repo under github.com/trnsci/. The umbrella does not vendor them.
+/trnfft/
+/trnblas/
+/trnrand/
+/trnsolve/
+/trnsparse/
+/trntensor/

trnsci-0.1.0/CHANGELOG.md

@@ -0,0 +1,54 @@
+# Changelog
+
+All notable changes to the trnsci umbrella package.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [0.1.0] — 2026-04-13
+
+Initial umbrella release.
+
+### Added
+
+- **Meta-package** that coordinates installation of the six trnsci sub-projects:
+  `trnfft`, `trnblas`, `trnrand`, `trnsolver`, `trnsparse`, `trntensor`.
+- **Optional extras**: `[fft]`, `[blas]`, `[rand]`, `[solver]`, `[sparse]`,
+  `[tensor]`, `[all]`, `[neuron]`, `[dev]`. `pip install trnsci[all]` pulls
+  in every sub-project.
+- **Cross-project DF-MP2 integration example** at
+  `examples/quantum_chemistry/df_mp2_synthetic.py`, composing `trnrand` +
+  `trnsparse` + `trnsolver` + `trnblas` + `trntensor` in one pipeline.
+- **NVIDIA CUDA sample ports** under `examples/nvidia_samples/`: direct ports
+  of `cuFFT/2d_r2c_c2r`, `cuda-samples/batchCUBLAS`, `MC_EstimatePi{P,Q}`,
+  `cuSOLVER/syevd`, `cuda-samples/conjugateGradient`, and
+  `cuTENSOR/contraction` against trnsci APIs, each citing the upstream
+  sample by URL.
+- **Speech-enhancement workflow** at `examples/speech_enhancement/demo.py` —
+  synthetic cIRM pipeline exercising trnfft's STFT, ComplexTensor, and
+  complex NN layers.
+- **Unified documentation site** at https://trnsci.dev/ — landing,
+  `why.md` essay, `cuda_rosetta.md` (CUDA → trnsci mapping table with
+  per-library deep dives), `trainium_positioning.md` (placing Trainium
+  between NVIDIA SMs and Google TPUs), and workflow pages for speech
+  enhancement and quantum chemistry. Sub-project docs are composed under
+  `trnsci.dev/<name>/` via `mkdocs-monorepo-plugin`.
+- **Canonical contribution norms**: `CONTRIBUTING.md` and
+  `CODE_OF_CONDUCT.md` (Contributor Covenant 2.1) mirrored across all
+  seven repos.
+- **CI workflows** (`test.yml`, `docs.yml`, `publish.yml`) on Node.js 24
+  (actions/checkout@v6, actions/setup-python@v6). `docs.yml` clones all
+  six sub-projects at build time and publishes the combined site; daily
+  cron + repository_dispatch keeps the site fresh.
+
+### Notes
+
+- All sub-projects pinned to the same neuronxcc floor (`>=2.24`) and the
+  same torch-neuronx floor (`>=2.9`).
+- Sub-projects remain independent repos with independent releases. The
+  umbrella tracks minimum sub-project versions via the extras above.
+- PyTorch fallback works end-to-end for every sub-project on any hardware.
+  NKI kernels are scaffolded; on-hardware validation on trn1 / trn2 is
+  the next milestone across the suite.
+
+[0.1.0]: https://github.com/trnsci/trnsci/releases/tag/v0.1.0

trnsci-0.1.0/CLAUDE.md

@@ -0,0 +1,38 @@
+# trnsci
+
+Umbrella for the trn-* scientific computing suite for AWS Trainium via NKI.
+
+## Layout
+
+```
+trnsci/
+├── trnfft/       # cuFFT-equivalent: FFT, complex tensors
+├── trnblas/      # cuBLAS-equivalent: BLAS Level 1-3
+├── trnrand/      # cuRAND-equivalent: PRNG + QMC
+├── trnsolve/     # cuSOLVER-equivalent: factorizations, eigh (package name: trnsolver)
+├── trnsparse/    # cuSPARSE-equivalent: sparse formats + SpMM
+├── trntensor/    # cuTENSOR-equivalent: einsum + decompositions
+├── examples/     # Cross-project integration examples
+├── tests/        # Integration tests
+├── docs/         # Umbrella mkdocs site (links into per-project docs)
+└── pyproject.toml  # Meta-package (trnsci[all] → all six)
+```
+
+Each sub-project has its own `CLAUDE.md`, `pyproject.toml`, `tests/`, and `.git/`. The umbrella is a coordinating layer — it does not own their code.
+
+## Conventions across the suite
+
+- Apache 2.0, Copyright 2026 Scott Friedman
+- Python ≥3.10, torch ≥2.1, numpy ≥1.24
+- Optional `[neuron]` extra pins `neuronxcc>=2.24` (NKI 2.24+ calling convention)
+- NKI dispatch pattern: each project exposes `set_backend("auto"|"pytorch"|"nki")` via `<pkg>/nki/dispatch.py`
+- Tests marked `@pytest.mark.neuron` for on-hardware-only tests
+- `pytest -m "not neuron"` is the CPU-only CI path
+
+## Cross-project composition
+
+`examples/df_mp2_integrated.py` is the canonical integration demo — shows how the sub-projects compose for a realistic workload (density-fitted MP2 energy). Treat it as the reference for cross-project API usage.
+
+## Release coordination
+
+Sub-projects version independently. The umbrella `trnsci` package version reflects the meta-package itself, not the sub-projects. When a sub-project releases, bump the corresponding minimum in `pyproject.toml` extras.

trnsci-0.1.0/CODE_OF_CONDUCT.md

@@ -0,0 +1,25 @@
+# Code of Conduct
+
+This project adopts the [Contributor Covenant](https://www.contributor-covenant.org/), version 2.1, as its code of conduct. The full text is available at:
+
+https://www.contributor-covenant.org/version/2/1/code_of_conduct/
+
+## Scope
+
+This Code applies within all project spaces — the GitHub repositories under the [trnsci](https://github.com/trnsci) organization, issue trackers, pull request discussions, and any public forums where an individual is representing the project or its community.
+
+## Reporting
+
+Concerns about behaviour in project spaces may be reported confidentially to:
+
+**scttfrdmn@gmail.com**
+
+All reports will be reviewed and investigated promptly and fairly. The project maintainers are obligated to respect the privacy and security of the reporter.
+
+## Enforcement
+
+Maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the Contributor Covenant, version 2.1, available at https://www.contributor-covenant.org/version/2/1/code_of_conduct.html. It is licensed under CC BY 4.0.

trnsci-0.1.0/CONTRIBUTING.md

@@ -0,0 +1,69 @@
+# Contributing to trnsci
+
+Thanks for your interest in contributing. This document covers the whole suite — the same guidelines apply to the umbrella and to each of the six sub-projects (`trnfft`, `trnblas`, `trnrand`, `trnsolver`, `trnsparse`, `trntensor`).
+
+## Where does my change belong?
+
+- **Scoped to a single library** — bug fix, new feature, added kernel in one sub-project → open a PR in that sub-project's repo.
+- **Cross-cutting** — integration examples, umbrella docs, CUDA-rosetta content, coordinated version bumps, shared tooling → open a PR against [trnsci/trnsci](https://github.com/trnsci/trnsci).
+
+If you aren't sure, open the PR where it's easiest and we'll move it.
+
+## Development setup
+
+```bash
+git clone git@github.com:trnsci/trnsci.git
+cd trnsci
+# Clone sibling sub-projects if you don't already have them:
+for p in trnfft trnblas trnrand trnsolver trnsparse trntensor; do
+  [ -d "$p" ] || git clone "git@github.com:trnsci/$p.git"
+done
+make install-dev
+make test-all
+```
+
+A single sub-project in isolation:
+
+```bash
+cd trnfft   # or any other
+pip install -e ".[dev]"
+pytest tests/ -v -m "not neuron"
+```
+
+## Tests
+
+- `pytest tests/ -v -m "not neuron"` — the CPU-only suite. Must pass on every PR.
+- `pytest tests/ -v -m neuron` — on-hardware suite, run from a machine with AWS credentials via `scripts/run_neuron_tests.sh`. Not part of standard CI.
+
+## Conventions
+
+- **License header** — new files get the Apache 2.0 notice and `Copyright 2026 Scott Friedman` where a notice is customary (long source files, not one-line configs).
+- **Python** — ≥ 3.10; `torch` ≥ 2.1; `numpy` ≥ 1.24.
+- **No emoji** in source, commits, or docs unless the feature is literally about emoji.
+- **Docstrings** only where they help a reader who doesn't have the context you had when writing. Don't restate the signature.
+- **No throwaway files** in the repo root — work-in-progress notes belong in PR descriptions or `docs/`.
+
+## Commit style
+
+Conventional-ish prefixes: `fix:`, `feat:`, `docs:`, `test:`, `bench:`, `chore:`, `refactor:`. Keep the subject line ≤ 72 characters. Longer context goes in the body.
+
+## Pull requests
+
+Before opening a PR:
+
+- [ ] `pytest tests/ -v -m "not neuron"` passes
+- [ ] If you changed public API or behaviour, `CHANGELOG.md` has an `[Unreleased]` entry
+- [ ] If you added a public symbol, the project's `docs/api.md` lists it
+- [ ] PR description says *what* changed and *why*, not just *what*
+
+## Issues
+
+Label each issue one of: `bug`, `feature`, `question`, `docs`, `infra`. Bugs include repro steps and expected-vs-actual output. Features describe the use case.
+
+## Code of conduct
+
+By participating, you agree to abide by the [Contributor Covenant v2.1](CODE_OF_CONDUCT.md). Report concerns to the contact listed there.
+
+## License
+
+Contributions are Apache 2.0, per the repository's [LICENSE](LICENSE). You attest you have the right to submit the code.

trnsci-0.1.0/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   Copyright 2026 Scott Friedman
+
+   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 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 accept support,
+      obligations, or other liability only on behalf of Yourself 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 Scott Friedman
+
+   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.

trnsci-0.1.0/Makefile

@@ -0,0 +1,36 @@
+.PHONY: install-dev test-all docs docs-serve bench-all clean
+
+SUBPROJECTS := trnfft trnblas trnrand trnsolve trnsparse trntensor
+
+install-dev:
+	@for p in $(SUBPROJECTS); do \
+		echo "==> pip install -e ./$$p"; \
+		pip install -e "./$$p[dev]" || exit 1; \
+	done
+	pip install -e ".[dev]"
+
+test-all:
+	@for p in $(SUBPROJECTS); do \
+		echo "==> pytest $$p"; \
+		( cd $$p && pytest tests/ -v -x --tb=short -m "not neuron" ) || exit 1; \
+	done
+	pytest tests/ -v -x --tb=short -m "not neuron"
+
+docs:
+	mkdocs build --strict
+
+docs-serve:
+	mkdocs serve
+
+bench-all:
+	@for p in $(SUBPROJECTS); do \
+		if [ -d "$$p/benchmarks" ]; then \
+			echo "==> benchmarks in $$p"; \
+			( cd $$p && pytest benchmarks/ --benchmark-only ) || true; \
+		fi; \
+	done
+
+clean:
+	find . -name __pycache__ -type d -exec rm -rf {} + 2>/dev/null || true
+	find . -name '*.egg-info' -type d -exec rm -rf {} + 2>/dev/null || true
+	rm -rf site/ build/ dist/