A method enabling computation of linear rates of change of spatial averages on visual field patterns that have varying test locations over time

This paper introduces and validates a new method for accurately computing linear rates of change in spatial averages across visual field series with varying test locations over time, demonstrating that it achieves slope estimation errors comparable to those of standard fixed-pattern analyses.

Original authors: Turpin, A., McKendrick, A.

Published 2026-05-13
📖 5 min read🧠 Deep dive

Original authors: Turpin, A., McKendrick, A.

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

The Big Problem: Measuring a Moving Target

Imagine you are trying to measure the average temperature of a large garden to see if it is getting hotter or colder over time.

In the medical world, doctors use a test called a "visual field test" to check how well a person sees across their entire vision, similar to checking different spots in that garden. Usually, they check the same 50 or 60 specific spots every time, like measuring the temperature at the same 50 trees. If the trees get hotter, the average goes up, and the doctor knows the garden is warming.

But what if the list of trees you check keeps changing?
Imagine that in January, you check 50 trees. In February, you decide to check those same 50 trees plus 10 new ones. In March, you check the original 50 plus 10 more new ones.

If you just take a simple average of all the trees you checked that month, your average temperature will look like it's dropping, even if the garden isn't changing at all. Why? Because the new trees you added might be in a shady, cool spot that you didn't check before. By adding them to the math, you are "diluting" the average with new, cooler data.

This is exactly the problem the authors (Andrew Turpin and Allison McKendrick) are solving. In eye care, doctors sometimes need to add new test spots to a patient's vision map to get a better look at a specific defect. The old math tricks for calculating "how fast is vision getting worse?" break down when the list of test spots changes.

The Solution: A Smarter Way to Do the Math

The authors propose a new method to calculate the rate of change that ignores the "noise" caused by adding new spots. They call this method sMD + sMD'.

Here is how it works, using a "Garden Party" analogy:

  1. The Old Way (Simple Average): You ask everyone at the party (all the test spots) how much they are enjoying the music. If you add 10 new people who just arrived and haven't heard the music yet, their silence lowers the average enjoyment score, even if the original guests are having a great time.
  2. The New Way (sMD + sMD'): The authors suggest a two-step check:
    • Step 1: Calculate the average enjoyment of everyone currently at the party (including the new people).
    • Step 2: Calculate the average enjoyment of only the people who were there last week.
    • The Trick: To figure out if the music is getting better or worse, you compare the "everyone" score from this week against the "old-timers" score from last week.

By doing this, you ignore the fact that new people just arrived. You only measure the change in the people who have been there the whole time. This prevents the math from being tricked by the addition of new test spots.

The "Spatial" Secret: Weighting the Map

The paper also mentions that not all spots on the vision map are equal. Some spots cover a bigger area of your vision than others.

  • The Analogy: Imagine your vision is a map of a country. Some test spots are like tiny villages; others are like massive cities. If you just count the "happiness" of every village and city equally, your average is skewed because the cities (which cover more land) are under-represented.
  • The Fix: The authors use a "spatial weighting" system. They give more importance to the test spots that cover larger areas of the eye, just like you would give more weight to the temperature of a massive city than a tiny village when calculating the country's average temperature.

Did It Work? (The Simulation)

The authors didn't just guess; they ran a computer simulation to test their idea.

  • The Setup: They created 50 fake eyes. Some were perfectly stable (not changing), and some were slowly getting worse at random spots. They simulated a scenario where the test pattern kept changing, adding 3 to 10 new spots at every visit.
  • The Comparison: They compared three methods:
    1. Simple Average: Just averaging all numbers (The "Bad" way).
    2. Weighted Average: Counting spots by size, but still using the old math (The "Okay" way).
    3. The New Method (sMD + sMD'): Weighting by size and ignoring new spots in the change calculation (The "Good" way).
  • The Result: The new method was almost perfect. It calculated the rate of change with almost zero error, matching the results you would get if you had stuck to a fixed, unchanging test pattern the whole time. The other methods were way off, often making stable eyes look like they were getting worse just because new spots were added.

The Bottom Line

The paper claims that it is now possible to accurately measure how fast a patient's vision is changing, even if the doctor changes the pattern of test spots from visit to visit.

By using a clever math trick that:

  1. Weighs spots based on how much vision they cover, and
  2. Ignores the "shock" of new spots when calculating the change from last time,

Doctors can get a true picture of disease progression (like glaucoma) without being fooled by the fact that they are testing more areas of the eye over time. The authors state this works for both adding new spots and removing them, making it a flexible tool for future, more personalized eye tests.

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 →