OHPL
A 2017 chemometrics method frozen in place, visited only when CRAN changes its documentation rules.
Comparison · Analytics
bpbounds vs factoextra
A side-by-side editorial comparison of bpbounds and factoextra — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r
bpbounds vs factoextra: at a glance
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.
What is factoextra?
factoextra woke from six years of silence and stopped being a FactoMineR front-end
factoextra supplies the fviz_* grammar most R users reach for when plotting PCA, correspondence analysis and clustering results. It sat effectively dormant from 2020 to early 2026, then shipped three releases in five months that resolved a six-year issue backlog, decoupled it from its original backends, and taught it to plot UMAP and t-SNE embeddings. The current version also reaches into tidymodels, plotting a PCA fitted inside a recipe or workflow directly.
bpbounds vs factoextra: editorial side-by-side
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.
factoextra
3.8ANALYTICS
factoextra woke from six years of silence and stopped being a FactoMineR front-end
◆ Current state
factoextra supplies the fviz_* grammar most R users reach for when plotting PCA, correspondence analysis and clustering results. It sat effectively dormant from 2020 to early 2026, then shipped three releases in five months that resolved a six-year issue backlog, decoupled it from its original backends, and taught it to plot UMAP and t-SNE embeddings. The current version also reaches into tidymodels, plotting a PCA fitted inside a recipe or workflow directly.
◆ Where it's heading
The direction is from wrapper to visualization layer. as_factoextra_pca() turned the fviz_pca_* family into something that consumes coordinates from anywhere — cmdscale, vegan, a custom decomposition, a recipes step — rather than only FactoMineR objects, and the vignette on extending factoextra to new backends says the maintainer intends others to plug in. The embedding support shows the same care: no scree plot, no correlation circle, and a convex hull instead of a confidence ellipse, because an embedding does not preserve the metric an ellipse would assume.
◆ Prediction
With recipes and workflows already wired in, the next likely step is covering more tidymodels dimension-reduction steps (step_umap, step_ica, step_pls) through the same as_factoextra_pca() entry point rather than adding new fviz_* functions per method.
Alternatives to bpbounds and factoextra
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 factoextra.
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 bpbounds alternatives → · See all factoextra alternatives →
Recent activity from bpbounds and factoextra
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 22d agofactoextrafactoextra 2.2.0 adds UMAP and t-SNE plotting, plus tidymodels recipes ⚡
- 1mo agobpboundsbpbounds clamps probability bounds and fixes a constraint-matrix swap
- 1mo agofactoextrafactoextra 2.1.0 decouples its plots from any specific backend ⚡
- 2mo agobpboundsbpbounds fixes swapped cells in the trivariate calculation
- 5mo agofactoextrafactoextra 2.0.0 ends a six-year dormancy with breaking modernization
- 2y agobpboundsbpbounds 0.1.6
- 3y agobpboundsbpbounds 0.1.5
- 6y agofactoextrafactoextra 1.0.7
- 6y agobpboundsVersion 0.1.4 on CRAN
- 6y agofactoextrafactoextra 1.0.6
- 7y agobpboundsVersion 0.1.3
- 8y agofactoextrafactoextra 1.0.5
Frequently asked questions
What is the difference between bpbounds and factoextra?
Both compete on the same themes — r — within Analytics. factoextra is currently shipping more aggressively (velocity 3.8 vs 0.0), with 1 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 bpbounds better than factoextra?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. factoextra is currently shipping more aggressively (velocity 3.8 vs 0.0), with 1 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 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.
What are the best alternatives to factoextra?
Top factoextra alternatives in Analytics are ranked by recent ship velocity. Browse the "factoextra alternatives" section above for the current picks, or visit /alternatives/factoextra for the full list with editorial commentary on each.