![]() This is not very feasible for my case considering that I would have to vary the time interval between two numerical stimuli within a trial. I understand that there was a post addressing the randomization of blocks, but I felt that it was more specific to experiments that only have one routine. While the experiment still works fine, randomization still doesn’t occur. To do this, I’ve placed a loop around all the blocks, with this loop titled “blocknames” in the picture. ![]() The next step for me is to randomize the presentation of these blocks, with one block denoting one level of SOA/time interval (e.g +750ms). I have already randomized the trials within each block. Hence, in total, there are 7 blocks here (only 4 are pictured though). One set of fixation_cross and VA_750ms (for example) constitutes a block. I have 7 levels of time intervals/SOAs (plus minus 750, 250 and 500, and 0ms), resulting in me creating my experiment in such a manner (see attached picture). They are supposed to press “a” if the numerical information is the same and “l” if it’s different.Īpart from varying the format of the visual numerical stimuli I am presenting, I also intend to vary the stimulus onset asynchrony (SOA)/time interval between the two stimuli. After the presentation of the 2nd stimulus, participants are to respond if these two stimuli are conveying the same information or not. Both visual numerical information and auditory numerical information will be presented sequentially. The visually presented numerical information will be presented in three forms - Arabic numerals (e.g 5), number words (e.g five), and non-symbolic magnitude (a picture of 5 dots). The Keyboard class, meanwhile, runs in a separate process and continually checks the keyboard hardware, allowing a precision more at the millisecond level.I am currently doing a reaction time and accuracy task that involves comparing visually presented numerical information and auditory numerical information. This is some time after the key is pressed - even if you are calling the function on every screen refresh (typically at 60 Hz), this limits the time resolution to 16.7 ms. This has the advantage that it returns the actual time that the key was pressed: when using event.getKeys(), one just infers the reaction time from the time that the function was called. The result is that it will return an empty list many times, until a key is actually pressed.īut PsychoPy's event module has actually been deprecated in favour of the newer Keyboard class. So it is usually called in a loop, often once per screen refresh, to detect when a keypress has occurred. It will always return an empty list unless a key has been pressed since the last call to the function. ![]() The question is, when I use the "getkeys" method, it always returns an empty list.Įvent.getKeys() is an instantaneous check of the keyboard buffer. ![]() I would feel my very gratitude to who helps. While timer.getTime() < time and (abs(rect.pos)< x/2 and abs(rect.pos)< y/2): Rect = visual.Rect(win, width = 50, height = 50, fillColor='white', pos = start_pos, name = 'target') Win = visual.Window(fullscr = False, size =, color = 'black', units = 'pix') #from import Keyboard as kbdįrom psychopy.iohub import launchHubServer I also tried eventclear, but seemed useless.įrom psychopy import visual, core, event,gui The RT shows that it main get the very first input in the buffer. The question is, when I use the "getkeys" method, it always returns an empty list. One has to push the botton(Here is keyboard) as soon as he hears the beep. It will run randomly from one side of the screen to the other. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |