churon
churon is spending its entire release history getting a Rust ONNX binding through CRAN.
Comparison · Analytics
fect vs gcube
A side-by-side editorial comparison of fect and gcube — release velocity, themes, recent moves, and the top alternatives to consider.
fect vs gcube: at a glance
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.
What is gcube?
gcube's recent releases are all packaging metadata, not simulation code
gcube simulates biodiversity data cubes — generating occurrence points, sampling them under configurable detection bias, and designating them to a grid — as a testbed for the B-Cubed project's indicator tooling. The visible release history is almost entirely metadata and release-automation work: Zenodo grant IDs, ROR URL fixes, publisher fields, funder and rights-holder descriptions. The simulation functionality itself is not what these entries are about.
fect vs gcube: editorial side-by-side
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.
gcube
0.0ANALYTICS
gcube's recent releases are all packaging metadata, not simulation code
◆ Current state
gcube simulates biodiversity data cubes — generating occurrence points, sampling them under configurable detection bias, and designating them to a grid — as a testbed for the B-Cubed project's indicator tooling. The visible release history is almost entirely metadata and release-automation work: Zenodo grant IDs, ROR URL fixes, publisher fields, funder and rights-holder descriptions. The simulation functionality itself is not what these entries are about.
◆ Where it's heading
The February 2026 cluster reads as a package wiring up its archival identity rather than developing: four releases in four days, one of them explicitly a test of the GitHub release path. That is characteristic of research software preparing to be cited — a Zenodo DOI, correct funder attribution and a checklist-compliant description are the deliverables when the funder requires them. Substantive work on mapping functions and grid designation appears earlier and only through tutorial fixes.
◆ Prediction
With the Zenodo integration and metadata now settled, expect attention to return to the simulation functions themselves, most likely driven by what the sibling indicator packages need to test against.
Alternatives to fect and gcube
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 fect or gcube.
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 fect and gcube
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 agogcubeGrant ID no longer uses a DOI
- 5mo agogcubeZenodo grant ID, publisher metadata and a ROR URL fix
- 6mo agogcubeRelease v1.4.2
- 7mo agogcubeRelease v1.4.1
- 7mo agofectRewrites complex fixed effect handling and fixes speed
- 7mo agogcubeInstallation instructions, spelling and funder descriptions
- 11mo agofectAdds heterogeneous treatment effect plots and caps default cores
- 1y agogcubeRelease v1.3.7
Frequently asked questions
What is the difference between fect and gcube?
They serve adjacent needs but don't currently overlap on shipped themes. fect and gcube 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 fect better than gcube?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. fect and gcube 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 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.
What are the best alternatives to gcube?
Top gcube alternatives in Analytics are ranked by recent ship velocity. Browse the "gcube alternatives" section above for the current picks, or visit /alternatives/gcube for the full list with editorial commentary on each.