New issue
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
restoring xgboost 0.82.1 version models (in R) with xgboost 1.1.1.1 or 1.2.01 still failing ? #6509
Comments
Thanks for the speedy response, does that imply I might have success saving and loading as RDS ? I will experiment with that in my reprex. |
@nirguk Probably not. The issue appears to be in the core module of XGBoost, and using RDS would not fix the issue. Besides, we do not recommend the use of RDS for model archival: https://www.rdocumentation.org/packages/xgboost/versions/1.2.0.1/topics/a-compatibility-note-for-saveRDS-save |
@nirguk Hello, I ran the script you provide and reproduced the same error. I am now investigating a possible fix. |
Oops accidentally closed the issue. The issue is still being investigated. |
Thanks hcho3, this would be extremely useful ! |
Update: I verified that the use of |
It turns out the issue also exists in Python as well, so it's not specific to the R package. |
@hcho3 We need to fill in an independent |
I submitted #6517 which works around the issue. Let me see if I can write a separate |
Superb, thanks a million 😀 |
@nir4most If you'd like to try it out now, you can follow the instructions to install XGBoost from the latest source. |
I am trying to adapt my workflow to later versions of xgboost, however earlier fitted models are causing me grief... I had hoped that the following comments indicated that a new compatability layer would solve this issue, however it seems not ?
I provide a reprex here:
https://github.com/nirguk/xgboost_versions
for example sake, I fit an xgb model on Titanic data with binary:logitraw as objective.
I save this with xgb.save and then
I try to load this in 1.1.1.1 and also in 1.2.0.1 with xgb.load, but receive error:
The text was updated successfully, but these errors were encountered: