Make an object move to make the task harder Making things dynamic could allow you to, for instance: a shape that tracked the mouse by setting the shape position to be mouse.getPos() things change their attributes in time).Į.g. Using code as arguments allows us to easily make stimuli ‘dynamic’ (i.e. If you actually need a dollar symbol to be in your text, do:
#PSYCHOPY KEY NAMES LIST UPDATE#
Set a text object to have text "ABC" and have it update every repeat You can use this as more than a variable from your conditions file e.g.: Most dialog entries have the option to take raw Python code if you start your entry with $ (or have that by default). Hacking the script is useful to see how things work but it’s better to add your edits back into the Builder view. If you do your changes will NOT be reflected back in the Builder experiment. You could tweak this code and see the effects your edits have on the running of the experiment. You could save and run this exported script (that’s what Builder does each time you press run). T is always the current time in sec since the start of the Routine to find out what variables a Builder experiment ‘knows’ about e.g.:.trial is over)īuilder doesn’t know your intentions so plans for everything Compiling your experiment to python or JavaScript ¶Ī first step to combining your code with a Builder is to compile a builder script to coder and peek what’s “under the hood”.Ĭompare this with scripts you may have written:ĭetermine whether all the components are finished (i.e. Being able to write code helps you do things that a graphical interface can’t. Generating ‘standard’ paradigms in Builder is generally easier than writing the code yourself. Extending Builder with code ¶ Using Builder to create your experiment ¶
0 kommentar(er)
