simlandr
Potential landscape tooling settling onto standard R generics after two rounds of renaming.
A side-by-side editorial comparison of eiaapi and svines — release velocity, themes, recent moves, and the top alternatives to consider.
A thin EIA energy-data client whose whole story is making bulk queries survive the API's limits.
eiaapi wraps the US Energy Information Administration API: eia_get() issues a single query, and eia_backfill() decomposes a large date range into chunks the API will actually serve. Three releases across two years cover the package's entire history, and the second and third both exist because of eia_backfill().
Stationary vine copulas for time series, released in lockstep with the rest of Nagler's vine stack.
svines fits stationary vine copula models to multivariate time series, extending the rvinecopulib engine with the serial dependence structure that makes vines usable for temporal data. The visible history is three releases carrying one real addition — pseudo-residual computation and logLik support at 0.2.2 — with the rest tracking its C++ dependency.
eiaapi wraps the US Energy Information Administration API: eia_get() issues a single query, and eia_backfill() decomposes a large date range into chunks the API will actually serve. Three releases across two years cover the package's entire history, and the second and third both exist because of eia_backfill().
The package's development is a single problem being worked: pulling more data than one request allows. Version 0.1.2 introduced eia_backfill() for exactly that, and 0.2.0 fixed it for non-hourly frequencies by adding the frequency and data arguments so it matches eia_get()'s interface and by reworking Date handling. That convergence of the two functions' signatures is the visible design direction — one query idiom regardless of range size.
With the two functions now taking aligned arguments, further work most plausibly extends coverage to more EIA endpoints or response shapes. The entries name no specific target.
svines fits stationary vine copula models to multivariate time series, extending the rvinecopulib engine with the serial dependence structure that makes vines usable for temporal data. The visible history is three releases carrying one real addition — pseudo-residual computation and logLik support at 0.2.2 — with the rest tracking its C++ dependency.
This package moves when rvinecopulib moves. The 0.2.4 release exists solely to adapt to a new rvinecopulib version, and 0.2.7 carries auto-generated GitHub release notes with no description at all. It shipped on the same day as kde1d 1.1.1, another package from the same maintainer, which is the pattern to watch: changes in the shared C++ layer surface as near-simultaneous releases across the vine family rather than as independent work.
The next release most plausibly follows another rvinecopulib update rather than adding modelling capability. Two of the three visible entries carry no substantive notes, so this feed will keep underreporting what changed.
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 eiaapi or svines.
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.
Conditional density and log-likelihood fill out a vine copula regression package.
A drop-in string API for base R, kept alive by upstream check failures.
See all eiaapi alternatives → · See all svines alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — time-series, r-package — within Analytics. eiaapi and svines 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. eiaapi and svines 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 eiaapi alternatives in Analytics are ranked by recent ship velocity. Browse the "eiaapi alternatives" section above for the current picks, or visit /alternatives/eiaapi for the full list with editorial commentary on each.
Top svines alternatives in Analytics are ranked by recent ship velocity. Browse the "svines alternatives" section above for the current picks, or visit /alternatives/svines for the full list with editorial commentary on each.