simlandr
Potential landscape tooling settling onto standard R generics after two rounds of renaming.
A side-by-side editorial comparison of delaporte and healthyR.data — release velocity, themes, recent moves, and the top alternatives to consider.
A Fortran-backed Delaporte distribution package where every release is compiler and CRAN weather.
Delaporte supplies the density, distribution, quantile and random-generation functions for the Delaporte distribution — a Poisson-negative-binomial convolution used for overdispersed count data — implemented in Fortran and called through C. The only user-facing addition in the visible history is explicit OpenMP thread control via getDelapThreads() and setDelapThreads() at 8.2.0.
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.
Delaporte supplies the density, distribution, quantile and random-generation functions for the Delaporte distribution — a Poisson-negative-binomial convolution used for overdispersed count data — implemented in Fortran and called through C. The only user-facing addition in the visible history is explicit OpenMP thread control via getDelapThreads() and setDelapThreads() at 8.2.0.
The maintenance burden here is portability, not statistics. Recent entries track a Fortran suffix change for Intel compiler compatibility, architecture-specific test tolerances, type-safety corrections on values crossing the C-to-Fortran boundary, and a thread-count variable relocated from R options to an environment variable to follow an upstream R commit. The distribution functions themselves are settled; what changes is how the compiled code is built and checked across CRAN's platform matrix.
Expect the next release to follow another CRAN toolchain or Writing R Extensions policy change, as the last several have. Two of the four visible entries carry no notes at all, so this feed will keep understating what actually shipped.
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 delaporte 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 delaporte 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. delaporte and healthyR.data 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. delaporte and healthyR.data 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 delaporte alternatives in Analytics are ranked by recent ship velocity. Browse the "delaporte alternatives" section above for the current picks, or visit /alternatives/delaporte 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.