Skip to content

[Impact report] Describe high-level implementation choices for propensity score#2443

Open
chiyc wants to merge 2 commits intomainfrom
chi.impact-propensity
Open

[Impact report] Describe high-level implementation choices for propensity score#2443
chiyc wants to merge 2 commits intomainfrom
chi.impact-propensity

Conversation

@chiyc
Copy link
Contributor

@chiyc chiyc commented Mar 10, 2026

Background

A recent support ticket asked for details about our propensity score implementation. The existing documentation for Causal Impact doesn't say how it's calculated. There is a linked whitepaper, but it's sparse on details about the propensity score.

Changes

This adds some findings from an investigation of the propensity modeler service code to answer the following questions:

  • How are the 10 subclasses constructed in practice?
  • Which model/inputs are used to estimate the propensity score (feature set, handling of missing values, regularization, balancing heuristics)?
  • How are weights computed across sub-classes (inverse variance, subclass size, or other)?
  • Any minimum sample size or diagnostics that would cause Causal Impact to skip or fail a subclass?

@chiyc chiyc requested a review from a team as a code owner March 10, 2026 17:32
@chiyc chiyc requested review from kathmath and removed request for a team March 10, 2026 17:32
@vercel
Copy link

vercel bot commented Mar 10, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
docs Ready Ready Preview, Comment Mar 10, 2026 6:21pm

Request Review

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant