Doublechecking 10987349 - 11013853 - Page 2

dswanson · 2003-06-20, 18:01

401 down, 197 to go. 15 mismatches to date.

We're still waiting for a server resynch before we do the triple-checks on the mismatches.

At the current rate, and barring stragglers on slower machines, we should be done with the range in a month or so. Soon I'll talk to George about picking up a neighboring range, probably something like 10950000 - 10987349.

garo · 2003-06-30, 20:50

wanna give us an update?

A whole lotta numbers are showing up as assigned on Primenet.

dswanson · 2003-06-30, 21:38

See new thread Doublechecking 10950053 - 10987343

dswanson · 2003-07-07, 14:21

500 down, 98 to go. 22 mismatches to date.

dswanson · 2003-08-11, 13:43

580 down, 18 to go. 24 mismatches to date.

Of the 18 remaining, 16 are on slow machines. These should be done in a little more than a month.

One of the other two still has its first-time result in the Primenet database, so I'm waiting for a synch before running it.

The other (11000347) STILL hasn't completed its first-time test. In fact, it hasn't had a single iteration run on it since I started this range back in February. Nonetheless, the computer it's on continues to check back in every few days, so I'm keeping my hands off of it. [Criswell, if you're out there, PLEASE move this to the top of your queue!]

shaneamy and I will be running triple-checks on the 24 mismatches after the next database synch.

dswanson · 2003-09-28, 04:50

597 down, 1 to go. The 1 is still waiting for Criswell, who has yet to add a single iteration to 11000347.

We're also running triple-checks on the mismatches. Only 7 remain. These should all be gone in a week or two, leaving the Criswell number as the only one unverified in this entire range.

dswanson · 2003-10-09, 04:54

It's obvious that Criswell is not going to finish his first-time test any time soon, so I'm declaring this range complete. Every number in this range other than 11000347 is now successfully doublechecked. Shane and I have punched a big gap into the unverified exponent list in HRF3.TXT:

Code:

10986683,shaneamy,Georgia,WZ1,00000000
10986889,jasper,New_Fred,WW1,00000000
10986971,ILC,P3-600RDIEST,WW1,00000000
10987247,sskory,linux.ss.2,WW2,00F10005
10987247,KellyCS,MondoWork,WW1,00000000
11014039,pbornemeier,Home3,WV1,00000000
11014103,yclin,grauert,WW1,00000402
11014103,S16869,CD134B9DC,WV1,00000000
11014111,S58327,CB344B12B,WX1,00000000
11014139,nmfree,nmfree,WW1,0001620D
11014139,RedSoft,ithif13,E2,

Here are a bunch of statistics for this range. A lot of this might be more appropriate to the DATA forum, but I'm posting it here to preserve continuity of this thread. I'll post a link to here in the DATA form.

Note that the high failure rate (4.73%) got a big assist from Userid S01965, who had a 70% failure rate on 10 exponents tested. Excluding S01965, the net failure rate for everyone else was a much more reasonable 3.69% ( = 22/(574+22) ).

Code:

Factors found (P-1):        13
Exponents doublchecked:    584
                         -----
Total exponents cleared:   597


Total numbers that needed triplecheck:       28
Total numbers that needed quadruplecheck:     1
                                          -----
Total failed tests:                          29

Test failure rate = 29/(584+29):           4.73%



----------------------------------------------------------------------
                       Summary of failed tests
----------------------------------------------------------------------
Exponent with                             Userid that     Userid that
at least 1       Userid(s) that           returned 1st    returned 2nd
failed test      returned bad result      good result     good result
----------------------------------------------------------------------
10988507         S38910                   dswanson        shaneamy
10988797         jmberne                  dswanson        shaneamy
10989203         narsley                  dswanson        shaneamy
10991797         eep                      dswanson        shaneamy
10992103         toolio                   dswanson        shaneamy
10992169         Bleys2000                dswanson        shaneamy
10993393         S27300                   Norb_Raddatz    dswanson
10993519         anansky                  S19456          dswanson
10993537         Rlavallee                dswanson        shaneamy
10993721         PH1                      dswanson        shaneamy
10994969         giebel                   dswanson        shaneamy
10998061         S34827,Team_Prime_Rib    dswanson        shaneamy
10999441         tsc                      dswanson        shaneamy
10999489         dextertje                dswanson        shaneamy
11000291         S01965                   dswanson        shaneamy
11000351         S02587                   dswanson        shaneamy
11000393         S01965                   dswanson        shaneamy
11000467         S01965                   S00113          dswanson
11000849         S01965                   dswanson        shaneamy
11000911         S01965                   jshowalter      dswanson
11000929         S01965                   S00113          dswanson
11001413         HP3                      dswanson        shaneamy
11001799         texastip                 dswanson        shaneamy
11002741         FH2                      dswanson        shaneamy
11002879         FH2                      dswanson        shaneamy
11007107         S01965                   pauljharper     dswanson
11010323         jmsandrsn                edoderoo        shaneamy
11011321         krikkio                  shaneamy        dswanson
11012087         S16478                   shaneamy        dswanson


---------------------------------------------------
Statistics on Userids that returned any bad results
---------------------------------------------------
             # of bad     # of good
Userid       results	  results
---------------------------------------------------
anansky          1            0
Bleys2000        1            0
dextertje        1            0
eep              1            0
FH2              2           24
giebel           1            0
HP3              1            0
jmberne          1            0
jmsandrsn        1            0
krikkio          1            0
narsley          1            0
PH1              1            0
Rlavallee        1            0
S01965           7            3
S02587           1            0
S16478           1            0
S27300           1            0
S34827           1            0
S38910           1            0
Team_Prime_Rib   1            3
texastip         1            0
toolio           1            0
tsc              1            0


------------------------------------------------
                 Factors found
------------------------------------------------
Exponent                 Factor             Bits
------------------------------------------------
10987841         3602179992480329067961    71.61
10993121          501959265012140521543    68.77
10996457          325845010199751083879    68.14
11000159           39921746980179464767    65.11
11002001         2413897970043187534681    71.03
11002603          440868640197879020201    68.58
11008901    209558514433320239408181377    87.44
11010551        61649654714772907335407    75.71
11010799           21000106016459484559    64.19
11011379         4605797639189753721761    71.96
11011751         1870224281614097377583    70.66
11011933           32265855910199840857    64.81
11013601           36534321597066119063    64.99

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Optimized doublechecking	biwema	Software	16	2008-10-22 04:28
switching to doublechecking	tha	Lone Mersenne Hunters	11	2004-05-17 15:43
Doublechecking 10950053 - 10987343	dswanson	Lone Mersenne Hunters	6	2003-12-10 04:54
Statistics from doublechecking 10987349 - 11013853	dswanson	Data	0	2003-10-09 05:07

2003-06-20, 18:01	#12
dswanson Aug 2002 C8₁₆ Posts	401 down, 197 to go. 15 mismatches to date. We're still waiting for a server resynch before we do the triple-checks on the mismatches. At the current rate, and barring stragglers on slower machines, we should be done with the range in a month or so. Soon I'll talk to George about picking up a neighboring range, probably something like 10950000 - 10987349.

2003-06-30, 20:50	#13
garo Aug 2002 Termonfeckin, IE 2⁴×173 Posts	wanna give us an update? A whole lotta numbers are showing up as assigned on Primenet.

2003-06-30, 21:38	#14
dswanson Aug 2002 2³×5² Posts	See new thread Doublechecking 10950053 - 10987343

2003-07-07, 14:21	#15
dswanson Aug 2002 2³×5² Posts	500 down, 98 to go. 22 mismatches to date.

2003-08-11, 13:43	#16
dswanson Aug 2002 2³·5² Posts	580 down, 18 to go. 24 mismatches to date. Of the 18 remaining, 16 are on slow machines. These should be done in a little more than a month. One of the other two still has its first-time result in the Primenet database, so I'm waiting for a synch before running it. The other (11000347) STILL hasn't completed its first-time test. In fact, it hasn't had a single iteration run on it since I started this range back in February. Nonetheless, the computer it's on continues to check back in every few days, so I'm keeping my hands off of it. [Criswell, if you're out there, PLEASE move this to the top of your queue!] shaneamy and I will be running triple-checks on the 24 mismatches after the next database synch.

2003-09-28, 04:50	#17
dswanson Aug 2002 2³×5² Posts	597 down, 1 to go. The 1 is still waiting for Criswell, who has yet to add a single iteration to 11000347. We're also running triple-checks on the mismatches. Only 7 remain. These should all be gone in a week or two, leaving the Criswell number as the only one unverified in this entire range.