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.

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

Visual P300 event markers not recorded #111

Closed
Maari13 opened this issue Jun 17, 2021 · 6 comments
Closed

Visual P300 event markers not recorded #111

Maari13 opened this issue Jun 17, 2021 · 6 comments
Labels
bug Something isn't working

Comments

@Maari13
Copy link

Maari13 commented Jun 17, 2021

ℹ Computer information

  • Platform OS: Windows 10
  • Python Version: Python 3.7.10
  • Brain Interface Used: Muse 2

📝 Provide detailed reproduction steps (if any)

  1. switch on your Muse device
  2. start streaming using BlueMuse or Petal Metrics (I tried with both and had the same issues)
  3. run the experiment with the command eegnb runexp -ip, and input the necessary parameters
  4. complete the experiment

✔️ Expected result

The title of the last column of the output/experimental data file is "Marker" and below it starting from the next row are zero markers denoting that no picture is presented at this time

❌ Actual result

The title of the last column is missing, and zeros start from data row 13 (row 14 of the file)

📷 Screenshots (this experimental was done using BlueMuse for streaming)

image

@Maari13 Maari13 added the bug Something isn't working label Jun 17, 2021
@ErikBjare
Copy link
Collaborator

ErikBjare commented Jun 18, 2021

I think this is a duplicate of #108

Are the markers not appearing at all, or is the column just missing values initially?

@Maari13
Copy link
Author

Maari13 commented Jun 18, 2021

The column is missing values initially: starting from data row 13 (or row 14 of the file) until the end of the file the values are present. I was wondering whether I can trust that the values that are present are aligned with the correct timestamp, or the fact that the markers start from row 13/14 means that they are shifted in time - I mean the marker on row 14 should really be on row 2?

@ErikBjare
Copy link
Collaborator

ErikBjare commented Jun 18, 2021

I'm fairly confident that they are aligned, but @JohnGriffiths might have a more confident answer.

@JohnGriffiths
Copy link
Collaborator

I agree. The lsl process writes to file what is received on the the current stream at each time point. I'm not aware of any way it would buffer or otherwise delay the stream output. Especially from the markers stream, which is running locally (as opposed to the EEG stream, which operates on Bluetooth data packets that are known to have a minimum and a variable lag).

@rschmaelzle
Copy link

Hi, I can confirm this issue. I was able to track it down - in part - to the muselsl-record function, where there is an if-condition that has a "save every 5s"-comment. Messing with this "catches" more markers (although it doesn't yet cure my problem). Hope this helps. I will keep digging myself into it a bit more.

@tmorshed
Copy link
Collaborator

tmorshed commented Apr 4, 2024

Closing to concatenate in #108.

@tmorshed tmorshed closed this as completed Apr 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

5 participants