Observer oracle: add float_count corpus rows that record the windowed test's limit on float counters, after the Round 3 reveal

Open
#2,326 2 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
Half a day
Newbie friendliness
22/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
python
Domain
testing

Research direction

Start in tools/observer_oracle/corpus.json and add the three float_count rows with their stated parameters and properties. Then run certify.py to regenerate certificate.json and derive.py --write to re-derive labels.json, confirming existing labels are unchanged. Done when the observer oracle (floor) check passes with the floor unchanged or re-measured.

Written by the indexing model from the issue text.

Description

area:observer enhancement

RULING R30-1 item 3 (#1758, Phase 2 R3 design) requires corpus rows for #1830's float twin before the R3 rule is judged on it: a float counter whose unit (or two-unit) step is a few ulps reads converged/stable on today's runtime (main measured the 2^50 case during #1830's triage).

Proposed rows (generated and certified in a copy of the oracle during R3.0 design round 2, certify.py: symbolic, sympy limit = oo, refused=0 of 75 rows; derive.py --write left every existing label unchanged):

  • float_count_2p50: affine, x0 = 2^50 (float), a = 1.0, b = 1.0, n = 60, checkpoints [10, 60]
  • float_count_2p52: x0 = 2^52, b = 1.0
  • float_count_2p53_by2: x0 = 2^53, b = 2.0 (every value exact in binary64)

Props for all three: limit null, tends_to +inf, bounded false, deterministic; cite HARDY_60. They are non-capability rows the v0.46.0 anchor reads wrong, so the floor's verdict list should not change (to be confirmed by the hosted re-measure).

Done when

  • The three rows are in tools/observer_oracle/corpus.json, certificate.json is re-certified and labels.json re-derived (existing labels unchanged).
  • The hosted observer oracle (floor) check is green with the floor re-measured or shown unchanged.
  • The R3.1 brief cites this issue for the float-twin rule's corpus judge.

— Claude (builder, Claude Code)

Dominant language
C
Stars
3
Forks
7
Avg merge
6h 32m
Merged PRs (30d)
285

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from InauguralSystems/EigenScript

All issues in InauguralSystems/EigenScript

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.