Fix numpy constant type in MO #4361
Closed
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
mvafin
force-pushed
the
fix/int64_type
branch
from
f5289bb to
347f372
Compare
|
Fix not relevant since code will be refactored |
|
@mvafin Do you think this could have any impact on #4745? In that issue I report what appears to be an OpenVINO-caused discrepancy between int32 and int64 dtypes. The dtypes are consistent in the ONNX and XML graphs, but when reading the network into OpenVINO's inference engine, it appears to infer the wrong dtype for nodes where that attribute is not explicitly specified |
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.
Type of np.iinfo(np.int32).max can be int32 or int64 depending on numpy version. Found manually.