![]() In order to complete the prospective memory task participants had to reset a clock every 60s by pressing the ‘x’ key while simultaneously performing the ongoing task. (In practice trials the ISI was substituted by a correct/incorrect and RT notification message.) The inter stimulus interval was filled with a white noise screen presented from. Pictures were displayed one by one in random order on a PC screen for 600 ms. IAPS emotional arousal ratings does not differ between the selected pictures (Negative: M = x, SD = x Positive: M = x, SD = x Neutral: M = x, SD = x). In total we use 25 negative, 25 positive and 25 neutral pictures. The images varied significantly in IAPS valence ratings, with lowest valence for negative pictures (M = x, SD = x), intermediate valence for neutral pictures (M = x, SD = x), and highest valence for positive pictures (M = x, SD = x). The stimuli we used was selected from from the International Affective Picture System IAPS (Lang et al., 2005). Participants had to decide whether or not the present picture was presented one stimulus before by pressing the ‘space’ key or by letting the stimulus pass in case of non hit. The ongoing task was a visual one-back task. The Time-Based Prospective Memory task was formulated with two components Msg="Correct! Time elapsed = " + elapsedTimeįor showing elapsed time in a textStim for a duration of 1 second, you only need to set the text of the text component to your new msg variable, and this can be done in the Builder component in the text box using $msg ![]() Note, this only works if you have a stimType column in your new conditions file: # Begin Experiment Insert the following in relevant code component tabs of the practice routine. For elapsed time, you could refer to your clocks. When a correct response is achieved on a target add the following in the “End Routine” tab in a code component, which can be fed into your feedback textbox in the next routine. ![]() You may have an extra column called “stimType” that uses -1, 0 and 1 to define trials as foil, pre-target, and target respectively. Then, use new conditions file that you have just created in the trial handler, but use sequential ordering in the loop handler, since the randomisation is already achieved. Save this new conditions file into a csv e.g., newConditionFile.csv. To do this, you would randomise your stim file holding only foil stim, and insert repeating targets at random locations. For example, 20 stim including 3 repeating targets (6 target presentations) creates conditions of 15% hit (i.e., 3 repetitions). For this, you could create your stim list at the beginning of the experiment and work out how many targets vs foils you would need to achieve 15% hits. Well, if you want a oneback, that would mean consecutive or repeating targets. So, in your feedback, you want to provide information from the actual trial, rather than a set text, e.g., “Oops, that was wrong”? If so, please provide details of what you want in the feedback and we can give guidance on that. ![]() Msg="Correct! RT=" + resp.rt # toFixed() is a JS function, so no need here. If stimFile = one_back and respPractice = 'y': If stimFile = one_back and respPractice = 'y' Ĭorrection # python code does not use curly braces to separate blocks of code Then at my feedback routine: # Begin experiment tab # set whatever keypress values are appropriate for this trial: M圜lock.reset() # At the relevant time, reset the clock to zero e.g., at beginning of a routine/trial # Set a junk value for the first trial, as by definition we can't # have a one-back value there: In my practice block I have a practice trial routine and a feedback routine within a loop:Īt my trial routine I have: # Begin Experiment tab I’m trying to “mimic” the feedback of the Navon task demo. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |