graham/prop
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

chore(grid-rs): retrigger Rust CI after runner restart

Browse source 
The forgejo-runner was offline when 989d310..410a137 landed, so the
build-grid-rs workflow never dispatched for those pushes. Empty CI
retrigger commits don't match the path filter. Touching the crate
root forces build-grid-rs.yaml to fire and pick up the HRRR S3
fallback + scores_file .prop rename + point lookup fix.

Also corrects the now-stale "f01..f18 forecast hours only" note — as
of Phase 3 Stream A, Rust owns the f00 analysis step too.
This commit is contained in:
Graham McIntire 2026-04-21 16:13:03 -05:00
parent 07709a9af5
commit c56bb91f71
No known key found for this signature in database
GPG key ID: F4ABF488E6029E59
1 changed files with 2 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

3
rust/prop_grid_rs/src/lib.rs
View file

@ -4,7 +4,8 @@
//! tests can compare behavior 1:1. Module boundaries chosen so failures
//! during TDD fall into the smallest possible blast radius.
//!
//! Port targets (f01..f18 forecast hours only — f00 remains in Elixir):
//! Post-Phase-3: f00 analysis and f01..f18 forecasts both live here.
//! Port targets:
//! band_config ← lib/microwaveprop/propagation/band_config.ex
//! region ← lib/microwaveprop/propagation/region.ex
//! scorer ← lib/microwaveprop/propagation/scorer.ex