ProbXiv
sign in
unchecked

Four-Terminal Planar Case of the Dinitz-Garg-Goemans Cost Conjecture

Nothing has been published against this problem here, and nobody has checked anything. That is the ordinary condition of an open problem, not a defect in the record.

planar-four-terminal-dggAlgorithms & optimizationposed by Yefim Dinitz, Naveen Garg & Michel Goemans, 1999recorded: variant

1 attempt · no person has looked

Statement

Does the Dinitz-Garg-Goemans cost-preserving unsplittable-flow rounding conjecture survive on acyclic planar instances with only four terminals? An explicit instance answers no: every cost-nonincreasing unsplittable routing has upper overload at least 335335 while the maximum demand is 294294.

Context

restricted planar four-terminal case

A concrete special case of the Dinitz-Garg-Goemans conjecture.

People

no project yet · nobody looking

Projects

none yet

Nobody is running a project on this. A project is a stated goal, a thread, and one thing somebody else could do. It takes a title, one sentence on what would count as progress, and that one task.

begin a project on this problem →

Interest

nobody looking

Nobody has said they are looking at this. A mark here is a statement about you, not a claim on the problem: you set it, you clear it, and it blocks nobody.

Attempts

1 attempt

No person has examined this. 1 attempt is published here and nothing has been checked against it at all. Saying whether the mathematics holds is the most useful thing anybody can do on this page.

review this attempt

  • #1

    Attempt 1

    computationGPT-5.6 Pro with Matthew Protti ·
    AI involvement
    ai co developed
    a person and a model developed the result together.
    models
    GPT-5.6 Pro
    people
    Matthew Protti

    GPT-5.6 Pro carried out much of the construction search, symbolic derivation, proof development, exact-verifier development, adversarial critique and manuscript preparation. The human author selected and framed the problem, directed the investigation, caught a cost-normalization error, required exact and adversarial checks, set the claim scope and approved the release. A later Codex session independently re-encoded the key graph, finite and symbolic checks and ran deterministic stress and release checks.

    Reviews

    0 human reviews · 0 machine checks

    No person has reviewed this attempt. It has not been checked at all.

    Endorsements

    0 endorsements

    No one has endorsed this attempt. An endorsement is a person stating that they checked this version and believe it is correct. None has been recorded — which is information, not an omission.

    Discussion of this attempt

    no comments

Discussion

no comments

Nothing has been said about this problem yet. Discussion is for questions about the statement, pointers to prior work and objections to an attempt. It is not review: a review is a verdict recorded against one version of one attempt, and it is counted separately.

Reading every thread is open to everyone. Posting needs an account with posting rights — sign in to check yours.