[Eeglablist] Error while rejecting continuous data (eeglab 14)

[Rafał Jończyk]

Thank you Tarik for advice. I will have a go at your suggestions. I think
there might be something with the latest version of eeglab given that I
have never experienced such problems in previous versions, and it's not the
first time that I am analyzing *cnt files from neuroscan in eeglab.

Has anyone else experienced a similar problem?

Best,
Rafał

2017-04-12 3:10 GMT+02:00 Tarik S Bel-Bahar <tarikbelbahar at gmail.com>:

> Hello Rafal, a few notes below that may help, all the best!
>
> ********************************
> Yes you could try just changing the format of all the events by looping
> through them and rewriting them.
> It may not be about the numeric format, it may be how they are read and/or
> stored (cell vs. strong array, or something basic like that).
> See also addnewevents function mentioned on list previously, and some
> related messages,
> which may allow you to write in new events that are accepted by eeglab.
> However, this may be problem with new build as you're seeing, thus a
> bugzilla note would be cool when you have a chance.
> Another thing to check is if the same thing happens with the eeglab
> tutorial data too,
> which would be telling if there's something unique about your data and/or
> it's event structure.
>
>
>
>
> On Tue, Apr 11, 2017 at 10:37 AM, Rafał Jończyk <rafal.jonczyk at gmail.com>
> wrote:
>
>> Dear eeglablist community,
>>
>>
>> I have experienced some problems with event structure -- that's my guess
>> -- when rejecting fragments of continuous data (raw *.cnt files resampled
>> to 250Hz & filtered) in the latest version of eeglab. Interestingly, this
>> does not happen when I am using eeglab 13.6.5b on the same computer. Note
>> that I am not rejecting the onset of the data.
>>
>>
>> The error:
>>
>>
>> eeg_insertbound(): 3 boundary (break) events added.
>>> eeg_insertbound(): 3 boundary (break) events added.
>>> Warning: converting all event types to strings
>>> BUG 1971 WARNING: IF YOU ARE USING A SCRIPT WITTEN FOR A PREVIOUS
>>> VERSION OF
>>> EEGLAB TO CALL THIS FUNCTION, BECAUSE YOU ARE REJECTING THE ONSET OF THE
>>> DATA,
>>> EVENTS WERE CORRUPTED. EVENT LATENCIES ARE NOW CORRECT (SEE
>>> https://sccn.ucsd.edu/wiki/EEGLAB_bug1971);
>>>
>>> Error using cell/strmatch (line 19)
>>> Requires character array or cell array of strings as inputs.
>>>
>>> Error in eeg_eegrej (line 147)
>>>     indBound2 = strmatch('boundary', { event2(:).type });
>>> Error while evaluating DestroyedObject Callback
>>
>>
>>
>> Could you give me a hint how to resolve the problem and continue working
>> with the latest version of eeglab? Is it because my events are numeric?
>>
>>
>>
>> Best,
>> Rafał
>>
>> --
>> Rafał Jończyk
>> Assistant Professor
>> Faculty of English
>> Adam Mickiewicz University, Poznań | Poland
>>
>> _______________________________________________
>> Eeglablist page: http://sccn.ucsd.edu/eeglab/eeglabmail.html
>> To unsubscribe, send an empty email to eeglablist-unsubscribe at sccn.uc
>> sd.edu
>> For digest mode, send an email with the subject "set digest mime" to
>> eeglablist-request at sccn.ucsd.edu
>>
>
>


-- 
Rafał Jończyk
Assistant Professor
Faculty of English
Adam Mickiewicz University, Poznań | Poland
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sccn.ucsd.edu/pipermail/eeglablist/attachments/20170412/bcd47a0f/attachment.html>