-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Fixes OneHotEncoding Issue #4974
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
Conversation
| CompareSelectedColumns<bool>("PredictedLabel", "PredictedLabel", transformedData, onnxResult); | ||
| CompareResults("F2", "F2", transformedData, onnxResult); | ||
| } | ||
| CheckEquality(subDir, onnxTextName); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Removing the pipeline to isolate transformer. OneHotEncoding is already used in a pipeline within RemoveVariablesInPipelineTest.
| var rightColumn = right.Schema[rightColumnName]; | ||
| var leftType = leftColumn.Type.GetItemType(); | ||
| var rightType = rightColumn.Type.GetItemType(); | ||
| Assert.Equal(leftType, rightType); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Review: Types don't necessarily have to be equal. For example, an ML.NET type can be Key{uint32} and uint32 in onnx.
ganik
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
![]()
harishsk
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
![]()
OneHotEncoding always increases the dimension by one, which is causing issues with Nimbus.
See: microsoft/NimbusML#472