Stimulus-presentation experiments
Build experiments with timing, randomization and logging.
20 project-authored proposals · taxonomy v1.1 · 0 new benchmark runs. Verifiers and partial-credit rules below are designs, not executed results.
- Typical applications
- PsychoPy Builder · E-Prime · OpenSesame
- Class GUI-need label
G2· GUI-essential
Task proposals · 20
Expand to inspect the complete original wording and proposed checks. Original proposal text remains English in both interfaces.
R08.09.01.01-T01 Build a Stroop task in PsychoPy Builder with a randomized condition loop
Original instruction
In PsychoPy Builder create instructions, trial and thanks routines. The trial routine shows a colour word (text component) and collects a keyboard response (r, g, b) with correct answers from input/conditions.xlsx (24 rows), looped randomly over 3 repeats. Save output/stroop.psyexp and confirm it runs to a data file.
- Platforms
mac· macOSwin· Windowslin· Linux- Applications
- PsychoPy Builder
- Interfaces
desk· Desktop GUI- GUI need · task setting
G2· GUI-essential- GUI need · ordinary access
CL· CLI-sufficient- Interaction primitives
click· Point & clickdrag· Drag & droptype· Text & forms- Work product
WP06· Code/engineering- Conditions
- None declared
- Proposed difficulty
- 2 / 5
Proposed verifier
XML: three routines in order, a loop with nReps 3, random order and the conditions file; keyboard allowed keys r,g,b with correctAns from the file. A scripted headless run must produce a 72-trial CSV with a correct-response column. PsychoPy Coder and the psychopy.experiment API are disabled, and a file-system audit flags a .psyexp not saved by Builder.
Proposed partial credit
30% routine structure; 25% loop settings; 25% keyboard and correctness; 20% run yields 72 trials.
R08.09.01.01-T02 Add a QUEST staircase to an orientation-discrimination task in PsychoPy
Original instruction
Open input/orientation.psyexp in PsychoPy Builder and replace the fixed-value loop with a QUEST staircase: start value 10°, start SD 5, pThreshold 0.82, gamma 0.5 (2-AFC), 40 trials, stop at that count. Keep the stimulus bound to the staircase level and save output/orientation_quest.psyexp.
- Platforms
mac· macOSwin· Windowslin· Linux- Applications
- PsychoPy Builder
- Interfaces
desk· Desktop GUI- GUI need · task setting
G2· GUI-essential- GUI need · ordinary access
CL· CLI-sufficient- Interaction primitives
click· Point & clicktype· Text & forms- Work product
WP06· Code/engineering- Conditions
- None declared
- Proposed difficulty
- 3 / 5
Proposed verifier
XML loop type QUEST with the stated parameters; the grating's ori parameter references the staircase variable with 'set every repeat'; a scripted run with a simulated observer converges to a threshold within 30% of the simulated true value over 40 trials. PsychoPy Coder and the psychopy.experiment API are disabled, and a file-system audit flags a .psyexp not saved by Builder.
Proposed partial credit
35% staircase type and parameters; 30% stimulus bound to level; 25% run converges; 10% trial count.
R08.09.01.01-T03 Create a jittered-ITI fMRI block design in PsychoPy with trigger waiting
Original instruction
In PsychoPy Builder build an fMRI task: wait for 5 scanner triggers ('5' key) before onset, then 8 blocks alternating faces and houses (images in input/stimuli/), each 12 s with 8 stimuli of 1.5 s, separated by ITIs drawn from input/iti.xlsx (4/6/8 s), and log onsets to a TSV. Save output/fmri_task.psyexp.
- Platforms
mac· macOSwin· Windowslin· Linux- Applications
- PsychoPy Builder
- Interfaces
desk· Desktop GUI- GUI need · task setting
G2· GUI-essential- GUI need · ordinary access
CL· CLI-sufficient- Interaction primitives
click· Point & clickdrag· Drag & droptype· Text & forms- Work product
WP06· Code/engineering- Conditions
long· Long-horizon- Proposed difficulty
- 4 / 5
Proposed verifier
Routine: stimuli 1.5 s (90 frames), blocks 12 s. Run on the grader's reference machine (60 Hz display): 5-trigger wait before the first stimulus, 8 alternating blocks, ITIs only from {4,6,8} with all present, onsets within ±1 frame of schedule; TSV columns onset, duration, trial_type. The .psyexp must open in Builder without warnings; Coder and the psychopy.experiment API are disabled and a file-system audit flags a .psyexp not saved by Builder.
Proposed partial credit
20% trigger wait; 25% block structure; 25% timing accuracy; 30% ITI jitter and onset file.
R08.09.01.01-T04 Build a two-choice reaction-time task with accuracy feedback in OpenSesame
Original instruction
In OpenSesame create a task: fixation 500 ms, a left/right arrow (sketchpad) until response (f/j keys), then feedback 'Correct'/'Incorrect' for 600 ms, looped over input/trials.csv (60 rows, random). Save output/rt_task.osexp and run it once in dummy mode to produce output/subject-0.csv.
- Platforms
mac· macOSwin· Windowslin· Linux- Applications
- OpenSesame
- Interfaces
desk· Desktop GUI- GUI need · task setting
G2· GUI-essential- GUI need · ordinary access
CL· CLI-sufficient- Interaction primitives
click· Point & clickdrag· Drag & droptype· Text & forms- Work product
WP06· Code/engineering- Conditions
- None declared
- Proposed difficulty
- 2 / 5
Proposed verifier
Parsed structure: loop over the 60-row file in random order, keyboard_response with f/j, conditional feedback items; the dummy-run CSV has 60 rows with response_time and correct columns and feedback contingent on correctness. The .osexp must load and run in the OpenSesame runtime unmodified, with inline_script items only where stated; OpenSesame's Python console is disabled and a file-system audit flags an .osexp not saved by OpenSesame.
Proposed partial credit
30% trial sequence; 25% response collection; 25% conditional feedback; 20% data file.
R08.09.01.01-T05 Program a delay-discounting task with adaptive titration in PsychoPy
Original instruction
In PsychoPy Builder build a delay-discounting task: on each trial offer an immediate amount versus £100 at a delay from input/delays.xlsx (7 delays), titrating the immediate amount by a halving staircase (6 trials per delay, start £50). Log each trial's indifference point and save output/dd.psyexp and output/run.csv from a simulated run.
- Platforms
mac· macOSwin· Windowslin· Linux- Applications
- PsychoPy Builder
- Interfaces
desk· Desktop GUI- GUI need · task setting
G2· GUI-essential- GUI need · ordinary access
CL· CLI-sufficient- Interaction primitives
click· Point & clicktype· Text & formsdrag· Drag & drop- Work product
WP06· Code/engineering- Conditions
long· Long-horizon- Proposed difficulty
- 5 / 5
Proposed verifier
Simulated run with a hyperbolic responder: 7 indifference points recovered within 10% of the simulated true values; titration step halves each trial (checked in the log); 42 trials total. The .psyexp must open in Builder without warnings and carry every default parameter Builder writes; Coder and the psychopy.experiment API are disabled and a file-system audit flags a .psyexp not saved by Builder.
Proposed partial credit
25% trial structure; 35% titration logic; 30% indifference points recovered; 10% logging.
R08.09.01.01-T06 Set E-Prime stimulus timing and a jittered ITI list in E-Studio
Original instruction
In E-Studio open input/task.es3 and set the target TextDisplay duration to 500 ms with input mask collection, add an ITI list of 800/1000/1200 ms sampled without replacement per block, and enable the pre-release of 0 ms on the target. Save output/task.es3 and run it once to produce output/task.edat3 and its TSV export.
- Platforms
win· Windows- Applications
- E-Prime
- Interfaces
desk· Desktop GUI- GUI need · task setting
G3· GUI-only- GUI need · ordinary access
G3· GUI-only- Interaction primitives
click· Point & clicktype· Text & forms- Work product
WP06· Code/engineering- Conditions
licensed· Licensed pro app- Proposed difficulty
- 3 / 5
Proposed verifier
Exported TSV: target durations 500±5 ms, ITI values only from the three levels, each appearing equally per block; the .es3 object properties must show the duration, input mask and pre-release settings. The .es3 is a binary E-Studio file, so the run export must come from the saved experiment. E-Prime automation APIs are absent from the VM, and a file-system audit flags .es3/.edat3/TSV files not written by E-Studio, E-Run or E-DataAid.
Proposed partial credit
30% target duration; 30% ITI list and sampling; 20% pre-release and input mask; 20% run exports.
R08.09.01.01-T07 Add counterbalancing across participants to an OpenSesame experiment
Original instruction
In input/task.osexp the two blocks always run in the same order. Add counterbalancing so odd subject numbers get block A then B and even numbers the reverse, with the stimulus-response mapping also swapped between groups, and record the assigned group in the data. Save output/task_cb.osexp and dummy runs for subjects 1 and 2.
- Platforms
mac· macOSwin· Windowslin· Linux- Applications
- OpenSesame
- Interfaces
desk· Desktop GUI- GUI need · task setting
G2· GUI-essential- GUI need · ordinary access
CL· CLI-sufficient- Interaction primitives
click· Point & clicktype· Text & formsdrag· Drag & drop- Work product
WP06· Code/engineering- Conditions
- None declared
- Proposed difficulty
- 3 / 5
Proposed verifier
Subject-1 and subject-2 data files show reversed block order and swapped key mappings, with a group column; the logic must be in the experiment (inline script or conditional run-if), not two separate experiment files. OpenSesame's Python console is disabled, and a file-system audit flags an .osexp not saved by OpenSesame.
Proposed partial credit
35% block order counterbalanced; 35% mapping swapped; 20% group logged; 10% single experiment file.
R08.09.01.01-T08 Build an n-back task with adaptive level changes in PsychoPy
Original instruction
In PsychoPy Builder build an n-back letter task starting at 2-back: letters 500 ms, ISI 1500 ms, 20+n trials per block, target rate 30%; after each block raise n if accuracy >85% and lower it if <65% (minimum 1). Run 6 blocks with a simulated responder and save output/nback.psyexp and output/run.csv.
- Platforms
mac· macOSwin· Windowslin· Linux- Applications
- PsychoPy Builder
- Interfaces
desk· Desktop GUI- GUI need · task setting
G2· GUI-essential- GUI need · ordinary access
CL· CLI-sufficient- Interaction primitives
click· Point & clicktype· Text & formsdrag· Drag & drop- Work product
WP06· Code/engineering- Conditions
long· Long-horizon- Proposed difficulty
- 5 / 5
Proposed verifier
Run log: target rate 30±5% per block; n changes follow the rule exactly given the simulated accuracies; trial counts equal 20+n; ISI and stimulus durations within 20 ms. The .psyexp must open in Builder without warnings and carry every default parameter Builder writes; Coder and the psychopy.experiment API are disabled and a file-system audit flags a .psyexp not saved by Builder.
Proposed partial credit
25% stimulus timing; 25% target generation; 35% adaptive rule; 15% logging.
R08.09.01.01-T09 Fix a PsychoPy experiment whose frame timing drops below the refresh rate
Original instruction
input/laggy.psyexp drops frames: large uncompressed images are loaded inside the trial routine and a text component is updated every frame unnecessarily. Fix it in Builder (preload stimuli, correct update settings, window settings) so a test run reports no dropped frames at 60 Hz, and save output/fixed.psyexp and output/timing_report.txt.
- Platforms
mac· macOSwin· Windowslin· Linux- Applications
- PsychoPy Builder
- Interfaces
desk· Desktop GUI- GUI need · task setting
G2· GUI-essential- GUI need · ordinary access
CL· CLI-sufficient- Interaction primitives
click· Point & clickvis· Visual judgmenttype· Text & forms- Work product
WP06· Code/engineering- Conditions
hidden· Hidden/stale state- Proposed difficulty
- 4 / 5
Proposed verifier
Static check: images preloaded and the text set constant. Rerun on the reference machine (60 Hz display): ≤1 dropped frame per 1,000, mean interval within 1 ms of 16.67, stimulus durations as originally designed (±20 ms), all conditions presented. The .psyexp must open in Builder without warnings; Coder and the psychopy.experiment API are disabled and a file-system audit flags a .psyexp not saved by Builder.
Proposed partial credit
40% no dropped frames; 30% design preserved; 20% stimuli preloaded correctly; 10% report.
R08.09.01.01-T10 Export a PsychoPy task to PsychoJS and verify it runs in a browser
Original instruction
Open input/flanker.psyexp in PsychoPy Builder, make it online-compatible (replace unsupported components, set units and resources), export the HTML/PsychoJS bundle to output/flanker_js/, and serve it locally to run one participant in a browser, saving the data to output/online_data.csv.
- Platforms
mac· macOSwin· Windows- Applications
- PsychoPy Builder · PsychoJS
- Interfaces
desk· Desktop GUIbrow· Browser- GUI need · task setting
G2· GUI-essential- GUI need · ordinary access
G2· GUI-essential- Interaction primitives
click· Point & clicktype· Text & formsnav· Pan/zoom/scroll- Work product
WP06· Code/engineering- Conditions
multiapp· Multi-app- Proposed difficulty
- 4 / 5
Proposed verifier
The bundle loads with no console errors; the browser run produces a CSV with the full trial count and correct condition columns; RT distribution plausible (median 200–1500 ms); resources listed in the experiment settings. The .psyexp must open in Builder without warnings and carry every default parameter Builder writes; Coder and the psychopy.experiment API are disabled and a file-system audit flags a .psyexp not saved by Builder.
Proposed partial credit
30% export builds; 30% runs without console errors; 30% data complete; 10% resources configured.
R08.09.01.01-T11 Build a Gorilla task tree with randomized spreadsheet conditions
Original instruction
In the Gorilla sandbox create an experiment with a consent node, a task built from input/task_spec.pdf (image stimulus, 2-choice buttons, 48 trials from the spreadsheet you upload), a questionnaire node, and a randomizer assigning participants to two spreadsheet versions. Preview it once and export the project to output/gorilla_export.zip.
- Platforms
web· Any OS (web)- Applications
- Gorilla
- Interfaces
brow· Browser- GUI need · task setting
G3· GUI-only- GUI need · ordinary access
G2· GUI-essential- Interaction primitives
click· Point & clickdrag· Drag & droptype· Text & forms- Work product
WP06· Code/engineering- Conditions
- None declared
- Proposed difficulty
- 3 / 5
Proposed verifier
Export parsed: nodes in the stated order with a randomizer branching to two spreadsheet versions; task has 48 trials with the response buttons and stimulus columns bound; preview data present with 48 rows. The sandbox account is issued no API token, so the experiment must be built in a browser session; the export's version history must show task-builder edits.
Proposed partial credit
25% node tree; 30% task configuration; 25% randomizer; 20% preview data.
R08.09.01.01-T12 Add eye-tracker calibration and gaze-contingent onset to a PsychoPy task
Original instruction
In PsychoPy Builder add to input/reading.psyexp an eye-tracker setup (ioHub mouse-simulated tracker for testing), a 9-point calibration routine before the first block, and make each trial's text appear only after fixation is held within 1° of a central cross for 300 ms. Save output/reading_et.psyexp and a test log output/et_run.csv.
- Platforms
mac· macOSwin· Windowslin· Linux- Applications
- PsychoPy Builder
- Interfaces
desk· Desktop GUI- GUI need · task setting
G2· GUI-essential- GUI need · ordinary access
CL· CLI-sufficient- Interaction primitives
click· Point & clicktype· Text & formsrt· Real-time control- Work product
WP06· Code/engineering- Conditions
tutorial· Follow docs/tutoriallong· Long-horizon- Proposed difficulty
- 5 / 5
Proposed verifier
Experiment has an eyetracker_setup component with 9-point calibration; the trial has a gaze-contingent start (1°, 300 ms); the simulated run log shows each text onset after a held fixation and aborted trials on fixation breaks. The .psyexp must open in Builder without warnings and carry every default parameter Builder writes; Coder and the psychopy.experiment API are disabled and a file-system audit flags a .psyexp not saved by Builder.
Proposed partial credit
25% tracker setup; 25% calibration routine; 35% gaze-contingent onset logic; 15% log evidence.
R08.09.01.01-T13 Set up precise audio stimulus timing in OpenSesame with PsychoPy backend
Original instruction
In OpenSesame build an auditory oddball: standard (input/standard.wav) and deviant (input/deviant.wav) tones at 85% / 15%, SOA 1000 ms, 200 trials, PsychoPy back-end with the audio buffer configured for low latency, logging onset times. Save output/oddball.osexp and a dummy run output/subject-0.csv.
- Platforms
mac· macOSwin· Windowslin· Linux- Applications
- OpenSesame
- Interfaces
desk· Desktop GUI- GUI need · task setting
G2· GUI-essential- GUI need · ordinary access
CL· CLI-sufficient- Interaction primitives
click· Point & clicktype· Text & forms- Work product
WP06· Code/engineering- Conditions
- None declared
- Proposed difficulty
- 3 / 5
Proposed verifier
Run log: 200 trials, deviant proportion 0.15±0.03, no adjacent deviants, SOA 1000 ms with logged onsets within ±1 frame on the reference machine; back-end psycho with the stated audio settings; onset timestamps logged per trial. The .osexp must load and run in the OpenSesame runtime unmodified, with inline_script items only where stated; OpenSesame's Python console is disabled and a file-system audit flags an .osexp not saved by OpenSesame.
Proposed partial credit
25% stimulus probabilities; 25% sequence constraints; 30% SOA accuracy; 20% backend/logging.
R08.09.01.01-T14 Implement a pseudo-randomized sequence with constraints in PsychoPy
Original instruction
For input/task.psyexp, generate a trial order for 120 trials of 4 conditions with no more than 2 repeats of the same condition, no immediate stimulus repetition, and each condition equally frequent per 40-trial block. Implement it inside the experiment (code component), write the realized order of a test run to output/order.csv, and save output/task_pseudo.psyexp.
- Platforms
mac· macOSwin· Windowslin· Linux- Applications
- PsychoPy Builder
- Interfaces
desk· Desktop GUI- GUI need · task setting
HY· Hybrid- GUI need · ordinary access
CL· CLI-sufficient- Interaction primitives
click· Point & clickcode· Code & commandstype· Text & forms- Work product
WP06· Code/engineering- Conditions
- None declared
- Proposed difficulty
- 3 / 5
Proposed verifier
order.csv satisfies all three constraints and has 30 trials per condition per block; re-running with a different seed yields a different but still valid order (so a hard-coded list fails).
Proposed partial credit
30% constraints satisfied; 25% block balance; 30% generated at runtime; 15% experiment saved.
R08.09.01.01-T15 Add a practice block with a performance gate to an OpenSesame task
Original instruction
Modify input/task.osexp so participants do a 20-trial practice block with feedback and only proceed if accuracy ≥80%; otherwise the practice repeats, up to 3 attempts, then the experiment ends with a message. Log attempts and accuracies, and save output/task_practice.osexp plus two dummy runs (passing and failing).
- Platforms
mac· macOSwin· Windowslin· Linux- Applications
- OpenSesame
- Interfaces
desk· Desktop GUI- GUI need · task setting
G2· GUI-essential- GUI need · ordinary access
CL· CLI-sufficient- Interaction primitives
click· Point & clicktype· Text & formsdrag· Drag & drop- Work product
WP06· Code/engineering- Conditions
- None declared
- Proposed difficulty
- 3 / 5
Proposed verifier
Simulated runs: a 90%-accurate responder proceeds after one practice; a 50%-accurate responder repeats 3 times and ends without the main block; logs contain attempt number and accuracy per practice block. The .osexp must load and run in the OpenSesame runtime unmodified, with inline_script items only where stated; OpenSesame's Python console is disabled and a file-system audit flags an .osexp not saved by OpenSesame.
Proposed partial credit
30% practice block with feedback; 35% gate logic; 25% max-attempts behaviour; 10% logging.
R08.09.01.01-T16 Build a trial-by-trial probabilistic reversal-learning task in PsychoPy
Original instruction
In PsychoPy Builder create a two-armed bandit with 80/20 reward probabilities that reverse after 8 consecutive choices of the better option (minimum 15 trials between reversals), 160 trials, with reward feedback and logging of chosen option, reward and current contingency. Save output/reversal.psyexp and output/sim_run.csv from a simulated learner.
- Platforms
mac· macOSwin· Windowslin· Linux- Applications
- PsychoPy Builder
- Interfaces
desk· Desktop GUI- GUI need · task setting
HY· Hybrid- GUI need · ordinary access
CL· CLI-sufficient- Interaction primitives
click· Point & clickcode· Code & commandstype· Text & forms- Work product
WP06· Code/engineering- Conditions
long· Long-horizon- Proposed difficulty
- 5 / 5
Proposed verifier
Simulated run: reward rates per option 0.80±0.05 / 0.20±0.05 within each contingency block; reversals occur exactly when the rule is met and never within 15 trials of the previous one; log includes contingency state per trial.
Proposed partial credit
25% bandit structure; 35% reversal rule; 25% reward probabilities; 15% logging.
R08.09.01.01-T17 Control: write the Stroop task directly as a PsychoPy Python script
Original instruction
Control pair of T01. Without Builder, write output/stroop.py using the PsychoPy library: read input/conditions.xlsx, present colour words with 3-repeat random order, collect r/g/b responses with correctness, and write a 72-trial CSV. Run it headless to produce output/data.csv.
- Platforms
lin· Linuxmac· macOS- Applications
- PsychoPy
- Interfaces
term· Terminal- GUI need · task setting
CL· CLI-sufficient- GUI need · ordinary access
CL· CLI-sufficient- Interaction primitives
code· Code & commands- Work product
WP06· Code/engineering- Conditions
- None declared
- Proposed difficulty
- 2 / 5
Proposed verifier
Same data checks as T01: 72 trials, conditions balanced, correct-response column accurate against the conditions file. Scored as the CLI control of T01; the .psyexp structural checks do not apply.
Proposed partial credit
40% conditions and order; 35% response and correctness; 25% data file complete.
R08.09.01.01-T18 Diagnose a condition file mismatch that breaks an E-Prime run
Original instruction
input/task.es3 aborts at runtime because the attributes referenced by its TextDisplay do not match the columns of input/stimlist.xlsx (two renamed columns and one extra level). In E-Studio fix the list and references so the task runs its full 96 trials, and record what was wrong in output/cause.txt. Save output/task_fixed.es3 and the run export.
- Platforms
win· Windows- Applications
- E-Prime
- Interfaces
desk· Desktop GUI- GUI need · task setting
G3· GUI-only- GUI need · ordinary access
G2· GUI-essential- Interaction primitives
click· Point & clicktype· Text & formsvis· Visual judgment- Work product
WP06· Code/engineering- Conditions
licensed· Licensed pro apphidden· Hidden/stale state- Proposed difficulty
- 3 / 5
Proposed verifier
Run export has 96 trials with all stimulus levels present and no runtime error; attribute names in the .es3 match the spreadsheet columns; cause.txt names both renamed columns and the extra level. The .es3 is a binary E-Studio file, so the run export must come from the saved experiment. E-Prime automation APIs are not installed on the VM, and a file-system audit log flags .es3/.edat3/TSV files not written by E-Studio, E-Run or E-DataAid.
Proposed partial credit
40% task runs fully; 30% attribute references fixed; 30% causes documented.
R08.09.01.01-T19 Add BIDS-compatible event logging to a PsychoPy fMRI task
Original instruction
Modify input/fmri_task.psyexp so each run writes a BIDS events TSV (onset, duration, trial_type, response_time, accuracy) with onsets measured from the first scanner trigger, plus a sidecar JSON describing the columns. Save output/task_bids.psyexp and the files from one test run under output/sub-01/.
- Platforms
mac· macOSwin· Windowslin· Linux- Applications
- PsychoPy Builder
- Interfaces
desk· Desktop GUI- GUI need · task setting
HY· Hybrid- GUI need · ordinary access
CL· CLI-sufficient- Interaction primitives
click· Point & clickcode· Code & commandstype· Text & forms- Work product
WP02· Records/table- Conditions
- None declared
- Proposed difficulty
- 3 / 5
Proposed verifier
events.tsv has the required columns, onsets start at 0 at the first trigger and increase monotonically, durations match the design within 20 ms; sidecar JSON documents every column; bids-validator reports no errors for the events files.
Proposed partial credit
30% onset reference correct; 30% column set and values; 25% sidecar; 15% validator clean.
R08.09.01.01-T20 Build a dual-task experiment with two response devices and SOA manipulation
Original instruction
In PsychoPy Builder build a psychological-refractory-period task: tone-pitch task answered with keys z/x and a visual letter task answered with n/m, SOAs of 50, 150, 450 and 900 ms from input/soa.xlsx, 160 trials, both RTs logged relative to their own stimulus onset. Save output/prp.psyexp and output/sim_run.csv.
- Platforms
mac· macOSwin· Windowslin· Linux- Applications
- PsychoPy Builder
- Interfaces
desk· Desktop GUI- GUI need · task setting
G2· GUI-essential- GUI need · ordinary access
CL· CLI-sufficient- Interaction primitives
click· Point & clicktype· Text & formsdrag· Drag & drop- Work product
WP06· Code/engineering- Conditions
long· Long-horizon- Proposed difficulty
- 5 / 5
Proposed verifier
Run log: realized SOAs within ±1 frame (16.7 ms) of nominal on the reference machine, equally frequent; two response columns each timed from its own stimulus; no response collection cross-talk (keys restricted per task); 160 trials. The .psyexp must open in Builder without warnings and carry every default parameter Builder writes; Coder and the psychopy.experiment API are disabled and a file-system audit flags a .psyexp not saved by Builder.
Proposed partial credit
25% two tasks with separate keys; 30% SOA accuracy; 30% dual RT logging; 15% trial count.
Mapped research references
No benchmark reference is assigned to this class in the current mapping.