I am trying to create a visuospatial short term memory task where the participant will be presented with a pattern of dots in a 4*4 matrix for about 1 second which they have to memorize. After a gap of about 2 seconds, the participant will be presented with a blank grid into which they should click with the mouse to reproduce the same pattern. I would also want the participant to be able to remove a dot by clicking again.
So here is my problem: I have been able to present a 4*4 grid with a randomized pattern of dot stimuli in it which goes about in a loop. I have done this without writing any code i.e. I have made a grid image in the background and added 16 polygons on the builder window. In the conditions file, I have specified the visibility of each dot (0 = invisible, 1 = visible). That is, I have 16 values on each row to control the visibility of the dots on that particular trial.
Next, I have gone back to each of my dot stimulus components and entered the appropriate column name in the opacity field of each stimulus (i.e. dot_1, dot_2, etc).
But how do I get the response from the participant?
Hi, did you ever figure this out? I am trying to create a similar experiment (4x4 matrix displaying dot locations, filler task, then recall dot locations). It’s proving tricky and I am spending hours going through forums to see how others have managed it. If you did manage to programme it, could you share please?
If you look at my code example in the topic How do I present one questionnaire after the participant clicks on one image displayed in sequence? (March) you can see an example of how to do this (my tiles happened to be in a circular arrangement but the idea is similar). Depending on your task instructions (‘click what you can remember’ vs ‘you must click at least n out of m squares’) you will want to change wrap the mouse part in a timer, a counter, or offer a ‘done’ button (could be ‘click outside the grid when done’).
I think doing the grid with filled rectangles is a good strategy, though someone with a better idea of draw-times, and memory usage would be able to comment. My guess is that this is a very low footprint experiment so it may not matter.
