[Eeglablist] Events not listed when extracting epochs with pop_epoch

Stephen Politzer-Ahles politzerahless at gmail.com
Fri Sep 14 16:03:46 PDT 2012


Hi Becky,

May I ask what kind of system your data are originally from?

I've had similar issues when working with .eeg data previously epoched in
Neuroscan. What worked for me was to use Edit -> Select epochs/events
instead of using Tools -> Extract Epochs. Then instead of selecting events
from the "Type" button (which only included one event type--'TLE'), I put
the codes associated with each condition in the 'epochtype' field. It seems
that, depending on the nature of your data, the codes you're looking for
may be in EEG.event.type or in EEG.event.epochtype, and yours might be the
latter if they were previously epoched in another system. This is just my
guess, though; the problem could be something different.

Best,
Steve

On Thu, Sep 13, 2012 at 3:55 PM, Becky Prince <becky.prince at york.ac.uk>wrote:

> Dear EEGLAB users,
>
> I'm trying to create epochs around a set of events in my data.  The event
> markers are all numbers (1 and 50:89).  When I go to Tools -> Extract
> Epochs, then click the '...' in the 'Time-locking event type(s)' row to
> select from the events in my data, only two event types (1 and 50) appear
> in the event types browser box.  I know that I have more event types
> because I've checked EEG.event.type and Edit -> Event values.
>
> For example, here is an event marked '55':
>  >> EEG.event(9)
>  ans =
>         type: '55  '
>         latency: 10726
>         duration: 0
>
> To extract the epochs around the events 50:89, I've tried scripting this:
>   EEG = pop_epoch( EEG, {  '50' '51' '52' '53' '54' '55' '56' '57' '58'
> '59'...
>     '60' '61' '62' '63' '64' '65' '66' '67' '68' '69'...
>     '70' '71' '72' '73' '74' '75' '76' '77' '78' '79'...
>     '80' '81' '82' '83' '84' '85' '86' '87' '88' '89'  },...
>     [-0.2  0.5], 'newname', '4_1_vad_ep', 'epochinfo', 'yes');
>
> But this produces an error (regardless of whether the event values are
> space-separated or comma-separated):
>   ??? Error using ==> pop_epoch at 229
>   pop_epoch(): empty epoch range (no epochs were found).
>
> I also get the above error when trying to epoch a single event value.
>  Does anyone know why the epoch extraction isn't working?  Did I miss a
> step somewhere, like editing the event fields or values?  I'd be very
> grateful for any advice!
>
> Thanks,
> Becky
>
>
>
>
> _______________________________________________
> Eeglablist page: http://sccn.ucsd.edu/eeglab/eeglabmail.html
> To unsubscribe, send an empty email to
> eeglablist-unsubscribe at sccn.ucsd.edu
> For digest mode, send an email with the subject "set digest mime" to
> eeglablist-request at sccn.ucsd.edu
>



-- 
Stephen Politzer-Ahles
University of Kansas
Linguistics Department
http://www.linguistics.ku.edu/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sccn.ucsd.edu/pipermail/eeglablist/attachments/20120914/bf3f3814/attachment.html>


More information about the eeglablist mailing list