Millisecond Forums

Using /correctmessage, /responsemessage or /branch to another <trial> that plays the respective <sound> are all valid approaches.

Never mind - I'm pretty sure I can call it as a correctmessage=true(sound,200)  etc.....

Dave - just a quick question again: Is it possible to have a sound stimulus play on response?  We're trying to put together a 'fruit squash' type game and when participants press the fruit we'd like to have a 'squash' sound played.  Is this possible?

You either need to compute mean latency using <values> and log the respective value to the data file or do the same using one of the built-in meanlatency properties.

Now just another quick question about <summarydata> : Can I get it to store meanlatency for an RT task, as per the last line of the raw data file?  I'm guessing that I will need to define this in the script somewhere within values or variable, and then enter it as a summary column (i.e., values.meanlatency)

No worries -- I probably should have made the point more salient to begin with. Let me know if anything else comes up!

Apologies for missing that part, Dave. Thanks for your help.  All sorted.

As already mentioned in my previous reply, you ought to multiply by pixels to cast the expression to the correct unit:<values>
/ vertres = 1px * display.height
/ horizres = 1px * display.width
</values>

Ok, so I'm not really getting anywhere with this. I have the following trial which is a cue image which I want to display centrally.  I'm trying to set the position to be defined using an expression. I know that I can show centrally using 50%,50%.  I'd rather use the expression for consistency though, and as a test to check I'm getting it right.

> What I'm thinking is dynamically defining a position.  For instance, can I create a variable (displaypos) which equals (verticalresolution/2)?Yes, you can do that. You'll want to use the display.width and/or display.height properties to do that. Details can be found in the documentation for the <display> element. Note that width and height are returned as pure integers, so you'll have to multiply by 1px to convert to pixels.