|
Group: Administrators
Posts: 13K,
Visits: 104K
|
<values> are the *wrong* thing to be used like that. A <values> entry is a global variable. <values> are static, not dynamic, i.e. unless you explicitly set it to something during the course of the procedure, it remains unchanged. When you use an expression as a <values> entry's value as in
<values>
/ latencyneudommean = totalmeanlatency(trial.ldtneutraldominant1, trial.ldtneutraldominant2, trial.ldtneutraldominant3, trial.ldtneutraldominant4, trial.ldtneutraldominant5, trial.ldtneutraldominant6)
</values>
that expression gets evaluated *once* at the very start when the script parses the <values> element. At this point in time there are no latencies -- hence the expression evaluates to zero and that's what the <values> entry's value remains.
If you want something that's evaluated dynamically, the object to use is <expressions>, as in
<expressions>
/ latencyneudommean = totalmeanlatency(trial.ldtneutraldominant1, trial.ldtneutraldominant2, trial.ldtneutraldominant3, trial.ldtneutraldominant4, trial.ldtneutraldominant5, trial.ldtneutraldominant6)
...
</expressions>
with
<summarydata>
/ columns = [..., expressions.latencyneudommean, ...]
...
</summarydata>
|