← Latest papers
📊 statistics

Ratio-based Loss Functions

This paper provides a systematic survey of ratio-based loss functions for regression tasks that focus on relative errors rather than absolute differences, analyzing their fundamental mathematical properties to establish a foundation for future research and the development of new loss functions.

Original authors: Lena Helgerth, Andreas Christmann

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

Original authors: Lena Helgerth, Andreas Christmann

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 trying to teach a computer to make predictions, like guessing the price of a house or the weight of a person. To do this, the computer needs a "scorecard" to judge how good its guesses are. In the world of machine learning, this scorecard is called a loss function. The lower the score, the better the guess.

For a long time, most scorecards worked like a ruler. If the computer guessed a house was \500,000 but it was actually \502,000, the "error" was simply the difference: $2,000. This is called a distance-based approach. It works great when you are measuring things where a fixed amount of error matters the same everywhere (like measuring the length of a table).

However, the authors of this paper argue that sometimes a ruler isn't the right tool. Sometimes, you need a magnifying glass or a percentage calculator. This is especially true when dealing with things that grow or shrink, like prices, populations, or biological measurements.

The Core Idea: Ratio vs. Distance

The paper introduces a new class of scorecards called Ratio-Based Loss Functions.

Instead of asking, "How far off was the guess?" (Distance), these new scorecards ask, "How close was the guess proportionally?" (Ratio).

The "Inflation" Analogy:
The authors use a great example to explain why this matters:

  • Imagine a newspaper costs \3**. If the price goes up by **\5, that's a huge deal (it's almost double the price!).
  • Now imagine a car costs \30,000**. If the price goes up by **\5, nobody notices. It's a drop in the bucket.

If you use a "ruler" (distance-based), both errors are just "\5." The computer thinks they are equally bad. But in reality, the newspaper error is massive, and the car error is tiny. A **ratio-based** scorecard sees this: it knows that missing the newspaper price by \5 is a 166% error, while missing the car price by $5 is a 0.01% error. It treats them very differently.

What the Paper Actually Does

The authors didn't just say, "Hey, ratios are cool." They did the heavy lifting to build a solid mathematical house for these new scorecards. Here is what they accomplished, translated into plain English:

  1. They Built a Blueprint (Definition):
    They created a strict, formal definition for what counts as a "ratio-based" loss function. They figured out how to handle the math when the computer's guess might be negative (which doesn't make sense for things like weight or price) by using a "link function"—think of it as a translator that converts the computer's raw numbers into a format the ratio can understand.

  2. They Checked the Structural Integrity (Properties):
    Before you can use a new type of scorecard in real algorithms, you need to know if it's safe and stable. The authors tested these new functions for:

    • Smoothness: Can the computer easily "slide" down the scorecard to find the best answer? (Mathematically: Differentiability).
    • Shape: Is the scorecard bowl-shaped so there's only one best answer? (Mathematically: Convexity).
    • Stability: If the input changes a little, does the score jump wildly, or does it change gently? (Mathematically: Lipschitz continuity).

    They found that while some of these new scorecards are very smooth and stable, others are tricky. For instance, making a scorecard that is both perfectly smooth and perfectly stable is harder with ratios than with rulers.

  3. They Showed the Toolbox (New Examples):
    The paper is a catalog of these new scorecards. They took existing ideas from other fields (like "Logarithmic Loss" or "Huber Loss") and reinvented them as ratio-based versions. They also invented some brand-new ones, like "Huber-type Relative Loss," which tries to get the best of both worlds: being sensitive to small errors but not panicking over huge outliers.

  4. They Clarified the Relationship:
    They proved that you can't just swap a ruler for a magnifying glass in every situation. You can sometimes turn a ratio problem into a distance problem by taking the logarithm (a math trick), but often, the two approaches are fundamentally different. A distance-based tool cannot capture the "relative" nature of an error, and a ratio-based tool cannot capture a fixed "absolute" error.

What They Did NOT Do

It is important to note what this paper didn't do, based on their own words:

  • They did not test these scorecards on a specific AI algorithm (like a specific neural network) to see if it wins a competition.
  • They did not calculate exactly how fast these new methods learn or how much data you need.
  • They did not apply this to a specific medical diagnosis or financial market prediction in this specific document.

The Bottom Line

Think of this paper as an architect's manual for a new type of building material. The authors have:

  1. Defined exactly what the material is.
  2. Tested its strength, flexibility, and durability.
  3. Provided a catalog of different shapes and sizes you can build with it.

They are handing this manual to other researchers, saying, "Here is a solid foundation. Now you can go build better AI systems that understand relative errors, rather than just absolute differences." They are inviting the community to use these new tools to solve problems where "proportion" matters more than "distance."

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 →