[QUOTE=gd_barnes;470016]For S256, the sieve depth is the same as what you previously posted. Why were there more factors found? Was the previous file incorrect?[/QUOTE]

No, the file and factors are correct.
There is an delay_bound which tolds the server to generate a file with all found factors after some time without new results returning from users. That bound was 24h. If no new results are coming back within 24h the server will generate an factors_found file.
Now we are using 72h.

Sieve depth is the same.

[QUOTE=MisterBitcoin;470017]No, the file and factors are correct.
There is an delay_bound which tolds the server to generate a file with all found factors after some time without new results returning from users. That bound was 24h. If no new results are coming back within 24h the server will generate an factors_found file.
Now we are using 72h.

Sieve depth is the same.[/QUOTE]

That sounds like a bad way to determine if all factor ranges are complete. In what other manner are you checking to see if all factor ranges are complete? In other words, how can you guarantee that there will not be some more factors that might be returned a week from now?

The BOINC software is checking if all results from the WU´s are comming back or not.

The WU-Generator generates ~10.000 WUs with each 2 Tasks/WU. The software checks if all Tasks are comming back in time, if not new tasks will be generated and sended.

It´s all automatic, like srbase. The software behind it is the same, it´s only speciefied.

R1019 has been sieved up to p=1e15. Factors checked, file attached.

[QUOTE=MisterBitcoin;470107]R1019 has been sieved up to p=1e15. Factors checked, file attached.[/QUOTE]

Nice sieve depth! :smile:

[QUOTE=MisterBitcoin;470096]The BOINC software is checking if all results from the WU´s are comming back or not.

The WU-Generator generates ~10.000 WUs with each 2 Tasks/WU. The software checks if all Tasks are comming back in time, if not new tasks will be generated and sended.

It´s all automatic, like srbase. The software behind it is the same, it´s only speciefied.[/QUOTE]

OK but I am still confused on how you posted a file and then found that additional factors had been found so that you had to post another file.

In the future, I will assume that you will only post [B]fully[/B] sieved files when you know that all factors have been reported.

So, here he go.
Sieve app passed 8 CPU years!

4 sieve files attached, P-Values below.

R103: 300e12
R368: 500e12
R1024: 1e15
R1029: 1e15

I´m now running stuff for Pepi and Masser. Curtis, if you need deeper sieve files feel free to PM me.

S497 reached p = 40T, sieve file is attached below.

Some information on expected primes for this file:
[CODE]expected # of primes: 0.13649300098661327
odds of at least one prime: 12.758757373549578%
(or, in other words) 1 in 7.837753871494719 chance of at least one prime
on average, 1 in 36338.85960560321 candidates should be prime[/CODE]

Reserving S61 for sieving, n = 100k to n = 250k.

Hi!
If i want to reserve and sieve S476, which settings in sr1sieve i must set and how long i must sieve?
Pre-thanks
P.S
I already sieved up to 1e9 in srsieve.

Reserving all single-k bases on Sierpinski-Side without sieve file. That should be ~48 bases.
We need ~1,5 days/sequence. I´m now preparing the bases that are suggested by Gary.

Sorry vasyannyasha, there is no need to sieve S476. Please check Riesel side for an single-k base without sieve file.

@Gary Sorry that this goes so fast. Since I´m on night shift I haven´t enough time to post an reservation on the following bases:

R968 from n=250K-500K; P=250e12
R888 from n=400K-1M; P=750e12
R883 from n=250K-500K; P=250e12
R995 from n=500K-1M; P=500e12

All 4 attached.

Reserving S290 from n=100K-250K. k=73 has only ~1800 tests on p=5e9.