HydroPortailStats
France's national flood statistics, ported out of Fortran and into R.
A side-by-side editorial comparison of bkmrhat and geocomplexity — release velocity, themes, recent moves, and the top alternatives to consider.
A parallel-chain helper for bkmr that has settled into pure upkeep.
bkmrhat wraps Bayesian kernel machine regression (bkmr) so users can run and diagnose multiple MCMC chains in parallel, then combine or continue them. The functional surface has been stable since 2022, when chain-combining picked up a low-memory path and a seed-collision bug was corrected. The most recent release adds only diagnostic metadata to the package description.
A spatial complexity package that shipped its method, then went quiet
geocomplexity computes geographical complexity from spatial dependence and configuration similarity across both vector and raster data, and uses it to build spatial weight matrices and a complexity-aware geographically weighted regression. That capability arrived complete in the 0.1.0 release of September 2024. The three releases since contain no functional change: a citation file, a dependency trim, one function moved out to a sibling package, and a maintainer surname correction.
bkmrhat wraps Bayesian kernel machine regression (bkmr) so users can run and diagnose multiple MCMC chains in parallel, then combine or continue them. The functional surface has been stable since 2022, when chain-combining picked up a low-memory path and a seed-collision bug was corrected. The most recent release adds only diagnostic metadata to the package description.
Three releases across five years, and the newest carries no user-facing change at all. The package is in maintenance: it does what it set out to do for bkmr users, and updates now arrive only when CRAN or an upstream dependency forces them.
Expect the next release to be another compliance or dependency-driven patch rather than new functionality; the entries show no in-progress feature work.
geocomplexity computes geographical complexity from spatial dependence and configuration similarity across both vector and raster data, and uses it to build spatial weight matrices and a complexity-aware geographically weighted regression. That capability arrived complete in the 0.1.0 release of September 2024. The three releases since contain no functional change: a citation file, a dependency trim, one function moved out to a sibling package, and a maintainer surname correction.
The package sits inside Wenbo Lyu's spatial statistics family, where shared functionality migrates into the common sdsfun package rather than being duplicated across dependents. moran_test left geocomplexity for sdsfun in 0.2.0, which is the same consolidation pattern visible across the author's other packages. What remains here is the method-specific surface, and it has not changed in eighteen months.
The entries give no signal of planned functional work; on this pattern the next release is as likely to be metadata or another function migration to sdsfun as anything user-visible.
Other Infra & APIs 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 bkmrhat or geocomplexity.
France's national flood statistics, ported out of Fortran and into R.
Sign, zero and narrative restrictions brought into the bsvars ecosystem.
Fast design-based estimators for experiments, coasting on CRAN patches.
The grammar of uncertainty visualization, now drawing the uncertainty in its own estimates.
IP address vectors for R that hit 1.0 and then went quiet.
A column-key toolkit for stitching decades of ecological field data into one table.
See all bkmrhat alternatives → · See all geocomplexity alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package, maintenance — within Infra & APIs. bkmrhat and geocomplexity 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. bkmrhat and geocomplexity 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 Infra & APIs products to evaluate alongside.
Top bkmrhat alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "bkmrhat alternatives" section above for the current picks, or visit /alternatives/bkmrhat for the full list with editorial commentary on each.
Top geocomplexity alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "geocomplexity alternatives" section above for the current picks, or visit /alternatives/geocomplexity for the full list with editorial commentary on each.