Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Stop training branch of tree once a specific feature is used #2518

Closed
ghost opened this issue Oct 20, 2019 · 2 comments
Closed

Stop training branch of tree once a specific feature is used #2518

ghost opened this issue Oct 20, 2019 · 2 comments

Comments

@ghost
Copy link

ghost commented Oct 20, 2019

I am doing some multivariate time series experiments with only partially stationary data. The idea is this:

  1. First I introduce an additional feature which is monotonically increasing (but not strictly), e.g. an integer year_index assuming that I have several years of data.
  2. Then I want to train a gradient boosting model. However, as soon as the feature year_index would normally be used, I want to leave the current branch of the tree unchanged.

The reasoning behind this idea is that if there is no better feature than year_index, then we have already exploited all information which is useful for generalization of future data.

Is it possible to achieve such an effect without changing the C++ code, e.g. by modifying a tree immediately after it has been created in a callback or with paramaters?

@StrikerRUS
Copy link
Collaborator

I suppose the described behavior can be achieved via a callback in which you dump a current model and search for a specific (allowed to be used only once) feature. Then you stop training in case of a successful search.

However, I'm going to add this issue into our feature requests hub for neater out of the box solution. Let's see how demanded this feature is.

@StrikerRUS StrikerRUS changed the title Question: Stop training branch of tree once a specific feature is used? Stop training branch of tree once a specific feature is used Dec 20, 2019
@StrikerRUS
Copy link
Collaborator

Closed in favor of being in #2302. We decided to keep all feature requests in one place.

Welcome to contribute this feature! Please re-open this issue (or post a comment if you are not a topic starter) if you are actively working on implementing this feature.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant