Repository navigation
v0.69.0
·
176 commits
to main
since this release
Streams break only where a present species' access changes, as bcfishpass breaks them (#326). Every persisted group re-segments under both configs, so the next provincial run re-models all 241 groups in fresh and fresh_default. Until then, groups within one schema sit on different segmentations.
- The break set is each present species' barriers after its lifts, reduced to the downstream-most position per flow path (
.lnk_pipeline_prep_minimal(), per species, never on the union). The independent falls, user-definite and subsurface sources still break where they sit. #223 reduced before the lifts and then kept every position, which this replaces; #225's rename is moot. On thebcfishpassconfig, 11 groups hold 0.9995 to 1.006 times bcfishpass's segments, and every one of the 454 link-only breaks has a named source.defaultdrops 2.1 to 2.7-fold (PCEA 106,079 → 39,566 segments). Parity is 120 of 122 pairs, and BT rearing in PCEA, FINA and LKEL now matches bcfishpass segment by segment to 1.2 km. - The
bcfishpassconfig takes bcfishpass's order-1 rearing exception for BT, CH, CO, ST and WCT oncwgroups, with its tests: a known width up to the minimum and a gradient within the rearing maximum. It needs fresh 0.43.0 (frs_order_child(channel_width_max =, gradient_max =)). PARS BT rearing against bcfishpass goes from −24.8 to −8.1 km; the rest is fresh's direct-child test (fresh#158). bcfishpass's CH / CO / ST / WCT waterbody and edge filter is not applied (at most 2.7 km per species per group). lnk_barriers_unify()persists every staged barrier row. A measure in FWA's millimetre gap between segments got no point fromFWA_LocateAlong(), and the row was dropped: 4 to 31 per group. The reduction still held those positions, so the barriers above them went unbroken..lnk_sql_locate()falls back to the nearest segment on the line. The upstream report is drafted as NewGraphEnvironment/fwapg#45 (upstream-draft).- Owed: the provincial re-model, and the PARS vignette's cross-config join, which the configs' separate segmentations invalidate (its guard refuses; #390). Kept: link-only BT spawning at exactly 2.0 m (FINA 4.6, PCEA 1.8, PARS 5.5 km) is fresh's
>=against bcfishpass's>; a bundle minimum 0.005 above bcfishpass's would reproduce it and was declined. Mechanics: RUNBOOK §2b and §7. Record:research/bcfp_segmentation_parity.md. Evidence:data-raw/logs/segmentation_326/.