churon
churon is spending its entire release history getting a Rust ONNX binding through CRAN.
Comparison · Analytics
cubist vs fect
A side-by-side editorial comparison of cubist and fect — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:reproducibilityr-package
cubist vs fect: at a glance
What is cubist?
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.
What is fect?
A counterfactual estimator turning itself into a platform for multiple estimands
fect implements counterfactual estimators for panel data with treatment effects — imputation-based fixed effects, interactive fixed effects, matrix completion. The 2026 releases move fast and bundle heavily: 2.1.0 rewrote complex fixed effect handling, 2.2.0 unified cross-validation under a single cv.method parameter and replaced method='gsynth' with an explicit time.component.from switch, 2.4.1 introduced a post-hoc estimand API, and 2.4.5 added group.fe for coarsened fixed effects plus a $sample slot exposing which cells entered estimation.
cubist vs fect: editorial side-by-side
cubist
0.0ANALYTICS
The R port of Quinlan's Cubist gets reproducibility fixes, not new modelling
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
Expect continued small maintenance releases tracking CRAN compiler requirements and the needs of the rules package, with no change to the modelling algorithm itself.
fect
0.0ANALYTICS
A counterfactual estimator turning itself into a platform for multiple estimands
◆ Current state
fect implements counterfactual estimators for panel data with treatment effects — imputation-based fixed effects, interactive fixed effects, matrix completion. The 2026 releases move fast and bundle heavily: 2.1.0 rewrote complex fixed effect handling, 2.2.0 unified cross-validation under a single cv.method parameter and replaced method='gsynth' with an explicit time.component.from switch, 2.4.1 introduced a post-hoc estimand API, and 2.4.5 added group.fe for coarsened fixed effects plus a $sample slot exposing which cells entered estimation.
◆ Where it's heading
The direction is separation of estimation from interpretation. Where the package once returned one effect from one fit, estimand() now dispatches typed estimands — ATT, cumulative ATT, APTT, log ATT — from any imputation fit, with effect() and att.cumu() soft-deprecated but byte-identical pending 3.0.0. Alongside that runs a transparency thread: the $sample matrix, out-of-sample comparison via fect_mspe(), and named component sources instead of opaque method aliases. The release notes are unusually precise about which results change and which do not.
◆ Prediction
The soft-deprecation notice names 3.0.0 as the removal point for effect() and att.cumu(), so a major release consolidating on the estimand() dispatcher is the clearly signposted next step.
Alternatives to cubist and fect
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 fect.
firatheme
firatheme woke up after four years and started fixing what ggplot2 changed underneath it.
bagyo
bagyo reached CRAN as a Philippine tropical cyclone dataset, with its tags stamped out of order.
rainette
rainette rebuilt its Reinert clustering in 0.2.0, tuned it in 0.3.0, and has coasted since.
questionr
questionr's survey helpers are finished; recent releases only keep pace with R-devel.
washdata
washdata is a fixed survey dataset; eight years of releases have changed only its packaging.
Recent activity from cubist and fect
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 2mo agofectAdds group.fe for coarsened fixed effects and a $sample slot
- 3mo agofectPost-hoc estimand API decouples estimands from the fit ⚡
- 4mo agofectUnified cross-validation and explicit control of time components
- 5mo agocubiststrip_time_stamps makes fitted models reproducible
- 7mo agofectRewrites complex fixed effect handling and fixes speed
- 9mo agocubistCubist 0.5.1
- 11mo agofectAdds heterogeneous treatment effect plots and caps default cores
- 1y agocubistCubist 0.5.0
- 2y agocubistCubist 0.4.4
- 4y agocubistCubist 0.4.0
Frequently asked questions
What is the difference between cubist and fect?
Both compete on the same themes — reproducibility, r-package — within Analytics. cubist and fect 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.
Is cubist better than fect?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. cubist and fect 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.
What are the best alternatives to cubist?
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.
What are the best alternatives to fect?
Top fect alternatives in Analytics are ranked by recent ship velocity. Browse the "fect alternatives" section above for the current picks, or visit /alternatives/fect for the full list with editorial commentary on each.