Skip to content

Commit e17b44f

Browse files
Release v0.44.2
#230 PARS vignette reader-facing prose cleanup (issue numbers, tunnel refs, disagreement detail removed; accessible km table reframed as standalone roll-up; mapping_code symbology paragraph dropped). Docs only. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014kSEJoad4Bc553qU8eFiE6
1 parent bceffc1 commit e17b44f

2 files changed

Lines changed: 6 additions & 2 deletions

File tree

DESCRIPTION

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
Package: link
22
Title: Stream Network Habitat Interpretation (Experimental)
3-
Version: 0.44.1
4-
Date: 2026-07-04
3+
Version: 0.44.2
4+
Date: 2026-07-06
55
Authors@R: c(
66
person("Allan", "Irvine", , "airvine@newgraphenvironment.com",
77
role = c("aut", "cre"),

NEWS.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,7 @@
1+
# link 0.44.2
2+
3+
Reader-facing prose cleanup on the PARS vignette (`vignettes/pars-habitat-connectivity.Rmd`), from review — no model, artifact, or numbers change. Dropped internal issue numbers and build-infrastructure ("tunnel") references, and cut the per-segment `mapping_code` disagreement detail (the top-diff-pattern columns and the "remaining disagreements" paragraph) since bull-trout parity is ~99%. The accessible / spawning / rearing km table stays but is reframed around `lnk_rollup_wsg()` as a standalone habitat-totals roll-up — link's own numbers, no reference required — that happens to match bcfishpass, rather than a proof-of-parity exercise. Removed the `mapping_code` symbology paragraph entirely: the colour semantics were easy to mis-state (e.g. red marks an accessible reach whose downstream PSCIS crossing is ranked a *barrier*, not merely "field-assessed"), and each map already carries its own colour legend.
4+
15
# link 0.44.1
26

37
Extend the PARS vignette to demonstrate `accessible_km` bcfishpass-equivalence ([#226](https://github.com/NewGraphEnvironment/link/issues/226)). `vignettes/pars-habitat-connectivity.Rmd` gains an **Accessible habitat (km)** section: a link-vs-bcfishpass roll-up table (bull-trout accessible / spawning / rearing, from the new cached `pars_accessible.rds`) plus computed prose — link models 6,822.5 km of accessible bull-trout habitat against bcfishpass's 6,822.9 km, a −0.01% difference (the [#223](https://github.com/NewGraphEnvironment/link/issues/223) access-segmentation fix; spawning/rearing agree within the 5% habitat band). `data-raw/wsg_vignette_data.R` grows the accessible roll-up (mirroring `data-raw/parity_crosssection.R`'s `lnk_rollup_wsg()` + `fresh.streams_vw_bcfp` `IN (1,2)` computation) and a **segmentation-parity guard** that refuses to build when `fresh` and `fresh_default` disagree by more than 1%. All cached artifacts were regenerated from the post-#223 state: this required re-modelling the `default` (Arctic grayling) config for `PARS` into `fresh_default`, which had been left on the pre-#223 segmentation (48,558 segments vs `fresh`'s 97,538) — a naive regeneration would have joined the grayling `mapping_code` onto mismatched geometry and corrupted the map. The re-model (`data-raw/wsg_run_one.R` + a `merge = TRUE` recompute for cross-WSG `;DAM`) brings both configs onto the same segmentation; the previously hardcoded grayling map-caption counts are now computed inline from the loaded layer so they track the artifact. Bull-trout `mapping_code` parity refreshes to 98.91% (from 99.04%, on the denser post-#223 segmentation). Verified with a database-free knit.

0 commit comments

Comments
 (0)