simlandr
Potential landscape tooling settling onto standard R generics after two rounds of renaming.
A side-by-side editorial comparison of eiaapi and fitVARMxID — 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().
A VAR-model fitting package acquiring the standard R methods it launched without
fitVARMxID fits vector autoregressive models via OpenMx identification, and is one of several packages maintained by the jeksterslab account. Its recent releases are small and additive: confint() and plot() methods, a save function, and before that a documentation pass. The feed also carries automated build commits that are pure CI artifacts.
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.
fitVARMxID fits vector autoregressive models via OpenMx identification, and is one of several packages maintained by the jeksterslab account. Its recent releases are small and additive: confint() and plot() methods, a save function, and before that a documentation pass. The feed also carries automated build commits that are pure CI artifacts.
This is a package settling into R conventions rather than growing capability. Adding confint() and plot() is the standard-methods work most modeling packages do once the estimation core is stable — it signals the author considers the fitting side done. Cadence is roughly quarterly and the changes get smaller each time.
Further method coverage — summary(), predict(), or coef() — is the likely next step, since confint() and plot() are usually the first two of that set rather than the last.
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 fitVARMxID.
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 fitVARMxID alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — time-series, r-package — within Analytics. fitVARMxID is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. 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. fitVARMxID is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. 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 fitVARMxID alternatives in Analytics are ranked by recent ship velocity. Browse the "fitVARMxID alternatives" section above for the current picks, or visit /alternatives/fitvarmxid for the full list with editorial commentary on each.