Individual-k reservations k=300-400 n=1M-3M

[Mini-Geek]

k=349 and 353 are at n=1.2M.

[kar_bon]

I've updated the k=300-2000 page on rieselprime.de with the data from here.

I also included a new page for the Mini Drive #4 (315, 321, 327, 333, 339, 345) and updated the Individual-page.

[unconnected]

k=311 done [1600k-2000k]
k=303 done [1000k-1500k]
k=303 ~75% done [1500k-2000k]

No primes, results are sent via email.
I would like to reserve k=301 and k=305.

[gd_barnes]

Originally Posted by unconnected

I would like to reserve k=301 and k=305.

I have now Emailed you the files for k=301 and 305. Good luck!

[unconnected]

Thank you. Hope I'll find prime sooner or later.

[Cruelty]

k=337 tested till n=2.56M.

[Mini-Geek]

k=349 and 353 are at n=1.3M.

[kar_bon]

@Gary, Max:

I've checked the results for the MiniDrive #4 (6 k's from 1M to 2M).
I've noticed, that the pair 315*2^1000000-1 was done twice!

This pair was tested with the MiniDrive #1 (same 6 k's from 600k-1M).
The resultfile "results_20090909_0001_GB_nplb_8000.txt" contains this pair.

In MiniDrive #4 it was tested again, because the n-range was/is xxx000-xxx000 instead of xxx001-xxx000.
So resultfile "results_20100519_0001_GB_nplb_3500.txt" contains this pair, too.

Please be sure to upload the range from 001-000 into the server.
Have a look at the sievefile you sent me for k=377: it contains the n-values for n=1000000 and n=2000000!

PS:
There're 3 k-values with n=1000000 in that sievefile: k=315, 377 and 383.

[gd_barnes]

Originally Posted by kar_bon

@Gary, Max:

I've checked the results for the MiniDrive #4 (6 k's from 1M to 2M).
I've noticed, that the pair 315*2^1000000-1 was done twice!

This pair was tested with the MiniDrive #1 (same 6 k's from 600k-1M).
The resultfile "results_20090909_0001_GB_nplb_8000.txt" contains this pair.

In MiniDrive #4 it was tested again, because the n-range was/is xxx000-xxx000 instead of xxx001-xxx000.
So resultfile "results_20100519_0001_GB_nplb_3500.txt" contains this pair, too.

Please be sure to upload the range from 001-000 into the server.
Have a look at the sievefile you sent me for k=377: it contains the n-values for n=1000000 and n=2000000!

PS:
There're 3 k-values with n=1000000 in that sievefile: k=315, 377 and 383.

Karsten,

Is this really a big deal? I do the 1n overlap on all files that I sieve.


Gary

[kar_bon]

Originally Posted by gd_barnes

Karsten,

Is this really a big deal? I do the 1n overlap on all files that I sieve.


Gary

Because it was your demand to all who reserve manual ranges to do the xxx001 to xxx000 range to be sure testing without losing any pair!

Anyway, no problem for me.

[gd_barnes]

Originally Posted by kar_bon

Because it was your demand to all who reserve manual ranges to do the xxx001 to xxx000 range to be sure testing without losing any pair!

Anyway, no problem for me.

??

There are 3 reasons why this does not apply here:

1. Because the 2 individual-k drives are separate drives and sieving efforts. The first individual-k drive ended at n=1M and the new one restarted from n=1M. This will not come up for n>1M.

2. The admins send people ranges with this drive and know to use xxx001 to xxx000 when sending files to people for ranges n>1M.

3. We never said anything about it in the 1st post here because of the above 2 reasons. It's only stated on drives where people are pulling subranges out of larger posted files both here and at CRUS. We only post small beginning files here.


You may remember that you made a similar statement about n=600000 for all of the various k=300 to 1001 drives. The main reason that I asked you if it's a problem for you now is that it will happen again at n=1M for other various drives. If it was creating a problem, I/we could remove all tests for n=1M in the future when we are sieving k=400-1001 for n=1M-2M but the files are so large and difficult to manipulate that's it's my preference to either (1) leave them in there (2) be very specific by sieving n=1000001 to 2000000. I guess it is just easier to sieve with -n 1e6 -N 2e6 rather than -n 1000001 -N 2e6.

As for how to handle them in the database when they are loaded: Make them a doublecheck.


Gary