fillpattern
Pattern fills for ggplot2, hardened against the ways users write sizes
Comparison · Analytics
ecodive vs invasimapr
A side-by-side editorial comparison of ecodive and invasimapr — release velocity, themes, recent moves, and the top alternatives to consider.
ecodive vs invasimapr: at a glance
What is ecodive?
ecodive rebuilt itself into a broad diversity-metric library, breaking as it went
ecodive computes alpha and beta diversity metrics for ecological and microbiome count data, including phylogenetic measures like Faith's PD and the UniFrac family. The 2.0.0 rewrite expanded it from a handful of metrics to roughly fourteen alpha and thirty beta measures while flipping the expected input orientation to samples-as-rows. Subsequent releases have been spent settling the normalisation interface that expansion exposed.
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.
ecodive vs invasimapr: editorial side-by-side
ecodive
0.0ANALYTICS
ecodive rebuilt itself into a broad diversity-metric library, breaking as it went
◆ Current state
ecodive computes alpha and beta diversity metrics for ecological and microbiome count data, including phylogenetic measures like Faith's PD and the UniFrac family. The 2.0.0 rewrite expanded it from a handful of metrics to roughly fourteen alpha and thirty beta measures while flipping the expected input orientation to samples-as-rows. Subsequent releases have been spent settling the normalisation interface that expansion exposed.
◆ Where it's heading
This is a package that made its breaking changes deliberately and in a cluster. After 2.0.0 reoriented input and removed the weighted parameter, 2.1.0 superseded rescale with norm, and 2.2.6 changed norm's default from percent to none and removed it from some beta functions entirely. That last one matters more than it reads: normalisation defaults silently change the numbers a metric returns, and the direction is toward making the user state their choice rather than inheriting one.
◆ Prediction
With the metric surface broad and the normalisation interface now explicit, expect the next releases to stabilise — documentation and edge-case handling around CLR and rarefaction rather than another interface break.
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.
Alternatives to ecodive and invasimapr
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 ecodive or invasimapr.
gcube
gcube's recent releases are all packaging metadata, not simulation code
cubist
The R port of Quinlan's Cubist gets reproducibility fixes, not new modelling
ggstats
ggstats keeps widening what a coefficient or Likert plot can be
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
See all ecodive alternatives → · See all invasimapr alternatives →
Recent activity from ecodive and invasimapr
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
- 4mo agoecodiveNormalisation now defaults to none, with CLR zero warnings
- 7mo agoecodiveecodive 2.2.2
- 10mo agoecodiverescale superseded by norm; crash fixes after the 2.0.0 rewrite
- 10mo agoecodive2.0.0 expands to ~14 alpha and ~30 beta diversity metrics ⚡
Frequently asked questions
What is the difference between ecodive and invasimapr?
They serve adjacent needs but don't currently overlap on shipped themes. ecodive and invasimapr 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 ecodive better than invasimapr?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. ecodive and invasimapr 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 ecodive?
Top ecodive alternatives in Analytics are ranked by recent ship velocity. Browse the "ecodive alternatives" section above for the current picks, or visit /alternatives/ecodive for the full list with editorial commentary on each.
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.