-
Notifications
You must be signed in to change notification settings - Fork 726
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
inference='auto' #205
Comments
Hey @vasilismsr, for even medium sized datasets or complex models like Random Forests or GBMs automatically enabling inference to do something, worse case bootstrap can be prohibitively expensive computational. I guess what I'm saying is, if the user doesn't know whether a particular inference method paired with their chosen models would be expensive or it, it should not be automated for them because from the user point of view it will look like the process gets stuck on the Obviously please correct me if I'm wrong. |
For example in my package which has this package as a dependency I replace the |
Thanks @arose13 ! Indeed, maybe having bootstrap as a default is a bad idea. Though we have some particular subclasses where inference is at no computational cost and there is an obvious default method. For instance, in Would then a solution of the form: |
We should add a "inference='auto'" or "inference=True" option to all estimators, which would use some default option for inference. For instance, this could be bootstrap or None (if we want to disallow inference in some estimators that we think bootstrap will be deceiving) or the more tailored methods.
This will allow the user to not require to know which one is the most appropriate method. Also it would allow one to not have to change the fit call whenever they change the estimator class.
The text was updated successfully, but these errors were encountered: