[FieldTrip] Several trigger names at same position

[Thomas Kustermann]

Hi Mick,

I hope I understood your problem correctly in that you want to identify
trials using a combination of successive triggers. If that's the case
you're most likely to solve the problem using a custom built trial-function
allowing you to identify trials using conditionals. An example can be found
here:
http://www.fieldtriptoolbox.org/example/making_your_own_trialfun_for_conditional_trial_definition

Best,
Thomas

On Thu, Jul 2, 2015 at 6:02 PM, Mick Lehmann <mick.lehmann at uzh.ch> wrote:

> Hi Fieldtrippers,
>
> I’m using the script for reading data and I have a special issue at
> cfg.trialdef.eventvalue (see script below). The thing is that I have
> several triggers at the exact same position and I want to analyze only a
> subgroup of events which is defined by a combination of two trigggernames /
> evenvalues. Does anybody know how to define those trials, meaning how to
> create an event as a combination of two triggernames?
>
> This is how the script looks like:
> VP = dir('*.dat');
> cfg = [];
> cfg.dataset                 = (VP.name);
>
>
> cfg.trialdef.eventtype      = 'Comment';
> cfg.trialdef.prestim        = 2;
> cfg.trialdef.poststim       = 6;
>
>
> cfg.trialdef.eventvalue     = {'HitHitReakt’ 'Cue_N3_neg'}; *The events
> should be read only if both conditions are fulfilled*
>
> cfg = ft_definetrial(cfg);
>
>
> cfg.demean = 'yes';
>
> dataHitHitReact = ft_preprocessing(cfg);
>
>
> dataHitHitReact = renamechannels(dataHitHitReact);
>
>
> save dataHitHitReact_preproc dataHitHitReact
>
>     fprintf('%s not found.\n',cfg.trialdef.eventvalue{1})
>
>
>
> I'm deeply grateful for any help.
>
> Thanks,
> Mick
>
>
>
> _______________________________________________
> fieldtrip mailing list
> fieldtrip at donders.ru.nl
> http://mailman.science.ru.nl/mailman/listinfo/fieldtrip
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.science.ru.nl/pipermail/fieldtrip/attachments/20150703/a3d78040/attachment-0002.html>