soilDBdata
soilDBdata exists so soilDB's tests can run without a NASIS connection.
Comparison · Analytics
invasimapr vs medrobust
A side-by-side editorial comparison of invasimapr and medrobust — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r package
invasimapr vs medrobust: 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 medrobust?
medrobust made its partial-identification bounds usable by giving them confidence intervals.
medrobust computes partial-identification bounds for mediation effects when exposure or mediator is differentially misclassified, part of the Data-Wise mediationverse. Its 0.2.0 release corrected three estimator defects against population oracles and added Imbens-Manski confidence intervals for the bounds; the two releases since have paired each identification path with a real public-domain dataset and a worked vignette. CRAN is deferred, with distribution through GitHub and r-universe.
invasimapr vs medrobust: 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.
medrobust
0.0ANALYTICS
medrobust made its partial-identification bounds usable by giving them confidence intervals.
◆ Current state
medrobust computes partial-identification bounds for mediation effects when exposure or mediator is differentially misclassified, part of the Data-Wise mediationverse. Its 0.2.0 release corrected three estimator defects against population oracles and added Imbens-Manski confidence intervals for the bounds; the two releases since have paired each identification path with a real public-domain dataset and a worked vignette. CRAN is deferred, with distribution through GitHub and r-universe.
◆ Where it's heading
The pattern is deliberate and symmetric: 0.3.0 shipped the mediator-side example on NCHS natality data, 0.4.0 its exposure-side mirror on NHANES, each demonstrating what the bounds do when reporting accuracy is allowed to depend on the outcome. Alongside that runs a consistent concern with failing usefully rather than loudly — bound_ne() returns NA bounds with a machine-readable reason and a typed condition instead of aborting, so a simulation replicate is recorded rather than lost, and non-finite endpoint standard errors produce a documented NA rather than a silent one. That is a package expecting to be run thousands of times inside someone else's loop.
◆ Prediction
Both identification paths now have a dataset, a vignette and interval coverage, so the next release is most likely the deferred CRAN submission rather than new methodology.
Alternatives to invasimapr and medrobust
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 medrobust.
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.
scTypeEval
scTypeEval judges single-cell annotations without needing a ground truth to judge them against.
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 medrobust alternatives →
Recent activity from invasimapr and medrobust
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
- 2mo agomedrobustNHANES exposure-side misclassification example dataset
- 2mo agomedrobustNatality example dataset; bounds degrade instead of aborting
- 2mo agomedrobustBounds corrected against oracles; Imbens-Manski intervals added ⚡
Frequently asked questions
What is the difference between invasimapr and medrobust?
Both compete on the same themes — r package — within Analytics. invasimapr and medrobust 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 medrobust?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. invasimapr and medrobust 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 medrobust?
Top medrobust alternatives in Analytics are ranked by recent ship velocity. Browse the "medrobust alternatives" section above for the current picks, or visit /alternatives/medrobust for the full list with editorial commentary on each.