20030915, 22:26  #1 
Sep 2003
5025_{8} Posts 
Server behavior for doing quick doublechecks if error code != 0
Is anyone familiar with the exact behavior of the server?
I believe the server does the following: When a result is returned with nonzero error code, the server immediately makes that exponent available for a second "firsttime" LL test. This is done to quickly catch bad results without waiting years for the leading edge of regular double checks to catch up. My question is, is this done for all error codes that are nonzero, or are some error codes like 0x000x00 also skipped over? Also, approximately when was this server behavior implemented? Thanks. 
20030915, 23:06  #2 
Aug 2002
Richland, WA
84_{16} Posts 
I don't believe the server automatically handles any aspect of the doublechecking process. Every once in a while, George manually rereleases the exponents that had too many errors. I do not know the precise error codes that George rereleases, but I do know the 0X000X00 codes are not rereleased.

20030915, 23:29  #3 
P90 years forever!
Aug 2002
Yeehaw, FL
1101111110111_{2} Posts 
Nick is right, I do this manually (actually I run an SQL query).
0X000X00 are not rerun. 00XX0000 are not rerun. 
20031005, 04:35  #4  
Sep 2003
2581_{10} Posts 
Quote:
Does this mean (errorcode & ~0x0F000F00) == 0 is not rerun (errorcode & ~0x00FF0000) == 0 is not rerun or do the two X's have to be identical 01000100 02000200 etc. and 00110000 00220000 etc. 

20031005, 14:13  #5 
Sep 2002
2·331 Posts 
A standard usage is X means, doesn't matter what the value is, so as long as the error code only has non zeros where an X is it is not rerun.
00000000 are not rerun. 00000X00 are not rerun. 0X000000 are not rerun. 0X000X00 are not rerun. 000X0000 are not rerun. 00X00000 are not rerun. 00XX0000 are not rerun. 
20031005, 15:07  #6  
P90 years forever!
Aug 2002
Yeehaw, FL
7,159 Posts 
Quote:
XY00XY00 is not rerun if the XY values are the same. That is, 03000300 is not rerun, but 03000400 is rerun. 00XX0000 is not rerun for any values of XX. 

20031005, 16:44  #7 
"Mike"
Aug 2002
73·107 Posts 
This probably is a bit off topic, but I've always wondered what the stuff in results.txt means... Like this:
WZ1: 82E972AA,4529786,00000000 I think the "WZ1" is the program code, and the next part is like a CRC checksum or something, and the last part is the error code... Can someone break it all down into crazy detail? 
20031007, 01:58  #8 
Aug 2002
Richland, WA
2^{2}·3·11 Posts 
From "readme.txt":
Code:
M1992031 is not prime. Res64: 6549369F4962ADE0. WV1: B253EF24,1414032,00000000 This means 2^19920311 is not prime  a LucasLehmer test says so. The last 64 bits of the last number in the LucasLehmer sequence is 6549369F4962ADE0. At some future date, another person will verify this 64bit result by rerunning the LucasLehmer test. WV1 is the program version number. B253EF24 is a checksum to guard against email transmission errors. 1414032 can be ignored it is used as part of the doublechecking process. The final 00000000 value is a set of 4 counters. These count the number of errors that occurred during the LucasLehmer test. I don't know exactly what each of the 4 error counters represent. Maybe George can answer. 
20031007, 12:38  #9  
Dec 2002
Frederick County, MD
2×5×37 Posts 
Quote:


20031007, 17:23  #11 
Feb 2003
13^{2} Posts 
There is some discusion of error codes in this thread

Thread Tools  
Similar Threads  
Thread  Thread Starter  Forum  Replies  Last Post 
Double checks  casmith789  PrimeNet  7  20150526 00:53 
Doublechecks under M24xxxxxx  DW52  PrimeNet  7  20110407 04:47 
Why do I get doublechecks on this machine?  Kaboom  PrimeNet  3  20110121 15:27 
Double checks  Rastus  Data  1  20031219 18:20 
Doublechecks come in pairs?  BigRed  Software  1  20021020 05:29 