-
Notifications
You must be signed in to change notification settings - Fork 1.9k
[1.0.0-preview] Bug? - Getting an exception while loading .ZIP model MultiClass-Classification trained with SdcaNonCalibrated #3209
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
Comments
Before this exception I am getting schema mismatch exception as below Schema mismatch for label column '': expected Key < UInt32 >, got Single To fix this exception I have added MapValuetoKey() and MapKeyToValue() transformations. Then when I start executing sample I am getting the other exception that it couldn't load model as mentioned earlier. |
adding @CESARDELATORRE for reference. This issue is happening only with SdcaNonCalibrated trainer |
Just to mention that right after training the model (multi-class classification) with SdcaNonCalibrated, the model works for making predictions. Also, we have tried with 3 different samples and three different datasets. We get the same behavior. If using another algorithm such as OVAAveragedPercentronTrainer, the model loads properly from the .ZIP file and the scenario works good end-to-end. So looks like a bug related to SdcaNonCalibrated? |
@Ivanidzo4ka Do I need to upgrade to latest version of ML.Net instead of ML.Net 1.0.0-preview to fix this error my sample? |
I am trying to migrate IRIS Classification sample in the repo here to v1.0.0-preview.
While loading the model for prediction I am getting the below error at the statement
the dataset format is like this
I have pushed the code to the Github repo here https://github.com/dotnet/machinelearning-samples/tree/migration/1.1.0-preview/samples/csharp/getting-started/MulticlassClassification_Iris
I did not understand the reason for the error. Could anyone help
The text was updated successfully, but these errors were encountered: