Skip to content

feat(config): point canonical pipeline at 2025_usa_cornerstone_v0_4 - #880

Merged
MoLi7 merged 1 commit into
mainfrom
mo__v0-4-canonical-config
Sep 8, 2026
Merged

MoLi7 merged 1 commit into
mainfrom
mo__v0-4-canonical-config

Conversation

@MoLi7

@MoLi7 MoLi7 commented Sep 8, 2026

Copy link
Copy Markdown
Member

cc:
Closes:

Stack: step 1 of 2 — v0.4 release: canonical config, then snapshot bump

What changed? Why?

Adds 2025_usa_cornerstone_v0_4.yaml: v0.3.2 methodology on the 2024 nowcast detail MUT, pinned to build v0.3.0_4276083. CANONICAL_USA_CONFIG and both workflow defaults point at it, so generate_snapshots on main cuts v0.4. Adds waterfall rungs v04_waterfall_g2_methods and v04_waterfall_g3_data; pins the v0.3 waterfall q to the v0.3.2 snapshot.

Impact

Moves N, D, A and q under the default config to 2025_usa_cornerstone_v0_4; .SNAPSHOT_KEY unchanged until the bump PR.

Review focus

  • Under nowcast the GHG FBS becomes GHG_national_Cornerstone_nowcast_2024; the v0.4 header and G3 rung say so.
  • Rung flags equal the v0.3 rungs on purpose; headers explain how MECS reaches them.

Testing

black, ruff, mypy, hermetic and realdata pytest locally.

Heads-up

After merge, dispatch generate_snapshots on main with config_name=2025_usa_cornerstone_v0_4; integration tests stay red until the bump PR lands.

🤖 Generated with Claude Code

MoLi7 commented Sep 8, 2026

Copy link
Copy Markdown
Member Author

This stack of pull requests is managed by Graphite. Learn more about stacking.

@MoLi7
MoLi7 requested a review from bl-young September 8, 2026 22:17
Adds the v0.4 release config: v0.3.2 methodology on the 2024 nowcast
detail MUT, pinned to build v0.3.0_4276083. CANONICAL_USA_CONFIG and the
generate_snapshots / generate_diagnostics workflow defaults follow it, so
the next snapshot cut on main is the v0.4 one. The v0.3 waterfall q is
pinned to the v0.3.2 release snapshot so its pins survive the bump.

Also adds the two v0.4 waterfall rungs, v04_waterfall_g2_methods (v0.4
less nowcasting and less the US data update) and v04_waterfall_g3_data
(v0.4 less nowcasting), with headers explaining why their flags equal the
v0.3 rungs and how the MECS fix reaches them through the GHG FBS parquets.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@MoLi7
MoLi7 force-pushed the mo__v0-4-canonical-config branch from a57f102 to 12c2090 Compare September 8, 2026 23:26

@bl-young bl-young left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

At a glance I think this all looks good.

# Data selection
#####
usa_detail_io_source: nowcast
nowcast_mut_vintage: 'v0.3.0_4276083'

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just want you to confirm this so the right one.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes. v0.3.0_4276083 is the 7 September rebuild (commit 4276083 on #875, progress_report §6a): newest for all eight years, all four 2024 tables present, and main differs from that commit in transform/iot only by the VA_ROW_PRESENCE_ATOL rename plus lineage metadata, so main reproduces it.

@MoLi7
MoLi7 merged commit 2fcbd68 into main Sep 8, 2026
6 checks passed
@MoLi7
MoLi7 deleted the mo__v0-4-canonical-config branch September 8, 2026 23:49
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.

2 participants