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.

Sign up for GitHub

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

Jump to bottom

Determine when to end stream #2

Open
HagaiHargil opened this issue Sep 30, 2021 · 2 comments
Open

Determine when to end stream #2

HagaiHargil opened this issue Sep 30, 2021 · 2 comments

Comments

@HagaiHargil
Copy link
Contributor

Currently rPySight doesn't know when to end reading from the data stream. During online acquisition it's less of a problem, but during replay the rendering window simply hangs instead of gracefully exiting.
@HagaiHargil
Copy link
Contributor Author

I need to do some Future shenanigans here - the thread that spawns the call_timetagger.py task needs to be polled during the looping and checked whether the TT is already done.

@HagaiHargil
Copy link
Contributor Author

I managed to fix the replay portion of this issue by checking whether the Arrow stream is closed. The question still remains on how to signal rPySight that a live acquisition is over. When the GUI will function again we might want to add a button there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@HagaiHargil