Thank you, you are correct, I figured that my analysis was actually using a
subset of the runs which doesn't contain all 69 conditions. I would still
like to use this subset of runs so I think I will make new para files that
assign less conditions (some conditions are stimuli of similar types that
Within a given session you must have all conditions represented. They
all do not need to be in the same run, but they must all appear at least
once across all runs. It looks like only 33 of the 69 are there. BTW, 69
is probably not a realistic number of conditions, way too big.
doug
Gabriel A.
Sorry about that, I attached the wrong error msg from while I was trying
"selxavg3-sess". They are numbered 1-69.
Wed Jul 14 18:24:59 EDT 2010
INFO (kan_ecev_207ab): RunList = 008 009 010 011 012 013 014 015 016 017 018
019 020 021
ERROR: there are 33 non-null conditions in the
paradigm file. How
69 conditions? Are they numbered 1-69? That output does not have the
right error msg in it.
Gabriel A. Tobon wrote:
> Hello,
>
> I have event related data with 69 different conditions, and every
> condition does not appear in every run. This causes selxavg-sess to
> throw an error. Part of th
Hello,
I have event related data with 69 different conditions, and every condition
does not appear in every run. This causes selxavg-sess to throw an error.
Part of the relevant debug output is below. Why does every condition need
to appear in every run?
Thank you,
Gabe
echo "$sess " | & tee
