EpistasisLab / EpistasisLab/tpot2

Idea for Successive Halving to avoid repeated re-evaluations of the same pipeline.

Open
#85 0 comments 0 reactions 0 assignees View on GitHub
enhancement
Dominant language
Jupyter Notebook
Stars
250
Forks
33
PR merge metrics
No merged PRs in 30d

Description

Currently, successive halving reduces computation by subsampling the number of rows. Every time the budget increases, the existing parent population is re-evaluated at the next budget, which may be inefficient. Another approach could be to make budgets related to CV folds. We could use only one fold to evaluate the first N generations. Then evaluate two folds when the budget increases. In this case, the parent population wouldn't have to be re-evaluated from scratch; it would just be evaluated on the next fold of CV.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.