fix: Change the translational layer from numpy to torch during conversion to handle additional data types#3445
Conversation
zewenli98
reviewed
Mar 19, 2025
Collaborator
zewenli98
left a comment
There was a problem hiding this comment.
just some minor comments
peri044
added a commit
that referenced
this pull request
Apr 1, 2025
…sion to handle additional data types (#3445)
peri044
pushed a commit
that referenced
this pull request
Apr 29, 2025
This file contains hidden or 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
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.
Description
We use numpy internally to convert from torch tensor into TensorRT tensor. This PR changes that to Pytorch for comprehensive data type support (eg: BF16)
Fixes #3439
Type of change
Checklist: