[Eeglablist] How to keep urevent information even after epoching

[Daniele Marinazzo]

Hi,
I remember seeing this issue coming up other times, maybe you will find the
proper answer in past or future replies.
Here is the link to a pipeline compiled by Antonio Schettino (UGent), which
if I remember correctly addresses and solves this issue.
https://osf.io/z4es2/

Hope this helps.
Daniele


On Mon, 16 Jul 2018, 06:10 Michelle Lee, <michelle.lee98 at gmail.com> wrote:

> Hello everyone,
>
> I am having some trouble with my ERPs in that none of them seem have a P1,
> P2 or EPN at all. We expected at least a little consensus to this pattern
> for all of our conditions.
> We think the problem lies in the latencies -somehow they were all changed
> after epoching.
>
> I did some research and someone mentioned how it was important to keep all
> original information in the EEG.urevent structure so that all original info
> (including latencies I'm assuming) will remain with the data even after
> epoching and manually removing trials.
>
> However I don't really know how I can achieve this; by default, eeglab
> seems to change the EEG.urevent timeline.
> If anyone can provide any insight I would be very grateful!
>
>
> Thanks,
>
> Michelle
>
>
> _______________________________________________
> 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sccn.ucsd.edu/pipermail/eeglablist/attachments/20180716/a7b7e3f8/attachment.html>