Fix for Reduce extractors and normalizer #3136
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description: Fixed extractor for Reduce operations from ONNX. If the
axis
value in the Reduce op is not specified then the extractor creates a numpy array the following way:int64_array(None)
. This value is not None because it is a numpy array. So the ReduceAxisNormalizer creates a Const withint64_array(None)
value. This causes an issue in the transformations where the value of Const is compared with some other floating point values because numpy tries to compare None value and some floating point value.JIRA: 43166
Code:
Validation:
Documentation: