UDP ephys #783
Open
UDP ephys #783
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
k1o0
force-pushed
the
udp_ephys
branch
2 times, most recently
from
c9bc812 to
51d3a20
Compare
|
Changes unknown |
oliche
requested changes
Jun 30, 2025
Member
oliche
left a comment
oliche
left a comment
There was a problem hiding this comment.
It may be nice to add one line to the documentation so that users are aware of this feature.
Also if it is there I would probably test it next time I have to perform a recording with some researchers here in Lisbon !
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Here is the UDP function for the ephys rig. It should work by calling prepare_ephys_session with the service-uri arg. Please double-check the behaviour of the abort process: when a user types 'abort' the local raw_ephys_data folder is removed (raises if not empty), followed by the remote experiment description stub and status files. The user is then prompted on whether to remove the empty local session folder. If they type yes (default: no), the local session folder is removed. The remote session folder is left untouched and the transfer_me.flag is not created.
I have not tested this with multiple chained protocols and am simply mocking the UDPs from a behaviour rig.