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

Acquisition pipeline should allow side-channels that produce data at a different rate #176

Open
cmeyer opened this issue Feb 23, 2024 · 0 comments
Labels
audience - developer affects internal development or blocks another issue effort - week a week or less impact - high has difficult or onerous workaround reach - small affects a few users weekly

Comments

@cmeyer
Copy link
Collaborator

cmeyer commented Feb 23, 2024

This is part of a larger project, but the idea is that if we want to return data that isn't produced in the primary acquisition loop (e.g. drift data) it is impossible to get that data out of the acquisition loop currently. This is partially implemented on a branch (by me) but not merged yet.

@cmeyer cmeyer added good first issue good for newcomers impact - high has difficult or onerous workaround stage - waiting reach - small affects a few users weekly audience - developer affects internal development or blocks another issue effort - week a week or less and removed good first issue good for newcomers stage - waiting labels Feb 23, 2024
@cmeyer cmeyer self-assigned this Mar 18, 2024
@cmeyer cmeyer removed their assignment Jul 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
audience - developer affects internal development or blocks another issue effort - week a week or less impact - high has difficult or onerous workaround reach - small affects a few users weekly
Projects
None yet
Development

No branches or pull requests

1 participant