Back to the main page.
Bug 2075 - Event Selection GUI (ft_trialfun_general)
| Status | CLOSED FIXED |
| Reported | 2013-03-22 12:46:00 +0100 |
| Modified | 2015-07-15 13:30:47 +0200 |
| Product: | FieldTrip |
| Component: | preproc |
| Version: | unspecified |
| Hardware: | PC |
| Operating System: | Linux |
| Importance: | P3 normal |
| Assigned to: | Jim Herring |
| URL: | |
| Tags: | |
| Depends on: | |
| Blocks: | |
| See also: |
- 2013-03-22 12:46:39 +0100
I had some trouble loading specific event codes using the GUI in ft_trialfun_general. (This is the GUI you get by setting cfg.trialdef.eventtype='gui'). While I would be allowed to select a specific event value, the trial selection window would list times for all events. The problem lies in this part of ft_trialfun_general: if (ischar(eventvalue(j)) && ~strcmp(eventvalue(j), 'Inf')) || ... (isnumeric(eventvalue(j)) && eventvalue(j)~=Inf)) settings=[settings; [eventtype(i), eventvalue(j)]]; else settings=[settings; [eventtype(i), {[]}]]; end It turns out that at least for my system, eventvalue(j) is a cell, so the ischar function will return a 0. This means that we get settings = ['trigger', []], which causes trial selection window to list all events. I made the following modification to the code on my system to get it to work properly: if (ischar(eventvalue(j)) && ~strcmp(eventvalue(j), 'Inf')) || ... (isnumeric(eventvalue(j)) && eventvalue(j)~=Inf) || ... (iscell(eventvalue(j)) && ischar(eventvalue{j}) && ~strcmp(eventvalue{j}, 'Inf')) settings=[settings; [eventtype(i), eventvalue(j)]]; else settings=[settings; [eventtype(i), {[]}]]; end But perhaps somebody would like to put in a more elegant fix to the actual code to account for the possible datatypes for eventvalue (i.e. cell/character/numeric or just cell/numeric?). Regards, Daniel Wong -- Daniel Wong, PhD (IBBME, University of Toronto) Erasmus Mundus Postdoctoral Fellow, Max Planck Institute Neural Oscillations Group Department of Psychology University of Konstanz Tel. +49 1609 9814144
Johanna - 2013-04-03 13:38:21 +0200
Hi Dan, Is this specific to using the GUI option? Also, can you please attach to this bug a small sample file of the relevant header/event file? What is the value of eventvalue that causes this problem? Also, what is your recording system? thanks!