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

Possible Resolutions to Out-of-Order frames in the nexus files #288

Open
Modularius opened this issue Dec 12, 2024 · 0 comments
Open

Possible Resolutions to Out-of-Order frames in the nexus files #288

Modularius opened this issue Dec 12, 2024 · 0 comments
Assignees

Comments

@Modularius
Copy link
Contributor

Description of task

If frames appearing out of temporal order in the nexus file proves problematic, a resolution should be decided upon. Possible solutions include:

Option Pros Cons
Discarding any incomplete frames at the aggregator stage Easy to implement If a single digitiser fails to transmit for an extended period, all frames would be lost during this fault
Maintain a latest timestamp variable and discard any digitiser messages that appears earlier, and does not belong to a currently cached partial frame Pretty easy to implement Some data loss
Add a pipeline component after the nexus writer that checks for out-of-order frames and reorders data as necessary No data loss Potentially difficult to implement, may not be feasible in real-time
Integrate aggregator and nexus writer No data loss Most difficult to implement, same problems as above, and loss of robustness
@Modularius Modularius self-assigned this Dec 12, 2024
@github-project-automation github-project-automation bot moved this to Backlog in Super-MuSR Dec 12, 2024
@Modularius Modularius moved this from Backlog to Todo in Super-MuSR Dec 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Todo
Development

No branches or pull requests

1 participant