Millisecond Forums

stimulus persistence after response not working

https://forums.millisecond.com/Topic22832.aspx

By nrouhani - 11/8/2017

hello! 

i'm trying to set up a trial where even after the response is collected, the stimulus persists. I (think) I followed the directions posted for previous questions on this, but it's still not working (i.e. having the erase = false). Would you have an idea of what i'm doing wrong? 

// STIMS
<picture memStim>
/ items = allStims
/ size = (30%, 30%)
/ select = values.memStim
/ erase = false
</picture>

<text newOld>
/ items = ("press 'n' if new, 'o' if old")
/ hjustify = center
/ size = (50%,50%)
/ fontstyle = ("Arial",30)
/ vposition = (55)
/ hposition = (50)
/ txbgcolor = (transparent)
/ txcolor = darkgrey
/ erase = false
</text>

// TRIAL
<block testing>
/ trials = [1-30 = oldSeq]
/ errormessage = false
/ screencolor = white
</block>

<trial oldSeq>
/ ontrialbegin = [values.memStim=list.memStims.nextindex]
/ pretrialpause = 1000
/ stimulustimes = [0=blankMem, memStim, newOld]
/ validresponse = ("n","o")
/ beginresponsetime = 0
/ responseinterrupt = trial
/ trialduration = 4000
</trial>
By Dave - 11/8/2017

nrouhani - Wednesday, November 8, 2017
hello! 

i'm trying to set up a trial where even after the response is collected, the stimulus persists. I (think) I followed the directions posted for previous questions on this, but it's still not working (i.e. having the erase = false). Would you have an idea of what i'm doing wrong? 

// STIMS
<picture memStim>
/ items = allStims
/ size = (30%, 30%)
/ select = values.memStim
/ erase = false
</picture>

<text newOld>
/ items = ("press 'n' if new, 'o' if old")
/ hjustify = center
/ size = (50%,50%)
/ fontstyle = ("Arial",30)
/ vposition = (55)
/ hposition = (50)
/ txbgcolor = (transparent)
/ txcolor = darkgrey
/ erase = false
</text>

// TRIAL
<block testing>
/ trials = [1-30 = oldSeq]
/ errormessage = false
/ screencolor = white
</block>

<trial oldSeq>
/ ontrialbegin = [values.memStim=list.memStims.nextindex]
/ pretrialpause = 1000
/ stimulustimes = [0=blankMem, memStim, newOld]
/ validresponse = ("n","o")
/ beginresponsetime = 0
/ responseinterrupt = trial
/ trialduration = 4000
</trial>

Most likely some _other_ element that inhabits the same screen area as "memStim" gets erase. The concrete candidate in your case is "blankMem", so you should make sure that that element's /erase setting is also 'false'.