simlandr
Potential landscape tooling settling onto standard R generics after two rounds of renaming.
Comparison · Analytics
invasimapr vs kde1d
A side-by-side editorial comparison of invasimapr and kde1d — release velocity, themes, recent moves, and the top alternatives to consider.
invasimapr vs kde1d: 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 kde1d?
A univariate density estimator that added zero-inflated data and reopened its C++ API to do it.
kde1d estimates univariate densities with local polynomial kernel methods, handling bounded, discrete and now zero-inflated variables through a single type argument, with the numerical work in a header-only C++ library usable outside R. Version 1.1.0 added the zero-inflated discrete-continuous mixture case and shipped a new C++ API as an explicit breaking change; 1.1.1 followed in June with auto-generated notes and no description.
invasimapr vs kde1d: 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.
kde1d
0.0ANALYTICS
A univariate density estimator that added zero-inflated data and reopened its C++ API to do it.
◆ Current state
kde1d estimates univariate densities with local polynomial kernel methods, handling bounded, discrete and now zero-inflated variables through a single type argument, with the numerical work in a header-only C++ library usable outside R. Version 1.1.0 added the zero-inflated discrete-continuous mixture case and shipped a new C++ API as an explicit breaking change; 1.1.1 followed in June with auto-generated notes and no description.
◆ Where it's heading
The package has alternated between performance work and widening the class of data it accepts. The 1.0.0 release was the performance milestone — FFT-based estimation, a better integration algorithm for the p, q and r functions, deterministic jittering replacing randomness, and standalone C++ headers. The 1.1.0 release is the scope milestone, adding a third data type to the two it already handled. Releases come from the same maintainer as svines and cluster on shared dates, so changes in the underlying C++ surface across the vine and density stack tend to ship together.
◆ Prediction
With the C++ API deliberately reworked for standalone use at 1.1.0, further work most plausibly consolidates that interface rather than adding data types. What 1.1.1 actually changed is not readable from its body.
Alternatives to invasimapr and kde1d
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 kde1d.
lavaanExtra
SEM reporting helpers converging on APA output, one CRAN resubmission at a time.
ibis.iSDM
A raster-to-terra migration is the only readable change in a feed of merge notes.
anyflights
A nycflights13 generator whose recent work is all about the data being right.
vinereg
Conditional density and log-likelihood fill out a vine copula regression package.
stringx
A drop-in string API for base R, kept alive by upstream check failures.
See all invasimapr alternatives → · See all kde1d alternatives →
Recent activity from invasimapr and kde1d
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
- 1y agokde1dkde1d 1.1.1
- 1y agokde1dZero-inflated mixtures and a new standalone C++ API ⚡
- 4y agokde1dBit-wise Boolean operations removed
- 5y agokde1ddkde1d() invisible output fixed
- 5y agokde1dValgrind false positive silenced
- 6y agokde1dqrng dependency dropped; undefined behaviour fixed
Frequently asked questions
What is the difference between invasimapr and kde1d?
They serve adjacent needs but don't currently overlap on shipped themes. invasimapr and kde1d 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 kde1d?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. invasimapr and kde1d 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 kde1d?
Top kde1d alternatives in Analytics are ranked by recent ship velocity. Browse the "kde1d alternatives" section above for the current picks, or visit /alternatives/kde1d for the full list with editorial commentary on each.