Can't program summary data in task


Author
Message
Jin
Jin
Distinguished Member (3.5K reputation)Distinguished Member (3.5K reputation)Distinguished Member (3.5K reputation)Distinguished Member (3.5K reputation)Distinguished Member (3.5K reputation)Distinguished Member (3.5K reputation)Distinguished Member (3.5K reputation)Distinguished Member (3.5K reputation)Distinguished Member (3.5K reputation)
Group: Forum Members
Posts: 26, Visits: 103
Hi all,

I am trying to program our Dot Probe task (in Inquisit 4) to output summary data as well as the raw data, but whenever I tried to input the summary data syntax, I get a "not a valid setting" error (i.e. 'date' is not a valid setting). I'm not sure what exactly is incorrect; I've compared our program to other Dot Probes and it seems like the summary data portion is more or less the same.

Additionally I am trying to write an expression that would output the mean latency for each of the trials, but I'm not sure how to write the expression? I have uploaded the file to this post.

Thank you

Attachments
FaceDotProbe_ed.exp (561 views, 13.00 KB)
Dave
Dave
Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)
Group: Administrators
Posts: 13K, Visits: 104K
As detailed in the documentation, the <summarydata>'s /columns attribute only accepts *properties* (as well as values and expressions). I.e.

<summarydata>
/ file = "FaceDotProb_summary.iqdat"
/ columns = [date, subject, blockcode, latency, error, percentcorrect, ...]
...
</summarydata>

needs to read

<summarydata>
/ file = "FaceDotProb_summary.iqdat"
/ columns = [script.startdate, script.subjectid, ...]
...
</summarydata>

Things like 'error', 'latency' or 'blockcode' make no sense in a summary data file. A summary data file is supposed to capture *a single line of summary statistics*, and 'error' or 'latency' are neither. Those things belong in the trial-by-trial raw data file.

You don't need to write an expression to capture the mean latency for each <trial> element to the summary file. You can directly log the respective property:

<summarydata>
...
/ columns = [..., trial.abbl.meanlatency, trial.abbl.totalmeanlatency, trial.abbr.meanlatency, trial.abbr.totalmeanlatency, ...]
...
</summarydata>

meanlatency and totalmeanlatency should be identical in your case, but note the difference as detailed in the documentation:

meanlatency property:
The mean response latency for the specified element within the current block.

totalmeanlatency property:
The mean response latency for the specified element over the entire experiment.

GO

Merge Selected

Merge into selected topic...



Merge into merge target...



Merge into a specific topic ID...




Reading This Topic

Explore
Messages
Mentions
Search