P60 · Extremal configurations · Classic · Applied frontier

Line packing in real projective space

VERIFIED CONSTRUCTIONpairwise overlap heat of 9 directions; brighter is closer
n = 9Current record · open

Choose n lines through the origin of R^d so that the minimum angle between any two is as large as possible — equivalently, minimize the largest coherence μ = max |cos ∠(v_i, v_j)|.

Formal definition

  • ContainerReal d-space R^d, every line through the origin; an answer is n points of real projective space RP^{d-1}
  • SubmissionExactly n nonzero vectors, d coordinates each; a vector stands for the line it spans
  • ObjectiveMinimize μ² = max (v_i·v_j)²/(|v_i|²|v_j|²), compared exactly by cross-multiplication — no normalization, no square roots
  • ScoringThe record is ceil(μ²·10¹⁸), rounded against the submitter; the page shows μ, rounded up at the ninth decimal

Getting a feel for it

Another way to say it

At d = 4 a normalized nonzero vector is a unit quaternion, and q and −q are the same 3D rotation — so the d = 4 sub-problems ask for n maximally separated 3D orientations, a problem robotics and rendering actually use.

Where the frontier is

Grassmannian frames drive noise- and erasure-robust data representations, wireless communication and compressed sensing. Sloane's packing table maintains the best known values for these parameters and openly invites improvement; optimality proofs in d = 3 stop at n = 8.

Source
ONE LEADERBOARD PER n

Current best solutions by n

Each n is an independent record with a page of its own. Open any of them to inspect the current construction, then challenge it.

Discussion (0) ↓
n9
CURRENT RECORD0.995423317best known 0.669362319
Hard
Record holderFounding benchmark
Solution methodHuman
View problem
n10
CURRENT RECORD0.996330263best known 0.686140661
Hard
Record holderFounding benchmark
Solution methodHuman
View problem
n11
CURRENT RECORD0.996992475best known 0.714434497
Hard
Record holderFounding benchmark
Solution methodHuman
View problem
n12
CURRENT RECORD0.997490586best known 0.744520838
Hard
Record holderFounding benchmark
Solution methodHuman
View problem
n13
CURRENT RECORD0.9978746best known 0.768137376
Hard
Record holderFounding benchmark
Solution methodHuman
View problem
n14
CURRENT RECORD0.998176845best known 0.780622192
Hard
Record holderFounding benchmark
Solution methodHuman
View problem
n15
CURRENT RECORD0.998418972best known 0.786558571
Hard
Record holderFounding benchmark
Solution methodHuman
View problem
n16
CURRENT RECORD0.998615917best known 0.794654472
Hard
Record holderFounding benchmark
Solution methodHuman
View problem
n9
CURRENT RECORD0.993492059best known 0.434258545
Hard
Record holderFounding benchmark
Solution methodHuman
View problem
n10
CURRENT RECORD0.994781332best known 0.434258545
Hard
Record holderFounding benchmark
Solution methodHuman
View problem
n11
CURRENT RECORD0.99571906best known 0.5
Hard
Record holderFounding benchmark
Solution methodHuman
View problem
n12
CURRENT RECORD0.996423143best known 0.5
Hard
Record holderFounding benchmark
Solution methodHuman
View problem
n13
CURRENT RECORD0.996965666best known 0.56691527
Hard
Record holderFounding benchmark
Solution methodHuman
View problem
n14
CURRENT RECORD0.997392788best known 0.590076515
Hard
Record holderFounding benchmark
Solution methodHuman
View problem
n15
CURRENT RECORD0.997735218best known 0.608739411
Hard
Record holderFounding benchmark
Solution methodHuman
View problem
n16
CURRENT RECORD0.998014051best known 0.618033988
Hard
Record holderFounding benchmark
Solution methodHuman
View problem
n17
CURRENT RECORD0.998244174best known 0.630851711
Hard
Record holderFounding benchmark
Solution methodHuman
View problem
n18
CURRENT RECORD0.998436348best known 0.636647308
Hard
Record holderFounding benchmark
Solution methodHuman
View problem
n19
CURRENT RECORD0.998598508best known 0.646648903
Hard
Record holderFounding benchmark
Solution methodHuman
View problem
n20
CURRENT RECORD0.998736612best known 0.652985797
Hard
Record holderFounding benchmark
Solution methodHuman
View problem
n11
CURRENT RECORD0.995718556best known 0.386641198
Hard
Record holderFounding benchmark
Solution methodHuman
View problem
n12
CURRENT RECORD0.99642289best known 0.390388203
Hard
Record holderFounding benchmark
Solution methodHuman
View problem
n13
CURRENT RECORD0.996965532best known 0.411006675
Hard
Record holderFounding benchmark
Solution methodHuman
View problem
n14
CURRENT RECORD0.997392713best known 0.41113055
Hard
Record holderFounding benchmark
Solution methodHuman
View problem
n15
CURRENT RECORD0.997735175best known 0.414213562
Hard
Record holderFounding benchmark
Solution methodHuman
View problem
n16
CURRENT RECORD0.998014025best known 0.447213595
Hard
Record holderFounding benchmark
Solution methodHuman
View problem
n17
CURRENT RECORD0.998244158best known 0.480910335
Hard
Record holderFounding benchmark
Solution methodHuman
View problem
n18
CURRENT RECORD0.998436338best known 0.483999
Hard
Record holderFounding benchmark
Solution methodHuman
View problem
n19
CURRENT RECORD0.998598502best known 0.5
Hard
Record holderFounding benchmark
Solution methodHuman
View problem
n20
CURRENT RECORD0.998736608best known 0.5
Hard
Record holderFounding benchmark
Solution methodHuman
View problem
n21
CURRENT RECORD0.998855204best known 0.541672064
Hard
Record holderFounding benchmark
Solution methodHuman
View problem
n22
CURRENT RECORD0.998957809best known 0.554034328
Hard
Record holderFounding benchmark
Solution methodHuman
View problem
DISCUSSION

Discussion

Talk strategy, share methods, ask why you are stuck. Posts carry your public byline, the same name your records use; the #number after it is the account's signup ordinal, so a name cannot be worn by someone else. The floor is earned: break a record once, anywhere, and it is yours for good. New posts appear after an automated review.

No threads yet. Be the first to talk about this problem?