-
Notifications
You must be signed in to change notification settings - Fork 63
Error loading a model that was saved with mlnet auto-train #423
Comments
@RokoToken thank you for reporting this. Could you share the model.zip and small subset of TrainingData.csv for us to repro this issue. thx |
Modified Titanic CSV Dataset
MLNet CLI Command:
Nimbus Code:
Error:
|
There was a similar issue 6mo ago -- #201 -- We were fixing NimbusML scoring of models trained in the AutoML.NET CLI. @RokoToken: Can you post your MLModel.zip? Also, which version of the CLI are you using? |
@justinormont @ganik |
Is there a workaround for this? Should I use an older version of MLNet CLI? Is there a way to modify the output column through the Nimbus pipeline? Something like:
|
@RokoToken, the workaround will be to find the pipeline params from AutoML.NET and re-train same pipeline using either just ML.NET or NimbusML. Also can you try using pipeline.score(...) |
@ganik: Do you see anything odd with the posted model? @RokoToken: I would expect that the AutoML․NET CLI is producing a normal ML․NET model. Your current version is the newest released version. You can also re-train your model from the generated code which the CLI produced. You can uncomment the line |
@RokoToken sorry for delay, could you share pls titanic.csv file. The model does look ok, so it should work. thx |
I was able to debug through and get scoring after few fixes in NimbusML python code (not ML.NET). However return scores are NaN. dataset = FileDataStream.read_csv('E:/sources/tmp/titanic.csv') pipeline = Pipeline() @justinormont Could you see if you can score this in ML.NET. I am not getting any scores from this model. |
Describe the bug
When using the mlnet auto-train tool to create a model, and then load that model using NimbusML, an exception is being thrown.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Loading and scoring the model should work as expected.
Actual behavior
You get an exception and scoring is not completed:
Desktop (please complete the following information):
Additional Context
The text was updated successfully, but these errors were encountered: