-
Notifications
You must be signed in to change notification settings - Fork 2
ds: UDP header format updates #232
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
Open
Tom-Willemsen
wants to merge
6
commits into
master
Choose a base branch
from
newer_header_format
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
e0e7e61
header_updates
Tom-Willemsen bf73fb1
Update PCB Board Number description in documentation
Tom-Willemsen 23bb6f3
Update doc/specific_iocs/datastreaming/Datastreaming_udp_packet_forma…
Tom-Willemsen da8d23a
Update UDP packet format veto descriptions
DaveTempleman 8681b79
Reference common veto bit definitions instead of duplicating
Tom-Willemsen 03e52f5
remove question from docs
Tom-Willemsen File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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.
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.
We'll need some docs somewhere of what the different "header types" are...
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 guess the intention is that these correspond to the information that's currently in wiring
.csvsuch asPacketType = DIM_OUT,SW_PosandCH, so that the "wiring table" is just left with an IP ->detector ID offsetmapping?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.
Jack's off on leave at the moment but when he's back we'll get the Header Types doc created.
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 guess if it is intended to encode permutations of
PacketType,SW_POS,CH, etc, then 65535 is probably sensible - it's plausible we could end up with a good few permutations.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.
What you have suggested last is what I envisaged for the packet type. Then have a look up table on the PC that works out what to do with the rest of the header and how the data all splits up.
I did consider trying to include that information in the header but I can see situations where we will end up with 128 bits of data. with 8 different types of data being sent out and I'm not sure we can encode that sort of flexibility directly into the header.
(could either be lots of diagnostics data or the pulse heigh of the surrounding 6 fibres in a Wavelength Shifting Fibre Detecor for position reconstruction)