Fix 'Missing messages!' warning#26
Merged
Merged
Conversation
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
1 participant
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.
With data taken at the detector lab, we noticed the "missing messages" warning in
_ingest_raw_data()when processing. This is because we started receiving SPIDR control packets (id'd with 0x5 header). A simple fix is to increment themsg_run_countwhen these packets appear, so now the count is what is expected.I also wrote the decoding for the "TPX3 command" (0x7) and "SPIDR control" (0x5) packets, but am leaving them commented out because they don't appear useful to us at the moment.