← Back to home
Comparison · Analytics

mritc vs tidycmprsk

A side-by-side editorial comparison of mritc and tidycmprsk — release velocity, themes, recent moves, and the top alternatives to consider.

Shared themes:r-package

mritc vs tidycmprsk: at a glance

Featuremritctidycmprsk
SectorAnalyticsAnalytics
Velocity score5.00.0
Sparks · 30d00
Top themesmedical-imaging, r-package, maintainer-change, dependenciescompeting-risks, survival-analysis, tidyverse, gtsummary
Last editorial update1h ago45m ago
WebsiteVisit →Visit →

What is mritc?

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.

Read the full mritc trajectory →

What is tidycmprsk?

Competing-risks modelling that now moves only when its neighbours do.

tidycmprsk wraps competing risks regression and cumulative incidence estimation in tidy-style output, so results slot into gtsummary tables and ggsurvfit plots. The last two releases are small: 1.1.2 sorts tidy.tidycuminc() output by stratum, 1.1.1 is an HTML5 documentation update for CRAN. The substantive work in the window is 1.1.0, which reorganised the gtsummary relationship.

Read the full tidycmprsk trajectory →

mritc vs tidycmprsk: editorial side-by-side

M
mritc
ANALYTICS
5.0

A dormant MRI tissue-classification package revived under a new maintainer.

◆ Current state

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.

◆ Where it's heading

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.

◆ Prediction

Expect further consolidation under the new maintainer — CRAN check fixes and test coverage — before any change to the classification methods themselves.

T
tidycmprsk
ANALYTICS
0.0

Competing-risks modelling that now moves only when its neighbours do.

◆ Current state

tidycmprsk wraps competing risks regression and cumulative incidence estimation in tidy-style output, so results slot into gtsummary tables and ggsurvfit plots. The last two releases are small: 1.1.2 sorts tidy.tidycuminc() output by stratum, 1.1.1 is an HTML5 documentation update for CRAN. The substantive work in the window is 1.1.0, which reorganised the gtsummary relationship.

◆ Where it's heading

The package has spent its releases handing responsibilities to neighbouring packages rather than growing its own surface. Plotting was deprecated then made defunct in favour of ggsurvfit::ggcuminc(), and 1.1.0 moved the regression table methods so that gtsummary could drop tidycmprsk as a dependency. What remains is the estimation core plus the S3 methods that let other packages consume it, which is a deliberate narrowing.

◆ Prediction

Expect releases to continue tracking changes in gtsummary and the broader tidy survival stack rather than adding estimation features.

Alternatives to mritc and tidycmprsk

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 mritc or tidycmprsk.

See all mritc alternatives → · See all tidycmprsk alternatives →

Recent activity from mritc and tidycmprsk

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 12d agomritcBuffer overflow and OpenMP name clash resolved
  2. 23d agomritcVisualisation dependencies made optional, RNifti now the default
  3. 23d agomritcJon Clayden takes over maintenance; C-level GC protection added
  4. 4mo agotidycmprsktidycmprsk 1.1.2
  5. 9mo agotidycmprsktidycmprsk 1.1.1
  6. 1y agotidycmprsktidycmprsk 1.1.0
  7. 2y agotidycmprsktidycmprsk 1.0.0
  8. 3y agotidycmprsktidycmprsk 0.2.0
  9. 4y agotidycmprsktidycmprsk 0.1.2

Frequently asked questions

What is the difference between mritc and tidycmprsk?

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.

Is mritc better than tidycmprsk?

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.

What are the best alternatives to mritc?

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.

What are the best alternatives to tidycmprsk?

Top tidycmprsk alternatives in Analytics are ranked by recent ship velocity. Browse the "tidycmprsk alternatives" section above for the current picks, or visit /alternatives/tidycmprsk for the full list with editorial commentary on each.