Prior scene context reshapes feature reliance during rapid perception

By combining eye tracking with feature-based encoding models, this study demonstrates that prior scene context facilitates rapid face detection by shifting the perceptual strategy from reliance on sensory-driven features to expectation-based spatial guidance, a change evident even in the first eye movement.

Original authors: Tasliyurt-Celebi, S., de Haas, B., L.-H. Vo, M., Dobs, K.

Published 2026-05-18
📖 3 min read☕ Coffee break read

Original authors: Tasliyurt-Celebi, S., de Haas, B., L.-H. Vo, M., Dobs, K.

Original paper licensed under CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). ⚕️ This is an AI-generated explanation of a preprint that has not been peer-reviewed. It is not medical advice. Do not make health decisions based on this content. Read full disclaimer

Imagine your brain is a detective trying to spot a specific person (a face) hidden inside a crowded, chaotic room (a natural scene). The paper asks: Does knowing what the room looks like before you enter help the detective find the person faster?

To answer this, the researchers set up two "games" with 38 volunteers each. They used special eye-tracking glasses to see exactly where people looked and how long it took them to spot a face.

The Two Games

  1. Game 1 (The Preview): Before the real picture appeared, participants saw a "faceless" version of the same scene. It was like looking at a map of the room before walking in.
  2. Game 2 (The Tunnel): This time, they saw the faceless map and a moving window that only let them see a small part of the real scene at a time. This made the job much harder, forcing them to rely even more on that initial map.

What They Found

The results showed that having that "faceless map" (the prior context) made people find faces much faster, especially when the faces were hard to spot.

Here is the most interesting part: The brain used the map immediately. Even the very first time the person's eyes moved to look at the scene, they were already guided by what they expected to see. They didn't just scan randomly; they went straight to where a face was likely to be based on the preview.

The Detective's Toolkit: Two Ways to Find a Clue

To understand how the brain did this, the researchers built a computer model with two types of "clues":

  • Clue Type A (The Sensory Input): This is what the eyes actually see right now—the shape of a nose, the color of skin, the contrast of features. It's like looking at a blurry photo and trying to guess what it is based purely on the pixels.
  • Clue Type B (The Expectation): This is the "spatial prior." It's the brain's guess of where a face should be based on the scene's layout. It's like knowing, "In a kitchen, people usually stand near the counter, not floating in the middle of the ceiling."

The Big Shift

The study found that both types of clues helped the brain work, but the balance changed depending on whether the preview was available.

  • Without the preview: The brain relied heavily on Clue Type A. It had to squint and analyze every pixel of sensory data to find the face.
  • With the preview: The brain leaned much more heavily on Clue Type B. It trusted its expectation of where the face would be. Because it knew where to look, it didn't need to work as hard to process the raw sensory details.

The Bottom Line

Think of it like searching for your keys. If you have no idea where you left them, you have to frantically look at every single object on the table (relying on sensory input). But if you remember, "I usually put my keys on the hook by the door," you walk straight to the hook and grab them without even looking at the rest of the table (relying on expectation).

This paper proves that when we have a "map" of the scene beforehand, our brains instantly switch from a "search mode" to a "targeted mode," using our expectations to guide our eyes before we even fully process what we see.

Drowning in papers in your field?

Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.

Try Digest →