[Eeglablist] How to keep urevent information even after epoching

[Arnaud Delorme]

Dear Michele,

It is unlikely that the problem is with epoching. These are the 8 test cases (programs) that run every night and check the integrity of the epoching function. 

https://sccn.ucsd.edu/svn/eeglab-testcases/trunk/unittesting_general/unittesting_popfunc/pop_epoch/
https://sccn.ucsd.edu/svn/eeglab-testcases/trunk/unittesting_general/unittesting_sigprocfunc/epoch/

Also it is a simple function. You can actually check yourself by zooming in on the data surrounding one event before and after epoching and check that it is the same. If there is a problem with event latencies, it probably occurs either when the events are written along with the raw data or when they are imported.

Best wishes,

Arno

> On Jul 13, 2018, at 6:15 AM, 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