py-why / py-why/EconML

SparseLinearDRLearner doesn't shrink point estimates to zero at all

Open
#729 0 comments 1 reaction 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

Hi, thanks for the amazing library!

I have some problems while experimenting with the SparseLinearDRLearner, and I hope I could borrow your mind on them.

  1. In my case, I have about 10000 samples and about 50 features in the CATE function, and I wish to obtain a sparse version of the function by using SparseLinearDRLearner. However, it seems that the SparseLinearDRLearner won't shrink any point estimates to zero at all regardless of the value of alpha (0.0001 to 10000). Could you explain why this may happen?

  2. When comparing the results of SparseLinearDRLearner and LinearDRLearner, I found that the point then p-values and confidence intervals presented in the summary tables can be very different for the same features. For example, for some feature A, the result of the SparseLinearDRLearner states that the p-value is 0.001 whereas that of the LinearDRLearner is 0.6, hence giving a totally different insight. How would you interpret this dichotomy? Thanks!

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

Start by reproducing the reported behavior with SparseLinearDRLearner and LinearDRLearner using roughly 10,000 samples, 50 features, and the stated alpha range. Compare their point estimates, p-values, and confidence intervals, then inspect the learner implementation and documentation to determine whether the observed differences are expected. Done means providing a clear explanation or identifying a reproducible defect.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
machine-learning
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.