soilDBdata
soilDBdata exists so soilDB's tests can run without a NASIS connection.
Comparison · Analytics
invasimapr vs medsim
A side-by-side editorial comparison of invasimapr and medsim — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:reproducibilityr package
invasimapr vs medsim: 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 medsim?
medsim is turning simulation runs into auditable artifacts, not just fast ones.
medsim is a young Monte Carlo harness for mediation-analysis simulation studies, first tagged in May 2026 and already at 0.5.1. The last two releases moved the package's center of gravity from running simulations to proving a run is trustworthy: chunk provenance headers, a single-SHA assertion across chunks, and a pilot-subset positive control. The statistical work sits in the missing-data line added in 0.2.0 — Fleishman non-normal generators, rate-calibrated MCAR/MAR/MNAR amputation, and a validated D4-stacked MBCO estimator.
invasimapr vs medsim: 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.
medsim
6.3ANALYTICS
medsim is turning simulation runs into auditable artifacts, not just fast ones.
◆ Current state
medsim is a young Monte Carlo harness for mediation-analysis simulation studies, first tagged in May 2026 and already at 0.5.1. The last two releases moved the package's center of gravity from running simulations to proving a run is trustworthy: chunk provenance headers, a single-SHA assertion across chunks, and a pilot-subset positive control. The statistical work sits in the missing-data line added in 0.2.0 — Fleishman non-normal generators, rate-calibrated MCAR/MAR/MNAR amputation, and a validated D4-stacked MBCO estimator.
◆ Where it's heading
The arc is toward defensible HPC runs: each 0.5.x gate closes a way a cluster job could silently produce wrong output, and 0.5.1 extends the same suspicion to the estimator itself by exposing the branch disagreement the standard ARIV averages away. Releases are cadenced against discovered defects rather than a roadmap — 0.5.0 cites seven findings from a pre-integration review, and 0.5.1 cites an adversarial review of 0.5.0. The audit surface is widening faster than the method surface.
◆ Prediction
The collapse-audit exclusion list has now been patched twice for method-specific diagnostic columns, so the next likely move is a contract letting methods declare their own discrete fields instead of medsim naming them centrally.
Alternatives to invasimapr and medsim
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 medsim.
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.
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.
See all invasimapr alternatives → · See all medsim alternatives →
Recent activity from invasimapr and medsim
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 7h agomedsimmedsim 0.5.1 — fixed-branch ARIV
- 16d agomedsimmedsim 0.5.0 — chunked-run integrity ⚡
- 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
- 1mo agomedsimseed= now honored in sequential fallback paths
- 2mo agomedsimDocs and dependency metadata synced to the 0.2.0 state
- 2mo agomedsimMissing-data mediation: amputation, non-normal DGMs, D4-MBCO ⚡
- 3mo agomedsimv0.1.1 — cleanup release
Frequently asked questions
What is the difference between invasimapr and medsim?
Both compete on the same themes — reproducibility, r package — within Analytics. medsim is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is invasimapr better than medsim?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. medsim is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 editorial sparks in the last 30 days against 0. 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 medsim?
Top medsim alternatives in Analytics are ranked by recent ship velocity. Browse the "medsim alternatives" section above for the current picks, or visit /alternatives/medsim for the full list with editorial commentary on each.