py-why / py-why/EconML

Could you add early stopping in the forest-based estimators?

Open
#633 0 comments 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

It's quite hard to guess the 'right' number of trees for a particular estimator, and a full-on hyperparameter search is quite expensive. Would be great to have an early stopping option, such as provided by most tree-based conventional ML models.

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 locating the forest-based estimators in the EconML codebase and reviewing how they configure and fit their underlying tree models. Compare the requested early-stopping behavior with existing tree-based machine-learning models and determine which estimators and parameters should be covered. Done means the scope, stopping criteria, and expected behavior are implemented consistently and verified with relevant estimator tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
machine-learning
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.