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

max_features #203

Open
mvalsania opened this issue Dec 8, 2024 · 2 comments
Open

max_features #203

mvalsania opened this issue Dec 8, 2024 · 2 comments
Labels

Comments

@mvalsania
Copy link
Contributor

How should we talk about the impact of max_features on the dvc?

I am trying to reference the formula we have ( O(klog(kd)) ) but I am still conflicted with the fact that we are not technically affecting the number of dimensions with this hyperparameter, we are affecting the number of dimensions that we take into consideration before deciding which dimension would lead to the best split. What is the right way to think about this? Should we think of this hyperparameter as indirectly and artificially affecting d?

Thanks!

@mikeizbicki
Copy link
Owner

The $d$ in the VC dimension formula for the decision tree is the dimension of the data space and unaffected by the max_features hyperparameter. The later does not affect the VC dimension, and is primarily used for reducing the runtime of training.

@mvalsania
Copy link
Contributor Author

Thanks!

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

No branches or pull requests

2 participants