simlandr
Potential landscape tooling settling onto standard R generics after two rounds of renaming.
Comparison · Analytics
invasimapr vs vinereg
A side-by-side editorial comparison of invasimapr and vinereg — release velocity, themes, recent moves, and the top alternatives to consider.
invasimapr vs vinereg: 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 vinereg?
Conditional density and log-likelihood fill out a vine copula regression package.
vinereg fits D-vine copula-based regression models on top of rvinecopulib and kde1d, in Thomas Nagler's package stack. The January 2025 pair - 0.10.0 and 0.11.0 tagged the same day - adds a pdf() function and then fixes conditional density computation for discrete variables while requiring the newer kde1d. Release notes run to one or two bullets each.
invasimapr vs vinereg: 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.
vinereg
0.0ANALYTICS
Conditional density and log-likelihood fill out a vine copula regression package.
◆ Current state
vinereg fits D-vine copula-based regression models on top of rvinecopulib and kde1d, in Thomas Nagler's package stack. The January 2025 pair - 0.10.0 and 0.11.0 tagged the same day - adds a pdf() function and then fixes conditional density computation for discrete variables while requiring the newer kde1d. Release notes run to one or two bullets each.
◆ Where it's heading
Work has concentrated on evaluation rather than fitting: cll() in 0.9.0, pdf() in 0.10.0, and the discrete-variable correction in 0.11.0 all concern what can be computed from a model already fitted. Releases arrive in same-day pairs, and the notes are terse enough that 0.10.0 reuses 0.9.0's wording verbatim, describing pdf() with cll()'s sentence. Version floors also track the sibling packages - kde1d here, rvinecopulib in 0.8.3.
◆ Prediction
Given the shared release rhythm across the stack, the next entry is as likely to be a dependency-driven bump as a new function; the discrete-variable path is the one area these notes show as recently unstable.
Alternatives to invasimapr and vinereg
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 vinereg.
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.
stringx
A drop-in string API for base R, kept alive by upstream check failures.
healthyR.data
From a bundled hospital dataset to a live CMS API client.
See all invasimapr alternatives → · See all vinereg alternatives →
Recent activity from invasimapr and vinereg
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 agovineregDiscrete conditional densities fixed; kde1d 1.1.0 required
- 1y agovineregpdf() added for conditional density
- 2y agovineregBoost compile flag and a weights error fixed
- 2y agovineregcll() computes conditional log-likelihood
- 4y agovineregvinecopulib floor raised for RcppThread compatibility
- 4y agovineregcpit() fixed and external marginals allowed via uscale
Frequently asked questions
What is the difference between invasimapr and vinereg?
They serve adjacent needs but don't currently overlap on shipped themes. invasimapr and vinereg 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 vinereg?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. invasimapr and vinereg 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 vinereg?
Top vinereg alternatives in Analytics are ranked by recent ship velocity. Browse the "vinereg alternatives" section above for the current picks, or visit /alternatives/vinereg for the full list with editorial commentary on each.