Skip to content

Conversation

moan0s
Copy link
Contributor

@moan0s moan0s commented Dec 16, 2021

This tries to solve the problem that a user not familiar with the setup forgot to activate the localite-flow but has a hard time of finding the source of the problem

@agricolab
Copy link
Member

agricolab commented Dec 18, 2021

The receiver looks for the localite_marker stream using resolve_stream from pylsl. This function has an inbuilt waiting time, that is, how long it looks before returning an empty list. It always returns after the waittime.

That means: If the timeout is different than the wait-time, that'll cause issues. You might want to forward the timeout argument via the Receiver to resolve_streams, and catch the empty list in the Receiver (e.g. here instead of the Coil. Alternatively, skip timeout completely, and just catch the empty list after the default wait time. That'll do the job of informing the examiner with an more informative error message.

https://github.com/labstreaminglayer/liblsl-Python/blob/master/pylsl/pylsl.py#L535-L538

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants