simlandr
Potential landscape tooling settling onto standard R generics after two rounds of renaming.
A side-by-side editorial comparison of impIndicator and vinereg — release velocity, themes, recent moves, and the top alternatives to consider.
Biodiversity impact indicators settle their vocabulary before 1.0
impIndicator computes indicators of alien-species impact from GBIF-style occurrence cubes, producing species-level, site-level and regional measures with visualisation. The latest release renames the three headline functions to compute_species_indicator(), compute_site_indicator() and compute_regional_indicator(), drops the division by total occupied sites, and fixes the exponential transformation of impact categories into scores. It is part of the b-cubed-eu family and leans on sibling tooling rather than reimplementing it.
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.
impIndicator computes indicators of alien-species impact from GBIF-style occurrence cubes, producing species-level, site-level and regional measures with visualisation. The latest release renames the three headline functions to compute_species_indicator(), compute_site_indicator() and compute_regional_indicator(), drops the division by total occupied sites, and fixes the exponential transformation of impact categories into scores. It is part of the b-cubed-eu family and leans on sibling tooling rather than reimplementing it.
Two threads run through the recent releases. One is uncertainty: 0.6.0 wires in dubicube for cross-validation and uncertainty estimation on the indicators, moving output from point estimates toward quantified confidence. The other is scoping and naming — user-supplied sf regions in 0.4.0, occurrence-cube construction in 0.5.0, then the 0.6.1 rename — the pattern of a package tightening its public vocabulary as it approaches a stable release.
With the naming settled and uncertainty estimation in place, the next step is most likely consolidation toward a 1.0 — documentation and vignettes against the renamed functions rather than further indicator types.
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.
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.
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.
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 impIndicator or vinereg.
Potential landscape tooling settling onto standard R generics after two rounds of renaming.
SEM reporting helpers converging on APA output, one CRAN resubmission at a time.
A raster-to-terra migration is the only readable change in a feed of merge notes.
A nycflights13 generator whose recent work is all about the data being right.
A drop-in string API for base R, kept alive by upstream check failures.
From a bundled hospital dataset to a live CMS API client.
See all impIndicator alternatives → · See all vinereg alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Analytics. impIndicator 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. impIndicator 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.
Top impIndicator alternatives in Analytics are ranked by recent ship velocity. Browse the "impIndicator alternatives" section above for the current picks, or visit /alternatives/impindicator for the full list with editorial commentary on each.
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.