-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
Read and create the booster model from a JSON file #5370
Comments
@StrikerRUS could help us out with this issue please? |
Hi. I see that the dump model functions were added in #97 as a way to analyze the underlying model. They're currently used in the trees to dataframe functions: LightGBM/python-package/lightgbm/basic.py Line 2820 in 44fe591
LightGBM/R-package/R/lgb.model.dt.tree.R Line 51 in 44fe591
I don't think that format was meant to be an alternative to the original serialization but there's an ongoing discussion in #4887 about using JSON as the default (and in the future only) serialization format. But to answer your question, I don't think it's currently possible to restore a booster from JSON. |
I appreciate your quick response! |
I think we can close it but feel free to comment on #4887 if you'd like to add anything to the proposal. |
This issue has been automatically locked since there has not been any recent activity since it was closed. To start a new related discussion, open a new issue at https://github.com/microsoft/LightGBM/issues including a reference to this. |
Hi guys!
I have looked through all the tasks related to saving models in JSON. Unfortunately, I could not figure out whether we can create a booster object from a JSON file?
I would really appreciate it if you could tell me how I can create a booster using json.
I think the size of the JSON model will be smaller than the STRING model.
Perhaps there is a lot of necessary information missing in the dump json model. Maybe that's why json weighs so much less.
I'll be glad if you correct me.
Reproducible example
Additional Comments
Related task: #2604
The text was updated successfully, but these errors were encountered: