simlandr
Potential landscape tooling settling onto standard R generics after two rounds of renaming.
A side-by-side editorial comparison of cTMed and healthyR.data — release velocity, themes, recent moves, and the top alternatives to consider.
Continuous-time mediation effects get standardized centrality, six years into steady patch work
cTMed computes direct, indirect and total effects for continuous-time mediation models, with delta-method, Monte Carlo and bootstrap variants of each. Development is a long run of patch releases from the jeksterslab account, roughly every two months, each adding a function or two. The latest adds standardized centrality measures and allows a diagonal sigma across ten standardized estimators.
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.
cTMed computes direct, indirect and total effects for continuous-time mediation models, with delta-method, Monte Carlo and bootstrap variants of each. Development is a long run of patch releases from the jeksterslab account, roughly every two months, each adding a function or two. The latest adds standardized centrality measures and allows a diagonal sigma across ten standardized estimators.
The package is filling out a matrix rather than changing shape: for each effect type there is a delta-method, a Monte Carlo and a bootstrap path, and each release closes another cell. The 2025 releases were largely externally forced — an Armadillo 15.0.x transition at CRAN, a citation addition after the Psychological Methods paper landed — which suggests the statistical core has been settled since the 1.0.6 standardization revision.
The diagonal-sigma option has now reached the standardized estimators; extending it to the remaining unstandardized variants is the obvious next cell to fill.
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 cTMed 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 cTMed 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. cTMed 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. cTMed 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 cTMed alternatives in Analytics are ranked by recent ship velocity. Browse the "cTMed alternatives" section above for the current picks, or visit /alternatives/ctmed 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.