20200313, 08:36  #452 
"Dave"
Sep 2005
UK
2^{3}·347 Posts 
I have had a request from kuratkull to remove k=193 from this drive so that they can search it as an individual. If there have been no objections by this time next week, I will accede to this request. There will still be plenty of k's left in the drive!

20200313, 09:41  #453 
Mar 2007
Estonia
149 Posts 
I have a reservation for k=195, which is the highest nash weight k<300 (nash 4106). I would also very much like to reserve k=193 (nash 760), since they are neighboring k's on relatively opposite edges of the weight spectrum. I am considering running both of those exclusively for the forseeable future and running them high. Thank you for your consideration.
Last fiddled with by kuratkull on 20200313 at 09:42 Reason: typo 
20200313, 16:20  #454  
"Curtis"
Feb 2005
Riverside, CA
1010101110011_{2} Posts 
Quote:


20200313, 16:50  #455 
Mar 2007
Estonia
225_{8} Posts 
Thanks for the offer. Sure i'll take it. A fine little group with variable nash weights to keep me busy for a while. I currently churn through 40n/h or 970n/24h at n=3M, the lower weight k's might get a nice little bump from this.

20200320, 07:50  #456 
"Dave"
Sep 2005
UK
5330_{8} Posts 
I have not received any objections so I have removed k=193 from the drive and it is now reserved by kuratkull. The first message in the thread has been amended accordingly.

20210320, 21:16  #457 
May 2007
Kansas; USA
11,383 Posts 
The sieve file attached to the first post here is missing the 2nd batch of k's. That is k=131, 133, 137, 139, 141, 143, 145, 161, 177, 181, and 187 are not included in the file.
Is this intentional? Am I missing something? I see that k=187 had a prime in the n=2.170M2.180M range. So perhaps the k's have not been missing for long. Is some sort of doublecheck needed for ranges higher than that? 
20210321, 09:30  #458 
"Dave"
Sep 2005
UK
2^{3}·347 Posts 
It wasn't intentional. I have doublechecked the sieve files that I used in 2019 and the extra k's were included. I have attached a corrected file for 20022300, produced from these sieve files. I use linux to produce the files as windows doesn't expand wildcards in the shell, and I appear to have deleted my WSL partition, so I'll produce the full file in the next couple of days. Note that unconnected did their testing before I uploaded the incorrect sieve file.
Last fiddled with by amphoria on 20210321 at 09:40 
20210321, 12:10  #459 
"Dave"
Sep 2005
UK
2^{3}×347 Posts 
I have now attached the full file from 2202 to 3000 with all k's to the first post.
Thanks Gary for spotting and alerting me to the error. 
20210507, 23:03  #460 
May 2007
Kansas; USA
10110001110111_{2} Posts 
The 2nd post in this thread here needs to have the most recent 3 primes added to it:
117*2^21176001 185*2^21279661 187*2^21726931 This makes a total of 47 primes for the drive...21 out of 30 k's now have a prime. Curtis: Done. Last fiddled with by VBCurtis on 20210508 at 02:33 
20211120, 19:25  #461 
Feb 2003
2^{7}·3·5 Posts 
Taking 22022300.

20220410, 09:08  #462 
Feb 2003
2^{7}×3×5 Posts 
22022300 complete, 2 primes found (137*2^22443981 and 185*2^22649061)

Thread Tools  
Similar Threads  
Thread  Thread Starter  Forum  Replies  Last Post 
The Third Megabit Drive  pinhodecarlos  Riesel Prime Search  140  20220309 23:04 
The First Megabit Drive  Kosmaj  Riesel Prime Search  373  20201112 15:48 
RPS 11th Drive: Search for more megabit primes  Kosmaj  Riesel Prime Search  186  20141204 14:03 
Any interest in yet another submegabit drive?  Kosmaj  Riesel Prime Search  20  20111117 04:10 
The 3rd RPS Drive: lowweight Ks for megabit prime  lsoule  Riesel Prime Search  140  20090302 15:01 