← Back to home
Comparison · Analytics

fect vs qtl2

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

Shared themes:r-package

fect vs qtl2: at a glance

Featurefectqtl2
SectorAnalyticsAnalytics
Velocity score0.02.5
Sparks · 30d00
Top themesr-package, causal-inference, panel-data, api-redesignqtl-mapping, statistical-genetics, bioinformatics, r-package
Last editorial update1h ago2h ago
WebsiteVisit →Visit →

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 →

What is qtl2?

The standard QTL mapping package in R opened its genome scan to user-supplied likelihood models.

qtl2 is the R toolkit for QTL mapping in experimental crosses, covering genotype probability calculation, genome scans with and without polygenic effects, permutation testing, SNP association, and the plotting that goes with them. The last year of work has pushed hard in two directions: tooling for high-throughput expression and protein QTL studies, and a generalisation of the scan engine itself so the log-likelihood being maximised can be supplied by the user. Note that the release history reached this feed out of order, so feed position is not a reliable guide to which release came first.

Read the full qtl2 trajectory →

fect vs qtl2: editorial side-by-side

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.

Q
qtl2
ANALYTICS
2.5

The standard QTL mapping package in R opened its genome scan to user-supplied likelihood models.

◆ Current state

qtl2 is the R toolkit for QTL mapping in experimental crosses, covering genotype probability calculation, genome scans with and without polygenic effects, permutation testing, SNP association, and the plotting that goes with them. The last year of work has pushed hard in two directions: tooling for high-throughput expression and protein QTL studies, and a generalisation of the scan engine itself so the log-likelihood being maximised can be supplied by the user. Note that the release history reached this feed out of order, so feed position is not a reliable guide to which release came first.

◆ Where it's heading

The eQTL and pQTL direction is the clearest thread — cis-trans plots, hotspot counting over a sliding window, multi-trait scan heat maps, and genome-wide genotype plots all arrived together, which is the toolkit an experiment with thousands of traits needs rather than one with a handful. Running underneath it is a steady generalisation of the core: a scan function that accepts an arbitrary likelihood, permutations that work with alternative scan functions, full variance-covariance output from single-position fits. Performance and parallelism get attention each cycle, including a more considerate default that leaves one core free. The rest is the ordinary maintenance of a long-lived package — renames to avoid tidyverse collisions, compiler warnings, and correctness fixes on specific cross types.

◆ Prediction

With scan1gen and permutation support for alternative scan functions in place, the natural next step is more model types built on that hook rather than more special-cased scan functions; the entries do not indicate which models are planned.

Alternatives to fect and qtl2

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 qtl2.

See all fect alternatives → · See all qtl2 alternatives →

Recent activity from fect and qtl2

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

  1. 27d agoqtl2chr_lengths() extended to cross2 objects
  2. 1mo agoqtl2A genome scan that takes your own likelihood function
  3. 2mo agoqtl2Hotspot counting and cis-trans plots for eQTL studies
  4. 2mo agofectAdds group.fe for coarsened fixed effects and a $sample slot
  5. 3mo agoqtl2Confidence interval plotting, plus a documentation correction
  6. 3mo agofectPost-hoc estimand API decouples estimands from the fit
  7. 4mo agofectUnified cross-validation and explicit control of time components
  8. 7mo agofectRewrites complex fixed effect handling and fixes speed
  9. 11mo agofectAdds heterogeneous treatment effect plots and caps default cores
  10. 1y agoqtl2Finer-grained parallelism for kinship-based scans
  11. 1y agoqtl2CSV readers renamed to avoid the readr collision

Frequently asked questions

What is the difference between fect and qtl2?

Both compete on the same themes — r-package — within Analytics. qtl2 is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is fect better than qtl2?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. qtl2 is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. 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 qtl2?

Top qtl2 alternatives in Analytics are ranked by recent ship velocity. Browse the "qtl2 alternatives" section above for the current picks, or visit /alternatives/qtl2 for the full list with editorial commentary on each.