OHPL
A 2017 chemometrics method frozen in place, visited only when CRAN changes its documentation rules.
Comparison · Analytics
APCalign vs bpbounds
A side-by-side editorial comparison of APCalign and bpbounds — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r
APCalign vs bpbounds: at a glance
What is APCalign?
APCalign spent this year fixing the counts it had been quietly getting wrong
APCalign standardises Australian plant names against the APC and APNI taxonomic resources and derives state-level native/introduced status from them. The feed is GitHub releases tagged by resource download date rather than semantic version, so titles carry no information about content. The two 2026 releases are the only substantive ones in the window: infrataxa support in the diversity functions, then a fix for a grep that had been matching the wrong columns.
What is bpbounds?
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.
APCalign vs bpbounds: editorial side-by-side
APCalign
2.5ANALYTICS
APCalign spent this year fixing the counts it had been quietly getting wrong
◆ Current state
APCalign standardises Australian plant names against the APC and APNI taxonomic resources and derives state-level native/introduced status from them. The feed is GitHub releases tagged by resource download date rather than semantic version, so titles carry no information about content. The two 2026 releases are the only substantive ones in the window: infrataxa support in the diversity functions, then a fix for a grep that had been matching the wrong columns.
◆ Where it's heading
Development is driven by users reporting that outputs do not match what they expect, and the fixes keep landing in the same two functions — create_species_state_origin_matrix() and native_anywhere_in_australia(). The infrataxa parameter and the reordered output columns came from user requests; the guard-ordering and grep fixes came from a filed issue. What is emerging is that the origin-matrix logic was written loosely and is now being tightened case by case, with tests and state diversity benchmarks added alongside.
◆ Prediction
Both recent releases touched the same pair of functions and the fixes were found by inspection rather than by tests failing, so more corrections in the native-status path are the likely next content — the benchmarks added in March are the mechanism that would surface them.
bpbounds
0.0ANALYTICS
bpbounds found the same swapped-cell bug twice and clamped its bounds back into range
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
Alternatives to APCalign and bpbounds
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 APCalign or bpbounds.
fastplyr
A fast dplyr stand-in that keeps finding new places to skip work entirely.
trias
Belgium's invasive-species indicator toolkit is in steady refinement, one plotting edge case at a time.
icesSAG
The ICES stock assessment client took upload away in 2024 and spent two years giving it back.
dggridR
A discrete global grid generator grew cell traversal and became a usable spatial index.
vegan
Community ecology's standard toolkit is retiring the functions a generation of scripts was built on.
See all APCalign alternatives → · See all bpbounds alternatives →
Recent activity from APCalign and bpbounds
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 16d agoAPCalignAPCalign fixes a grep that scanned taxon names for native status
- 1mo agobpboundsbpbounds clamps probability bounds and fixes a constraint-matrix swap
- 2mo agobpboundsbpbounds fixes swapped cells in the trivariate calculation
- 4mo agoAPCalignAPCalign adds infrataxa to the state origin and diversity functions
- 1y agoAPCalignTaxonomic resource snapshot from APC and APNI
- 1y agoAPCalignRelease tags switch to APC download date
- 1y agoAPCalignFix for the quiet option
- 2y agobpboundsbpbounds 0.1.6
- 3y agobpboundsbpbounds 0.1.5
- 6y agobpboundsVersion 0.1.4 on CRAN
- 7y agobpboundsVersion 0.1.3
Frequently asked questions
What is the difference between APCalign and bpbounds?
Both compete on the same themes — r — within Analytics. APCalign is currently shipping more aggressively (velocity 2.5 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.
Is APCalign better than bpbounds?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. APCalign is currently shipping more aggressively (velocity 2.5 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.
What are the best alternatives to APCalign?
Top APCalign alternatives in Analytics are ranked by recent ship velocity. Browse the "APCalign alternatives" section above for the current picks, or visit /alternatives/apcalign-r for the full list with editorial commentary on each.
What are the best alternatives to bpbounds?
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.