STACAS
Single-cell batch correction that learned to use cell labels, then spent three releases chasing Seurat.
Comparison · Analytics
gdverse vs TidyDensity
A side-by-side editorial comparison of gdverse and TidyDensity — release velocity, themes, recent moves, and the top alternatives to consider.
gdverse vs TidyDensity: at a glance
| Feature | gdverse | TidyDensity |
|---|---|---|
| Sector | Analytics | Analytics |
| Velocity score | 0.0 | 0.0 |
| Sparks · 30d | 0 | 0 |
| Top themes | spatial statistics, geographical detector, confidence intervals, reticulate | statistical-distributions, random-generation, parameter-estimation, tidyverse |
| Last editorial update | 2h ago | 58m ago |
| Website | Visit → | Visit → |
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 TidyDensity?
A distribution catalogue that grows by one family at a time, and rarely breaks anything.
TidyDensity generates tidy-format random data from statistical distributions, with parameter estimation, AIC calculation, summary tables and automatic plotting for each one. Its releases follow a fixed template — breaking changes, new features, minor fixes — and the breaking section is usually empty. Growth comes distribution by distribution: Bernoulli, Burr, triangular, chi-square, zero-truncated negative binomial and others each arrive with a matching set of param_estimate, aic and stats_tbl helpers.
gdverse vs TidyDensity: 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.
TidyDensity
0.0ANALYTICS
A distribution catalogue that grows by one family at a time, and rarely breaks anything.
◆ Current state
TidyDensity generates tidy-format random data from statistical distributions, with parameter estimation, AIC calculation, summary tables and automatic plotting for each one. Its releases follow a fixed template — breaking changes, new features, minor fixes — and the breaking section is usually empty. Growth comes distribution by distribution: Bernoulli, Burr, triangular, chi-square, zero-truncated negative binomial and others each arrive with a matching set of param_estimate, aic and stats_tbl helpers.
◆ Where it's heading
The package is filling out a matrix rather than changing shape — every new distribution gets the same four or five companion functions, so the surface grows predictably and the design does not. What variation exists comes from utilities that work across distributions: MCMC sampling, bootstrap helpers, time series conversion, distribution comparison. The two genuine breaking changes in this window were both internal reworks, moving generation onto data.table and rewriting quantile normalization for speed.
◆ Prediction
The established pattern of adding a distribution with its full helper set is the most likely continuation. Recent releases have been small, suggesting the catalogue is approaching the distributions its author considers worth covering.
Alternatives to gdverse and TidyDensity
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 TidyDensity.
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 TidyDensity alternatives →
Recent activity from gdverse and TidyDensity
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 agoTidyDensityquantile_normalize rewritten, changing its output
- 1y agoTidyDensityDocumentation corrections for two distribution functions
- 1y agogdverseAdds package citation metadata
- 1y agogdverseExperimental confidence intervals for the q statistic
- 1y agogdversePlot method bug fixes across four detector models
- 2y agoTidyDensityZero-truncated distributions and AIC helpers added in bulk
- 2y agoTidyDensityMCMC sampling and quantile normalization join the utilities
- 2y agoTidyDensityGeneration moves to data.table; native pipe raises the R floor
- 2y agoTidyDensityDistributions convertible to time series objects
Frequently asked questions
What is the difference between gdverse and TidyDensity?
They serve adjacent needs but don't currently overlap on shipped themes. gdverse and TidyDensity 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 TidyDensity?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. gdverse and TidyDensity 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 TidyDensity?
Top TidyDensity alternatives in Analytics are ranked by recent ship velocity. Browse the "TidyDensity alternatives" section above for the current picks, or visit /alternatives/tidydensity for the full list with editorial commentary on each.