soilDBdata
soilDBdata exists so soilDB's tests can run without a NASIS connection.
Comparison · Analytics
clinify vs invasimapr
A side-by-side editorial comparison of clinify and invasimapr — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r package
clinify vs invasimapr: at a glance
What is clinify?
clinify is closing the gap between flextable defaults and regulatory table specs.
clinify shapes clinical trial tables into the Word deliverables regulatory submissions require, wrapping flextable and officer. Version 0.4.0 is on CRAN and is almost entirely typographic control: spanner rules that follow the header instead of hard-coded column numbers, header padding named for where the space actually sits, and explicit row pitch. The structural release was 0.3.0, which introduced document objects and broke three APIs to get there.
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.
clinify vs invasimapr: editorial side-by-side
clinify
2.5ANALYTICS
clinify is closing the gap between flextable defaults and regulatory table specs.
◆ Current state
clinify shapes clinical trial tables into the Word deliverables regulatory submissions require, wrapping flextable and officer. Version 0.4.0 is on CRAN and is almost entirely typographic control: spanner rules that follow the header instead of hard-coded column numbers, header padding named for where the space actually sits, and explicit row pitch. The structural release was 0.3.0, which introduced document objects and broke three APIs to get there.
◆ Where it's heading
The package is working through the places where flextable's defaults and a statistical reporting spec disagree, and the notes are unusually explicit about why each default is wrong — a cell's bottom border draws below its bottom padding, so space under a header moves the rule rather than opening a gap beneath it; flextable leaves rows at a nominal quarter inch when the spec names an exact pitch. Each addition is built to survive an organisation's own clinify_table_default() rather than assuming clinify's styling runs last.
◆ Prediction
Header, spanner and row-pitch control all landed together, so the next gap in the same series is title and footnote geometry — the remaining page furniture that 0.3.0's two-part split left roughly specified.
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 clinify 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 clinify or invasimapr.
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 clinify alternatives → · See all invasimapr alternatives →
Recent activity from clinify and invasimapr
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 15d agoclinifySpanner rules, header padding and exact row pitch
- 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
- 1y agoclinifyDocument objects: clindoc() and multi-table output ⚡
Frequently asked questions
What is the difference between clinify and invasimapr?
Both compete on the same themes — r package — within Analytics. clinify is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 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 clinify better than invasimapr?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. clinify is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 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 clinify?
Top clinify alternatives in Analytics are ranked by recent ship velocity. Browse the "clinify alternatives" section above for the current picks, or visit /alternatives/clinify 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.