-
Notifications
You must be signed in to change notification settings - Fork 5
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
Predictions differ #8
Comments
Do you have the result of "ebm2onnx.get_dtype_from_pandas(test_df)" or can you share the test set? |
Hi @MainRo, thanks for looking into it! |
I started to analyze the issue but did not find yet where it comes from. The scores associated with each term do not seem correct in the converted model.
|
@Hoeze forget my previous comment. Can you check the type of the splice_site_is_expressed column when training the model? Especially, check that it is declared as an int and not a float. This is a categorical column and the values in the dataframe are 0 or 1. The type of the column in the parquet file is integer, but I see that internally, ebm considers them as floats before doing the categorical encoding. The difference comes from this feature, and it is probable that it is because at some point it is converted to a float. When I change the type of this column to string and update the internal types of the ebm model, I have similar values between interpret and onnx. |
Thanks a lot @MainRo, now this makes a lot of sense. I manually fixed this in the onnx models using onnx-modifier. |
Description
I would like to convert an interpret v0.2.7 model to ONNX for conserving it for the future.
However, the predictions that I get strongly differ from the original model:
What I Did
My conversion script:
Further, you can find all necessary files to reproduce my issue in the attached zip file:
onnx_test.zip
Any help would be highly appreciated!
The text was updated successfully, but these errors were encountered: