misc. k<300 statuses and primes

[gd_barnes]

Originally Posted by henryzz

why not add to that completing the individual reservations drive

That's too much work to complete all of it to n=1M. 800K-1M is much more work than 600K-800K.

Also, notice that I said k=300-1001 to n=800K. That means that the individual-k drive would also have to be at n=800K. But with so many k's being possibly individually reserved, that may be a stretch. The nature of the drive is to allow individuals to progress more at their own pace. Notice that I state in the 1st post of the drive to plan on completing reservations within ~6 months. This is probably more realistic:

k=400-1001 to n=800K and
[ 50-75% of k's in individual drive to n=800K -or-
25-40% of k's in individual drive to n=1M ]


Gary

[henryzz]

it seems like we are getting through it so fast
now i count i see 9/50 are complete and 2 reserved ks are above 900k
there are also another 11 ranges reserved which are below 900k

[gd_barnes]

Originally Posted by henryzz

it seems like we are getting through it so fast
now i count i see 9/50 are complete and 2 reserved ks are above 900k
there are also another 11 ranges reserved which are below 900k

Looks can be decieving! :-)

Ian, with resources clearly more than myself (or faster than myself, lol), has reserved almost all very low-weight k's and therefore easily completed them. For instance the highest-weight k=315 has something like 5 times as many pairs as many of the low-weight k's.

We may run a mini-drive on 5 high-weight k's starting in Jan. to help get some of them up past n=700K or 800K.


Gary

[gd_barnes]

k=147 is now at n=770K; nothing to report.

It's now on 2 cores so is moving along faster now.

[gd_barnes]

k=147 is now at n=797K; nothing to report

k=289 double-check is now at n=760K; one prime was confirmed:

289*2^728205-1

Each running on 2 cores.

I'm suspending these efforts for ~2 weeks to put additional cores on the sieving drive.


Gary

[gd_barnes]

To report the ranges as nice and round numbers:

k=147 is now at n=800K

k=289 is now at n=765K

Nothing to report.

Both running on 2 cores each.

[gd_barnes]

I just now moved all machines to port 8000 so I'll post a couple of statuses now:

k=289 just completed to n=800K and unreserved.

k=147 is at n=820K; continuing to n=1M after the rally.

Nothing to report.

I assume that no one will pick up k=289 in the near future since it is likely a double check to the next known prime at n>1M. But if anyone does, I have a sieve file to P=26T for n=800K-1M.


Gary

[gd_barnes]

k=147 is now at n=857K still running on 2 cores to n=1M. No primes since n=600K.

I'll likely pause it at n=~900K to do some sieving on another effort.

On another note: Karsten, please reflect k=31 as fully searched to n=1.3M with no gaps. As reported in the double-check drive, it has now been fully double-checked up to n=500K. You can also take my name off of it since Steven at RPS has it reserved for n>1.3M.


Thanks,
Gary

[gd_barnes]

k=147 was stopped at n=874K about a week ago to start on the k=1003-2000/n=500K-1M sieving effort. No primes found since n=600K.

It will start back up in ~2 months after the sieving is done.

[gd_barnes]

k=147 has started back up. It is currently at n=878K. Continuing on to n=1M on 2 cores.

[gd_barnes]

k=147 is now at n=900K; nothing to report; continuing