![]() |
|
|
#1 |
|
Mar 2006
Germany
2×1,531 Posts |
R. De Troia found this:
31*2^406105-1 although this k was tested to n=1.3M !?!? I marked the range with a questionmark and with a '(...)' for the prime n's. Last fiddled with by kar_bon on 2008-12-02 at 08:55 |
|
|
|
|
|
#2 |
|
Nov 2003
70468 Posts |
k=31 was reported as tested to 500k by Steven (L1), and I think another Steven (L330) started from there. I'm not aware of L1 missing any primes, or reporting false ones, but at the time when he did his tests there were some buggy versions of LLR floating around.
|
|
|
|
|
|
#3 |
|
Mar 2006
Columbus, OH
7×11 Posts |
I did start this k=31 from 500k & up.
-Steven |
|
|
|
|
|
#4 |
|
Nov 2003
2×1,811 Posts |
L637 reported one more k=31 prime:
31*2^421129-1 I wrote to Steven, and asked him whether he has any idea how he missed them. I remember Jean said that the bug in early LLR versions didn't affect small Ks, but he never said what does "small" exactly mean. Maybe k=31 was not small enough? |
|
|
|
|
|
#5 |
|
"Gary"
May 2007
Overland Park, KS
110000000001112 Posts |
NPLB has double-checked all k<=25 for n=100K-260K. The next k<300 range to double-check in that drive is k=27-31 for n=100K-260K. I'll run that range after our 1st drive is done in ~2 weeks. At least we'll then know that k=31 is good to n=260K since n<100K was previously double-checked a long time ago.
Personally, I don't think the first Steven (L1) tested it up to n=500K. The chances of even "somewhat" buggy software missing 2 primes in a small range like that are very remote. I suspect he mixed up his k's or ranges when he reported them. Gary Last fiddled with by gd_barnes on 2008-12-10 at 09:41 |
|
|
|
|
|
#6 |
|
"Curtis"
Feb 2005
Riverside, CA
2·2,927 Posts |
Too bad the new Steven (my student) didn't start at 400k.. He would have been excited to find two primes so quickly!
-Curtis |
|
|
|
|
|
#7 |
|
Nov 2003
362210 Posts |
Yet another one found by Steven, who is double-checking k=29:
29*2^347896-1 I'm afraid the problem was one of first, early verions of LLR, which was known to have bugs. The relevant link is here. That's LLR time-stamped March 22, 2004. It was not corrected before September 2004. Last fiddled with by Kosmaj on 2009-02-05 at 08:40 |
|
|
|
|
|
#8 |
|
Apr 2004
2738 Posts |
I also found 27*2^282700-1 last month. I am currently checkinh, 5, 7, 9, 11, 13, 15, 19, 21 ,23, 25, 27, 29 from 260k to 500k.
Steven Harvey |
|
|
|
|
|
#9 |
|
Apr 2004
11×17 Posts |
If anyone wants to assist, I'd be happy to send you a presieved range for any of these k, 5,7,9,11, 13, 15, 19, 21, 23, 25, 27, 29. I am currently up to at least 280k on all, & higher on 27 and 29.
Steven Harvey |
|
|
|
|
|
#10 |
|
May 2005
65C16 Posts |
k=25 tested from n=400000 using LLR version 3.62 (AFAIR). If someone really wants to perform doublecheck on this one, then I can provide result file for comparison
|
|
|
|
|
|
#11 |
|
Apr 2004
2738 Posts |
I would like the 25 from 400k result file for comparison purposes.
Please send it to me or post it here, zipped preferably. When did you do the check?? Thanks! |
|
|
|
![]() |
| Thread Tools | |
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| missed factor? | tha | Data | 79 | 2021-11-19 15:55 |
| Factor missed by TF | bcp19 | PrimeNet | 15 | 2015-08-10 11:57 |
| More missed factors | lycorn | Data | 76 | 2015-04-23 06:07 |
| P-1 Missed factor | tha | Data | 7 | 2014-04-30 20:54 |
| Missed factors | TheMawn | Information & Answers | 7 | 2014-01-10 10:23 |