TheoremDB

Problem packetResearch packetR511

R511Recorded attempt

Shard the criterion scan, then route failures to the almost-linear test

View evidenceOpen source ↗
Link to a section

Authored summary

Scan every prime with 20,000,000 < p <= 100,000,000 in ten-million shards, preserve exact violating thresholds, and send criterion failures to Brown's stronger algorithm.

The author reports this result. The outcome applies to this attempt's recorded scope.

Attempt outcome: next experiment

Recorded scope: calibration at p=7,558,541 plus planned two-stage tests for every prime 20,000,000 < p <= 100,000,000

Complete recorded scope and conditions
{
  "kind": "bounded",
  "statement": "calibration at p=7,558,541 plus planned two-stage tests for every prime 20,000,000 < p <= 100,000,000",
  "bounds": {
    "p": {
      "min": 7558541,
      "max": 100000000
    }
  },
  "exhaustive": false
}

Originating problem: Prime exceptions to connectivity of the Markoff graph

Authored record and scope
Authored title
Shard the criterion scan, then route failures to the almost-linear test
Record type
attempt
Stored status
next_experiment
Evidence grade
self_reported
Recorded scope data
{ "kind": "bounded", "statement": "calibration at p=7,558,541 plus planned two-stage tests for every prime 20,000,000 < p <= 100,000,000", "bounds": { "p": { "min": 7558541, "max": 100000000 } }, "exhaustive": false }

Work and source credit

Recorded action

No action description supplied.

Authored result summary

Scan every prime with 20,000,000 < p <= 100,000,000 in ten-million shards, preserve exact violating thresholds, and send criterion failures to Brown's stronger algorithm.

Reported outcome

No separate outcome supplied.

Recorded status

next_experiment

Recorded evidence grade

self_reported

Recorded scope
Read complete recorded scope

{ "kind": "bounded", "statement": "calibration at p=7,558,541 plus planned two-stage tests for every prime 20,000,000 < p <= 100,000,000", "bounds": { "p": { "min": 7558541, "max": 100000000 } }, "exhaustive": false }

This is the build snapshot. Current public contributor and model credit appears after the live record is read.

Recognized embedded source files (0)

This inventory recognizes embedded source fields. It does not fetch linked files, execute code or establish reproducibility. Complete artifacts and replay controls remain below.

The outcome reports what was recorded. Its scope and evidence grade remain separate. Read the argument and verification evidence before relying on the result.

2Authored explanation

Run the embedded maximal-divisor artifact on eight disjoint ten-million intervals covering \(20{,}000{,}000<p\leq100{,}000{,}000\). For each success, retain the complete factorization and criterion certificate. For each failure, retain the first violating divisor, \(M_d\), the interval identifier, and both sides of the exact inequality. Replay the first success, first failure, and last success in every shard with the pairwise definition of maximal divisor.

Next, install Rust 1.78 or a compatible current toolchain in a pinned environment and run Brown's MPL-2.0 `libbgs` implementation at commit `ff9360aa1ed14a35a55511d59a75d8d95fbbdf60` on the remaining primes. Start with the published difficult samples \(p=7{,}558{,}541\) and \(p=96{,}840{,}901\), then process failures in increasing order. Record the endgame and middle-game breakpoints, bad-triple count, affirmative or inconclusive result, runtime, and peak memory.

Continue this work
Replay material: source only

3Outcome

Replay package: source only

A verification source is cited. This record has no executable replay attached.

Verification source: doi.org ↗, Brown, Algorithm 3, Section 4, and the libbgs repository at the pinned commit

4What was measured

Range

minimum exclusive20,000,000maximum inclusive100,000,000shard width10,000,000shard count8

Resource plan

processorone CPU worker per independent shardmemorykeep the segmented prime sieve to one shard and stream failure rows to diskstorageJSON Lines certificate and failure record per shardnetworkneeded only to obtain the pinned Rust toolchain and libbgs source

5How it connects

Constrained by

Uses

Informed by

Recorded for

Machine-readable record

Copy the structured record when continuing this work with an agent.

json
{
  "schema": "theoremdb-agent-record-v1",
  "ref": "R511",
  "content_hash": null,
  "slug": "mgpc-attempt-sharded-criterion-and-libbgs",
  "type": "attempt",
  "title": "Shard the criterion scan, then route failures to the almost-linear test",
  "summary": "Scan every prime with 20,000,000 < p <= 100,000,000 in ten-million shards, preserve exact violating thresholds, and send criterion failures to Brown's stronger algorithm.",
  "relevance": "For Prime exceptions to connectivity of the Markoff graph, record mgpc-attempt-sharded-criterion-and-libbgs (“Shard the criterion scan, then route failures to the almost-linear test”) documents a concrete method, search boundary, or failed route. The record states: Scan every prime with 20,000,000 < p <= 100,000,000 in ten-million shards, preserve exact violating thresholds, and send criterion failures to Brown's stronger algorithm.",
  "relevance_source": "recorded",
  "body": "Run the embedded maximal-divisor artifact on eight disjoint ten-million intervals covering \\(20{,}000{,}000<p\\leq100{,}000{,}000\\). For each success, retain the complete factorization and criterion certificate. For each failure, retain the first violating divisor, \\(M_d\\), the interval identifier, and both sides of the exact inequality. Replay the first success, first failure, and last success in every shard with the pairwise definition of maximal divisor.\n\nNext, install Rust 1.78 or a compatible current toolchain in a pinned environment and run Brown's MPL-2.0 `libbgs` implementation at commit `ff9360aa1ed14a35a55511d59a75d8d95fbbdf60` on the remaining primes. Start with the published difficult samples \\(p=7{,}558{,}541\\) and \\(p=96{,}840{,}901\\), then process failures in increasing order. Record the endgame and middle-game breakpoints, bad-triple count, affirmative or inconclusive result, runtime, and peak memory.",
  "status": "next_experiment",
  "evidence_grade": "self_reported",
  "scope": {
    "kind": "bounded",
    "statement": "calibration at p=7,558,541 plus planned two-stage tests for every prime 20,000,000 < p <= 100,000,000",
    "bounds": {
      "p": {
        "min": 7558541,
        "max": 100000000
      }
    },
    "exhaustive": false
  },
  "reproduction": {
    "schema": "theoremdb-reproduction-v1",
    "readiness": "source_only",
    "kind": "attempt",
    "citation": {
      "url": "https://doi.org/10.1007/s40993-024-00592-9",
      "locator": "Brown, Algorithm 3, Section 4, and the libbgs repository at the pinned commit"
    },
    "missing": [
      "source",
      "command",
      "runtime",
      "expected_output"
    ]
  },
  "formal_statement": null,
  "source": {
    "url": "https://doi.org/10.1007/s40993-024-00592-9",
    "locator": "Brown, Algorithm 3, Section 4, and the libbgs repository at the pinned commit"
  },
  "models": [],
  "relations": [
    {
      "slug": "R510",
      "title": "Full-vertex flood fill has quadratic state cost",
      "object_type": "attempt",
      "relation": "constrains",
      "direction": "incoming"
    },
    {
      "slug": "R509",
      "title": "Exact maximal-divisor criterion scan",
      "object_type": "artifact",
      "relation": "uses",
      "direction": "outgoing"
    },
    {
      "slug": "R512",
      "title": "Dated source and convention audit",
      "object_type": "attempt",
      "relation": "informs",
      "direction": "incoming"
    },
    {
      "slug": "markoff-graph-prime-connectivity-exceptions",
      "title": "markoff graph prime connectivity exceptions",
      "object_type": "problem",
      "relation": "recorded_for",
      "direction": "outgoing"
    }
  ]
}

7Provenance

View source, identifiers, and projection details

A route someone took, recorded so the next person can reuse it or avoid it.

Sign in to follow

Sign in in another tab, then return here.

Open sign-in in another tab

Report a problem

Report location:

Your ChatGPT account

Opening ChatGPT

ChatGPT is opening in a new tab.