compositional.mle
An MLE package rebuilt around composable solvers, then renamed to match.
A side-by-side editorial comparison of hubData and mritc — release velocity, themes, recent moves, and the top alternatives to consider.
The Arrow data layer for forecast hubs, spending its releases on cloud and materialisation bugs.
hubData is the access layer for hubverse forecasting hubs, connecting to local and cloud-stored model output through Arrow and handing back lazy connections or materialised tibbles. Its releases divide sharply between schema and utility additions in the 1.x line and, more recently, a run of defect fixes in the cloud and Arrow integration. Two of those fixes involved data being silently wrong rather than an error being raised.
A dormant MRI tissue-classification package revived under a new maintainer.
mritc performs MRI tissue classification in R using Gaussian mixture and hidden Markov models. After a long dormancy it changed hands to a new maintainer, and the three releases in this window all land within weeks of each other — two of them seconds apart, a backfill of the handover release alongside the first substantive one. The work so far is modernisation rather than new methodology.
hubData is the access layer for hubverse forecasting hubs, connecting to local and cloud-stored model output through Arrow and handing back lazy connections or materialised tibbles. Its releases divide sharply between schema and utility additions in the 1.x line and, more recently, a run of defect fixes in the cloud and Arrow integration. Two of those fixes involved data being silently wrong rather than an error being raised.
The package has largely finished adding surface and is now paying down the cost of sitting on top of Arrow and S3: ALTREP-backed columns escaping into user sessions, cloud hubs whose declared format differs from what is actually written, and metadata arrays parsing inconsistently. Each fix narrows the gap between what the storage layer does and what an R user expects. The performance-motivated default flip in 2.0.0 points the same way, prioritising large cloud hubs over conservative local behaviour.
Expect continued fixes at the Arrow and cloud boundary, particularly where declared hub configuration and actual stored format disagree, which has now produced defects twice.
mritc performs MRI tissue classification in R using Gaussian mixture and hidden Markov models. After a long dormancy it changed hands to a new maintainer, and the three releases in this window all land within weeks of each other — two of them seconds apart, a backfill of the handover release alongside the first substantive one. The work so far is modernisation rather than new methodology.
The clear direction is reducing what the package demands of the systems it installs on: heavyweight visualisation dependencies moved to optional, tkrplot dropped entirely, and the default plotting backend switched to a package already present in the dependency tree. A test suite and coverage tooling arrived where there had been none. The remaining releases are CRAN-check fallout from that restructuring, which is the expected shape of a revival.
Expect further consolidation under the new maintainer — CRAN check fixes and test coverage — before any change to the classification methods themselves.
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 hubData or mritc.
An MLE package rebuilt around composable solvers, then renamed to match.
nabla dropped its C++ engine to chase exact derivatives at any order.
Eight months from first release to keyring caching and workload identity.
A research-project workflow package where the interesting work is in the plumbing.
A cyclomatic complexity checker that ships once every couple of years, and lands when it does.
Extreme value sampling in pure upkeep mode, mostly answering to Rcpp and CRAN.
See all hubData alternatives → · See all mritc alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Analytics. mritc is currently shipping more aggressively (velocity 5.0 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. mritc is currently shipping more aggressively (velocity 5.0 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 hubData alternatives in Analytics are ranked by recent ship velocity. Browse the "hubData alternatives" section above for the current picks, or visit /alternatives/hubdata for the full list with editorial commentary on each.
Top mritc alternatives in Analytics are ranked by recent ship velocity. Browse the "mritc alternatives" section above for the current picks, or visit /alternatives/mritc for the full list with editorial commentary on each.