[breaking] Remove the predictor
param, allow fallback to prediction using DMatrix
.
#9129
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This lowers the fallback from the sklearn interface directly to C++ gbtree. The fallback logic is clearer: when devices don't match. Along with this, the
predictor
parameter will be removed, and the predictor used inside xgboost will be decided solely by the booster context.DeviceOrd
struct is implemented to indicate the device. It will eventually replace thegpu_id
parameter.predictor
parameter is removed.DMatrix
wheninplace_predict
is not available.Some of the code hasn't been updated yet, including the jupyter notebook for GPU SHAP and the benchmarking code in GPUTreesshap. I will update them once the
device
parameter is in place.