simlandr
Potential landscape tooling settling onto standard R generics after two rounds of renaming.
A side-by-side editorial comparison of tEDM and vinereg — release velocity, themes, recent moves, and the top alternatives to consider.
The temporal half of the stscl EDM pair, tracking its spatial sibling
tEDM applies empirical dynamic modeling to time series — cross mapping, convergent cross mapping and the logistic map — as the temporal counterpart to spEDM, with which it shares a maintainer and a C++ core. The recent releases are consolidation rather than expansion: index handling in cross mapping corrected, generics taught to accept varying E, k and tau, and the associated paper now cited in the README. Only three releases are visible in the feed.
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.
tEDM applies empirical dynamic modeling to time series — cross mapping, convergent cross mapping and the logistic map — as the temporal counterpart to spEDM, with which it shares a maintainer and a C++ core. The recent releases are consolidation rather than expansion: index handling in cross mapping corrected, generics taught to accept varying E, k and tau, and the associated paper now cited in the README. Only three releases are visible in the feed.
tEDM moves in lockstep with spEDM. Configurable distance metrics, varying E/k/tau inputs, strict floating-point comparison and the S3 plotting font unification all appear in both packages within days or weeks, as does the maintainer surname correction. The recent balance has tilted toward correcting library and prediction index handling — the kind of repeated attention that suggests the indexing model was the weak point of the shared core.
Expect tEDM to keep inheriting the shared-core changes spEDM lands, with its own releases staying small and centred on cross-mapping parameter handling rather than new method surface.
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 tEDM 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 tEDM 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. tEDM 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. tEDM 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 tEDM alternatives in Analytics are ranked by recent ship velocity. Browse the "tEDM alternatives" section above for the current picks, or visit /alternatives/tedm 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.