Load and save the lightGBM classifier not producing the same results - Githubissues

microsoft / SynapseML

Simple and Distributed Machine Learning

http://aka.ms/spark

MIT License

5.02k stars 832 forks source link

Load and save the lightGBM classifier not producing the same results #2053

Open kushagra1606 opened 11 months ago

kushagra1606 commented 11 months ago

SynapseML version

0.10.2

System information

Language version (e.g. python 3.8, scala 2.12): python 3.8
Spark Version (e.g. 3.2.3): 3.3.2
Spark Platform (e.g. Synapse, Databricks): Databricks

Describe the problem

Trained a lightGBM classifier. I tried to save this in the native format and load it back again with the below code -

LightGBMClassificationModel.loadNativeModelFromString(model.getNativeModel())

I am not getting the same results with the load and save model as compared to original.

Can someone please help?

Code to reproduce issue

LightGBMClassificationModel.loadNativeModelFromString(model.getNativeModel())

Other info / logs

No response

What component(s) does this bug affect?

[ ] area/cognitive: Cognitive project
[ ] area/core: Core project
[ ] area/deep-learning: DeepLearning project
[ ] area/lightgbm: Lightgbm project
[ ] area/opencv: Opencv project
[ ] area/vw: VW project
[ ] area/website: Website
[ ] area/build: Project build system
[ ] area/notebooks: Samples under notebooks folder
[ ] area/docker: Docker usage
[ ] area/models: models related issue

What language(s) does this bug affect?

[ ] language/scala: Scala source code
[ ] language/python: Pyspark APIs
[ ] language/r: R APIs
[ ] language/csharp: .NET APIs
[ ] language/new: Proposals for new client languages

What integration(s) does this bug affect?

[ ] integrations/synapse: Azure Synapse integrations
[ ] integrations/azureml: Azure ML integrations
[ ] integrations/databricks: Databricks integrations

github-actions[bot] commented 11 months ago

Hey @kushagra1606 :wave:! Thank you so much for reporting the issue/feature request :rotating_light:. Someone from SynapseML Team will be looking to triage this issue soon. We appreciate your patience.