OHPL
A 2017 chemometrics method frozen in place, visited only when CRAN changes its documentation rules.
A side-by-side editorial comparison of bpbounds and Fulcrum — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | bpbounds | Fulcrum |
|---|---|---|
| Sector | Analytics | Analytics |
| Velocity score | 0.0 | 6.3 |
| Sparks · 30d | 0 | 0 |
| Top themes | causal inference, instrumental variables, r, partial identification | gis, esri-migration, offline-maps, field-data-capture |
| Last editorial update | 1h ago | 8h ago |
| Website | Visit → | — |
bpbounds found the same swapped-cell bug twice and clamped its bounds back into range
bpbounds computes nonparametric Balke-Pearl bounds on the average causal effect from instrumental variable data, in the bivariate and trivariate cases. After years of pure packaging maintenance, the two 2026 releases are analytical corrections. Bounds on intervention probabilities are now clamped to [0, 1] so derived causal risk ratio bounds cannot fall outside their feasible range, and a cell-ordering error in the trivariate three-category instrument path has been repaired.
Fulcrum is betting its whole map stack on Esri, with a hard Google Maps cutoff on September 1.
Fulcrum is a field data collection platform, and nearly every entry in the last month touches mapping. The web app ships weekly fix batches for layer rendering (KML/KMZ, MBTiles, ArcGIS Feature Services), while iOS and Android push near-weekly builds against the ArcGIS SDK. Feature work is thin right now; the visible surface is stabilization around a mapping engine migration already in flight.
bpbounds computes nonparametric Balke-Pearl bounds on the average causal effect from instrumental variable data, in the bivariate and trivariate cases. After years of pure packaging maintenance, the two 2026 releases are analytical corrections. Bounds on intervention probabilities are now clamped to [0, 1] so derived causal risk ratio bounds cannot fall outside their feasible range, and a cell-ordering error in the trivariate three-category instrument path has been repaired.
The direction is toward agreement with the reference Stata implementation and away from silently wrong output. The clamping change is described as matching the same fix in the Stata package, which suggests the two implementations are being reconciled rather than developed independently. The cell-ordering defect is the more instructive one: it was fixed in the calculation function in 0.1.7 and then again in the constraint matrix in 0.1.8, meaning the same x=0,y=1 / x=1,y=0 swap had been written in two places.
Since the recent fixes came from an external contributor's report and both touched the trivariate three-category path, the untested corners of that path are where further corrections would surface — but the release notes give no roadmap beyond parity with the Stata package.
Fulcrum is a field data collection platform, and nearly every entry in the last month touches mapping. The web app ships weekly fix batches for layer rendering (KML/KMZ, MBTiles, ArcGIS Feature Services), while iOS and Android push near-weekly builds against the ArcGIS SDK. Feature work is thin right now; the visible surface is stabilization around a mapping engine migration already in flight.
The direction is a full consolidation onto Esri. The legacy Google Maps engine is being retired on September 1 with automatic migration for anyone who hasn't switched, and Esri now carries Google's satellite and street basemaps so the imagery argument is neutralized. Underneath, the mobile SDK moved to ArcGIS 300.0.0 and ONNX on-device inference was dropped for a new INFERENCE format with labels.txt support. Offline is the second thread: downloadable layers can now be updated in place rather than deleted and recreated.
Expect the weeks before September 1 to stay dominated by migration-shaped fixes and Esri feature parity work, with the MMPK layer and Photo FastFill early-access programs the most likely to graduate to general availability next.
Other Analytics products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either bpbounds or Fulcrum.
A 2017 chemometrics method frozen in place, visited only when CRAN changes its documentation rules.
A fast dplyr stand-in that keeps finding new places to skip work entirely.
Belgium's invasive-species indicator toolkit is in steady refinement, one plotting edge case at a time.
The ICES stock assessment client took upload away in 2024 and spent two years giving it back.
A discrete global grid generator grew cell traversal and became a usable spatial index.
Community ecology's standard toolkit is retiring the functions a generation of scripts was built on.
See all bpbounds alternatives → · See all Fulcrum alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Fulcrum is currently shipping more aggressively (velocity 6.3 vs 0.0), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Fulcrum is currently shipping more aggressively (velocity 6.3 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
Top bpbounds alternatives in Analytics are ranked by recent ship velocity. Browse the "bpbounds alternatives" section above for the current picks, or visit /alternatives/bpbounds for the full list with editorial commentary on each.
Top Fulcrum alternatives in Analytics are ranked by recent ship velocity. Browse the "Fulcrum alternatives" section above for the current picks, or visit /alternatives/fulcrum for the full list with editorial commentary on each.