Whac-a-mole attention task: experimenter console

Version 0.3. This tab is for the experimenter. The participant sees a separate display tab, opened with the button below; this tab controls it and collects the data. A run is 480 happy moles to hit, 60 distractors to leave alone, and 60 trials with a happy mole and a distractor together, in random order.

Set up the participant's screen

  1. Click Open participant display. A new tab opens showing only the grey screen and the moles. If nothing opens, open a new tab yourself and go to localhost:8000/display.html.
  2. Drag that tab out of this window, so it becomes its own window, and move it to the participant's screen. Press F in it for full screen.
  3. Come back to this tab. The line above turns to "connected", and Start run becomes available. You can also start by pressing T in the display, as the scanner's trigger would.

Keep the display visible during a run: browsers pause hidden tabs, which stops the game's clock.

Attention trace

Each dot is a good mole that was hit. Its height is how far that reaction time strayed from the run's average, smoothed across neighbouring hits. This is a simplified version of the variance time course in Esterman et al. (2013). Above the dashed median line counts as less stable responding. Yellow ticks mark simulated scan volumes, and red marks show errors.

Start a run to see the trace.

Event log

Newest first. Times are seconds since the trigger. Simulated volume events are kept in the full log but not listed here.

  • No events yet.

Run data

The run table is the one to open first: one row per trial, with where each mole appeared, what should have been pressed, every button that was pressed, and the reaction times. The events table is the same run in the BIDS layout for the fMRI model. The full log keeps every event, the settings, and display-timing stats. Downloads go to the browser's usual downloads folder.

What is real here and what is not

The schedule, response rules, timestamps, and export format follow the project blueprint as amended on September 21 and 25, 2026. The trigger and scan volumes are simulated (further presses of T in the display during a run are logged as real trigger pulses), the drawings are not yet matched for size and brightness, and browser timing is tied to screen refresh rather than validated against scanner hardware.

Source code and the full project blueprint: github.com/RKarnik10/Engagement-Game