simlandr
Potential landscape tooling settling onto standard R generics after two rounds of renaming.
A side-by-side editorial comparison of fitVARMxID and healthyR.data — release velocity, themes, recent moves, and the top alternatives to consider.
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.
From a bundled hospital dataset to a live CMS API client.
healthyR.data supplies the data layer for the healthyverse packages. It began by shipping hospital data inside the package and now fetches from CMS and provider endpoints at call time through get_cms_meta_data(), fetch_cms_data(), and their provider counterparts. The most recent release is a single httr2 compatibility fix.
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.
healthyR.data supplies the data layer for the healthyverse packages. It began by shipping hospital data inside the package and now fetches from CMS and provider endpoints at call time through get_cms_meta_data(), fetch_cms_data(), and their provider counterparts. The most recent release is a single httr2 compatibility fix.
The 2023 release added roughly twenty current_*_data() accessors, one per CMS measure file - a wide but static surface. The 2024 releases replaced that approach with metadata lookup plus generic fetchers, then taught the fetchers to handle CSV, Excel, and ZIP payloads rather than API responses alone. The package's weight has moved from what it ships to what it can retrieve.
With the fetch layer generalised, the next visible work is more likely record-limit and error handling around httr2 than further per-measure accessors.
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 fitVARMxID or healthyR.data.
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 fitVARMxID alternatives → · See all healthyR.data alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — 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 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.
Top healthyR.data alternatives in Analytics are ranked by recent ship velocity. Browse the "healthyR.data alternatives" section above for the current picks, or visit /alternatives/healthyr-data for the full list with editorial commentary on each.