[QUOTE=MisterBitcoin;469679]@Gary I didn´t reserved R102. :)[/QUOTE]

Yes you did:
[URL]http://mersenneforum.org/showpost.php?p=467504&postcount=344[/URL]

Would you like to release it?

[QUOTE=gd_barnes;469683]Yes you did:
[URL]http://mersenneforum.org/showpost.php?p=467504&postcount=344[/URL]

Would you like to release it?[/QUOTE]

Ups. :smile:
R102 is sieved up to 30e12, file attached.

I´d like to have k´s remain for

R431
R598

Instead of continuing to sieve and test very difficult bases with a lot of k's remaining or that have already been tested to a deep depth, I would like to suggest this for a project direction for the time being:

Sieve and test the bases with the lowest difficulty on this list:
[URL]http://www.noprimeleftbehind.net/crus/vstats_new/crus-unproven.htm[/URL]

Just click on the "relative difficulty" column to sort them ascending by difficulty. Specifically I suggest sieving the bases with difficulty < 10000. There are 4 Riesel and 7 Sierp bases. None of them have more than 4 k's remaining.

For the bases tested to n=100K, sieve n=100K-250K. For the bases tested to n=200K, sieve n=200K-500K. S263 is the only base that has already been sieved. It has already been sieved for n=350K-1M to P=50T. You could just sieve that one further.

These bases will give us the best "bang for our buck" in that they can be tested fairly quickly and there may be several proofs of them.

[QUOTE=gd_barnes;469719]Instead of continuing to sieve and test very difficult bases with a lot of k's remaining or that have already been tested to a deep depth, I would like to suggest this for a project direction for the time being:

Sieve and test the bases with the lowest difficulty on this list:
[URL]http://www.noprimeleftbehind.net/crus/vstats_new/crus-unproven.htm[/URL]

Just click on the "relative difficulty" column to sort them ascending by difficulty. Specifically I suggest sieving the bases with difficulty < 10000. There are 4 Riesel and 7 Sierp bases. None of them have more than 4 k's remaining.

For the bases tested to n=100K, sieve n=100K-250K. For the bases tested to n=200K, sieve n=200K-500K. S263 is the only base that has already been sieved. It has already been sieved for n=350K-1M to P=50T. You could just sieve that one further.

These bases will give us the best "bang for our buck" in that they can be tested fairly quickly and there may be several proofs of them.[/QUOTE]

I´ll follow that route. Anyway rebirther requested to make some files for n=25K-100K.
For now the sequences I reserved are running. If that is finished I´ll load R6 for Masser.

How did you generate the Difficulty?

[QUOTE=MisterBitcoin;469721]How did you generate the Difficulty?[/QUOTE]

Mark (Rogue) came up with it. It's based on the number of tests remaining for an n=25K range on a sieve to P=1T multiplied by the size of a test at the current test limit.

Reb, we already have plenty of bases already tested to n=100K now. All bases with < 200 k's remaining have now been tested to n=100K or are reserved by others and are close. How about we use more resources to test bases with few k's remaining (perhaps < 10 k's remaining) that are only tested to n=100K or 200K. Let's get a lot of those tested to the n=250K to 500K range.

Bases with > 200 k's remaining at n=25K will not be proven in our lifetimes.

[QUOTE=gd_barnes;469746]Mark (Rogue) came up with it. It's based on the number of tests remaining for an n=25K range on a sieve to P=1T multiplied by the size of a test at the current test limit.

Reb, we already have plenty of bases already tested to n=100K now. All bases with < 200 k's remaining have now been tested to n=100K or are reserved by others and are close. How about we use more resources to test bases with few k's remaining (perhaps < 10 k's remaining) that are only tested to n=100K or 200K. Let's get a lot of those tested to the n=250K to 500K range.

Bases with > 200 k's remaining at n=25K will not be proven in our lifetimes.[/QUOTE]

@Gary: Add them to the recommended list.

Error in sieve file for R1029
 

There is an tiny error in the sieve file for R1029.

[CODE]26 1602635
26 1602651
26 16 2653
26 1602705[/CODE]

Line: 17126

I´ve fixed it for yoyo@home so the sieve should run without probs.

Reserving S497 for sieving, n = 200k to n = 500k.

There are a few more factors found from S256. There is an updated version attached.
Notice: We are using version 1.4.1 sr1sieve for Win, so far there no false factors found.

R800 has been sieved up to P=500e12, factors checked. Sieve file attached.

[QUOTE=MisterBitcoin;470005]There are a few more factors found from S256. There is an updated version attached.
Notice: We are using version 1.4.1 sr1sieve for Win, so far there no false factors found.

R800 has been sieved up to P=500e12, factors checked. Sieve file attached.[/QUOTE]

For S256, the sieve depth is the same as what you previously posted. Why were there more factors found? Was the previous file incorrect?