randomwalk
randomwalk spent every release getting an R simulation to run in the browser, not on a server.
A side-by-side editorial comparison of cubist and qtl2 — release velocity, themes, recent moves, and the top alternatives to consider.
The R port of Quinlan's Cubist gets reproducibility fixes, not new modelling
Cubist is the R interface to Quinlan's rule-based regression model, wrapping the original C sources behind an R API and feeding the tidymodels rules package. The 0.6.0 release adds a strip_time_stamps control that removes date, time and duration information from model output, and now errors rather than silently misbehaving when a date or date-time column is passed. Error reporting moves from base stop() and warning() to cli.
The standard QTL mapping package in R opened its genome scan to user-supplied likelihood models.
qtl2 is the R toolkit for QTL mapping in experimental crosses, covering genotype probability calculation, genome scans with and without polygenic effects, permutation testing, SNP association, and the plotting that goes with them. The last year of work has pushed hard in two directions: tooling for high-throughput expression and protein QTL studies, and a generalisation of the scan engine itself so the log-likelihood being maximised can be supplied by the user. Note that the release history reached this feed out of order, so feed position is not a reliable guide to which release came first.
Cubist is the R interface to Quinlan's rule-based regression model, wrapping the original C sources behind an R API and feeding the tidymodels rules package. The 0.6.0 release adds a strip_time_stamps control that removes date, time and duration information from model output, and now errors rather than silently misbehaving when a date or date-time column is passed. Error reporting moves from base stop() and warning() to cli.
The direction is custodial: this is a mature algorithm with a stable definition, so the work is making a decades-old C codebase behave predictably inside a modern R workflow. The reproducibility thread is the clearest one — embedded timestamps mean two identical models compare as different objects, which breaks caching, testing and any workflow that hashes results. Alongside it runs slow C hygiene, from keyword symbol overwrites in 0.5.0 to unused-variable warnings in 0.6.0.
Expect continued small maintenance releases tracking CRAN compiler requirements and the needs of the rules package, with no change to the modelling algorithm itself.
qtl2 is the R toolkit for QTL mapping in experimental crosses, covering genotype probability calculation, genome scans with and without polygenic effects, permutation testing, SNP association, and the plotting that goes with them. The last year of work has pushed hard in two directions: tooling for high-throughput expression and protein QTL studies, and a generalisation of the scan engine itself so the log-likelihood being maximised can be supplied by the user. Note that the release history reached this feed out of order, so feed position is not a reliable guide to which release came first.
The eQTL and pQTL direction is the clearest thread — cis-trans plots, hotspot counting over a sliding window, multi-trait scan heat maps, and genome-wide genotype plots all arrived together, which is the toolkit an experiment with thousands of traits needs rather than one with a handful. Running underneath it is a steady generalisation of the core: a scan function that accepts an arbitrary likelihood, permutations that work with alternative scan functions, full variance-covariance output from single-position fits. Performance and parallelism get attention each cycle, including a more considerate default that leaves one core free. The rest is the ordinary maintenance of a long-lived package — renames to avoid tidyverse collisions, compiler warnings, and correctness fixes on specific cross types.
With scan1gen and permutation support for alternative scan functions in place, the natural next step is more model types built on that hook rather than more special-cased scan functions; the entries do not indicate which models are planned.
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 cubist or qtl2.
randomwalk spent every release getting an R simulation to run in the browser, not on a server.
fastml added survival modelling and leakage-proof resampling, moving past classification and regression.
abclass built out angle-based classifiers in 2022, then went quiet except for CRAN upkeep.
churon is spending its entire release history getting a Rust ONNX binding through CRAN.
firatheme woke up after four years and started fixing what ggplot2 changed underneath it.
bagyo reached CRAN as a Philippine tropical cyclone dataset, with its tags stamped out of order.
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Analytics. qtl2 is currently shipping more aggressively (velocity 2.5 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. qtl2 is currently shipping more aggressively (velocity 2.5 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 cubist alternatives in Analytics are ranked by recent ship velocity. Browse the "cubist alternatives" section above for the current picks, or visit /alternatives/cubist for the full list with editorial commentary on each.
Top qtl2 alternatives in Analytics are ranked by recent ship velocity. Browse the "qtl2 alternatives" section above for the current picks, or visit /alternatives/qtl2 for the full list with editorial commentary on each.