← Latest papers
🔢 mathematics

Counterexamples to integer-coefficient criteria for recurrence along functions from a Hardy field

This paper provides negative answers to two questions posed by Bergelson, Moreira, and Richter by constructing counterexamples using elementary Bohr sets that demonstrate functions from a Hardy field can satisfy integer-coefficient derivative-span conditions yet fail to guarantee thick or even non-empty common return-time sets.

Original authors: Kangbo Ouyang, Leiye Xu, Shuhao Zhang

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

Original authors: Kangbo Ouyang, Leiye Xu, Shuhao Zhang

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

The Big Picture: Predicting the Future of Numbers

Imagine you are a detective trying to predict when a specific pattern will reappear in a long, chaotic sequence of numbers. In mathematics, this is called recurrence.

The paper you are reading is about a specific type of number sequence generated by "Hardy field" functions. Think of these functions as machines that spit out numbers that grow at a steady, predictable rate (like t3/2t^{3/2}, which grows faster than a square but slower than a cube).

For a long time, mathematicians believed they had a perfect "rulebook" (a set of criteria) to guarantee that these patterns would reappear often and in long, unbroken chains. This rulebook relied on looking at the real-number coefficients (the exact, messy decimals) of the functions.

The Question: The authors of this paper asked: Can we simplify this rulebook? Can we ignore the messy decimals and just look at the whole numbers (integers) inside the functions? If the whole-number rules are satisfied, does the pattern still have to reappear?

The Answer: No. The authors proved that the "whole-number" rulebook is not strong enough. You can satisfy all the integer rules, and the pattern might still fail to reappear, or it might reappear in a very broken, sparse way.


The Main Characters: The "Growth Machines"

To prove their point, the authors built two specific "machines" (pairs of functions) that act like tricksters.

1. The "Almost-There" Machine (Theorem 1.5)

Imagine two runners, Runner A and Runner B.

  • Runner A runs at a speed of t3/2t^{3/2}.
  • Runner B runs at a speed of λt3/2+t\lambda t^{3/2} + t (where λ\lambda is a weird, non-repeating decimal like π\pi).

The Trap:
If you look at the whole number parts of their speeds, they seem to follow a perfect rule. They pass the "integer check."

  • The Expectation: You would expect that if you pick a starting point, you will eventually find a long stretch of time where both runners hit specific checkpoints simultaneously.
  • The Reality: The authors found a specific "track" (a set of numbers) where the runners do hit the checkpoints, but they never do so in a long, unbroken line. They hit them in a scattered, broken way.
  • The Metaphor: It's like a train schedule that looks perfect on paper (integer times), but when you actually try to catch the train, you only catch it for a split second, then have to wait a long time, then catch it again for a split second. You never get a long, continuous ride.

2. The "Ghost" Machine (Theorem 1.6)

This is an even more extreme version. The authors tweaked the second runner slightly (adding a shift ξ\xi).

  • The Trap: This pair also passes the "integer check."
  • The Reality: On a specific track, the two runners never meet at the same checkpoint at the same time. The set of times they meet is empty.
  • The Metaphor: It's like two people trying to shake hands. They are both following the rules of the handshake protocol (the integer rules), but because of a tiny, invisible offset (the decimal part), their hands are always just a millimeter apart. They never actually touch.

3. The "Three-Way" Trick (Theorem 1.7)

The authors added a third runner to the mix to answer a different question: What if we look at the "shadow" of the functions (the polynomials they look like)?

  • They showed that even if the "shadows" of the functions look like they should work together perfectly (jointly intersective), the actual functions can still refuse to meet.
  • The Metaphor: Imagine three dancers. Their shadows on the wall look like they are perfectly synchronized. But in reality, on the dance floor, they are completely out of step and never meet in the center.

How They Did It: The "Bohr Obstruction"

How did they prove these runners never meet? They used a concept called a Bohr set.

Think of a Bohr set as a "safe zone" or a "fence" in a circular world (like a clock face).

  • The authors constructed a specific "fence" (a set of numbers EE) that the runners are forced to stay near.
  • Because of the way the numbers are built (using that weird irrational number λ\lambda), the "fence" is shaped in a way that forces the runners to miss each other.
  • It's like setting up a maze where the walls are invisible. The runners follow the rules, but the geometry of the maze ensures they can never cross paths in the way the "integer rulebook" predicted they should.

The Takeaway

The paper delivers a "negative answer" to two big questions in the field of Ergodic Ramsey Theory (a branch of math that studies order in chaos).

  1. You can't just use whole numbers. You cannot replace the complex, real-number rules with simple integer rules and expect the same guarantee of recurrence.
  2. The "Shadow" isn't enough. Even if the polynomial "shadows" of the functions look promising, the actual functions might still fail to produce the expected patterns.

In short: The universe of these number sequences is more subtle than we thought. Just because the "whole number" parts of the rules look good doesn't mean the whole picture is good. The tiny, invisible decimal parts can completely break the pattern.

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 →