compositional.mle
An MLE package rebuilt around composable solvers, then renamed to match.
A side-by-side editorial comparison of hubExamples and mritc — release velocity, themes, recent moves, and the top alternatives to consider.
Example data for the hubverse, moving whenever the standards it demonstrates move.
hubExamples ships the reference datasets that hubverse vignettes and downstream packages use to demonstrate forecast and target data. Its releases track the hubverse specification rather than any independent roadmap: 1.0.0 exists because the target time series standard changed, and 0.1.0 because the oracle output terminology did. The current release, 1.0.1, is a single fix for column deserialisation on systems without arrow.
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.
hubExamples ships the reference datasets that hubverse vignettes and downstream packages use to demonstrate forecast and target data. Its releases track the hubverse specification rather than any independent roadmap: 1.0.0 exists because the target time series standard changed, and 0.1.0 because the oracle output terminology did. The current release, 1.0.1, is a single fix for column deserialisation on systems without arrow.
This is a downstream member of the hubverse package family, alongside hubUtils, hubData and hubValidations, and it moves when they define something new. The pattern across all four entries is the same: a standard changes upstream, hubExamples updates its data objects and vignettes to match. Sibling package hubAdmin has not shipped since November 2025, so the cohort is not currently in a coordinated wave.
The next release will most likely follow the next hubverse data-standard revision rather than lead it.
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 hubExamples 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 hubExamples 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 hubExamples alternatives in Analytics are ranked by recent ship velocity. Browse the "hubExamples alternatives" section above for the current picks, or visit /alternatives/hubexamples 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.