STACAS
Single-cell batch correction that learned to use cell labels, then spent three releases chasing Seurat.
Comparison · Analytics
gdverse vs rempsyc
A side-by-side editorial comparison of gdverse and rempsyc — release velocity, themes, recent moves, and the top alternatives to consider.
gdverse vs rempsyc: 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 rempsyc?
Publication-ready psychology tables and plots, tracking APA style as closely as the software allows.
rempsyc produces APA-formatted tables and figures for psychology research — nice_table() for results tables, plus plotting helpers for scatter plots, violin plots, densities and simple slopes. Its releases are CRAN submissions that bundle a long run of development versions, so each entry reads as a digest rather than a single change. The most recent, 0.2.0, added point labelling and per-group correlation statistics to nice_scatter and fixed nice_lm() failing on factor covariates with more than two levels.
gdverse vs rempsyc: 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.
rempsyc
0.0ANALYTICS
Publication-ready psychology tables and plots, tracking APA style as closely as the software allows.
◆ Current state
rempsyc produces APA-formatted tables and figures for psychology research — nice_table() for results tables, plus plotting helpers for scatter plots, violin plots, densities and simple slopes. Its releases are CRAN submissions that bundle a long run of development versions, so each entry reads as a digest rather than a single change. The most recent, 0.2.0, added point labelling and per-group correlation statistics to nice_scatter and fixed nice_lm() failing on factor covariates with more than two levels.
◆ Where it's heading
Two forces drive this package and neither is its own roadmap. The first is APA style: when the 7th edition advised against beta for standardized coefficients, the package switched its output to italic b with an asterisk. The second is the surrounding ecosystem — formatting is aligned to what lavaanExtra and afex produce, contrast handling was delegated to easystats' modelbased, and Excel correlation matrix export was handed entirely to the correlation package to cut maintenance.
◆ Prediction
The pattern of delegating functionality to specialist packages while keeping the formatting layer is well established and likely continues. Because releases bundle many small dev versions, the next one will probably again mix plotting refinements with fixes surfaced by upstream changes.
Alternatives to gdverse and rempsyc
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 rempsyc.
ggtrace
A debugger for ggplot2's internals, hardening its grip as the internals it traces keep moving.
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.
See all gdverse alternatives → · See all rempsyc alternatives →
Recent activity from gdverse and rempsyc
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
- 11mo agorempsycPoint labels and per-group correlations added to nice_scatter
- 1y agogdverseAdds package citation metadata
- 1y agogdverseExperimental confidence intervals for the q statistic
- 1y agorempsycExcel correlation export delegated to the correlation package
- 1y agogdversePlot method bug fixes across four detector models
- 2y agorempsycTable spacing control and a fix for name collision with afex
- 2y agorempsycStandardized coefficients switch to APA 7th edition b* notation
- 2y agorempsycLegend and standardization-check fixes
- 2y agorempsycnice_table starts coercing model objects automatically
Frequently asked questions
What is the difference between gdverse and rempsyc?
They serve adjacent needs but don't currently overlap on shipped themes. gdverse and rempsyc 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 rempsyc?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. gdverse and rempsyc 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 rempsyc?
Top rempsyc alternatives in Analytics are ranked by recent ship velocity. Browse the "rempsyc alternatives" section above for the current picks, or visit /alternatives/rempsyc for the full list with editorial commentary on each.