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 19 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.
here's how I would reduce duplication:
iconverter
tocurr_input.defaultConverter()
below (& do the same for the outputs further down)defaultConverter()
just has to check if the input parameter is non-empty, otherwise it tries to get a standard converter (as currently implemented)inConvMap
can be removed entirely (maybe not right away if you still want to test things)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.
Ok, yes, this is cleaner, Ill make this change now, thanks. Regarding 5), I think we still want to let the user define their own converter. For example, in the case of FACILE the server would be configured to request FloatToApFixed16F6 as the converter, but if a dedicated FACILE for FPGA producer is written, it can use the same server and would need to use a different converter.
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 can imagine there might be cases where the user wants to provide an alternate converter, but I'm confused about your example. Why would a dedicated producer need to use a different converter for the same server?
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.
Im envisioning a dedicated FPGA producer that is aware of the
ap_fixed<16,6>
type that is needed by the server, so it places each input in the data vector already converted, so the converter is basically just a defaultUINT16
converter.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.
Ah okay, I understand now.