ggtrace
A debugger for ggplot2's internals, hardening its grip as the internals it traces keep moving.
Comparison · Analytics
gdverse vs STACAS
A side-by-side editorial comparison of gdverse and STACAS — release velocity, themes, recent moves, and the top alternatives to consider.
gdverse vs STACAS: at a glance
What is gdverse?
gdverse is turning geographical detector methods into inference, not just point estimates.
A geographical detector toolkit for spatial stratified heterogeneity, shipping small numbered releases every few months. Recent work centres on statistical rigour: confidence intervals for the q-statistic (experimental in 1.3-2, made more robust in 1.6), reported significance for interaction detection, and a fix for stratification collision in that same interaction path. The rest is Python-interop maintenance — reticulate compatibility, parallel stability in cpd_disc, and dependency configuration.
What is STACAS?
Single-cell batch correction that learned to use cell labels, then spent three releases chasing Seurat.
STACAS integrates single-cell RNA-seq datasets by finding and weighting anchors between them, with rPCA-distance-based downweighting and an optional semi-supervised mode that uses cell type labels to discard inconsistent anchors. IntegrateData.STACAS() performs the integration natively rather than handing off, and StandardizeGeneSymbols() normalises gene naming across datasets before anchors are computed.
gdverse vs STACAS: editorial side-by-side
gdverse
0.0ANALYTICS
gdverse is turning geographical detector methods into inference, not just point estimates.
◆ Current state
A geographical detector toolkit for spatial stratified heterogeneity, shipping small numbered releases every few months. Recent work centres on statistical rigour: confidence intervals for the q-statistic (experimental in 1.3-2, made more robust in 1.6), reported significance for interaction detection, and a fix for stratification collision in that same interaction path. The rest is Python-interop maintenance — reticulate compatibility, parallel stability in cpd_disc, and dependency configuration.
◆ Where it's heading
The arc is from computing detector statistics to qualifying them. Confidence intervals, significance reporting and non-centrality parameter estimation are all about telling users how much to trust a q-value, which is the gap between a research script and a package other people cite. The Python-dependency work is the recurring tax on that: several releases exist mainly to keep reticulate-backed models passing checks.
◆ Prediction
Expect the experimental q-statistic confidence intervals to be promoted to a stable, documented interface across the detector family, since the last two releases have both worked on their robustness and reporting.
STACAS
0.0ANALYTICS
Single-cell batch correction that learned to use cell labels, then spent three releases chasing Seurat.
◆ Current state
STACAS integrates single-cell RNA-seq datasets by finding and weighting anchors between them, with rPCA-distance-based downweighting and an optional semi-supervised mode that uses cell type labels to discard inconsistent anchors. IntegrateData.STACAS() performs the integration natively rather than handing off, and StandardizeGeneSymbols() normalises gene naming across datasets before anchors are computed.
◆ Where it's heading
The method work concentrated in version 2.0 and has been stable since; everything after is Seurat compatibility and operational robustness. Versions 2.1.1 through 2.3.0 track Seurat v5 assays, v3-to-v5 conversion, multi-layer objects and SCT normalisation, with the genuinely useful additions — a reference seed dataset, max.seed.datasets for large-scale integration, min.sample.size — arriving as side effects of that work. The package is from the same lab as GeneNMF, and its release rhythm follows the single-cell ecosystem's upstream churn rather than an internal roadmap.
◆ Prediction
Expect the next release to follow further Seurat object-model changes, which have driven the last three. Nothing in the entries indicates new anchor-scoring or correction methodology in progress.
Alternatives to gdverse and STACAS
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 gdverse or STACAS.
kde1d
A univariate density estimator that added zero-inflated data and reopened its C++ API to do it.
svines
Stationary vine copulas for time series, released in lockstep with the rest of Nagler's vine stack.
gghighlight
A single-purpose ggplot2 extension that has spent six years tracking ggplot2 instead of growing.
rtrek
A Star Trek data package that became a Memory Alpha web client and has been patching scrapers ever since.
eiaapi
A thin EIA energy-data client whose whole story is making bulk queries survive the API's limits.
See all gdverse alternatives → · See all STACAS alternatives →
Recent activity from gdverse and STACAS
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 6mo agogdverseInteraction detection reports significance; stratification collision fixed
- 10mo agogdversePython examples wrapped to stop CRAN check failures
- 10mo agogdversecpd_disc refactored for parallel stability and reticulate compatibility
- 1y agoSTACASMulti-layer objects and Seurat v3-to-v5 conversion handled
- 1y agogdverseAdds package citation metadata
- 1y agogdverseExperimental confidence intervals for the q statistic
- 1y agogdversePlot method bug fixes across four detector models
- 2y agoSTACASscale.data option for extreme batch effects; gene name conversion table
- 3y agoSTACASReference seeding, gene symbol standardisation, large-scale integration path
- 4y agoSTACASSemi-supervised integration and rPCA anchor downweighting ⚡
- 5y agoSTACASSeurat 4.0.0 compatibility and SCTransform support
Frequently asked questions
What is the difference between gdverse and STACAS?
They serve adjacent needs but don't currently overlap on shipped themes. gdverse and STACAS are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is gdverse better than STACAS?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. gdverse and STACAS are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
What are the best alternatives to gdverse?
Top gdverse alternatives in Analytics are ranked by recent ship velocity. Browse the "gdverse alternatives" section above for the current picks, or visit /alternatives/gdverse for the full list with editorial commentary on each.
What are the best alternatives to STACAS?
Top STACAS alternatives in Analytics are ranked by recent ship velocity. Browse the "STACAS alternatives" section above for the current picks, or visit /alternatives/stacas for the full list with editorial commentary on each.