compositional.mle
An MLE package rebuilt around composable solvers, then renamed to match.
A side-by-side editorial comparison of hubUtils and mritc — release velocity, themes, recent moves, and the top alternatives to consider.
The hubverse's shared plumbing, tracking schema versions and converting output types.
hubUtils is the low-level dependency the rest of the hubverse builds on: schema version tracking, config file reading, example test hubs, and conversion between forecast output types. Its releases are small and cadenced to the hubverse schema itself, with a version bump arriving whenever the config schema advances. The recent work is performance rather than surface.
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.
hubUtils is the low-level dependency the rest of the hubverse builds on: schema version tracking, config file reading, example test hubs, and conversion between forecast output types. Its releases are small and cadenced to the hubverse schema itself, with a version bump arriving whenever the config schema advances. The recent work is performance rather than surface.
The through-line is that this package absorbs whatever the schema is doing — v5, then v6 with target-data configuration, each arriving with matching accessors and example hubs so the sibling packages can be tested against something real. convert_output_type() is the one piece of genuine computation here, and it has now been optimised by roughly an order of magnitude, suggesting it is being used at scales the original implementation did not anticipate. Everything else is accessors and fixtures.
Expect the next substantive release to track the next hubverse schema version, with any independent work concentrated on convert_output_type(), the only performance-sensitive function in the package.
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 hubUtils 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 hubUtils 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 hubUtils alternatives in Analytics are ranked by recent ship velocity. Browse the "hubUtils alternatives" section above for the current picks, or visit /alternatives/hubutils 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.