py-why / py-why/EconML

Handle the binary outcome in metalearners

Open
#83 4 comments 0 reactions 1 assignee View on GitHub

@heimengqi is already working on this.

Since Nov 9, 2019.

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

Description

Problem

When we use the ordinary classification models provided by sklearn, we get poor results because metalearners call the predict methods that return 0 or 1.

It would be because metalearners in EconML now focus on the continuous outcome.

Solution

I modified the predict methods in two ways:

  • create wrappers of sklearn models
  • override methods after the initialization of metalearners

I uploaded a jupyter notebook in gist to explain the modification.

Discussion and Proposition

I would like to find better solutions to handle the binary outcome (from my point of view, it would not be reasonable to add an option to handle the binary outcome in EconML right now). Do you have any ideas?

And I would appreciate it if you could provide a supplementary explanation about handling the binary outcome anywhere in your document.

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.