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

OverflowError when HD-EEG data streamed to SigVisualizer #20

Open
iPsych opened this issue Mar 2, 2020 · 3 comments · May be fixed by #21
Open

OverflowError when HD-EEG data streamed to SigVisualizer #20

iPsych opened this issue Mar 2, 2020 · 3 comments · May be fixed by #21

Comments

@iPsych
Copy link

iPsych commented Mar 2, 2020

LSL SigVisualizer repeatedly crashes when It receive streamed EEG Inlet from 256ch EGI Amplifier. The program starts properly and visualize very short part of initial eeg signals from 256chs, than crash.

Traceback (most recent call last):

  File "/Users/User/Downloads/App-SigVisualizer-64fe663e88246c14fbd60b14eff84c228f5a85a6/paintwidget.py", line 216, in paintEvent

    -self.dataBuffer[0][ch_idx] + chan_offset)

OverflowError: argument 4 overflowed: value must be in the range -2147483648 to 2147483647

Abort trap: 6
@Yida-Lin
Copy link
Member

Yida-Lin commented Mar 3, 2020

Hi @iPsych , I currently do not have a physical amplifier here so I could not reproduce this issue. Do you have an XDF file recording that came from that amp, that I can use to simulate on my end?

@mvidaldp
Copy link

I had the same problem. After debugging for a while I realized it lies on a downsampling error:

A quick fix is to change this line:

stream_params['downSampling'] = srate > 1000

Setting downSampling to False up to 1024 instead of 1000 Hz, since it's a common sampling rate in EEG recordings. Thus if your stream sampling rate is below 1000 it will work without this hack.

@Yida-Lin, @iPsych, please could you fix this?

I'm quite sure it's the same error referenced on the other OverFlow issue:
#18

@Yida-Lin Yida-Lin linked a pull request Nov 20, 2020 that will close this issue
@Yida-Lin
Copy link
Member

Hi @mvidaldp thank you for your suggestion; sounds good, I created a PR #21 and could you please help verify whether it solves the problem? Thanks!

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 a pull request may close this issue.

3 participants