11/6/2022 0 Comments Read psyscope output into r
RatingScale exposes a flag, noResponse, which is True if the subject has not made a response. what happens will vary greatly, but the key idea is that there's a process for checking things every frame that will drop right into the existing model that the builder follows. So you might want something like that: a method called once per frame that can return some data and / or a status flag for your hardware. this will not only draws things on the screen but also checks the mouse and keyboard every frame. READ PSYSCOPE OUTPUT INTO R CODEWill write the python code that calls (). in builder/components/(), this lineīuff.writeIndented("%(name)s.draw()\n" % (self.params)) This is (for example) what the ratingscale.py component does (which is the one that I'm most familiar with). if so, they can just drop into the frame-by-frame loop. I'm wondering if, instead of writing a different kind of loop, maybe you can write your hardware handlers in a way that they can return data when queried on a frame by frame basis. so a loop gets created by the builder, and can handle everything for a given routine. My guess is that this is the loop you are asking about. (for me this is line # 670 of experiment.py). draw() method of patchStim, waiting for a key-press, and so on. Is what creates the while loop that goes frame by frame, e.g., calling the. In the () method, under the comment "#create the frame loop for this routine", the line:īuff.writeIndented('while %s and (t
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |