Add support for latest xgboost version #407
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
As per this post on StackOverflow, I was able to sidestep this issue by downgrading to from XGBoost version 1.4.2 to version 1.3.0 (apparently 1.3.0 is the latest version supported by ELI5). However...being forced to downgrade XGBoost isn't a satisfactory solution. ELI5 should be compatible with the latest version of XGBoost. |
|
The fix was released in 0.13 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
eli5 fails when booster.feature_names is
None, which is now the default behavior in xgboost when passing in a vanilla numpy array.See dmlc/xgboost@9da2287 for the relevant commit in xgboost