You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
LightGBM added random forest support in July 2017. ML.NET should expose this functionality.
This is exposed as another booster type. Currently we support { Tree Booster, Dropout Tree Booster, and Gradient-based One-Size Sampling } (src) boosters of LightGBM.
I don't see that LightGBM provides a default for these parameters. So we need to provide reasonable defaults for the user; without ff/bagfrac set to <1.0, LightGBM throws an error. I think ff=0.5 & bagfrac=0.5 may be a bit low; perhaps 0.7? As always benchmarks on representative datasets speak louder than I.
This adds to our existing FastTree Random Forest implementation, and is another implementation that could be use for #1729.
The text was updated successfully, but these errors were encountered:
harishsk
added
P2
Priority of the issue for triage purpose: Needs to be fixed at some point.
and removed
P1
Priority of the issue for triage purpose: Needs to be fixed soon.
labels
Jan 10, 2020
LightGBM added random forest support in July 2017. ML.NET should expose this functionality.
This is exposed as another booster type. Currently we support { Tree Booster, Dropout Tree Booster, and Gradient-based One-Size Sampling } (src) boosters of LightGBM.
For our defaults for the new booster type we could copy the test:
https://github.com/Microsoft/LightGBM/blob/fb28070e1daa500b087d3102145ae48988030195/tests/python_package_test/test_engine.py#L53-L62
I don't see that LightGBM provides a default for these parameters. So we need to provide reasonable defaults for the user; without ff/bagfrac set to <1.0, LightGBM throws an error. I think
ff=0.5
&bagfrac=0.5
may be a bit low; perhaps 0.7? As always benchmarks on representative datasets speak louder than I.This adds to our existing FastTree Random Forest implementation, and is another implementation that could be use for #1729.
The text was updated successfully, but these errors were encountered: