[Eeglablist] Changes in eeg_checkset.m between EEGLAB version 11.04_03b and 11.04_04b

[Arnaud Delorme]

Dear Rakesh,

yes, we planned to support event type in string format only, to make it simpler and more robust.
However, this created problems with ERPLAB so we removed the feature in EEGLAB 12.

So the answer is 

1) you could handle both possibilities

2) you could have some code convert all the event to be string such as 

EEGTMP = EEG;
EEGTMP.event(1).type = num2str(EEG.event(1).type);
EEGTMP = eeg_checkset(EEGTMP, 'eventconsistency');

Best,

Arno

On 31 Mar 2013, at 08:24, Rakesh Sengupta wrote:

> Dear Arno, 
> 
> I am Rakesh Sengupta from Center for Neural and Cognitive Sciences, University of Hyderabad, India.
> 
> Recently we developed a toolkit for prepossessing EEG data in collaboration with Dr. Metthew Belmonte, basically aligning it to the behavioral data generated from the experiment ( Events and their latency values). 
> 
> In that toolkit, we used a EEGLAB functions, pop_loadset.m to load EEG .set file and pop_saveset.m to save updated EEG .set file. Recently we encountered some error in executing the code. So we reviewed the EEGLAB functions in question, and found that there is some difference in eeg_checkset.m (which is required by pop_loadset.m function). The detatils are given below
> 
> EEGLAB version: 11.04_03b :- 
>              
>                       Always Converts the event types to string.
> 
> EEGLAB version: 11.04_04b :- 
>  
>                      Converts all event types to string if the event type are heterogeneously integer or string but not if that are homogeneously integer. 
> 
> So, our question is, should we assume that the event types will always be strings or integers or should we need to handle both possibilities?.
> 
> Many Thanks, 
> 
> Regards,
> Rakesh

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sccn.ucsd.edu/pipermail/eeglablist/attachments/20130401/1624e2fc/attachment.html>