Plain language

What this result means

This result matters because the rule is local and exact. A set is valid only if no chosen point sees two other chosen points at the same squared distance. That one repeated distance would immediately create an isosceles triangle.

  • AlphaEvolve published strong sets at n=64 and n=100, but not the open n values reported here.
  • The 54 claimed rows are the evolve_sweep records in RECORDS.jsonl.
  • The largest reported sets are n=77 and n=79, each with 116 selected points.

Visual notes

How to read the result

Line chart of no-isosceles grid set sizes for open n values, with AlphaEvolve n=64 and n=100 shown as hollow reference points.
Open grid sizesWhite points are Numaro first-known rows. Hollow points are AlphaEvolve's published n=64 and n=100 rows, which are not beaten.
Scatter plot of the 116-point no-isosceles set in the 77 by 77 grid.
Actual n=77 setThe 116 points are rendered from RECORDS.jsonl. The dashed midlines show the symmetry-preserving search space.
Distance-ring visualization around one selected point in the n=77 no-isosceles set.
Distance testFor one anchor, each squared distance is unique. The checker repeats the same exact test around every selected point.

Result table

Fifty-four first-known no-isosceles grid values for open n values.

CellBaselineNumaroDeltaNote
n=22none listed36first-knownfirst claimed row
n=23none listed40first-knowninteger-coordinate set
n=24none listed40first-knowninteger-coordinate set
n=25none listed40first-knowninteger-coordinate set
n=26none listed42first-knowninteger-coordinate set
n=27none listed44first-knowninteger-coordinate set
n=29none listed48first-knowninteger-coordinate set
n=31none listed52first-knowninteger-coordinate set
n=32none listed52first-knowninteger-coordinate set
n=33none listed52first-knowninteger-coordinate set
n=35none listed56first-knowninteger-coordinate set
n=36none listed56first-knowninteger-coordinate set
n=37none listed64first-knowninteger-coordinate set
n=38none listed60first-knowninteger-coordinate set
n=39none listed60first-knowninteger-coordinate set
n=40none listed64first-knowninteger-coordinate set
n=41none listed64first-knowninteger-coordinate set
n=42none listed64first-knowninteger-coordinate set
n=43none listed68first-knowninteger-coordinate set
n=44none listed68first-knowninteger-coordinate set
n=45none listed72first-knowninteger-coordinate set
n=46none listed70first-knowninteger-coordinate set
n=47none listed72first-knowninteger-coordinate set
n=48none listed74first-knowninteger-coordinate set
n=49none listed76first-knowninteger-coordinate set
n=50none listed78first-knowninteger-coordinate set
n=51none listed80first-knowninteger-coordinate set
n=52none listed80first-knowninteger-coordinate set
n=53none listed84first-knowninteger-coordinate set
n=54none listed80first-knowninteger-coordinate set
n=55none listed84first-knowninteger-coordinate set
n=56none listed84first-knowninteger-coordinate set
n=57none listed88first-knowninteger-coordinate set
n=58none listed92first-knowninteger-coordinate set
n=59none listed92first-knowninteger-coordinate set
n=60none listed92first-knowninteger-coordinate set
n=61none listed92first-knowninteger-coordinate set
n=62none listed92first-knowninteger-coordinate set
n=63none listed96first-knownneighbor of published n=64
n=65none listed96first-knownneighbor of published n=64
n=66none listed100first-knowninteger-coordinate set
n=67none listed104first-knowninteger-coordinate set
n=68none listed104first-knowninteger-coordinate set
n=69none listed104first-knowninteger-coordinate set
n=70none listed104first-knowninteger-coordinate set
n=71none listed112first-knowninteger-coordinate set
n=72none listed112first-knowninteger-coordinate set
n=73none listed112first-knowninteger-coordinate set
n=74none listed112first-knowninteger-coordinate set
n=75none listed112first-knowninteger-coordinate set
n=76none listed112first-knowninteger-coordinate set
n=77none listed116first-knownlargest value in table
n=78none listed112first-knowninteger-coordinate set
n=79none listed116first-knownlargest value in table

Method

How it was found

The campaign improved the generator of point sets, not just one fixed set. The best rows came from an evolved construction that keeps symmetry while adding and removing whole orbits of points.

  • Loaded and checked the published AlphaEvolve n=64 and n=100 reference sets for calibration.
  • Observed that direct point-level search plateaued at lower density.
  • Evolved construction parameters for symmetry group, axis, ruin fraction, local search, and candidate count.
  • Kept the 54 evolve_sweep rows whose saved point sets pass the exact no-isosceles check.

Verification

How it was checked

For each selected point P, the checker computes the squared distance from P to every other selected point. If a squared distance appears twice, P and those two points form an isosceles triangle, so the set fails. All 54 reported evolve_sweep rows pass this exact integer check.

Scope

What is not being claimed

These are first-known lower bounds for open n values, not optimality proofs. They are not beats of AlphaEvolve's published n=64 and n=100 values. The missing open sizes in this sweep are n=28, n=30, and n=34; n=64 already had a published AlphaEvolve row.

References

Baseline sources

Citation

How to cite

Numaro Autoresearch Team. "First-known no-isosceles grid sets for open n values." Numaro Research Report NUMARO-2026-010, 2026.

@techreport{numaro2026NoIsoscelesGrid,
  title = {First-known no-isosceles grid sets for open n values},
  author = {Numaro Autoresearch Team},
  institution = {Numaro},
  number = {NUMARO-2026-010},
  year = {2026},
  url = {https://numaro.tech/research/no-isosceles-grid-2026/}
}