[Eeglablist] ERP grand average does not reflect actual latency
daniele.marinazzo at gmail.com
Tue Mar 28 12:09:10 PDT 2017
focusing only on a tiny part of the erp, and only on the average, is not a
good way to analyze the data, since it makes too many assumptions on the
underlying distribution of data, individual variability, and on the ERP
time course as a whole.
Guillaume Rousselet, Cyril Pernet and others have explained this in great
detail, with code and examples, see for example these papers
and in these blog posts with code
hope this helps
On Tue, Mar 28, 2017 at 3:30 AM, Shih-Chun Kao <shihchunkao at gmail.com>
> Dear list,
> If I found a statistically significant P3 latency effect (~50ms) between
> two conditions in a within-subject design study but my grand average plot
> does not show such difference, what would be the cause for inconsistent
> results and what does such inconsistency suggest? I understand grand
> average is not the best illustration but I thought 50ms is a pretty big
> difference. Thank you!
> Eeglablist page: http://sccn.ucsd.edu/eeglab/eeglabmail.html
> To unsubscribe, send an empty email to eeglablist-unsubscribe at sccn.
> 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...
More information about the eeglablist