How the tests work

This page explains what each task measures, what you do during the task, and what counts as an error.

“Respond as quickly and accurately as you can. Accuracy and consistency both matter.”
Open instrument

General rule

All tasks are short and standardized. The goal is not perfection. The goal is consistent execution that can be compared over time.

  • Wait for the task signal.
  • Respond only when required.
  • Try to be both fast and accurate.
  • Avoid clicking or tapping too early.

Reaction Time

Measures simple response speed and response consistency.

What you do:

  • Wait for the signal to appear.
  • Click or tap as quickly as possible when it appears.
  • Repeat across trials.

What gets recorded:

  • reaction time on valid responses
  • false starts
  • session variability

A false start means responding before the signal appears.

Go / No-Go

Measures response initiation and inhibition control.

What you do:

  • Respond immediately on GO trials.
  • Do nothing on NO-GO trials.

What gets recorded:

  • reaction time on GO trials
  • misses on GO trials
  • false alarms on NO-GO trials
  • session variability

Missing a GO trial and responding on a NO-GO trial are both treated as errors.

Divided Attention

Measures performance while handling two demands at once.

What you do:

  • Perform the Go / No-Go task.
  • At the same time, count brief blue flashes during the session.
  • Enter the flash count at the end.

What gets recorded:

  • GO reaction time
  • misses and false alarms
  • flash-count accuracy
  • combined execution stability

This is not only a response task. It is a dual-demand task.

Precision (Target Pointing)

Measures motor accuracy and motor consistency across repeated target hits.

What you do:

  • Tap or click the target as accurately as possible when it appears.
  • Repeat across trials.

What gets recorded:

  • distance from target center
  • normalized error
  • response timing
  • consistency across trials

Best results come from a stable position and, when available, fullscreen use.

About errors and unusable sessions

Errors are not hidden. FCE records them because they are part of the functional signal.

  • early responses can count as false starts
  • misses and false alarms affect inhibitory tasks
  • very noisy or incomplete sessions may be marked Not usable

Not usable does not mean failure. It means the session was not reliable enough for comparison.

Use Training first if needed

If a task feels unfamiliar, use Training mode before building baseline or running checks.

Training lets you get used to the task without affecting your baseline.