time stamp jump bug

Open
#102 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
python

Research direction

Start by reproducing the timestamp jump in the PyLSL and LabRecorder EEG recording workflow described in the report, comparing consecutive samples across the listed devices and operating systems. Done means identifying the source of the approximately +/-200,000 timestamp change and confirming either an end-user fix or a verified correction.

Written by the indexing model from the issue text.

Description

In something around ~2-3% of my LSL recordings (using PyLSL and LabRecorder) there are times in the EEG stream where the time stamp will have around +/- 200,000 added to it from one sample to the next. If this can be fixed with a change on my end I'd appreciate a solution - It can be manually fixed when analyzing offline data but it does cause an extra hassle when running at least 40+ sessions (have used 3 different eeg devices and 2 different computers, a windows and mac, and encountered this issue)

Dominant language
HTML
Stars
778
Forks
194
Avg merge
13m
Merged PRs (30d)
1

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from sccn/labstreaminglayer

All issues in sccn/labstreaminglayer

Similar issues

More Data Engineering issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.