Fix dynamic axes for ONNX models #1187
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
deliahu
approved these changes
Jun 30, 2020
vishalbollu
pushed a commit
that referenced
this pull request
Jun 30, 2020
(cherry picked from commit 53c0b37)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes #1186.
It appears that setting the input shape to a generic string should signify to the user that the shape is dynamic and can be of any size. Currently, the Cortex ONNX client only checks if
"dynamic_axes"is a substring of the shape dimension's value (if it's a string). As it appears to me, that's only a convention and the string can be set to anything.checklist:
make testandmake lint