← Back to home
Comparison · Analytics

crossmap vs fect

A side-by-side editorial comparison of crossmap and fect — release velocity, themes, recent moves, and the top alternatives to consider.

crossmap vs fect: at a glance

Featurecrossmapfect
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themespurrr extension, functional programming, deprecations, furrrr-package, causal-inference, panel-data, api-redesign
Last editorial update42m ago2h ago
WebsiteVisit →Visit →

What is crossmap?

crossmap's roadmap is set by purrr and furrr — it deprecates what upstream deprecates.

A small package for mapping over combinations of arguments, following purrr and furrr conventions. Its own functional additions stopped after xpluck() in 2023 and the cross_fit() clustering work in 2022. Everything since tracks upstream: xmap_raw() and future_xmap_raw() are now defunct because purrr removed map_raw() and furrr removed future_pmap_raw(), and re-exported parallel helpers now come from parallelly rather than future.

Read the full crossmap trajectory →

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.

Read the full fect trajectory →

crossmap vs fect: editorial side-by-side

C
crossmap
ANALYTICS
0.0

crossmap's roadmap is set by purrr and furrr — it deprecates what upstream deprecates.

◆ Current state

A small package for mapping over combinations of arguments, following purrr and furrr conventions. Its own functional additions stopped after xpluck() in 2023 and the cross_fit() clustering work in 2022. Everything since tracks upstream: xmap_raw() and future_xmap_raw() are now defunct because purrr removed map_raw() and furrr removed future_pmap_raw(), and re-exported parallel helpers now come from parallelly rather than future.

◆ Where it's heading

The package has settled into being a compatible extension rather than an independent one — its release notes read as a mirror of purrr's and furrr's deprecation schedules. Note that the release stamps are unreliable here: several versions were backfilled minutes apart and the 0.3.x tags carry timestamps in reverse version order, so feed position says nothing about what shipped when.

◆ Prediction

Expect the next release to be driven by another purrr or furrr change rather than new functionality, since that has been the sole trigger for the last four.

F
fect
ANALYTICS
0.0

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 crossmap 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 crossmap or fect.

See all crossmap alternatives → · See all fect alternatives →

Recent activity from crossmap and fect

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 2mo agofectAdds group.fe for coarsened fixed effects and a $sample slot
  2. 3mo agofectPost-hoc estimand API decouples estimands from the fit
  3. 4mo agofectUnified cross-validation and explicit control of time components
  4. 6mo agocrossmapRaw-vector mapping functions removed
  5. 6mo agocrossmapRe-exports moved to the parallelly namespace
  6. 7mo agofectRewrites complex fixed effect handling and fixes speed
  7. 11mo agocrossmapFuture-backed tests skipped on CRAN
  8. 11mo agocrossmapInternal test fixes
  9. 11mo agofectAdds heterogeneous treatment effect plots and caps default cores
  10. 3y agocrossmapxpluck adds multi-index plucking
  11. 4y agocrossmapCluster specifications supported in cross_fit

Frequently asked questions

What is the difference between crossmap and fect?

They serve adjacent needs but don't currently overlap on shipped themes. crossmap 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 crossmap better than fect?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. crossmap 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 crossmap?

Top crossmap alternatives in Analytics are ranked by recent ship velocity. Browse the "crossmap alternatives" section above for the current picks, or visit /alternatives/crossmap 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.