Skip to content

standgen: pin GDAM flow-matching model v2_west.2 - #742

Merged
amarcozzi merged 1 commit into
mainfrom
standgen-gdam-v2-west-2
Oct 19, 2026
Merged

amarcozzi merged 1 commit into
mainfrom
standgen-gdam-v2-west-2

Conversation

@amarcozzi

Copy link
Copy Markdown
Contributor

Pins standgen's GDAM requests to the flow-matching model v2_west.2 (was v2_west.1).

Do not merge until GDAM v2_west.2 is live on the public GDAM service (catalog entry + manifest + checkpoints). Until then GDAM rejects the version and every standgen GDAM call fails.

Changes

  • standgen/handlers/gdam.py: GDAM_MODEL["version"] → v2_west.2.
  • standgen/config.py: the batch-timing comment says its numbers are for v2_west.1; v2_west.2 draws in one network pass instead of an 8-step solve, so it is faster. Measured numbers to follow.
  • tests/handlers/test_gdam.py: expected request body updated.

v2_west.2 uses the same inputs and request shape as v2_west.1. Only the drawn DIA / CR / SPCD values change: on the held-out test plots, DBH CRPS is about 3.5% lower than v2_west.1 across the nine clusters.

Tests

  • uv run pytest tests/ --ignore=tests/integration: 285 passed.
  • Integration tests not run locally (they need GCP).

@amarcozzi
amarcozzi marked this pull request as ready for review October 19, 2026 17:00
@amarcozzi
amarcozzi merged commit 831c87a into main Oct 19, 2026
1 check passed
@amarcozzi
amarcozzi deleted the standgen-gdam-v2-west-2 branch October 19, 2026 17:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant