← Latest papers
🤖 machine learning

How Faithful Is Trajectory-Based Data Attribution? Error Sources, Remedies, and Practical Guidelines

This paper provides the first systematic analysis of error sources in trajectory-based data attribution, identifying optimizer mismatch as a dominant issue and proposing AdamW-influence, a closed-form error proxy, and a K-step look-ahead framework to significantly improve attribution accuracy and offer practical guidelines for reliable data selection.

Original authors: Junwei Deng, Pingbang Hu, Suliang Jin, Hao Lu, Jiachen T. Wang, Shichang Zhang, Jiaqi W. Ma

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

Original authors: Junwei Deng, Pingbang Hu, Suliang Jin, Hao Lu, Jiachen T. Wang, Shichang Zhang, Jiaqi W. Ma

Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer

Imagine you are baking a massive cake (training a modern AI model) using a huge bowl of ingredients (training data). Sometimes, you want to know: "Which specific egg or pinch of sugar actually made the cake taste better or worse?" This is called data attribution.

For a long time, scientists used a method called "Trajectory-Based Attribution" to answer this. They tried to "rewind" the baking process step-by-step to see how removing one ingredient would change the final result.

However, this paper argues that the current way of doing this "rewind" is often broken, leading to wrong answers. The authors act like mechanics who have opened up the engine to find exactly where the gears are grinding and how to fix them.

Here is a simple breakdown of their findings and fixes:

1. The Problem: The "Wrong Map" (Config-Level Error)

The Analogy: Imagine you are trying to navigate a city using a map designed for a bicycle, but you are actually driving a heavy truck with a turbo engine. Even if you follow the map perfectly, you will get lost because the map doesn't understand how your truck handles turns or acceleration.

The Reality: Most modern AI models are trained using a sophisticated "engine" called AdamW. However, the popular data attribution tools were built assuming the models were trained with an older, simpler engine called SGD.

  • The Result: The tools were using the "bicycle map" for the "turbo truck." This caused massive errors in figuring out which data points were helpful.
  • The Fix: The authors built a new tool called AdamW-influence. This is a map specifically designed for the turbo truck.
  • The Outcome: By using the right map, they improved the accuracy of their predictions by 10% to over 300% across different types of AI models (from simple image classifiers to large language models like Llama).

2. The Second Problem: The "Rough Sketch" (Algorithm-Level Error)

The Analogy: Even with the right map, if you try to predict the future by drawing a straight line on a curvy road, you will eventually drift off course. The longer the road you try to predict, the bigger the mistake.

The Reality: To make the calculations fast, these tools use a "first-order approximation." Think of this as approximating a winding road as a straight line.

  • The Culprits: The authors found two main things that make this "straight line" guess worse:
    1. Steepness (Learning Rate): If the steps taken during training are huge (high learning rate), the straight-line guess fails quickly.
    2. Distance (Trajectory Length): The further back in time you try to look, the more the "straight line" drifts away from the actual curvy path.
  • The Fix: They created a "Error Proxy." This is like a dashboard warning light that tells you, "Hey, the straight-line guess is getting unreliable right now," without needing to re-bake the whole cake to check. It helps users know when to trust the data scores and when to be skeptical.

3. The Practical Guide: How to Pick Ingredients (Data Selection)

The Analogy: Imagine you are a chef picking ingredients for a soup while you are cooking it.

  • Offline Strategy: You wait until the soup is finished, taste it, and then say, "If I had picked these specific carrots instead of those ones, it would have been better." (This is slow and expensive).
  • Online Strategy: You pick ingredients as you go, guessing how they will affect the soup in the next few minutes.

The New Rulebook: The authors unified these two strategies into a single framework called the "K-Step Look-Ahead."

  • K is how far into the future you look.
  • The Insight: You don't need to look all the way to the end of the soup (Offline). Looking just a few steps ahead (Online) is often just as good, if you use the right tools.
  • The Sweet Spot:
    • If you take small steps (low learning rate), you can look further ahead (larger K) without making mistakes.
    • If you take big steps (high learning rate), you should only look a short distance ahead (small K) to avoid errors piling up.

Summary of the "Recipe" for Practitioners

The paper gives a clear recipe for anyone using these tools:

  1. Stop using the old "SGD" tools if you are training with AdamW (which almost everyone is). Use the new AdamW-influence instead.
  2. Don't look too far ahead when picking data online. If you look too far into the future, the "straight line" guess becomes too noisy.
  3. Tune your horizon (K) with your learning rate. If you are taking small steps, you can look further ahead. If you are taking big steps, keep your gaze short.

By fixing the "map" and understanding the "straight line" limits, the authors have turned data attribution from a black box into a reliable, actionable tool for improving AI models.

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 →