[Eeglablist] what is 'event latencies recomputed' warning

[Delorme, Arnaud]

Hi Neeraj,

Yes, everything is fine.
We have renamed the second warning to 

eeg_insertbound(): boundary events inserted and N events removed

It does mention that event latencies have been recomputed because when boundary events are inserted, EEGLAB recompute event latencies to exclude the missing data portions. This is a technicality that might confuse people though, so we have removed that text.

Cheers,

Arno

> On Jan 7, 2020, at 4:45 PM, Neeraj Sharma <neerajww at gmail.com> wrote:
> 
> Hi,
> 
> Almost for all my BDF files (12 nos) I get the below warning message:
> eeg_insertbound(): N1 boundary (break) events added.
> eeg_insertbound(): event latencies recomputed and N2 events removed.
> 
> where N1 and N2 are in some hundreds.
> But on verifying the event count after epoching, I find that nothing has
> been removed.  Can someone help me to gain confidence that the warnings can
> be safely discarded, and event timestamps are preserved. I verified and
> found it is safe. But the wording of the warning appears too strong to let
> it go.
> 
> I think the warning comes because I alter the EEG.event.type for some of
> the event labels.
> 
> Best regards,
> Neeraj
> _______________________________________________
> 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