rainette
rainette rebuilt its Reinert clustering in 0.2.0, tuned it in 0.3.0, and has coasted since.
Comparison · Analytics
ecodive vs fect
A side-by-side editorial comparison of ecodive and fect — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-package
ecodive vs fect: at a glance
What is ecodive?
ecodive rebuilt itself into a broad diversity-metric library, breaking as it went
ecodive computes alpha and beta diversity metrics for ecological and microbiome count data, including phylogenetic measures like Faith's PD and the UniFrac family. The 2.0.0 rewrite expanded it from a handful of metrics to roughly fourteen alpha and thirty beta measures while flipping the expected input orientation to samples-as-rows. Subsequent releases have been spent settling the normalisation interface that expansion exposed.
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.
ecodive vs fect: editorial side-by-side
ecodive
0.0ANALYTICS
ecodive rebuilt itself into a broad diversity-metric library, breaking as it went
◆ Current state
ecodive computes alpha and beta diversity metrics for ecological and microbiome count data, including phylogenetic measures like Faith's PD and the UniFrac family. The 2.0.0 rewrite expanded it from a handful of metrics to roughly fourteen alpha and thirty beta measures while flipping the expected input orientation to samples-as-rows. Subsequent releases have been spent settling the normalisation interface that expansion exposed.
◆ Where it's heading
This is a package that made its breaking changes deliberately and in a cluster. After 2.0.0 reoriented input and removed the weighted parameter, 2.1.0 superseded rescale with norm, and 2.2.6 changed norm's default from percent to none and removed it from some beta functions entirely. That last one matters more than it reads: normalisation defaults silently change the numbers a metric returns, and the direction is toward making the user state their choice rather than inheriting one.
◆ Prediction
With the metric surface broad and the normalisation interface now explicit, expect the next releases to stabilise — documentation and edge-case handling around CLR and rarefaction rather than another interface break.
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 ecodive 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 ecodive or fect.
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.
singlercapture
singleRcapture reached 1.0.0 with no release notes at all — the arc has to be read backwards.
crossmap
crossmap's roadmap is set by purrr and furrr — it deprecates what upstream deprecates.
fracture
fracture solved decimal-to-fraction conversion years ago and now only answers to CRAN.
See all ecodive alternatives → · See all fect alternatives →
Recent activity from ecodive 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
- 4mo agoecodiveNormalisation now defaults to none, with CLR zero warnings
- 7mo agofectRewrites complex fixed effect handling and fixes speed
- 7mo agoecodiveecodive 2.2.2
- 10mo agoecodiverescale superseded by norm; crash fixes after the 2.0.0 rewrite
- 10mo agoecodive2.0.0 expands to ~14 alpha and ~30 beta diversity metrics ⚡
- 11mo agofectAdds heterogeneous treatment effect plots and caps default cores
Frequently asked questions
What is the difference between ecodive and fect?
Both compete on the same themes — r-package — within Analytics. ecodive 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 ecodive better than fect?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. ecodive 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 ecodive?
Top ecodive alternatives in Analytics are ranked by recent ship velocity. Browse the "ecodive alternatives" section above for the current picks, or visit /alternatives/ecodive 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.