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

Implement checking of FrameReceiver status before starting acquisitions #56

Open
GDYendell opened this issue Feb 6, 2025 · 0 comments
Assignees

Comments

@GDYendell
Copy link
Contributor

Previously the FrameProcessorAdapter performed checks via the FrameReceiverAdapter that the frameReceiver has all of its free buffers available to avoid confusing failures. This was removed here.

The generated start_writing method should be disabled (.enabled = False, e.g. here and a @command method added to FrameProcessorController the does the checks and then calls the start_writing method, which is still available internally, just not exposed to the transport layer (I think).

Acceptance Criteria

  • FrameProcessorAdapterController does not allow start writing if frame receiver status is bad.
@GDYendell GDYendell moved this to Current Sprint in FastCS Development Feb 6, 2025
@GDYendell GDYendell moved this from Current Sprint to In Progress in FastCS Development Feb 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: In Progress
Development

No branches or pull requests

2 participants