Open adam2392 opened 8 months ago
I don't know if this YAGNI or not. By definition, having max_feature > 1
and bootstrap=True
would not be a bootstrap by definition anymore. Is there any concrete example where not having this feature is detrimental.
This allows flexibility in terms of the trees and may help in supporting other issues that require more fine-grained control over what is in-bag vs oob such as https://github.com/scikit-learn/scikit-learn/issues/19710.
Could you provide a bit more background. It might be an interesting context to consider for a decision.
I don't know if this YAGNI or not. By definition, having
max_feature > 1
andbootstrap=True
would not be a bootstrap by definition anymore. Is there any concrete example where not having this feature is detrimental.
I asume you meant max_samples
here(?)
Bootstrap is defined as sampling without replacement. Let M
be the number of bootstrap samples and N
be the number of samples in your dataset. It just happens to be the case that when M == N
, you get 63% unique samples in your bootstrap set. However, you can sample M > N
, and there is no fundamental reason that wouldn't be considered a bootstrap sample.
Could you provide a bit more background. It might be an interesting context to consider for a decision.
Sure! My collaborators and I commonly do research on random forests because of desirable theoretical guarantees. One of the interesting advances lately has to do with what we can do with out-of-bag samples. Out-of-bag samples is inversely related to your in-bag samples, and rn sklearn constrains the trade-off you're allowed to make here.
More concretely, we are interested in hypothesis testing with random forests by using the test-statistic estimated on out-of-bag samples. It is possible to leverage out-of-bag samples to estimate a test statistic per tree and average across trees. However, there is a trade-off between how good your estimate of the test statistic is (# of out-of-bag samples) and how well your tree is fit (# of in-bag samples). By default sklearn upper-bounds how many out-of-bag samples you are allowed (i.e. 1.0 - 0.63 = 0.37). However, we want to estimate out-of-bag statistics on 20% of the data, not 37% of the data. This requires one to bootstrap sample M = 1.6 * N
times, which then on expectation results in out-of-bag estimates on 20% of the data and in-bag training of the tree on 80% of the data.
Note we're setting bootstrap to True, so there is no way to hack this by using say StratifiedShuffleSplit
cv object because that would then make each forest (not tree) have different in-bag/out-of-bag data. We want different in-bag/out-of-bag data per tree, so the easiest thing to do is a simple change in sklearn. I've sketched out that there is only a few LOC needed to be changed (mostly due to error checking).
Lmk if I can elaborate further!
To add to the motivation and use-cases described above: The typical training paradigm of 80/20 split used in machine learning is pretty sensible. The train/test split used in cross-validation can be seen as analogous to inbag/oob splits. However, inbag/oob splits can occur at most with a 63/37 split due to max_samples
being constrained to at most 1.0.
It's a pretty simple LOC/logic change, backwards-compatible and allows more flexibility in trading off oob-estimates and training the trees.
Describe the workflow you want to enable
Currently, random/extra forests can bootstrap sample the data such that
max_samples \in (0.0, 1.0]
. This enables an out-of-bag sample estimate in forests.However, this only allows you to sample in principle up to at most 63% unique samples and then 37% of unique samples are for out-of-bag estimation. However, you should be able to control this parameter to a proportion greater. For instance, perhaps I want to leverage 80% of my data to fit each tree, and 20% to estimate oob performance. This requires one to set
max_samples=1.6
.Beyond that, no paper suggests that 63% is required cutoff for bootstrapping the samples in Random/Extra forest. I am happy to submit a PR if the core-dev team thinks the propose solution is simple and reasonable.
See https://stats.stackexchange.com/questions/126107/expected-proportion-of-the-sample-when-bootstrapping for a good reference and explanation.
Describe your proposed solution
The proposed solution is actually backwards-compatable and adds minimal complexity to the codebase.
def _get_n_samples_bootstrap(n_samples, max_samples): """ Get the number of samples in a bootstrap sample.