Research notes on every problem, and a library of the papers behind them. Built from the open erdos repository.
Updated
Binomial GCD Thresholds Through Order Thirty
evidence/: Exact enumeration of the binomial-gcd thresholds through order thirty, using the stated finite domain and inline arithmetic witnesses.
Question and finite scope
The E0699 problem page, using the erdosproblems.com formulation accessed, asks:
Is it true that for every there exists some prime such that
This experiment checks every integer triple in the finite domain
It also tests the strict variant, which replaces with . The exact computation finds different answers on this domain. The non-strict threshold holds on all 1,015 triples, while the strict threshold fails exactly at
The listed failure set is fixed as the expectation before the checker runs. Ordinary and optimized runs compute it from the stated integer formulas, without reading stored outputs. This is author-checked finite coverage, not independent acceptance.
Exact enumeration and witnesses
The native check computes each binomial row with
math.comb, then computes every required gcd with math.gcd. Trial division
through the integer square root lists the primes through thirty. For each
gcd it checks divisibility by those primes at the two thresholds.
This prime list is complete for the task. If a prime divides , then it divides , so it is at most . The exhaustive loops include both parity cases for , , and the endpoint . Their number of triples is
There are no eligible pairs for . The count is a coverage check; the explicit loops, prime-divisor argument, and exact predicates supply the connection to the finite question.
The following exact witnesses can also be checked directly from the factorial formula for binomial coefficients:
| Their gcd | |||
|---|---|---|---|
| 4 | 6 | ||
| 120 | 252 | ||
| 120 | 8008 | ||
| 3276 | 40116600 | ||
| 98280 | 40116600 |
For the last two rows,
whereas and . Minimum prime exponents give the displayed gcds. Each exception has largest common prime exactly , so it satisfies the erdosproblems.com threshold and fails the strict one. The first row supplies a strict success. These individual witnesses alone do not exclude further exceptions.
Reproduction and standing
From the repository root, with its locked environment installed, run:
uv run --no-sync python wiki/research/finite_experiments/binomial_gcd_search/evidence/main.pyThe default is the full declared domain; there is no reduced mode. It uses
Python integers, the standard library and the root tools package. All
inputs are the stated bounds and small witness constants in the new
implementation. It reads no input files, depends on no external output or
source manifest, and writes no files. No asset packet is required.
The observed full run finished in about 0.05 seconds, including command
startup, under a 60-second external limit. The optimized run also completed
with the same failure sets and ALL CHECKS PASS (10 checks). The program
prints both observed failure sets, checks the exact witnesses and domain
count, and exits nonzero if any required result fails, including under
python -O. A strict exception is an expected observation; an additional
exception or any non-strict failure makes the declared finite classification
fail. Interrupted execution establishes no complete coverage.
The failure protocol was checked with the actual classifier on : requiring its false strict predicate produced a named failed obligation and exit code 1 under both ordinary and optimized Python. The prime-list checks also reject 1 and the composite divisor 6 as prime witnesses.
The arithmetic and exhaustive classification are author-recorded and have no independent review or formal-verification standing. No all-order result follows from this finite domain, and the strict exceptions do not disprove the erdosproblems.com question. This account changes no problem status and claims no new computational frontier or current literature assessment.