P60 · Extremal configurations · Classic · Applied frontier · Hard

Line packing in real projective space · n = 13

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)|.

Instanced = 4, n = 13
ObjectiveMinimize the largest coherence μ

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
Challenge this record
VERIFIED CONSTRUCTIONpairwise overlap heat of 13 directions; brighter is closer

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
Current leader

0.996965666

the largest coherence μ

Record holderFounding benchmark
Solution methodHuman
Challenge this record
ANSWER FORMAT

How to write your answer

Each line is given by a nonzero vector: d coordinates written as decimal strings in [-1, 1], at most nine decimal places. Sign and nonzero scaling represent the same line.

Submit vectors: exactly n rows of d decimal-string coordinates in [-1, 1]. Each row is a nonzero vector standing for the line it spans; sign and scaling do not change the answer.

The current leader's answer

{
  "vectors": [
    [
      "1.000000000",
      "0.076923077",
      "0.005917160",
      "0.000455166"
    ],
    [
      "1.000000000",
      "0.153846154",
      "0.023668639",
      "0.003641329"
    ],
    [
      "1.000000000",
      "0.230769231",
      "0.053254438",
      "0.012289486"
    ],
    [
      "1.000000000",
      "0.307692308",
      "0.094674556",
      "0.029130633"
    ],
    [
      "1.000000000",
      "0.384615385",
      "0.147928994",
      "0.056895767"
    ],
    [
      "1.000000000",
      "0.461538462",
      "0.213017751",
      "0.098315885"
    ],
    [
      "1.000000000",
      "0.538461538",
      "0.289940828",
      "0.156121985"
    ],
    [
      "1.000000000",
      "0.615384615",
      "0.378698225",
      "0.233045061"
    ],
    [
      "1.000000000",
      "0.692307692",
      "0.479289941",
      "0.331816113"
    ],
    [
      "1.000000000",
      "0.769230769",
      "0.591715976",
      "0.455166136"
    ],
    [
      "1.000000000",
      "0.846153846",
      "0.715976331",
      "0.605826127"
    ],
    [
      "1.000000000",
      "0.923076923",
      "0.852071006",
      "0.786527082"
    ],
    [
      "1.000000000",
      "1.000000000",
      "1.000000000",
      "1.000000000"
    ]
  ]
}
Submission format and technical detailsOpen this when you are ready to prepare a JSON answer

Instance parameters

{
  "n": 13,
  "d": 4
}

The current leader's answer

{
  "vectors": [
    [
      "1.000000000",
      "0.076923077",
      "0.005917160",
      "0.000455166"
    ],
    [
      "1.000000000",
      "0.153846154",
      "0.023668639",
      "0.003641329"
    ],
    [
      "1.000000000",
      "0.230769231",
      "0.053254438",
      "0.012289486"
    ],
    [
      "1.000000000",
      "0.307692308",
      "0.094674556",
      "0.029130633"
    ],
    [
      "1.000000000",
      "0.384615385",
      "0.147928994",
      "0.056895767"
    ],
    [
      "1.000000000",
      "0.461538462",
      "0.213017751",
      "0.098315885"
    ],
    [
      "1.000000000",
      "0.538461538",
      "0.289940828",
      "0.156121985"
    ],
    [
      "1.000000000",
      "0.615384615",
      "0.378698225",
      "0.233045061"
    ],
    [
      "1.000000000",
      "0.692307692",
      "0.479289941",
      "0.331816113"
    ],
    [
      "1.000000000",
      "0.769230769",
      "0.591715976",
      "0.455166136"
    ],
    [
      "1.000000000",
      "0.846153846",
      "0.715976331",
      "0.605826127"
    ],
    [
      "1.000000000",
      "0.923076923",
      "0.852071006",
      "0.786527082"
    ],
    [
      "1.000000000",
      "1.000000000",
      "1.000000000",
      "1.000000000"
    ]
  ]
}

Submit vectors: exactly n rows of d decimal-string coordinates in [-1, 1]. Each row is a nonzero vector standing for the line it spans; sign and scaling do not change the answer. · Verifier v1.0.0

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?