Whether xgboost_requires needs to be changed
See original GitHub issueI’m sorry if I made a mistake in the place to post.
https://github.com/dask/dask-ml/blob/main/setup.py
Currently dask-ml
depends on the following OSS when building with xgboost function:
xgboost_requires = ["dask-xgboost", "xgboost"]
https://github.com/dmlc/xgboost/blob/master/python-package/setup.py
However currently xgboost
owns the dask
option.
Does xgboost_requires
need to be modified?
xgboost+dask
only ordask-xgboost
andxgboost+dask
Issue Analytics
- State:
- Created 3 years ago
- Comments:11 (6 by maintainers)
Top Results From Across the Web
decision trees - Is it necessary to normalize data for XGBoost?
Your rationale is indeed correct: decision trees do not require normalization of their inputs; and since XGBoost is essentially an ensemble ...
Read more >How to Control Your XGBoost Model | Capital One
XGBoost is a powerful gradient boosting tool for machine learning models, learn how pruning, regularization, and early stopping can help ...
Read more >XGBoost: Order Does Matter. | by Bitya Neuhof | Medium
Running XGBoost with default parameters and no parallel computing yields a completely deterministic set of trees. If you change the value of the ......
Read more >When to NOT use XGBoost? | Data Science and ... - Kaggle
Hi @ jessicali9530! I think the main limitation to using XGBoost is overfitting on small samples. Also, when you have a lot of...
Read more >XGBoost: Everything You Need to Know - Neptune.ai
Finally, if you see that your hyperparameter tuning is still having minimal impact try to switch to more simpler regression methods like Linear,...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I think we can just remove the xgboost stuff in the setup.py and update the docs at https://ml.dask.org/xgboost.html to use it.
People should just use
xgboost.dask
, and there’s really no reason to add it under the dask_ml.xgboost namespace.cc @hcho3 @trivialfis @JohnZed (for vis)