Bug in IO module for BrainVision: Wrong conversion from Seconds to Hertz
See original GitHub issueIn BrainVision Recorder *.vhdr files, the highpass filter settings are often listed as “low-cutoff in seconds”. The relevant mne.io function translates this into Hz as such:
With this method, the standard setting of low-cutoff=10s
is translated to highpass=0.1Hz. However, the BrainProducts website specifies 0.016Hz (see under “Lower cutoff frequency (high pass) / time constant”).
The conversion from seconds to Hz is probably not implemented correctly in the mne.io function for brainvision. Or am I missing something?
Some references:
Issue Analytics
- State:
- Created 6 years ago
- Comments:6 (5 by maintainers)
Top Results From Across the Web
What's new — MNE 1.2.2 documentation
Fix bug in mne.io.read_raw_brainvision() when BrainVision data are ... (keep time in seconds) instead of time_format='ms' (convert time to ...
Read more >Bug List
ID△ Product△ Comp▽ Assignee△ Status△ Resolution△ Changed△
670 EEGLAB Plugin f bugzilla‑owner RESO DUPL 2008‑07‑09
669 EEGLAB Plugin f bugzilla‑owner RESO FIXE 2008‑11‑12
700 EEGLAB Plugin...
Read more >raveio: File-System Toolbox for RAVE Project
BugReports https://github.com/beauchamplab/raveio/issues ... read-brainvision-eeg . ... install_modules(modules, dependencies = FALSE).
Read more >OpenViBE Bug Tracker - Inria
BrainVision VAmp can acquire data at 10 or 20 KHz in "fast mode", but even in this mode the only option in OpenViBE...
Read more >Importing Continuous and Epoched Data - EEGLAB Wiki
File-IO is a Fieldtrip module that imports a variety of data formats. ... build a matrix of random test data (32 channels, 100...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hello. My name is David Medine and I am a developer at Brain Products. The reason they use a time constant to represent the nature of a filter is for strange, convoluted, historical reasons.
What is important is that sappelhoff is correct. The denominator should have a factor of 2pi in it.
Thanks for the confirmation @dmedine. Looks like #5000 should be correct, then.