eeglab latency to event without sfreq
See original GitHub issuewhen working on annotations to events I realize that the eeglab reader
convert eeg.latency
to sample index with int(latency)
see: https://github.com/mne-tools/mne-python/blob/master/mne/io/eeglab/eeglab.py#L697
reading https://sccn.ucsd.edu/wiki/Chapter_03:_Event_Processing it seems that latency is in seconds to converting to events would require sfreq
@jona-sassenhagen @smgutstein @mmagnuski thoughts? is this a bug?
Issue Analytics
- State:
- Created 6 years ago
- Comments:10 (10 by maintainers)
Top Results From Across the Web
b. Events - EEGLAB Wiki
Select menu item Edit → Event values to inspect the imported event types and latencies. Importing events from a MATLAB array or text...
Read more >Makoto's useful EEGLAB code - SCCN
The following code addresses this issue so that EEG.event and EEG.epoch have only one event that has latency zero. % Delete non-time-locking ...
Read more >Command line tools - Semantic Scholar
EEGLAB Data Structures. 1. EEG. - root 'dataset' structure .data. - the dataset data (2-D, 3-D matrix) .chanlocs. - channel locations substructure .event....
Read more >167 questions with answers in EEGLAB | Science topic
When I import eeg data inside of eeglab it does not show me any events which is ... No positive peak(P100) was found...
Read more >to figure out how to make scripts in eeglab. First run a ...
latency of the trigger. c. Add event triggers into file: file>importeventfile>from matlab array: type in “EEG.event” into array.
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
Open a new issue
There are some points mentioned here that are left to adress - one of which is dealing with float latencies. Should I open a separate issue about that or should we leave this one open?