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
Triton data converter (CMSSW_11_2_0_pre9) #2
base: master
Are you sure you want to change the base?
Triton data converter (CMSSW_11_2_0_pre9) #2
Changes from 2 commits
2762c02
05f2ca0
b4a3f2c
5bade57
d9bf227
920ee4f
47fb54c
70a522b
037c8b0
90ce2ed
e653471
6e336a3
8ebdcd0
15c99a4
81077f0
3231ad8
daabb94
2dabb92
9c14bf5
4037115
9faebc0
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.
I'm not sure if this change is correct. The original purpose here was a runtime check that the type in the user's code (
DT
) corresponds to the model specification on the server (byteSize_
). The converter can have a different byte size in the FPGA case, but is that what the server will return from the model specification?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.
I think this is necessary. I think the model specification on the server should use a type with the appropriate bitwidth (i.e. for the ap_fixed<16,6> FPGA setup the server returns UINT16 for the data type, and for a FP16 GPU model I think something similar would get done). But the user wants to just load the data as float32s in these cases.