20180213, 10:33  #1 
Dec 2002
Amsterdam, Netherlands
2^{2}·19 Posts 
Suspect results
Recently I have a bunch of suspect results on a bunch of different machines which had recently a power failure. Since all have a suspect status and I can't find exactly why, although I suspect the power failure, I want to ask if anyone is interested in an early double check of one of the following exponents:
77956897 C  Suspect 20180213 77934083 C  Suspect 20180210 77890711 C  Suspect 20180209 77920327 C  Suspect 20180208 77916463 C  Suspect 20180207 77905741 C  Suspect 20180205 77897749 C  Suspect 20180204 Thanks in advance! 
20180213, 18:25  #2  
Serpentine Vermin Jar
Jul 2014
7^{2}·67 Posts 
Quote:
In fact, it looks like all of them except M77897749 already are assigned to someone, and all within a day of when they were submitted by you. That other one is actually already doublechecked and verified (your result was fine apparently). 

20180213, 19:24  #3 
Aug 2012
Mass., USA
2·3·53 Posts 
I also just got a suspect result for an exponent in the same range (77911433). I had messages about roundoff error > 0.4 throughout the test. This makes me think it may be an issue with the FFT size being used on LL tests in this range. My exponent has also already been reassigned.

20180213, 20:47  #4 
"Victor de Hollander"
Aug 2011
the Netherlands
10010011000_{2} Posts 
It is at the boundary of the 4096K FFT / 4480K FFT, so that could explain the 0.4 roundoff errors and suspect result status.

20180213, 20:50  #5 
Sep 2003
3^{2}·7·41 Posts 
All of your exponents were already assigned as of a few days ago. Most are already partly completed, and one was successfully double checked.

20180214, 21:56  #6 
Serpentine Vermin Jar
Jul 2014
6323_{8} Posts 
Yup, that. Which is why I'd be interested at some point to analyze bad (or even suspectbutgood) results around the FFT boundaries. Could help narrow down any bands of badness and make the strategic doublechecking a little more focused on the ones most likely to be bad.

20180216, 15:44  #7 
Dec 2002
Amsterdam, Netherlands
2^{2}·19 Posts 
Thanks for the responses! Glad to see there is no structural problem with the machines causing the suspect results.

20180217, 00:06  #8  
Einyen
Dec 2003
Denmark
31×97 Posts 
You can add these values to prime.txt to help near the FFT boundaries..
From undoc.txt: Quote:


Thread Tools  
Similar Threads  
Thread  Thread Starter  Forum  Replies  Last Post 
Suspect results  bgbeuning  PrimeNet  7  20170720 16:18 
Suspect result  stebbo  PrimeNet  23  20170603 11:14 
Suspect Software Incompatibility  Dionysus  Software  3  20160207 13:49 
Two very suspect results  tha  Data  6  20150522 16:46 
suspect LL assigned again to me  rudi_m  PrimeNet  10  20090212 09:56 