ecodive
ecodive rebuilt itself into a broad diversity-metric library, breaking as it went
Comparison · Analytics
invasimapr vs susier
A side-by-side editorial comparison of invasimapr and susier — release velocity, themes, recent moves, and the top alternatives to consider.
invasimapr vs susier: at a glance
What is invasimapr?
invasimapr halved its install size and became citable; the science stayed put.
invasimapr estimates species invasiveness and site invasibility from trait, environmental and resident-community data, exposing a traits → competition → invasion-fitness pipeline behind seven high-level wrappers. Its three releases are all packaging and standards work: a first citable archive in June 2026, then a maturity release bringing it in line with the B-Cubed software development guide. The one behavioral addition in that release is an opt-in standardise_inputs argument on compute_invasion_fitness(), off by default.
What is susier?
Fine-mapping workhorse susieR spends its releases hunting null-effect trimming bugs
susieR implements the Sum of Single Effects regression model for variable selection and fine-mapping, widely used in statistical genetics. The recent releases are a tight run of correctness work concentrated in one area: null effect trimming. Version 0.15.55 fixed trimming under the Servin-Stephens residual variance method, 0.15.56 fixed it again for non-uniform prior weights fourteen minutes later, 0.15.57 corrected an ELBO null space term for RSS with X and a matrix symmetry check, and 0.15.58 addressed an alpha0/beta0 issue. Version 0.16.0 migrates the C++ bindings from Rcpp to cpp11 with cpp11armadillo.
invasimapr vs susier: editorial side-by-side
invasimapr
0.0ANALYTICS
invasimapr halved its install size and became citable; the science stayed put.
◆ Current state
invasimapr estimates species invasiveness and site invasibility from trait, environmental and resident-community data, exposing a traits → competition → invasion-fitness pipeline behind seven high-level wrappers. Its three releases are all packaging and standards work: a first citable archive in June 2026, then a maturity release bringing it in line with the B-Cubed software development guide. The one behavioral addition in that release is an opt-in standardise_inputs argument on compute_invasion_fitness(), off by default.
◆ Where it's heading
The pressure is toward being installable and auditable rather than more capable — install slimmed from roughly 100 MB to 56 MB, R CMD check warnings and notes resolved, sp moved to Suggests, a Darwin Core-aligned data dictionary added, and a Zenodo concept DOI with CITATION.cff, codemeta.json and .zenodo.json. The package moves in lockstep with its B-Cubed sibling dissmapr, tagged within minutes of each other at both 0.1.0 and 0.2.1, which points at project-level standards deadlines rather than independent release decisions. Trait dispersion metrics and scenario exploration remain on the roadmap.
◆ Prediction
Standards compliance is now complete and the roadmap names functional trait dispersion metrics and scenario exploration tools, so the next release is the first that can plausibly be about invasion ecology rather than packaging.
susier
0.0ANALYTICS
Fine-mapping workhorse susieR spends its releases hunting null-effect trimming bugs
◆ Current state
susieR implements the Sum of Single Effects regression model for variable selection and fine-mapping, widely used in statistical genetics. The recent releases are a tight run of correctness work concentrated in one area: null effect trimming. Version 0.15.55 fixed trimming under the Servin-Stephens residual variance method, 0.15.56 fixed it again for non-uniform prior weights fourteen minutes later, 0.15.57 corrected an ELBO null space term for RSS with X and a matrix symmetry check, and 0.15.58 addressed an alpha0/beta0 issue. Version 0.16.0 migrates the C++ bindings from Rcpp to cpp11 with cpp11armadillo.
◆ Where it's heading
The version-number churn understates how narrow this work is — four consecutive releases touching the same trimming and residual-variance machinery suggests one area where the implementation and the intended behavior had drifted apart. The 0.16.0 binding migration is the only structural change, and it is invisible to users while mattering for build portability and long-term maintenance. Development is clearly active, with automated release tooling and dependency bumps flowing through the same stream.
◆ Prediction
With the binding migration just landed, near-term releases are likely to address fallout from it alongside continued fixes in the same trimming and residual-variance code.
Alternatives to invasimapr and susier
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 invasimapr or susier.
simStateSpace
State-space data simulation for R, filled in one function at a time
rollama
rollama turns a local-LLM wrapper into an instrument for reproducible annotation
ggmapinset
A ggplot2 inset-map extension that is now infrastructure for other packages
hoopr
hoopR rebuilds its HTTP layer on httr2 to stop segfaulting on modern systems
nswgeo
NSW boundary data for R, refreshed as the official sources move
See all invasimapr alternatives → · See all susier alternatives →
Recent activity from invasimapr and susier
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1mo agoinvasimaprVersion bump; notes identical to 0.2.0
- 1mo agoinvasimaprB-Cubed standards alignment; install slimmed to 56 MB
- 1mo agoinvasimaprinvasimapr v0.1.0: First citable release
- 3mo agosusierMigrates C++ bindings from Rcpp to cpp11 and cpp11armadillo
- 3mo agosusierFixes alpha0/beta0 handling under Servin-Stephens
- 4mo agosusierCorrects the null space ELBO term for RSS with X
- 5mo agosusierFixes null effect trimming with non-uniform prior weights
- 5mo agosusierFixes null effect trimming under Servin-Stephens estimation
Frequently asked questions
What is the difference between invasimapr and susier?
They serve adjacent needs but don't currently overlap on shipped themes. invasimapr and susier 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 invasimapr better than susier?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. invasimapr and susier 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 invasimapr?
Top invasimapr alternatives in Analytics are ranked by recent ship velocity. Browse the "invasimapr alternatives" section above for the current picks, or visit /alternatives/invasimapr for the full list with editorial commentary on each.
What are the best alternatives to susier?
Top susier alternatives in Analytics are ranked by recent ship velocity. Browse the "susier alternatives" section above for the current picks, or visit /alternatives/susier for the full list with editorial commentary on each.