Skip to content
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

Lo Segmented packet DE fields can be spread across packets #1143

Closed
Tracked by #922
sdhoyt opened this issue Nov 12, 2024 · 0 comments · Fixed by #1144
Closed
Tracked by #922

Lo Segmented packet DE fields can be spread across packets #1143

sdhoyt opened this issue Nov 12, 2024 · 0 comments · Fixed by #1144
Assignees
Labels
Ins: Lo Related to the IMAP-Lo instrument Level: L0 Level 0 processing
Milestone

Comments

@sdhoyt
Copy link
Contributor

sdhoyt commented Nov 12, 2024

For the Lo L0 Direct event segmented packets, we have a new understanding that an individual field within the direct event can be spread across packets. For example, the first 4 bits of a direct event time can be in packet 1 and the last 8 bits of the direct event time can be in packet 2. Commas were previously introduced to the combined binary string to mark where the segments end to help handle padding at the end of each packet to make them divisible by 8. However, since fields can be split across packets, there shouldn't be padding across packets and the comma is no longer needed.

@sdhoyt sdhoyt mentioned this issue Nov 12, 2024
12 tasks
@sdhoyt sdhoyt self-assigned this Nov 12, 2024
@sdhoyt sdhoyt added Ins: Lo Related to the IMAP-Lo instrument Level: L0 Level 0 processing labels Nov 12, 2024
@sdhoyt sdhoyt added this to IMAP Nov 12, 2024
@sdhoyt sdhoyt added this to the Nov 2024 milestone Nov 12, 2024
@github-project-automation github-project-automation bot moved this to Done in IMAP Nov 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Ins: Lo Related to the IMAP-Lo instrument Level: L0 Level 0 processing
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

1 participant