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

Add options #22

Closed
wants to merge 5 commits into from
Closed

Conversation

cunningjames
Copy link

Add ability to specify additional parameters to RandomForestRegressor, with some minor error checking and two additional tests.

Options are passed in as dictionary argument rf_opts. n_estimators is ignored in favor of the argument to the constructor; oob_score is ignored and always set to True; warm_start is ignored (assumed to be False).

Two reasons this is helpful for me, at least: the random forest fit is often faster (particularly on my laptop) with n_jobs set to 1. I'm also hoping to investigate the shap interpretability package, but the underlying algorithms perform extremely poorly on deep trees, so the ability to specify max_depth would make that a bit easier.

This is a repeat of another pull request, closed by me, attempting to fix formatting issues that cause continuous integration to fail.

James Cunningham added 5 commits November 21, 2018 20:55
Implement early stopping for the MERF fitting procedure, based on relative tolerance. The default value has been changed to "None" to reflect that the option will be ignored unless specified.
Attempted to fix formatting for early stopping, so as not to anger the continuous integration.
Add ability to specify additional parameters to RandomForestRegressor, with some minor error checking and two additional tests.
@resdntalien
Copy link
Contributor

@cunningjames This just has some lint errors that need to be fixed. I can take a look at reviewing this tomorrow as well. Thanks for contributing!

@resdntalien
Copy link
Contributor

@cunningjames I merged another PR with the same feature. I'm gonna go ahead and close this one. v0.3 (which I'm about to release now) will have this change.

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

Successfully merging this pull request may close these issues.

None yet

2 participants