STACAS
Single-cell batch correction that learned to use cell labels, then spent three releases chasing Seurat.
Comparison · Analytics
gratia vs invasimapr
A side-by-side editorial comparison of gratia and invasimapr — release velocity, themes, recent moves, and the top alternatives to consider.
gratia vs invasimapr: at a glance
What is gratia?
The tidy front-end for GAMs, now stable enough that upstream ggplot2 sets its release calendar.
gratia wraps mgcv-fitted generalized additive models in tidy data frames and ggplot2 graphics — smooth_estimates(), fitted_values(), derivatives(), draw() and appraise() cover evaluation, prediction and diagnostics. The API reached its intended shape at 0.9.0, when every generated column was renamed to a dot-prefixed form, and 0.10.0 added conditional_values() for covariate-conditional prediction plots.
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.
gratia vs invasimapr: editorial side-by-side
gratia
0.0ANALYTICS
The tidy front-end for GAMs, now stable enough that upstream ggplot2 sets its release calendar.
◆ Current state
gratia wraps mgcv-fitted generalized additive models in tidy data frames and ggplot2 graphics — smooth_estimates(), fitted_values(), derivatives(), draw() and appraise() cover evaluation, prediction and diagnostics. The API reached its intended shape at 0.9.0, when every generated column was renamed to a dot-prefixed form, and 0.10.0 added conditional_values() for covariate-conditional prediction plots.
◆ Where it's heading
The package has moved through a long rewrite cycle and out the other side. Successive releases replaced evaluate_smooth() with smooth_estimates(), rebuilt draw() on top of it, then renamed the entire output vocabulary to avoid colliding with user variables. That work is finished; 0.11.1 is driven almost entirely by ggplot2 4.0.0 compatibility, with new mgcv family support for quantile residuals riding along. Development now tracks upstream breakage rather than internal redesign.
◆ Prediction
Expect the next releases to continue absorbing ggplot2 4.x and mgcv changes, with incremental family coverage in quantile_residuals() as the visible new work. The entries give no signal on which mgcv families come next.
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 gratia 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 gratia or invasimapr.
ggtrace
A debugger for ggplot2's internals, hardening its grip as the internals it traces keep moving.
kde1d
A univariate density estimator that added zero-inflated data and reopened its C++ API to do it.
svines
Stationary vine copulas for time series, released in lockstep with the rest of Nagler's vine stack.
gghighlight
A single-purpose ggplot2 extension that has spent six years tracking ggplot2 instead of growing.
rtrek
A Star Trek data package that became a Memory Alpha web client and has been patching scrapers ever since.
See all gratia alternatives → · See all invasimapr alternatives →
Recent activity from gratia 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
- 11mo agogratiaggplot2 4.0.0 compatibility, plus four more quantile-residual families
- 1y agogratiaconditional_values() replaces vis.gam for conditional prediction plots
- 2y agogratiaparametric_effects() joins the dot-prefix rename; LSS families begin
- 2y agogratiaEvery generated column gains a dot prefix ⚡
- 3y agogratiaReal variable names in smooth_samples(), plus dplyr 1.1.0 fixes
- 4y agogratiaM1 example output fixes and confint tibble returns
Frequently asked questions
What is the difference between gratia and invasimapr?
They serve adjacent needs but don't currently overlap on shipped themes. gratia 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 gratia better than invasimapr?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. gratia 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 gratia?
Top gratia alternatives in Analytics are ranked by recent ship velocity. Browse the "gratia alternatives" section above for the current picks, or visit /alternatives/gratia 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.