Clever Quest Lab ← Labs

Visual Memory Test

Squares flash for a tenth of a second and one comes back: answer Same or Changed, and the page turns your answers into a capacity K with a 95% interval.

Settings

This run

No finished run yet. Your result appears here.

History

Runs you finish on this device are listed here.

See all your results

Slovenčina

Runs on your device. Nothing you type or record is uploaded. Keeps working without a connection while the page is open. Works with touch. Saves each run's hit and false alarm rates and capacity K per set size, your settings and the language; Clear history deletes the runs.

Added · Updated : chart points have their own legend colour and are no longer cut off at 100%, Enter or Space on the test field starts, and a phone scrolls to This run

What the test measures

Visual working memory holds what you have just seen for a second or two while you use it. The question here is how many objects it holds at once. You see 2, 3, 4, 6 or 8 coloured squares for a tenth of a second, and then one of them comes back. If you kept that square in mind, you know whether its colour changed; if not, you can only guess. How many squares you keep is your capacity, K.

How a trial runs

A run has 24 trials for each number of squares, 12 changed and 12 the same, 120 in all, in random order, with a short break in the middle. It takes 5 to 6 minutes. Before your first run there are 8 practice trials that tell you whether you were right; they do not count.

The design follows an experiment by Luck and Vogel that Cowan (2001) describes: 1 to 12 coloured squares for 100 ms, a 900 ms blank, then the same display or one with a single square changed. Performance was nearly perfect with 1 to 3 squares, slightly worse with 4 and much worse with more. Here the test display shows only the one square, so you know which square to check.

A screen draws whole frames, so the flash is timed in frames: 6 frames at 60 Hz. The page measures the frame rate before each run, records how long every flash was really on, and repeats a trial later in the run when a frame was dropped, for example because the computer was busy.

How K is calculated

For each number of squares N the page counts the hit rate h (the share of changed trials where you answered Changed) and the false alarm rate f (the share of unchanged trials where you also answered Changed).

K = N × (h − f)

This is Cowan's formula. Rouder et al. (2011) derive it from a slot model: you hold K of the N squares, so the tested square is in memory with probability K/N and then you answer correctly; otherwise you guess Changed at some rate u. So h = K/N + (1 − K/N)u and f = (1 − K/N)u, and the guessing cancels out in h − f. An example: with 4 squares, 11 of 12 changes caught and 2 false alarms in 12, K = 4 × (11/12 − 2/12) = 3.0. Pashler's formula, K = N(h − f)/(1 − f), is for tests where the whole display returns; Rouder et al. show that the two are not interchangeable, so a single-square test uses Cowan's.

Kmax, the main result, is one K and one guessing rate u fitted by maximum likelihood to all your answers with 4, 6 and 8 squares: the values under which your answers were most probable. With 2 or 3 squares K cannot come out above N, and a single slip there pulls it down, so those trials draw the start of the curve but stay out of Kmax, as Rouder et al. suggest for set sizes below your capacity.

The 95% interval of Kmax holds every K under which your answers are not much less probable than under Kmax: twice the difference in log likelihood stays below 3.84, the 95% point of the chi-squared distribution with one degree of freedom. For K at each number of squares the page draws your trials again at random with replacement 2,000 times, recomputes K and keeps the middle 95%. Shown values stay within 0 to N; when every answer at a set size is right, the table says all correct.

In the first chart the dashed line is the slot model with your Kmax, K = min(N, Kmax). In the second it is the share of correct answers the model predicts, (1 + min(1, Kmax/N))/2: 100% while N is at most Kmax, then falling towards 50%.

What to look for

Things to try

Comparing your result

History compares runs on the same input whose refresh rates are within 10% (or both below 50 Hz), because screens differ in size, brightness and timing. Luck and Vogel (2013) report that a 10-minute change localisation task, a version where a square always changes and you point to it, had a test-retest reliability of 0.77 over 1.5 years. This page uses a different task and 120 trials, so read the interval of a run rather than its decimal. There is no percentile or score against other people: one run is too short for that, and the published figures come from other procedures.

Limits

Controls

FAQ

Why is my K with 2 squares exactly 2?

Because K cannot be larger than N: answer every trial with 2 squares correctly and h = 1, f = 0, K = 2 × 1 = 2. Less than 2 there means you missed some.

Why does the test say the flash cannot be timed?

It measures your screen first. Below 50 frames a second, or with uneven frames, a 100 ms flash cannot be shown exactly; remote desktop and power-saving modes are common causes. Closing other tabs or plugging in a laptop often helps; otherwise press Run anyway, and the result is marked less precise.

Sources