SingleTreePolicyInterpreter (causal forest) Follow-Up
Nobody has claimed this yet.
- Dominant language
- Jupyter Notebook
- Stars
- 4.8k
- Forks
- 827
- PR merge metrics
- No merged PRs in 30d
Description
Hi Keith,
@kbattocchi
I had a follow-up question on the SingleTreePolicyInterpreter (causal forest) Interpreter in general. My questions are:
- If I have 3 Y-variables (i.e. sales, retention, session duration), would be SingleTreePolicyInterpreter consider all 3 of them when building the policy tree and when calculating the
[value - cost]in each leaf plus the overall "average policy gain" displayed at the top of the tree? or do I need to do this 3 times for each Y? - For the parameter "
sample_treatment_costs", I tried using a numpy array because for each user, the cost would be different (based on their LTV). Is that possible because when I tried it, it was expecting a double scalar. Is there any work-around or must this parameter be a constant? - If my two Treatments are
"discount"or"customer support", how do I know using the SingleTreePolicyInterpreter for which users"
- increase discounts for? (for insensitive users)
- decrease discounts for?(for sensitive users)
- increase customer support for? (for non-saavy users)
- decrease customer support for? (for saavy users)
Currently, my tree outputs only: "Discount" and "customer support" but not the direction (increase or decrease). How could I get to that? Do I need to work directly with the individual CATEs of each subject which drifts away from the SingleTreePolicyInterpreter approach?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the SingleTreePolicyInterpreter entry point and its sample_treatment_costs parameter. Clarify whether multi-outcome policies, per-user treatment costs, and treatment direction are supported, then define the required API behavior and tests before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- numpy, python
- Domain
- machine-learning
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100