SB2-
Have you considered using sr2sieve to sieve all these at once, instead of sequentially sieving each individually? I imagine you could sieve much more effiiciently, to 2 or 3T, by running a batch of 10 or 12 at once.

I am sieving just 6 k values from 600k to 1.2M, and at 10T (180k candidates in sieve) I'm still removing candidates faster than 1 per 20 min. These low-weight numbers are vastly less dense, but still would benefit from a deeper sieve.

If you like, I can build the sr2data.txt for use from the zip file you uploaded already for those 10, and email it to you.

I'll update your reservations on the low-weight stats page later this week.
-curtis

TBH, I have been just using what I know, NewPGen .... I suppose I could learn to use sr2sieve. Does it have the ability to split the work across numerous machines?

[QUOTE=VBCurtis;100737]SB2-
Have you considered using sr2sieve to sieve all these at once, instead of sequentially sieving each individually? I imagine you could sieve much more effiiciently, to 2 or 3T, by running a batch of 10 or 12 at once.

I am sieving just 6 k values from 600k to 1.2M, and at 10T (180k candidates in sieve) I'm still removing candidates faster than 1 per 20 min. These low-weight numbers are vastly less dense, but still would benefit from a deeper sieve.

If you like, I can build the sr2data.txt for use from the zip file you uploaded already for those 10, and email it to you.

I'll update your reservations on the low-weight stats page later this week.
-curtis[/QUOTE]

If you will send the file with instructions I will give it a shot.

These instructions are scattered around on this forum, and it doesn't hurt to have them in one more post:

Find geoff's thread about new sieving software, and a link to his download site. if you use the first link, you'll have to go up a few levels to get to the sr2sieve and/or sr1sieve folders.

unfortunately, only srsieve can create a new sieve, so you might wish to continue to use NewPGen for that-- I did for a while. Once the sieve is at 1G, save the file.

When you have a batch of files at 1G, use srfile (see helpfile for it, in the srsieve folder) to merge the files into a single file. command format is "srfile -a name1.txt name2.txt (etc)". This will output a single file in ABCD format, ready for sr2sieve. The -a switch controls the save format as ABCD, which is sr2's preferred format (also very small compared to npg format).

sr2sieve sieves over a range of p, without regard to the marker in the sieve file. you can easily split work among machines by telling each machine to sieve a different range-- 1G to 500G on CPU1, 500G to 1T on CPU2, etc. Merging factor files is easy, done rieselsieve style:
Each sieving run will output a factors-found file, named "factorsxxx", where xxx is the starting p-value in billions. Sr2sieve does not alter the input file in any way-- your sieve is unchanged until you remove the factors with srfile. I use "srfile -h" for the list of commands at this point, but the gist is to use the -k switch to remove factors from the sieve file.

Finally, srfile -g splits the combined many-k sieve into individual sieve files, which are saved in NewPGen format ready for LLR testing.

I rambled.. if you have questions, or just want me to build the sr2data file for you the first time, I'm happy to. Email is this name at gmail, or PM me.
-Curtis

Quick Update

Thanks to VBCurtis' help with creating the sieve file, and detailed instructions for Dummies <--me!, these 20 K's are now being sieved from 1 < n < 1M p=2T, ETA to completion 7 days.


236377
249127
279731
284579
294907
313979
323563
362737
370421
384029
412843
469933
700057
1002401
1005449
1006469
1034503
1210421
10013593
10108837


In hopes of not duplicating work, next batch of 20 K's that I have started sieving listed below. This batch will be sieved from 1 < n < 2M.

332159
434729
441907
451049
464353
464909
465187
473279
492787
643843
648433
685183
686711
700477
780427
783073
790841
844559
10284899
37616317


If there are conflicts with work that someone has aready started on one of these K values please let me know so I can stop it and move to another. I realize it is hard to keep up with what is being worked on with so few updates. So from now on I will try to update my progress and ranges being worked on at least once a week.

Status update: k=56251213 now at 1.74M and still going

k=36231101 --->469002<--- LLR Tested from 300k to 1M - releasing

k=278713 tested to n = 1M (no new primes) released

Is k=22183 still available?
If yes, I'm reserving it from 30k

nuggetprime

As far as I can tell, 22183 is open for work. I suggest you sieve it to n=1M, as low-weight numbers have few candidates to test. Something on the order of 9-10 weeks to LLR all the way to 1M on a modern Pentium 4 is reasonable, after 2-3 days of sieving. LLR testing to n=500k should take around 2 weeks.
-Curtis

K=3817 LLR tested to 1M, continuing to 2M