[Eeglablist] Bug in pop_select?

[Makoto Miyakoshi]

Dear Fernando,

Thank you for reporting a potential bug.
I wonder if you are so kind to register your finding in the bug report list.
https://urldefense.com/v3/__https://github.com/sccn/eeglab/issues__;!!Mih3wA!VS0RrTZ-Sl-2GapOMh92efyPEsvP6MBICYLX3zS2xTa264niyQFaqA9DsPHkfMRD7BofiA$ 

I have never tried [-6 -2] but I do see that one may need to do like that
depending on the event structure.
I hope you also have another event at '-2' latency so that you can re-epoch
your data to that event so that you can avoid this issue.

Makoto

On Tue, Jul 21, 2020 at 9:11 AM Fernando Valle-Inclán <
fvalleinclan at gmail.com> wrote:

> Hi everyone,
>          I came across what seems to be a bug. I have epochs from -12 to 1
> s. When I select a time window including the 0 point (e.g., EEG =
> pop_select( EEG, 'time', [-6, -0] ), it works. However, when the time
> window does not include the 0 point (e.g., EEG = pop_select( EEG, 'time',
> [-6, -2] ), the resulting EEG structure contains only one epoch. Am I doing
> something wrong
> Thanks
> Fernando
> _______________________________________________
> 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
>