← Latest papers
🤖 machine learning

A Closer Look at In-Distribution vs. Out-of-Distribution Accuracy for Open-Set Test-time Adaptation

This paper benchmarks existing open-set test-time adaptation methods on corrupted CIFAR-10 and ImageNet datasets to reveal their inability to effectively balance in-distribution accuracy and out-of-distribution rejection, while proposing a sigmoid-based baseline to address these trade-offs.

Original authors: Zefeng Li, Evan Shelhamer

Published 2026-06-02
📖 5 min read🧠 Deep dive

Original authors: Zefeng Li, Evan Shelhamer

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 have a very smart robot chef who has spent years learning to cook perfect meals using a specific set of ingredients (like carrots, potatoes, and beef). This robot is great at recognizing these familiar ingredients. But what happens if you suddenly hand it a bowl of glitter, a live frog, or a weirdly shaped rock?

This paper is about testing how well these robot chefs can handle two things at once when they are working in the real world:

  1. Adapting to new versions of familiar ingredients (e.g., carrots that are slightly burnt or covered in mud).
  2. Refusing to cook weird, unknown things (e.g., the frog or the rock) instead of trying to force them into a recipe.

The authors call the familiar stuff "In-Distribution" (InD) and the weird stuff "Out-of-Distribution" (OOD).

The Problem: The "Over-Eager" Chef

The paper finds that current robot chefs are very good at adapting to the burnt or muddy carrots. They can figure out, "Oh, this carrot is dirty, but I'll still cook it." However, they are terrible at saying, "Wait, this is a frog! I don't know what to do with this!"

Instead, the chefs often get confused. They try to force the frog into a "beef" category or a "vegetable" category because their programming tells them they must pick a category for everything. They get so eager to adapt to the new environment that they accidentally start cooking the frogs, which leads to bad results.

The Experiments: Testing the Chefs

The researchers tested several different "robot chef" strategies (methods like SAR, OSTTA, UniEnt, and SoTTA) in two main kitchens:

  • The Small Kitchen (CIFAR-10): Simple pictures of things like cats and dogs.
  • The Big Kitchen (ImageNet): Millions of complex pictures.

They tested the chefs in two scenarios:

  1. The "Near" Stranger: Showing the chef a picture of a "garlic bread" when they only know "hot dogs." These are similar (both food), but still unknown.
  2. The "Far" Stranger: Showing the chef a picture of "cracked mud" or "porous sponge." These are totally different from food.

They also tested what happens when the mix of food changes. Sometimes the chef gets a plate with 50% carrots and 50% frogs. Other times, they get a plate with 90% frogs, or a whole sequence of plates that are only frogs.

The Big Discovery: The "All-or-Nothing" Trap

The study found a major trade-off.

  • If you tune the chef to be super confident about the carrots, they become terrible at spotting the frogs. They will happily cook the frog thinking it's a weird carrot.
  • If you tune them to reject the frogs, they often become too cautious about the carrots, refusing to cook them even when they are just a little dirty.

Most current methods are like chefs who are so focused on being right about the carrots that they accidentally serve frogs to customers.

The New Idea: Changing the Menu (Sigmoid vs. Softmax)

The paper proposes a clever fix. Currently, the chefs use a system called Softmax. Imagine this as a menu where the chef must pick exactly one item, and the probabilities of all items must add up to 100%. If the chef is unsure, they still have to pick the "least wrong" option.

The researchers tried switching to Sigmoid. Imagine this as a menu where the chef can say, "I'm 90% sure this is a carrot, but I'm 0% sure this is a frog." They don't have to force a choice. They can simply say, "I don't know what this is," and reject it.

The Result:

  • Chefs using the new Sigmoid menu were much better at spotting the frogs (rejecting the unknown).
  • They were slightly less perfect at cooking the carrots, but the trade-off was worth it because they stopped serving frogs.
  • This new approach was especially helpful when the mix of food changed wildly (e.g., when the chef suddenly got a plate of 75% frogs).

The "Batch" Surprise

The researchers also looked at how the chefs handle batches of food.

  • Mixed Batches: When a plate has a mix of carrots and frogs, the chefs get very confused and perform poorly.
  • Separated Batches: When the chef gets a plate of only frogs, followed by a plate of only carrots, they actually handle it better.

This suggests that the confusion comes from trying to learn from the frogs while trying to learn from the carrots at the exact same moment. The "batch normalization" (a technical part of how the chef processes the food) gets messed up when the two types of data are mixed together.

The Bottom Line

The paper concludes that we need to stop trying to make our AI chefs perfect at everything at once.

  1. Current methods are too eager to adapt and often fail to reject unknown, dangerous inputs.
  2. Changing the output style (from "pick one" to "pick many or none") helps the AI know when to say "I don't know."
  3. The future needs methods that can balance being helpful with familiar things and being safe with unknown things, rather than just being good at one and terrible at the other.

In short: We need to teach our AI to know the difference between a dirty carrot and a frog, and to have the confidence to say, "No, I'm not cooking that."

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 →