firstcharlatency and lastcharlatency data

Back

Home
»
Millisecond Forums
»
Inquisit 4
»
firstcharlatency and lastcharlatency data

firstcharlatency and lastcharlatency data

Author	Message
mcarr4	mcarr4 posted 13 Years Ago Topic Details Share Topic
Group: Forum Members Posts: 4, Visits: 1	Hi There are two types of trials that I want to record firstcharlatency and lastcharlatency for (this is the basic outline): <openended emotion> /stimulusframes = [1=emotion] </openended> <openended concrete> /stimulusframes = [1=concrete] </openended> So in the <data> I have specified that I want to record openended.emotion.firstcharlatency, openended.emotion.lastcharlatency, openended.concrete.firstcharlatency, and openended.concrete.lastcharlatency The problem is that in the data output, these values continue to carry through each row even when they are not relevant. For example, if an emotion trial is run, and next a concrete trial is run, then in the data output the ‘firstcharlatency and lastcharlatency’ for the emotion trial will still show up on the line of data for the concrete trial. Is there a way to only record these latencies for the relevant trials? Or could I reset the values to 0 using /ontrialbegin? When I tried, it said it was a read-only property. Thanks for the help!! -Michelle
	Reply Like 5
Dave	Dave posted 13 Years Ago ANSWER Post Details Share Post
Group: Administrators Posts: 13K, Visits: 108K	Is there a way to only record these latencies for the relevant trials? That's what you're doing already. The point is: Of course those variables don't change anymore after the respective trials have been run, thus the values stay the same. Or could I reset the values to 0 using /ontrialbegin? When I tried, it said it was a read-only property. No. A latency is a read-only property -- latency data is provided by your subjects and one should not be able to change that data (think of all the catastrophic errors that might cause). Your only option would be to write the respective latencies to <values> entries, reset those values back to 0 (or something like 'n/a') at some point and then record those values to the data file (instead of the trial properties you're logging right now). However, all of this strikes me as an unnecessary exercise as it is trivial to discard the firstchar- and lastchar-latency columns for all except the relevant trials when processing and aggregating the raw data for analysis.
	Reply Like 4
mcarr4	mcarr4 posted 13 Years Ago ANSWER Post Details Share Post
Group: Forum Members Posts: 4, Visits: 1	Right! that is true. As usual, a simple solution from a different perspective. Thanks!
	Reply Like 4