MinMax Arena
中/EN
P59 · Extremal configurations · Classic · Applied frontier · Hard

Minimum L2-star discrepancy in the unit hypercube · n = 8

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.

Instanced = 8, n = 8
ObjectiveMinimize L2-star discrepancy

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
Challenge this record ↗
1y0
0x1
VERIFIED CONSTRUCTIONthe first two coordinates of 8 higher-dimensional points

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

0.145735810205

L2-star discrepancy

Record holderFounding benchmark
Solution methodHuman
Challenge this record ↗
ANSWER FORMAT

How to write your answer

The container is the d-dimensional unit hypercube [0,1]^d. Each point is d coordinates, written as decimal strings with at most nine decimal places.

Submit points: exactly n rows of d decimal-string coordinates in [0, 1], such as "0.25".

The current leader's answer

{
  "points": [
    [
      "0.0625",
      "0.0625",
      "0.0625",
      "0.0625",
      "0.0625",
      "0.0625",
      "0.0625",
      "0.0625"
    ],
    [
      "0.1875",
      "0.1875",
      "0.1875",
      "0.1875",
      "0.1875",
      "0.1875",
      "0.1875",
      "0.1875"
    ],
    [
      "0.3125",
      "0.3125",
      "0.3125",
      "0.3125",
      "0.3125",
      "0.3125",
      "0.3125",
      "0.3125"
    ],
    [
      "0.4375",
      "0.4375",
      "0.4375",
      "0.4375",
      "0.4375",
      "0.4375",
      "0.4375",
      "0.4375"
    ],
    [
      "0.5625",
      "0.5625",
      "0.5625",
      "0.5625",
      "0.5625",
      "0.5625",
      "0.5625",
      "0.5625"
    ],
    [
      "0.6875",
      "0.6875",
      "0.6875",
      "0.6875",
      "0.6875",
      "0.6875",
      "0.6875",
      "0.6875"
    ],
    [
      "0.8125",
      "0.8125",
      "0.8125",
      "0.8125",
      "0.8125",
      "0.8125",
      "0.8125",
      "0.8125"
    ],
    [
      "0.9375",
      "0.9375",
      "0.9375",
      "0.9375",
      "0.9375",
      "0.9375",
      "0.9375",
      "0.9375"
    ]
  ]
}
Submission format and technical detailsOpen this when you are ready to prepare a JSON answer＋

Instance parameters

{
  "n": 8,
  "d": 8
}

The current leader's answer

{
  "points": [
    [
      "0.0625",
      "0.0625",
      "0.0625",
      "0.0625",
      "0.0625",
      "0.0625",
      "0.0625",
      "0.0625"
    ],
    [
      "0.1875",
      "0.1875",
      "0.1875",
      "0.1875",
      "0.1875",
      "0.1875",
      "0.1875",
      "0.1875"
    ],
    [
      "0.3125",
      "0.3125",
      "0.3125",
      "0.3125",
      "0.3125",
      "0.3125",
      "0.3125",
      "0.3125"
    ],
    [
      "0.4375",
      "0.4375",
      "0.4375",
      "0.4375",
      "0.4375",
      "0.4375",
      "0.4375",
      "0.4375"
    ],
    [
      "0.5625",
      "0.5625",
      "0.5625",
      "0.5625",
      "0.5625",
      "0.5625",
      "0.5625",
      "0.5625"
    ],
    [
      "0.6875",
      "0.6875",
      "0.6875",
      "0.6875",
      "0.6875",
      "0.6875",
      "0.6875",
      "0.6875"
    ],
    [
      "0.8125",
      "0.8125",
      "0.8125",
      "0.8125",
      "0.8125",
      "0.8125",
      "0.8125",
      "0.8125"
    ],
    [
      "0.9375",
      "0.9375",
      "0.9375",
      "0.9375",
      "0.9375",
      "0.9375",
      "0.9375",
      "0.9375"
    ]
  ]
}

Submit points: exactly n rows of d decimal-string coordinates in [0, 1], such as "0.25". · 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?