Skip to main content
Pre-release

This release is a pre-release and may not be stable for production use.

fresh-fuchs

Stochastic, risk-aware forest landscape planning on the TSA29 mini instance (~100,000 ha subset of Williams Lake TSA29).

The research design is a nested decision problem:

  • Outer (policy / administration). Landscape-scale policy on target species / development-type composition by area share and on harvest policy (AAC as f(development type, rotation age)), evaluated risk-sensitively on Monte-Carlo distributions of NPV using downside-risk measures (CVaR).
  • Inner (enterprise / implementation). Harvest scheduling and replanting decisions (which species to plant) maximizing NPV subject to the outer policy constraints, formulated as a Model I linear program.

Full-Monte-Carlo outer problem: sample disturbance (fire) and — later — price realizations; solve the inner LP once per scenario (full foresight within a scenario); evaluate each policy on the resulting NPV distribution.

Reuses the UBC-FRESH ecosystem rather than re-implementing it: ws3 (wood-supply engine and LP machinery), femic (tsa29mini instance bundle and model bridge), fhops (harvest-cost estimation), nemora (DBH distribution fit and sampling), and freshforge (workflow + matrix orchestration and evidence). fresh-salvage provides economic calibration anchors (reference only).

Status

v0.1.0a1 (Phase 5 release). The end-to-end pipeline is implemented, validated, and tested: extended ws3 model build -> full-MC fire scenarios -> per-scenario inner LP (NPV max) -> NPV distribution -> policy grid search -> CVaR-based ranking, wrapped in freshforge workflows/matrices with evidence. See ROADMAP.md for the phase/issue tracker map and planning/v0.1.0a1-plan.md for the detailed master plan.

Quick Start

CI-safe synthetic end-to-end (no private data; the public-safe synthetic instance in fresh_fuchs.instance.synthetic):

pip install -e ".[dev,orchestration]"
from fresh_fuchs.orchestration import fuchs_workflow_spec, run_fuchs_workflow

spec = fuchs_workflow_spec(horizon=2, n_scenarios=3, master_seed=42)
result = run_fuchs_workflow(spec, workdir="outputs/synthetic")
assert result.ok

Real-bundle pipeline (requires the bundle extra and the annex bundle):

pip install -e ".[dev,bundle]"
fresh-fuchs --help
# build-model -> scenario-run -> policy-grid -> policy-rank

Documentation

Sphinx docs under docs/: installation, quickstart, model semantics, CLI reference, architecture, and development guides.

License

MIT, Copyright (c) 2026 UBC FRESH Lab.

Metadata

Release files for fresh-fuchs 0.2.0a1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for fresh-fuchs 0.2.0a1
File Size Uploaded
fresh_fuchs-0.2.0a1.tar.gz 121.1 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for fresh-fuchs 0.2.0a1
File Interpreter ABI Platform
fresh_fuchs-0.2.0a1-py3-none-any.whl Python 3 none any Details

Total release size: 215.7 kB

Release files / fresh_fuchs-0.2.0a1.tar.gz

Download URL fresh_fuchs-0.2.0a1.tar.gz
Size 121.1 kB
Tags Source
SHA-256 checksum
How to use checksums
52dcc2c6ded418ad6b1652f8c4b1dcf67e5295f06f13210e5a6104f1a286aef5
BLAKE2b-256 checksum
How to use checksums
177f00a33d0b1b0321b4f67ad6962e15ce3bbdbeb30e6de9147ff3ae01662cf6
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 28, 2026.

Transparency log

Release files / fresh_fuchs-0.2.0a1-py3-none-any.whl

Download URL fresh_fuchs-0.2.0a1-py3-none-any.whl
Size 94.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
0d015724ec3b968496816fb2e7511682d7dafe31f165c877305d9a26f51fdb5d
BLAKE2b-256 checksum
How to use checksums
6d378f4aaf550e57ef0e0b6f5c804b29097766a47b4fe3085acd8f0d76ba697c
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 28, 2026.

Transparency log
Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page