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.
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
TFLite failures resulted from TF latest version upgrade resolved #6774
TFLite failures resulted from TF latest version upgrade resolved #6774
Changes from 1 commit
d918564
04c9b16
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Could you give a hint as to the reason for these changes ? is there any reason why the existing mechanism doesn't work in your research ?
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.
Yes, generally, we want to move towards keras quantization as TF gets more mature. What issues do you see?
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.
The issue here was the test case was not behaving as expected. When we need a quantized graph with quantized inference, then we should provide quant input(Uint8 or int8, based on settings chosen). But here it was feeding float input to the graph, so the failure. Also i think current change is to keep a uniform steps as followed similar to case of other operators. Any specific reason to move towards Keras quantization than TF quant ?
Please let me know, if still need to keep Keras quant. Thanks!