← Latest papers
📊 statistics

High-probability zeroth-order online convex optimisation beyond Euclidean geometry

This paper establishes unified high-probability regret bounds for zeroth-order online convex optimization with q\ell_q-Lipschitz losses and p\ell_p-regularized FTRL using cone-measure sampling, proving optimality for q[1,2]q \in [1,2] while identifying an intrinsic gap for q>2q > 2.

Original authors: David Janz, El-Mahdi El-Mhamdi, Arya Akhavan

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

Original authors: David Janz, El-Mahdi El-Mhamdi, Arya Akhavan

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 find the lowest point in a vast, foggy valley (the "minimum" of a function). In a perfect world, you would have a map or a compass that tells you exactly which way is "down" (a gradient). But in this paper, the authors are dealing with a situation where you have no map and no compass. You can only take a step, feel the ground, and ask, "Is it higher or lower here?" This is called zeroth-order optimization.

The paper tackles a specific, tricky version of this problem: Online Convex Optimization.

  • "Online" means you are making decisions one by one, like playing a game where you don't know the next move in advance.
  • "Convex" means the valley has a nice, smooth bowl shape (no hidden hills or weird bumps), which makes finding the bottom theoretically possible.
  • "Zeroth-order" means you only get to taste the ground at two specific spots to guess the slope, rather than seeing the whole hill.

Here is the breakdown of their work using simple analogies:

1. The Problem: Guessing the Slope in the Dark

Usually, to find the bottom of a valley, you need to know the slope. Since you can't see the slope, you have to guess it. The standard way to do this is to poke the ground at two points close to each other (one step forward, one step back) and see the difference in height. This is called a two-point finite-difference estimator.

The authors ask: How do we guess the slope best if the ground is shaped differently?

  • Is the valley shaped like a circle (Euclidean)?
  • Is it shaped like a diamond (L1 norm)?
  • Is it shaped like a square (L infinity norm)?

They study how to guess the slope when the "ground" (the loss function) and the "rules of the game" (the geometry) can be any of these shapes.

2. The Innovation: The "Cone" Sampling Strategy

To guess the slope, you need to pick a direction to poke the ground.

  • Old way: Most people pick a direction randomly, like rolling a die to pick a direction on a perfect sphere (like a basketball).
  • This paper's way: The authors suggest picking a direction based on a "cone measure" on different shapes (like a diamond or a cube).

The Analogy: Imagine you are blindfolded in a room.

  • If the room is a sphere, you might spin around and point in a random direction.
  • If the room is a cube, pointing randomly at the corners might be better than pointing at the flat walls, depending on what you are trying to find.
  • The authors figured out that for certain shapes of the "valley," pointing toward the corners (or specific edges) of a cube or diamond gives you a much better guess of the slope than pointing randomly on a sphere.

3. The Big Claim: "High-Probability" Guarantees

Most previous studies said, "On average, over many tries, this method works well."
The authors say: "No, we can prove that almost every single time you run this, it will work well."

  • The Metaphor: Imagine a weather forecaster.
    • Old method: "On average, it rains 50% of the time." (This doesn't help you if you need to know if it will rain today).
    • New method: "We can guarantee with 99% certainty that it will not rain today."
  • The paper proves that their algorithm is reliable. It doesn't just work "on average"; it works consistently, even in the worst-case scenarios, provided the "fog" (the noise in the data) isn't too crazy.

4. The "Anytime" Feature

The algorithm is data-driven and anytime.

  • Analogy: Imagine you are playing a video game where you don't know how many levels there are. Some algorithms need you to tell them, "The game ends in 100 levels," so they can plan their moves.
  • This algorithm doesn't care. It can start playing, and if the game ends in 10 levels or 10,000 levels, it adapts on the fly. It doesn't need to know the "horizon" (the end of the game) to play optimally.

5. The "Gap" in the Results

The authors found a fascinating limitation.

  • For "smooth" valleys (q ≤ 2): Their method is the absolute best possible way to guess the slope. They proved you can't do better.
  • For "spiky" valleys (q > 2): There is a gap. Their method works, but it's not quite as perfect as the theoretical limit suggests.
  • The Metaphor: Imagine trying to find a needle in a haystack.
    • If the haystack is soft and round (q ≤ 2), their tool finds the needle perfectly.
    • If the haystack is made of sharp, jagged spikes (q > 2), their tool still finds the needle, but it seems the tool itself (the way they poke the ground) might be the problem, not their math. They suspect that for these "spiky" shapes, we might need a completely different kind of "poke" in the future.

Summary of What They Did

  1. Created a new way to guess slopes by poking the ground in directions based on different geometric shapes (spheres, diamonds, cubes).
  2. Proved it works almost every time (high probability), not just on average.
  3. Made it flexible so it works without knowing how long the task will last.
  4. Found a limit: It's perfect for some shapes, but for very "spiky" shapes, the current method of guessing slopes might be inherently flawed, leaving a puzzle for future researchers.

In short, they built a more reliable, adaptable, and mathematically proven "blindfolded explorer" for finding the bottom of complex, multi-shaped valleys.

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 →