bootStateSpace
A parametric bootstrap for state-space models, shipped and then left alone.
A side-by-side editorial comparison of impIndicator and randomwalk — release velocity, themes, recent moves, and the top alternatives to consider.
Biodiversity impact indicators settle their vocabulary before 1.0
impIndicator computes indicators of alien-species impact from GBIF-style occurrence cubes, producing species-level, site-level and regional measures with visualisation. The latest release renames the three headline functions to compute_species_indicator(), compute_site_indicator() and compute_regional_indicator(), drops the division by total occupied sites, and fixes the exponential transformation of impact categories into scores. It is part of the b-cubed-eu family and leans on sibling tooling rather than reimplementing it.
randomwalk spent every release getting an R simulation to run in the browser, not on a server.
A random walk and fractal-growth simulation package whose entire visible history is about its browser deployment. Six releases in four weeks moved a Shinylive dashboard from a blank black page to a working app — WebAssembly mounted from GitHub releases, CORS resolved by same-origin serving, missing plotting dependencies installed in-browser, then an async version using crew workers with its own debug log. A correctness fix followed, adding termination-position validation so simulations stop producing isolated pixels, and the most recent release publishes the package itself as a webR binary repository.
impIndicator computes indicators of alien-species impact from GBIF-style occurrence cubes, producing species-level, site-level and regional measures with visualisation. The latest release renames the three headline functions to compute_species_indicator(), compute_site_indicator() and compute_regional_indicator(), drops the division by total occupied sites, and fixes the exponential transformation of impact categories into scores. It is part of the b-cubed-eu family and leans on sibling tooling rather than reimplementing it.
Two threads run through the recent releases. One is uncertainty: 0.6.0 wires in dubicube for cross-validation and uncertainty estimation on the indicators, moving output from point estimates toward quantified confidence. The other is scoping and naming — user-supplied sf regions in 0.4.0, occurrence-cube construction in 0.5.0, then the 0.6.1 rename — the pattern of a package tightening its public vocabulary as it approaches a stable release.
With the naming settled and uncertainty estimation in place, the next step is most likely consolidation toward a 1.0 — documentation and vignettes against the renamed functions rather than further indicator types.
A random walk and fractal-growth simulation package whose entire visible history is about its browser deployment. Six releases in four weeks moved a Shinylive dashboard from a blank black page to a working app — WebAssembly mounted from GitHub releases, CORS resolved by same-origin serving, missing plotting dependencies installed in-browser, then an async version using crew workers with its own debug log. A correctness fix followed, adding termination-position validation so simulations stop producing isolated pixels, and the most recent release publishes the package itself as a webR binary repository.
The package is being built as a browser artifact first and an R package second: the readme, the vignettes and the release notes all point at a hosted dashboard rather than at library(). The last release completes that by making the compiled WebAssembly build installable by anyone via webr::install(), which turns the deployment work into something reusable outside this project. Version numbers are unreliable here — v0.2.0 was published two weeks after v1.0.2 — so read the dates, not the tags.
With the webR repository published, the next work most likely moves back to the simulation itself, though the entries give no direct evidence of planned features.
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 impIndicator or randomwalk.
A parametric bootstrap for state-space models, shipped and then left alone.
A Brazilian housing-data palette package went from internal tooling to public 1.0 in five days.
The bridge between Stata/SPSS labelled data and tidy R keeps widening, one integration at a time.
flashlight hit 1.0 by giving away its SHAP feature and making most of its API internal.
A palette generator became a palette platform — and changed the metric behind every color it picks.
An extreme-value toolkit reorganised its whole API into prefixed families and tripled its estimator count.
See all impIndicator alternatives → · See all randomwalk alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. impIndicator and randomwalk 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. impIndicator and randomwalk 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 impIndicator alternatives in Analytics are ranked by recent ship velocity. Browse the "impIndicator alternatives" section above for the current picks, or visit /alternatives/impindicator for the full list with editorial commentary on each.
Top randomwalk alternatives in Analytics are ranked by recent ship velocity. Browse the "randomwalk alternatives" section above for the current picks, or visit /alternatives/randomwalk for the full list with editorial commentary on each.