lavaanExtra
SEM reporting helpers converging on APA output, one CRAN resubmission at a time.
A side-by-side editorial comparison of gdverse and simlandr — release velocity, themes, recent moves, and the top alternatives to consider.
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.
Potential landscape tooling settling onto standard R generics after two rounds of renaming.
simlandr builds potential landscape plots from simulations of dynamic systems, with barrier-height calculations and batch simulation grids. Its three substantive releases are all consolidation: parameters renamed, functions renamed, defaults removed. By 0.3.0 the bespoke accessors had been replaced by ggplot2's autolayer() and base summary(), and the package carried print, summary, and plot methods for its own classes.
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.
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.
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.
simlandr builds potential landscape plots from simulations of dynamic systems, with barrier-height calculations and batch simulation grids. Its three substantive releases are all consolidation: parameters renamed, functions renamed, defaults removed. By 0.3.0 the bespoke accessors had been replaced by ggplot2's autolayer() and base summary(), and the package carried print, summary, and plot methods for its own classes.
Every release trades a package-specific name for a conventional one - var and par became arg and ele, get_geom() became an autolayer() method, get_barrier_height() became a summary() method, hash_big.matrix became hash_big_matrix. The one methodological change, an adjusted minimal energy path algorithm, arrived inside a release otherwise full of renames. Removing default values for barrier calculation because they were often unsuitable reads as the maintainer deciding the defaults were doing harm.
The feed stops at 0.3.0 in late 2022, mid-consolidation; these entries give no indication of what followed, if anything did.
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 simlandr.
SEM reporting helpers converging on APA output, one CRAN resubmission at a time.
A raster-to-terra migration is the only readable change in a feed of merge notes.
A nycflights13 generator whose recent work is all about the data being right.
Conditional density and log-likelihood fill out a vine copula regression package.
A drop-in string API for base R, kept alive by upstream check failures.
From a bundled hospital dataset to a live CMS API client.
See all gdverse alternatives → · See all simlandr alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. gdverse and simlandr 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. gdverse and simlandr 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.
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.
Top simlandr alternatives in Analytics are ranked by recent ship velocity. Browse the "simlandr alternatives" section above for the current picks, or visit /alternatives/simlandr for the full list with editorial commentary on each.