aolabNeuro/brain-python-interface

end of experiment being truncated on ecube

Open

#49 opened on Apr 7, 2021

View on GitHub
 (3 comments) (0 reactions) (0 assignees)Python (2 forks)auto 404
bughelp wanted

Repository metrics

Stars
 (4 stars)
PR merge metrics
 (PR metrics pending)

Description

the final event code and between 20-30 clock cycles are consistently being truncated from the end of the experiment in the ecube digital recordings.

my theory: when we command servernode to end the recording, it hasn't yet received those 20-30 cycles, due to a ~150ms delay probably due to latency between the ecube and servernode.

solution: introduce at least that much delay at the end of the experiment before commanding the ecube to stop recording. better solution: have whitematter introduce a feature that triggers recording start/stop on a given digital input

Contributor guide

Research direction
Investigate the recording stop command and add a delay before stopping the ecube recording.
Tech stack
python
Domain
backend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Python
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60