tradespace
For analysts with a table of evaluated designs, to learn which metrics trade. See the
docs,
the paper and examples/adcs/ for a
case study.
git clone https://github.com/DynamicalSystemsGroup/tradespace
cd tradespace && uv sync
# package only: uv sync --no-default-groups; uv run --no-default-groups
from tradespace import (
HyperbolicTradeSpace,
LogAffinePreconditioner,
make_frontier_data,
trade_off_report,
)
A, _ = make_frontier_data(300, 3, random_state=0)
A[:, 1] = 10 / A[:, 1] # pretend column 1: smaller is better
M = LogAffinePreconditioner(orientation=[1, -1, 1]).fit_transform(A)
ts = HyperbolicTradeSpace(temperature=20.0).fit(M) # real table: `select_temperature`
print(trade_off_report(ts, M).exponents.round(2))
Layout
src/tradespace/: the Python package (fit a frontier, read its trade-offs).docs/: the user guide and API reference, built into the docs site.paper/: the paper as two notebooks and what rebuilds them;site/is the root page that links the docs and the paper.examples/adcs/: the cubesat attitude-control case study the paper uses: model, data, experiments, system model.derivation/: the proofs of the method's results as SymPy scripts, one per lemma.tests/: the test suite;scripts/: build and check tools.claims_register.toml: each claim the paper and docs make and what backs it.glossary.yaml: the terms, one name per object;history.yaml: the record behind the history and acknowledgements page.CHANGELOG.md: what changed, by work package.work-packages/: the build's record; not needed to use the method.GOVERNANCE.md: the release rules, the file that declares their settings (.github/governance.toml) and the check that runs first in CI.CLAUDE.md: conventions for contributors working with Claude Code.mkdocs.yml,Dockerfile,pyproject.toml,uv.lock,.python-version: build and environment files.LICENSE,.github/(CI workflows) and the dot-files.gitattributes,.gitignore,.dockerignore: license and repository settings.
Metadata
Release files for tradespace 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| tradespace-0.1.0.tar.gz | 720.5 kB | With provenance | Details for tradespace-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| tradespace-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for tradespace-0.1.0-py3-none-any.whl |
Total release size: 797.7 kB
Release files / tradespace-0.1.0.tar.gz
| Download URL | tradespace-0.1.0.tar.gz |
|---|---|
| Size | 720.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2067bb81e55a9698e9b944d2f011a37f0192bd657d39438cba085f9ac2dd259e
|
|
BLAKE2b-256 checksum How to use checksums |
789ca53b14bbb9bf8189a910e8dc033c8270bb5263b8880e68018920348c2c4d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 18, 2026.
Transparency logRelease files / tradespace-0.1.0-py3-none-any.whl
| Download URL | tradespace-0.1.0-py3-none-any.whl |
|---|---|
| Size | 77.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
67b72b6158b02daac0df00068a872087a0811634a428ca5e955674be97972cd7
|
|
BLAKE2b-256 checksum How to use checksums |
223df5278d3689ce417f102461d2b5d1bc3d66979c3cfc4086c84e3068ab4054
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 18, 2026.
Transparency logSecurity for tradespace 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for tradespace-0.1.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 18, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.