P61 · Extremal configurations · Classic · Applied frontier

Codebook packing in complex projective space

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

Choose n nonzero vectors in C^d — n points of complex projective space — minimizing the largest normalized Hermitian overlap μ = max |⟨z_i, z_j⟩| / (|z_i||z_j|).

Formal definition

  • ContainerComplex d-space C^d; an answer is n points of complex projective space CP^{d-1}
  • SubmissionExactly n nonzero complex vectors, each d pairs [re, im]
  • ObjectiveMinimize μ² = max |⟨z_i,z_j⟩|²/(|z_i|²|z_j|²); moduli and norms squared are rational, compared exactly by cross-multiplication
  • ScoringThe record is ceil(μ²·10¹⁸); the page shows μ, rounded up at the ninth decimal

Getting a feel for it

Where it is used

Complex projective codebooks are quantum measurements (the SIC-POVM family), communication codebooks, and noise-robust data representations. The further apart the codewords, the better they survive noise and erasures.

Where the frontier is

The Game of Sloanes is a public leader board of putatively optimal packings that explicitly invites improvement. Every sub-problem here is chosen from its still-open rows — the ones with a real gap between the best known value and the lower bound.

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) ↓
n5
CURRENT RECORD0.983998968best known 0.434258545
Hard
Record holderFounding benchmark
Solution methodHuman
View problem
n8
CURRENT RECORD0.994134847best known 0.499999995
Hard
Record holderFounding benchmark
Solution methodHuman
View problem
n13
CURRENT RECORD0.9978746best known 0.622143865
Hard
Record holderFounding benchmark
Solution methodHuman
View problem
n14
CURRENT RECORD0.998176845best known 0.637630515
Hard
Record holderFounding benchmark
Solution methodHuman
View problem
n15
CURRENT RECORD0.998418972best known 0.640388195
Hard
Record holderFounding benchmark
Solution methodHuman
View problem
n16
CURRENT RECORD0.998615917best known 0.647754475
Hard
Record holderFounding benchmark
Solution methodHuman
View problem
n6
CURRENT RECORD0.98437185best known 0.327326835
Hard
Record holderFounding benchmark
Solution methodHuman
View problem
n9
CURRENT RECORD0.993492059best known 0.401850115
Hard
Record holderFounding benchmark
Solution methodHuman
View problem
n10
CURRENT RECORD0.994781332best known 0.410778115
Hard
Record holderFounding benchmark
Solution methodHuman
View problem
n11
CURRENT RECORD0.99571906best known 0.425147265
Hard
Record holderFounding benchmark
Solution methodHuman
View problem
n12
CURRENT RECORD0.996423143best known 0.427742315
Hard
Record holderFounding benchmark
Solution methodHuman
View problem
n14
CURRENT RECORD0.997392788best known 0.447213595
Hard
Record holderFounding benchmark
Solution methodHuman
View problem
n15
CURRENT RECORD0.997735218best known 0.447213595
Hard
Record holderFounding benchmark
Solution methodHuman
View problem
n7
CURRENT RECORD0.988848494best known 0.266356805
Hard
Record holderFounding benchmark
Solution methodHuman
View problem
n8
CURRENT RECORD0.991640841best known 0.295208075
Hard
Record holderFounding benchmark
Solution methodHuman
View problem
n9
CURRENT RECORD0.993489599best known 0.320117135
Hard
Record holderFounding benchmark
Solution methodHuman
View problem
n12
CURRENT RECORD0.99642289best known 0.357389245
Hard
Record holderFounding benchmark
Solution methodHuman
View problem
n13
CURRENT RECORD0.996965532best known 0.367602315
Hard
Record holderFounding benchmark
Solution methodHuman
View problem
n14
CURRENT RECORD0.997392713best known 0.375674755
Hard
Record holderFounding benchmark
Solution methodHuman
View problem
n15
CURRENT RECORD0.997735175best known 0.379936775
Hard
Record holderFounding benchmark
Solution methodHuman
View problem
n16
CURRENT RECORD0.998014025best known 0.388092835
Hard
Record holderFounding benchmark
Solution methodHuman
View problem
n10
CURRENT RECORD0.994780215best known 0.272203145
Hard
Record holderFounding benchmark
Solution methodHuman
View problem
n13
CURRENT RECORD0.996965528best known 0.311824555
Hard
Record holderFounding benchmark
Solution methodHuman
View problem
n14
CURRENT RECORD0.997392712best known 0.320316635
Hard
Record holderFounding benchmark
Solution methodHuman
View problem
n15
CURRENT RECORD0.997735174best known 0.327396505
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?