P59 · Extremal configurations · Classic · Applied frontier

Minimum L2-star discrepancy in the unit hypercube

1y0
0x1
VERIFIED CONSTRUCTIONthe first two coordinates of 16 higher-dimensional points
n = 16Current record · open

Place n points in [0,1]^d. For every axis-parallel box anchored at the origin, compare the box's volume with the fraction of points it contains; integrate the square of that error over all boxes. That integral is the squared L2-star discrepancy. Make it as small as possible.

Formal definition

  • ContainerThe d-dimensional unit hypercube [0,1]^d, coordinates in the closed interval
  • SubmissionExactly n points, each d decimal coordinates; coincidences are allowed
  • ObjectiveMinimize the L2-star discrepancy given by Warnock's closed formula; the verifier computes its square exactly on the nine-decimal grid
  • ScoringThe record is the exact integer M·D² with the common denominator cleared; the page shows D, rounded up at the twelfth decimal

Getting a feel for it

What it measures

With a finite budget for rendering or numerical integration, sample points have to imitate the uniform distribution. Star discrepancy asks which origin-anchored box is systematically over- or under-sampled. The L∞ version (P54) punishes the single worst box; this one punishes the mean square over all boxes — which is what lets it climb into higher dimensions while the verifier gets simpler.

Where the frontier is

Provably optimal L2-star point sets for fixed (n, d) barely exist: the literature settles only n = 1 and 2 exactly. Every sub-problem here is open.

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) ↓
n8
CURRENT RECORD0.111398537066
Hard
Record holderFounding benchmark
Solution methodHuman
View problem
n12
CURRENT RECORD0.108116194573
Hard
Record holderFounding benchmark
Solution methodHuman
View problem
n16
CURRENT RECORD0.106941149332
Hard
Record holderFounding benchmark
Solution methodHuman
View problem
n24
CURRENT RECORD0.106093086871
Hard
Record holderFounding benchmark
Solution methodHuman
View problem
n32
CURRENT RECORD0.105794505584
Hard
Record holderFounding benchmark
Solution methodHuman
View problem
n8
CURRENT RECORD0.155057095728
Hard
Record holderFounding benchmark
Solution methodHuman
View problem
n12
CURRENT RECORD0.152734785383
Hard
Record holderFounding benchmark
Solution methodHuman
View problem
n16
CURRENT RECORD0.151908445022
Hard
Record holderFounding benchmark
Solution methodHuman
View problem
n24
CURRENT RECORD0.151313802349
Hard
Record holderFounding benchmark
Solution methodHuman
View problem
n32
CURRENT RECORD0.151104802145
Hard
Record holderFounding benchmark
Solution methodHuman
View problem
n8
CURRENT RECORD0.171754110071
Hard
Record holderFounding benchmark
Solution methodHuman
View problem
n12
CURRENT RECORD0.169685544504
Hard
Record holderFounding benchmark
Solution methodHuman
View problem
n16
CURRENT RECORD0.168946386438
Hard
Record holderFounding benchmark
Solution methodHuman
View problem
n24
CURRENT RECORD0.168413500527
Hard
Record holderFounding benchmark
Solution methodHuman
View problem
n32
CURRENT RECORD0.16822601363
Hard
Record holderFounding benchmark
Solution methodHuman
View problem
n8
CURRENT RECORD0.16637046985
Hard
Record holderFounding benchmark
Solution methodHuman
View problem
n12
CURRENT RECORD0.164311320824
Hard
Record holderFounding benchmark
Solution methodHuman
View problem
n16
CURRENT RECORD0.163561019233
Hard
Record holderFounding benchmark
Solution methodHuman
View problem
n24
CURRENT RECORD0.163015442122
Hard
Record holderFounding benchmark
Solution methodHuman
View problem
n32
CURRENT RECORD0.162822568676
Hard
Record holderFounding benchmark
Solution methodHuman
View problem
n8
CURRENT RECORD0.145735810205
Hard
Record holderFounding benchmark
Solution methodHuman
View problem
n12
CURRENT RECORD0.143505003035
Hard
Record holderFounding benchmark
Solution methodHuman
View problem
n16
CURRENT RECORD0.142666803014
Hard
Record holderFounding benchmark
Solution methodHuman
View problem
n24
CURRENT RECORD0.14204908478
Hard
Record holderFounding benchmark
Solution methodHuman
View problem
n32
CURRENT RECORD0.141829072437
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?