py-why / py-why/EconML

Binary treatment and Continuous outcome

Open
#780 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Jupyter Notebook
Stars
4.8k
Forks
827
PR merge metrics
No merged PRs in 30d

Description

In the case of Binary treatment[1 for treatment group 0 for control group] and Continuous outcome,

CASE1 : discrete_treatment=True

est = CausalForestDML(criterion='het')

set parameters for causal forest

est = CausalForestDML(criterion='het', random_state=1,
discrete_treatment=True,
honest=True,
inference=True,
cv=2,
model_t=LogisticRegressionCV(),
model_y=Lasso()
)

CASE2 : discrete_treatment=False
est = CausalForestDML(criterion='het', random_state=1,
discrete_treatment=False,
honest=True,
inference=True,
cv=2,
model_t=Lasso(),
model_y=Lasso()
)

CASE1 and CASE 2 basically work same function ?
In this case, which one is more fir between CASE 1 or CASE 2 ?

I wonder discrete_treatment=TRUE is applies for only multiple treatment not binary treatment.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No file or test is named. Start by reading the CausalForestDML documentation for discrete_treatment and the shown LogisticRegressionCV and Lasso configurations, then compare the binary-treatment cases. Done means documenting whether discrete_treatment applies to binary treatment and which configuration is appropriate.

Written by the indexing model from the issue text.

Assessment

Tech stack
machine-learning, python, scikit-learn
Domain
documentation, machine-learning
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.