← Back to home
Comparison · Analytics

fect vs fillpattern

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

Shared themes:r-package

fect vs fillpattern: at a glance

Featurefectfillpattern
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesr-package, causal-inference, panel-data, api-redesignggplot2, data-visualization, accessibility, graphics
Last editorial update2h ago56m 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 fillpattern?

Pattern fills for ggplot2, hardened against the ways users write sizes

fillpattern provides pattern fills — stripes, bricks, dots — for ggplot2 and base R graphics, aimed at figures that must stay legible in greyscale or to colour-blind readers. The 1.0.3 release is mostly defensive: size modifier strings ending in a colon no longer swap width for height, modify_size() reports invalid units instead of crashing and understands in, inches and cm, and a background colour bug in scale_fill_pattern() is fixed. The minimum R version rises to 4.2.0 for recent graphics engine features.

Read the full fillpattern trajectory →

fect vs fillpattern: 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.

F
fillpattern
ANALYTICS
0.0

Pattern fills for ggplot2, hardened against the ways users write sizes

◆ Current state

fillpattern provides pattern fills — stripes, bricks, dots — for ggplot2 and base R graphics, aimed at figures that must stay legible in greyscale or to colour-blind readers. The 1.0.3 release is mostly defensive: size modifier strings ending in a colon no longer swap width for height, modify_size() reports invalid units instead of crashing and understands in, inches and cm, and a background colour bug in scale_fill_pattern() is fixed. The minimum R version rises to 4.2.0 for recent graphics engine features.

◆ Where it's heading

Development is slow and entirely reactive to how the string-based size interface fails. The pattern across releases is the same: a user hits an edge — very small fill areas in 1.0.2, malformed unit strings in 1.0.3 — and the fix is either a graceful fallback or a clearer error. Leaning on R's newer graphics engine rather than reimplementing pattern rendering keeps the package small at the cost of raising its version floor.

◆ Prediction

Expect further releases to stay in the same register: parsing and validation fixes for the size and unit interface, with the pattern set itself unlikely to change.

Alternatives to fect and fillpattern

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

See all fect alternatives → · See all fillpattern alternatives →

Recent activity from fect and fillpattern

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 agofillpatternSize string parsing fixed; invalid units now report instead of crash
  5. 7mo agofectRewrites complex fixed effect handling and fixes speed
  6. 11mo agofectAdds heterogeneous treatment effect plots and caps default cores
  7. 2y agofillpatternSmall fill areas no longer crash; min_size falls back to solid
  8. 2y agofillpatternfillpattern 1.0.1

Frequently asked questions

What is the difference between fect and fillpattern?

Both compete on the same themes — r-package — within Analytics. fect and fillpattern 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 fillpattern?

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

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