3. Explain why it gives regression discontinuity designs a hard time when the variable…
- User
- Explain why it gives regression discontinuity designs a hard time when the variable that determines treatment is measured granularly – for example, measuring only which bucket someone falls into, when each bucket covers a range, rather than their actual value of the variable that determines treatment.
- Assistant
Here’s why a “bucketed” (or coarsely measured) running variable makes RDD much harder:
-
Loss of Precise Distance-to-Cutoff
• In standard RDD, you know each unit’s exact score (x_i), so you can zoom in arbitrarily close to the cutoff (c).
• With buckets, you only know the interval ([b_j, b_{j+1})) that (x_i) falls into. You lose information about how close each unit really is to (c).Consequence: You can’t shrink your bandwidth below the bucket width. Any “local” estimate must pool units whose true scores may vary widely within the bucket.
-
Discrete Support & Few “Near-Cutoff” Values
Suppose buckets are 0–10, 10–20, 20–30, … and the cutoff is 20. Then the only observed running-variable values just below (c) are “10–20” and just above are “20–30.”┌───────────┬───────────┐
│ Bucket │ Relation │
│ (observed)│ to cutoff │
├───────────┼───────────┤
│ 10–20 │ below │
│ 20–30 │ above │
└───────────┴───────────┘You effectively have only two support points around the cutoff. That kills everything “local”:
- No fine grid to check continuity of other covariates.
- You can’t use local linear/polynomial fits—there aren’t enough distinct (x) values.
-
Attenuation (Bias Toward Zero)
When you round or group (x), you introduce classical measurement error in the running variable. In RDD this typically attenuates the jump estimate:
[ \widehat{\tau}\text{bucketed} ;=; \text{Bias}(\tau);<;\tau\text{true}. ] Intuition: some treated units whose true (x_i) was just above (c) get lumped with untreated, and vice-versa, blurring the discontinuity. -
Violation of the “Local Randomization” Logic
A key RDD assumption is that, arbitrarily close to (c), treatment is “as good as random.” But if your smallest possible neighborhood is the entire bucket (say width = 10 points), you’re averaging over a huge part of the running-variable distribution—so the “as-random” logic breaks down. -
Practical Remedies (and Why They’re Imperfect)
• Use a Fuzzy RD approach. Treat bucketed assignment as probabilistic—i.e. first stage: (P(T_i=1\mid \text{bucket})) jumps at cutoff. But that loses power and still suffers from coarse support.
• Coarsening-robust bandwidths. Pick bandwidth large enough to cover multiple buckets and model bucket means. But then you’re mixing very “far” observations.
• Seek finer data! Often the only real cure is to obtain the true running variable or smaller buckets.
—
In short, coarse-bucket measurement:- Eliminates the ability to focus “infinitely” close to the cutoff,
- Discretizes your support into only a couple of masses around the threshold,
- Introduces measurement error that shrinks the estimated jump, and
- Undermines the local-randomization intuition that makes RDD so compelling.
Without knowing people’s actual scores, you can’t credibly isolate the treatment effect at the precise cutoff.
-
- User
You are interested in the effect of library fines on whether long-overdue library books get returned. You find a local library who decided to forgive all library fines owed by people who owed below 51-55 range called the library many times until they got theirs removed too. So a few people below the cutoff didn’t get treated, and a few people above it did. If you estimated this using a sharp regression discontinuity estimator anyway, how would this affect your results and why? Assume the true effect of canceling fines is that it increases return rates by 10%.
- Assistant
Below the cutoff (fines < $50) almost everyone is treated, and above it (fines ≥ $50) almost nobody is—except for those tiny handfuls who “cross‐over” by insisting or by calling. In other words:
• If the cutoff perfectly assigned treatment,
P(treated│score<c)=1 and P(treated│score≥c)=0.
⇒ a sharp‐RDD jump in outcomes at c would identify the full 10 pp effect.
• In reality, because of non‐compliance,
P(treated│score<c)=1–p₁ (a few below refuse to be “untreated”)
P(treated│score≥c)=p₂ (a few above get treated)
so the actual jump in treatment probability at c isΔP = [1–p₁] – [p₂] < 1.When you then run a sharp‐RDD and simply compute
ΔOutcome = E[Y│score≥c] – E[Y│score<c],what you’re really grabbing is the Intent‐to‐Treat (ITT) effect:
ΔOutcome = True Effect × ΔP.Since ΔP is a little smaller than 1, your naïve RDD estimate will be attenuated. Numerically, if (say) 98% compliance survives below and 3% wrongly get treated above, then
ΔP ≃ 0.98 – 0.03 = 0.95
and
Naïve ΔY ≃ 10 pp × 0.95 = 9.5 pp
instead of the full 10 pp.
––––––––––––––––––––––––––––––––––––––––––––––––
Bottom line: by ignoring the cross-overs and treating it as “sharp,” you end up with a diluted (downward‐biased) estimate—what you really recover is the reduced‐form or ITT effect, not the full on-treatment effect. To get back to the 10 pp you’d re-scale by the jump in treatment probability (i.e. move to a fuzzy‐RDD/2SLS approach). - User
Can you give me the 5 most important points to take away from this page?
- Assistant
Here are the five core take-aways from the “Fixed Effects” chapter (https://theeffectbook.net/ch-FixedEffects.html):
-
Purpose of Fixed Effects
• FE models “soak up” all unobserved, time-invariant differences across units (e.g. individuals, firms, schools) by effectively giving each unit its own intercept.
• This means any constant omitted variable (like innate ability or regional climate) can no longer bias your β̂ for time-varying regressors. -
Two Equivalent Estimators
• Dummy‐Variable (LSDV) Approach: Include a separate dummy for every unit (minus one) in your OLS.
• Within (Demeaning) Approach: Subtract each unit’s own average from y and all x’s, then regress “demeaned” y on demeaned x.
• They deliver identical β̂’s—“within” is just far more computationally efficient when N is large. -
Extending to Two-Way FE
• You can also include time fixed effects (one dummy per period) to purge common shocks (policy changes, recessions, seasonality).
• Equation:
yᵢₜ = αᵢ + λₜ + β xᵢₜ + εᵢₜ
• Identification comes from deviations of xᵢₜ both from the unit’s mean and from the period’s mean. -
What FE Can (and Can’t) Identify
✔️ Estimates of time-varying regressors, based solely on within-unit over-time variation.
✖️ Effects of time-invariant covariates—they’re perfectly collinear with the unit dummies.
✖️ Omitted time-varying confounders—if something else varies over time and affects y, you still need parallel-trends or other strategies. -
FE vs. Random Effects (RE)
• Fixed Effects: allows arbitrary correlation between the unit intercepts (αᵢ) and xᵢₜ ⇒ consistent under minimal assumptions.
• Random Effects: treats αᵢ as uncorrelated with xᵢₜ ⇒ more efficient but often unrealistic.
• Use FE when you suspect unit-specific traits (observed or not) are related to your regressors.
—
📌 Bottom-line: Fixed effects give you a clean within-unit comparison over time, stripping out all constant heterogeneity—but they only “fix” constant confounders and cannot recover effects of time-invariant variables. -
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.