randomwalk
randomwalk spent every release getting an R simulation to run in the browser, not on a server.
A side-by-side editorial comparison of fitVARMxID and gdverse — release velocity, themes, recent moves, and the top alternatives to consider.
A VAR-model fitting package acquiring the standard R methods it launched without
fitVARMxID fits vector autoregressive models via OpenMx identification, and is one of several packages maintained by the jeksterslab account. Its recent releases are small and additive: confint() and plot() methods, a save function, and before that a documentation pass. The feed also carries automated build commits that are pure CI artifacts.
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.
fitVARMxID fits vector autoregressive models via OpenMx identification, and is one of several packages maintained by the jeksterslab account. Its recent releases are small and additive: confint() and plot() methods, a save function, and before that a documentation pass. The feed also carries automated build commits that are pure CI artifacts.
This is a package settling into R conventions rather than growing capability. Adding confint() and plot() is the standard-methods work most modeling packages do once the estimation core is stable — it signals the author considers the fitting side done. Cadence is roughly quarterly and the changes get smaller each time.
Further method coverage — summary(), predict(), or coef() — is the likely next step, since confint() and plot() are usually the first two of that set rather than the last.
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.
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 fitVARMxID or gdverse.
randomwalk spent every release getting an R simulation to run in the browser, not on a server.
fastml added survival modelling and leakage-proof resampling, moving past classification and regression.
abclass built out angle-based classifiers in 2022, then went quiet except for CRAN upkeep.
churon is spending its entire release history getting a Rust ONNX binding through CRAN.
firatheme woke up after four years and started fixing what ggplot2 changed underneath it.
bagyo reached CRAN as a Philippine tropical cyclone dataset, with its tags stamped out of order.
See all fitVARMxID alternatives → · See all gdverse alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. fitVARMxID is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. fitVARMxID is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 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.
Top fitVARMxID alternatives in Analytics are ranked by recent ship velocity. Browse the "fitVARMxID alternatives" section above for the current picks, or visit /alternatives/fitvarmxid for the full list with editorial commentary on each.
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.