trade-study
Multi-objective trade-study orchestration: define factors, build parameter grids, run hierarchical study phases, and extract Pareto fronts — for any domain where you compare alternatives against competing objectives.
Statement of need
Comparing design alternatives against multiple objectives is a common task across scientific simulation, engineering trade-offs, and ML hyperparameter tuning. Researchers typically glue together separate tools for grid construction, execution, scoring, and Pareto analysis, writing ad-hoc scripts that are hard to reproduce or extend to multi-phase studies (screening → refinement → benchmark).
trade-study provides a single orchestration layer that composes these
steps into a reproducible, protocol-driven workflow. Users supply a
Simulator (generates data) and a Scorer (evaluates it); the
framework handles grid construction, parallel execution, Pareto
extraction, and phase chaining. All components are modular and
optional — use only what you need.
This package targets researchers and practitioners who need:
- structured multi-phase experimental design (screen → refine → benchmark),
- multi-objective Pareto analysis across heterogeneous factors, and
- a reproducible Python API that separates domain logic from study orchestration.
Why trade-study?
| Need | Without trade-study | With trade-study |
|---|---|---|
| Parameter grid | Manual itertools.product or one-off scripts |
build_grid(factors, method="sobol") — full factorial, LHS, Sobol, Halton |
| Multi-objective ranking | Call pymoo directly, handle direction normalization | extract_front(scores, directions) — direction-aware |
| Phased studies | Custom loop with manual filtering between stages | Study(phases=[Phase(..., filter_fn=top_k_pareto_filter(k=20)), ...]) |
| Adaptive search | Set up optuna study from scratch | run_adaptive(world, scorer, factors, observables, n_trials=600) |
| Reproducibility | Scattered scripts, no standard protocol | Simulator / Scorer protocols + save_results() / load_results() |
Existing tools solve pieces of this problem — optuna for adaptive optimization, pymoo for multi-objective solvers, SALib for sensitivity analysis — but none provide the hierarchical phase orchestration that connects them into a single study.
Quick start
from trade_study import (
Direction,
Factor,
FactorType,
Observable,
Phase,
Study,
build_grid,
top_k_pareto_filter,
)
# 1. Define objectives
accuracy = Observable("accuracy", Direction.MAXIMIZE)
latency = Observable("latency_ms", Direction.MINIMIZE)
cost = Observable("cost_usd", Direction.MINIMIZE)
# 2. Define factors and build a design grid
factors = [
Factor("learning_rate", FactorType.CONTINUOUS, bounds=(1e-4, 1e-1)),
Factor("backend", FactorType.CATEGORICAL, levels=["A", "B", "C"]),
]
grid = build_grid(factors, method="lhs", n_samples=500)
# 3. Run a hierarchical study
study = Study(
world=MySimulator(), # implements Simulator protocol
scorer=MyScorer(), # implements Scorer protocol
observables=[accuracy, latency, cost],
phases=[
Phase(
"screening",
grid=grid,
filter_fn=top_k_pareto_filter(k=20),
),
Phase("benchmark", grid="carry", filter_fn=None),
],
)
study.run(n_jobs=-1)
# 4. Inspect results
print(study.summary())
front = study.front("benchmark") # non-dominated config indices
hv = study.front_hypervolume("benchmark", ref_point) # hypervolume indicator
Protocols
Users implement two protocols to plug in their domain:
from trade_study import Scorer, Simulator
class MySimulator:
"""Implements the Simulator protocol."""
def generate(self, config: dict) -> tuple:
"""Return (truth, observations) for a given config."""
...
class MyScorer:
"""Implements the Scorer protocol."""
def score(self, truth, observations, config: dict) -> dict[str, float]:
"""Return {observable_name: value} for a single trial."""
...
Installation
pip install trade-study[all]
Or install only the extras you need:
pip install trade-study[design,pareto]
| Extra | Packages | Purpose |
|---|---|---|
design |
pyDOE3, SALib, scipy | Grid construction and sensitivity screening |
pareto |
pymoo | Non-dominated sorting and indicators |
scoring |
scoringrules | Proper scoring rules (CRPS, WIS, etc.) |
stacking |
arviz, scipy | Bayesian and score-based ensemble weights |
adaptive |
optuna | Multi-objective Bayesian optimization |
parallel |
joblib | Parallel grid execution |
all |
All of the above |
Core dependency: numpy only.
API overview
Design
from trade_study import Factor, FactorType, build_grid, screen
factors = [
Factor("x", FactorType.CONTINUOUS, bounds=(0.0, 1.0)),
Factor("method", FactorType.CATEGORICAL, levels=["a", "b", "c"]),
]
grid = build_grid(factors, method="sobol", n_samples=1024)
si = screen(run_fn, factors, method="morris", n_trajectories=3000)
Execution
from trade_study import run_grid, run_adaptive
# Grid mode: evaluate all configs (optional parallelism)
results = run_grid(world, scorer, grid, observables, n_jobs=-1)
# Adaptive mode: multi-objective Bayesian optimization (NSGA-II)
results = run_adaptive(world, scorer, factors, observables, n_trials=600)
Pareto analysis
from trade_study import extract_front, hypervolume, pareto_rank
front_idx = extract_front(results.scores, directions)
ranks = pareto_rank(results.scores, directions)
hv = hypervolume(results.scores[front_idx], ref_point, directions)
Stacking
from trade_study import stack_scores, stack_bayesian, ensemble_predict
weights = stack_scores(score_matrix) # simplex-constrained optimization
weights = stack_bayesian(idata_dict) # arviz stacking (Yao et al. 2018)
combined = ensemble_predict(predictions, weights)
I/O
from trade_study import save_results, load_results
save_results(results, "study_results")
results = load_results("study_results")
Related packages
| Package | Description |
|---|---|
| TradeStudy.jl | Julia implementation of the same framework |
Development
uv sync --extra dev
just ci # lint → mypy --strict → pytest with coverage
just format # auto-format
just check # auto-fix lint
License
MIT
Release files for trade-study 0.2.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 | |
|---|---|---|---|
| trade_study-0.2.0.tar.gz | 59.4 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| trade_study-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 97.8 kB
Release files / trade_study-0.2.0.tar.gz
| Download URL | trade_study-0.2.0.tar.gz |
|---|---|
| Size | 59.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6930db8956a40b103aa182807af9a6c0161bd3affe0571eb6f97c5277a2ba2c3
|
|
BLAKE2b-256 checksum How to use checksums |
c80ad51367b66a08c17dc9032bcdda0f8a2c9287e83e53643d6aaba1a48e8667
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Aug 17, 2026.
Transparency logRelease files / trade_study-0.2.0-py3-none-any.whl
| Download URL | trade_study-0.2.0-py3-none-any.whl |
|---|---|
| Size | 38.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5154b764e9a8b8b2171794ec75f7d4ebb8f35d3a301fb86c0ecc0cfb6d4b1649
|
|
BLAKE2b-256 checksum How to use checksums |
6848e606b81e2444ae3e7baa89ae0a47493c1fb053d6d531c9ab0bb68655f9a1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Aug 17, 2026.
Transparency log