simlandr
Potential landscape tooling settling onto standard R generics after two rounds of renaming.
A side-by-side editorial comparison of healthyR.data and qtl2convert — release velocity, themes, recent moves, and the top alternatives to consider.
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.
A conversion utility in pure maintenance mode, tracking R-devel breakage release by release
qtl2convert is the format-shim of the R/qtl2 ecosystem: it moves genotype probabilities and genetic maps between DOQTL, R/qtl and R/qtl2 representations. The last three releases contain no new conversion functions at all — 0.32 fixed a C string comparison flagged by CRAN, 0.34 restored attribute-clearing that R-devel 4.7 changed underneath the package, and 0.36 adjusted parallel core defaults plus a test tweak. The functional surface has been stable since 0.26 added cross2_ril_to_genril().
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.
qtl2convert is the format-shim of the R/qtl2 ecosystem: it moves genotype probabilities and genetic maps between DOQTL, R/qtl and R/qtl2 representations. The last three releases contain no new conversion functions at all — 0.32 fixed a C string comparison flagged by CRAN, 0.34 restored attribute-clearing that R-devel 4.7 changed underneath the package, and 0.36 adjusted parallel core defaults plus a test tweak. The functional surface has been stable since 0.26 added cross2_ril_to_genril().
This is a package whose release cadence is driven by its dependencies, not its roadmap. Two of the last three releases exist purely because upstream R or CRAN's check suite moved; the maintainer responds within weeks and ships. The cores=0 change in 0.36 is the only user-visible behavior shift in over a year, and it landed simultaneously in sibling package qtl2fst — this is a maintainer-wide convention change, not a qtl2convert decision.
Expect the next release to be triggered by another R-devel or CRAN check change rather than a feature request, following the same pattern as 0.32 and 0.34.
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 healthyR.data or qtl2convert.
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 healthyR.data alternatives → · See all qtl2convert alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Analytics. healthyR.data and qtl2convert 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. healthyR.data and qtl2convert 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 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.
Top qtl2convert alternatives in Analytics are ranked by recent ship velocity. Browse the "qtl2convert alternatives" section above for the current picks, or visit /alternatives/qtl2convert for the full list with editorial commentary on each.