We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The recent 1.0.0 release of xgboost brings the xgboost.dask interface . A relevant example is here - https://github.com/dmlc/xgboost/blob/master/demo/dask/sklearn_cpu_training.py
the related documentation is here - https://xgboost.readthedocs.io/en/latest/tutorials/dask.html
there are intertwined usecases - e.g. xgb.dask.DaskDMatrix vs the work being done in #605
How do you see both these projects co-existing ? will one subsume the other ? we are currently on dask-ml and wondering which direction to go in.
The text was updated successfully, but these errors were encountered:
See dask/dask-xgboost#39.
My thoughts are at dask/dask-xgboost#39 (comment).
Sorry, something went wrong.
Let's keep the discussion on dask-xgboost vs. xgboost over there, if you have more to add.
Work like #605 will of course have to be done here.
No branches or pull requests
The recent 1.0.0 release of xgboost brings the xgboost.dask interface .
A relevant example is here - https://github.com/dmlc/xgboost/blob/master/demo/dask/sklearn_cpu_training.py
the related documentation is here - https://xgboost.readthedocs.io/en/latest/tutorials/dask.html
there are intertwined usecases - e.g. xgb.dask.DaskDMatrix vs the work being done in #605
How do you see both these projects co-existing ? will one subsume the other ? we are currently on dask-ml and wondering which direction to go in.
The text was updated successfully, but these errors were encountered: