compositional.mle
An MLE package rebuilt around composable solvers, then renamed to match.
A side-by-side editorial comparison of kwb.geosalz and mritc — release velocity, themes, recent moves, and the top alternatives to consider.
A research-project workflow package where the interesting work is in the plumbing.
kwb.geosalz documents the data workflows for GeoSalz, a groundwater salinisation project run by Kompetenzzentrum Wasser Berlin, packaging retrieval, checking and plotting steps as reproducible R code. The current release replaces an SFTP dependency with curl and reports listing files on the SFTP server running 50 to 100 times faster. Earlier releases added data-availability workflows against Berlin's open water portal and functions for well-field abstraction figures.
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.
kwb.geosalz documents the data workflows for GeoSalz, a groundwater salinisation project run by Kompetenzzentrum Wasser Berlin, packaging retrieval, checking and plotting steps as reproducible R code. The current release replaces an SFTP dependency with curl and reports listing files on the SFTP server running 50 to 100 times faster. Earlier releases added data-availability workflows against Berlin's open water portal and functions for well-field abstraction figures.
Releases track the project's own data-collection reality rather than a software roadmap: new data source appears, a workflow is added; a transfer library becomes a liability, it is swapped out. The measurement-chain pipeline is the recurring subject, appearing in plotting fixes at 0.7.1 and the transport rewrite at 0.7.2. Cadence is roughly annual and the changelog is written for project members, which makes external readability secondary by design.
Expect the next release to follow the measurement-chain data as it accumulates, most likely more plotting or availability-checking work rather than new infrastructure.
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 kwb.geosalz 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 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.
A package retired in 2017 just got rewritten against R's public C API.
See all kwb.geosalz 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 kwb.geosalz alternatives in Analytics are ranked by recent ship velocity. Browse the "kwb.geosalz alternatives" section above for the current picks, or visit /alternatives/kwb-geosalz 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.