fillpattern
Pattern fills for ggplot2, hardened against the ways users write sizes
A side-by-side editorial comparison of cubist and reliagrowr — 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.
A reliability growth package put its models behind an MCP server for AI assistants to call.
ReliaGrowR fits reliability growth models to failure data — Crow-AMSAA and Duane, with maximum likelihood estimation, confidence bounds, prediction, and reliability demonstration test planning. The last year widened it well past growth curves into repairable systems: parametric non-homogeneous Poisson process fitting with automatic change point detection, non-parametric mean cumulative function estimation, and system exposure calculation. The most recent release adds goodness-of-fit statistics and exposes the package's functions as Model Context Protocol tools.
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.
ReliaGrowR fits reliability growth models to failure data — Crow-AMSAA and Duane, with maximum likelihood estimation, confidence bounds, prediction, and reliability demonstration test planning. The last year widened it well past growth curves into repairable systems: parametric non-homogeneous Poisson process fitting with automatic change point detection, non-parametric mean cumulative function estimation, and system exposure calculation. The most recent release adds goodness-of-fit statistics and exposes the package's functions as Model Context Protocol tools.
Two arcs run in parallel. The statistical one is a steady march from plotting a growth curve to modelling recurrent failures properly — segmented NHPP models that detect their own change points, Nelson-Aalen estimation, Cramér-von Mises and Kolmogorov-Smirnov statistics for judging the fits. The interface one is newer and more unusual: the package now ships an MCP server, and its sibling plotting package followed with one two weeks later, so this is a deliberate direction across the maintainer's reliability suite rather than a single experiment. Naming and S3 conventions were cleaned up early, which is what made a uniform tool surface plausible later.
Given the sibling packages moved to MCP within weeks of each other, the remaining tools in the suite are the obvious next candidates; on the statistical side, goodness-of-fit having just arrived suggests model comparison and selection helpers are the natural follow-on.
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 reliagrowr.
Pattern fills for ggplot2, hardened against the ways users write sizes
gcube's recent releases are all packaging metadata, not simulation code
ggstats keeps widening what a coefficient or Likert plot can be
ecodive rebuilt itself into a broad diversity-metric library, breaking as it went
State-space data simulation for R, filled in one function at a time
rollama turns a local-LLM wrapper into an instrument for reproducible annotation
See all cubist alternatives → · See all reliagrowr alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Analytics. cubist and reliagrowr are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). 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. cubist and reliagrowr are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). 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 reliagrowr alternatives in Analytics are ranked by recent ship velocity. Browse the "reliagrowr alternatives" section above for the current picks, or visit /alternatives/reliagrowr for the full list with editorial commentary on each.