soilDBdata
soilDBdata exists so soilDB's tests can run without a NASIS connection.
Comparison · Analytics
invasimapr vs scTypeEval
A side-by-side editorial comparison of invasimapr and scTypeEval — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r package
invasimapr vs scTypeEval: 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 scTypeEval?
scTypeEval judges single-cell annotations without needing a ground truth to judge them against.
scTypeEval evaluates the consistency of single-cell cell type annotations without a ground-truth reference, using pseudobulk distances, Wasserstein distances and reciprocal classification as alternative dissimilarity strategies. It cleared Bioconductor's submission process on its first cycle, moving from a 0.99.30 pre-release in April 2026 to version 1.0.0 in the Bioconductor 3.23 release a month later. It accepts matrix, Seurat and SingleCellExperiment inputs.
invasimapr vs scTypeEval: 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.
scTypeEval
0.0ANALYTICS
scTypeEval judges single-cell annotations without needing a ground truth to judge them against.
◆ Current state
scTypeEval evaluates the consistency of single-cell cell type annotations without a ground-truth reference, using pseudobulk distances, Wasserstein distances and reciprocal classification as alternative dissimilarity strategies. It cleared Bioconductor's submission process on its first cycle, moving from a 0.99.30 pre-release in April 2026 to version 1.0.0 in the Bioconductor 3.23 release a month later. It accepts matrix, Seurat and SingleCellExperiment inputs.
◆ Where it's heading
The visible history is short and shaped entirely by the Bioconductor pipeline — the 0.99.x series is that project's submission convention, and 1.0.0 is what acceptance looks like rather than a maturity claim by the authors. What the pre-release notes emphasise is breadth of input format and of dissimilarity strategy rather than a single recommended method, which suggests the package is positioned as a comparison harness rather than a scoring tool. Nothing in these two entries indicates work beyond getting accepted.
◆ Prediction
With only a submission cycle in the record, there is not enough here to predict a direction; the next release will most likely be whatever the Bioconductor 3.24 cycle requires, and the first post-acceptance release is what will show whether development continues.
Alternatives to invasimapr and scTypeEval
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 scTypeEval.
collinear
collinear has broken its API twice to stop making the user pick thresholds.
nert
nert put fourteen TERN datasets behind one dispatcher and called it stable.
medrobust
medrobust made its partial-identification bounds usable by giving them confidence intervals.
probmed
probmed went from one probabilistic effect size to a family of them in sixteen days.
fluxnet-package
fluxnet keeps swapping its own plumbing — first a Python downloader, now a DuckDB backend.
See all invasimapr alternatives → · See all scTypeEval alternatives →
Recent activity from invasimapr and scTypeEval
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 agoscTypeEvalAccepted into the Bioconductor 3.23 release
- 4mo agoscTypeEvalBioconductor pre-release: ground-truth-agnostic annotation evaluation
Frequently asked questions
What is the difference between invasimapr and scTypeEval?
Both compete on the same themes — r package — within Analytics. invasimapr and scTypeEval 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 scTypeEval?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. invasimapr and scTypeEval 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 scTypeEval?
Top scTypeEval alternatives in Analytics are ranked by recent ship velocity. Browse the "scTypeEval alternatives" section above for the current picks, or visit /alternatives/sctypeeval for the full list with editorial commentary on each.