-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
[MO] Range output_type correction for FP16 #6590
Merged
lazarevevgeny
merged 14 commits into
openvinotoolkit:master
from
pavel-esir:change_range_output_type
Aug 2, 2021
Merged
[MO] Range output_type correction for FP16 #6590
lazarevevgeny
merged 14 commits into
openvinotoolkit:master
from
pavel-esir:change_range_output_type
Aug 2, 2021
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
pavel-esir
requested review from
a team,
mvafin,
achetver,
popovaan and
rkazants
and removed request for
a team
July 12, 2021 11:28
jane-intel
reviewed
Jul 12, 2021
jane-intel
reviewed
Jul 12, 2021
model-optimizer/unit_tests/extensions/back/ChangeRangeOutputType_test.py
Outdated
Show resolved
Hide resolved
jane-intel
reviewed
Jul 12, 2021
popovaan
reviewed
Jul 21, 2021
jane-intel
approved these changes
Jul 21, 2021
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.
Consider addressing @popovaan comment
pavel-esir
force-pushed
the
change_range_output_type
branch
from
July 27, 2021 08:25
4842dc3
to
5e75ef8
Compare
achetver
approved these changes
Jul 29, 2021
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.
Looks good to me
lazarevevgeny
suggested changes
Jul 29, 2021
lazarevevgeny
approved these changes
Jul 30, 2021
rnugmanx
pushed a commit
to rnugmanx/openvino
that referenced
this pull request
Aug 26, 2021
* added ChangeRangeOutputType.py * applied review comments * corrected error message - warn user to use FP32 * renamed ChangeCastOutputType.py et ell. * merged ChangeRangeOutputType.py, ChangeCastOutputType.py into a singe file * corrections * typo fix * applied comments: faster find_and_replace loop, wording correction
andrei-cv
pushed a commit
to andrei-cv/openvino
that referenced
this pull request
Aug 30, 2021
* added ChangeRangeOutputType.py * applied review comments * corrected error message - warn user to use FP32 * renamed ChangeCastOutputType.py et ell. * merged ChangeRangeOutputType.py, ChangeCastOutputType.py into a singe file * corrections * typo fix * applied comments: faster find_and_replace loop, wording correction
akuporos
pushed a commit
to akuporos/openvino
that referenced
this pull request
Sep 29, 2021
* added ChangeRangeOutputType.py * applied review comments * corrected error message - warn user to use FP32 * renamed ChangeCastOutputType.py et ell. * merged ChangeRangeOutputType.py, ChangeCastOutputType.py into a singe file * corrections * typo fix * applied comments: faster find_and_replace loop, wording correction
11 tasks
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.
Root cause analysis: during conversion to FP16 Range attribute
output_type
instead of being changed tonp.float16
was keptnp.float32
Solution:
output_tensor = [1, 2, ..., 100 000]
cannot ce casted to fp16 even if Range inputs are of fp32 type, such models essentially cannot be casted to fp16 without modification of the original file.Ticket: xxx-59003
Code:
Validation:
Documentation: