NFS@Home needs some crunch!

[pinhodecarlos]

Last 16e Lattice Sieve application wu received is at ~q=837M.
Last 16e Lattice Sieve V5 application wu received is at ~q=991M (second chunk restarted at 950M going to 1,000M: meaning going backwards from 1,000M until meet 16e in the middle).
Last 16e Lattice Sieve V5 application already sent all wu's from 1,000M to 1,400M (first chunk).

Overall Q range sieve of 2,1037- started at 20M to 1,400M.

Q range situation is this:
20M-837M (sent through 16e application, remaining wu's close to be done)
837M-950M (unsent)
950M-991M (sent, remaining wu's close to be done)
991M-1000M (unsent, will be sent through 16e V5 application)
1000M-1400M (sent through 16e V5 application, remaining wu's close to be done)

 

[pinhodecarlos]

Last 16e Lattice Sieve application wu received is at ~q=849M.
Last 16e Lattice Sieve V5 application wu received is at ~q=932M (third chunk restarted at 30M going to 950M: meaning going backwards from 1,000M until meet 16e in the middle).
Last 16e Lattice Sieve V5 application already sent all wu's from 950M to 1,400M.

Overall Q range sieve of 2,1037- started at 20M to 1,400M.

Q range situation is this:
20M-849M (sent through 16e application, remaining wu's close to be done)
849M-930M (unsent)
930M-932M (sent, remaining wu's close to be done)
932M-950M (unsent)
950M-1400M (sent through 16e V5 application, remaining wu's close to be done)

Lot's of aborted wu's being done on the range below 800M.

If you are only running lasieve5f application please consider also checking lasievef application. Linux users will run both, windows users only lasievef.
NFS@Home is hitting a moment where the two q regions sieved separately by 16e and 16 V5 are going to collide so it is better for linux users to check both applications. I already did and also because let's a lot of aborted wu's below 800M to be done. So I am going to run a mix of the two.

 

[pinhodecarlos]

Last 16e Lattice Sieve application wu received is at ~q=921M.
16e Lattice Sieve V5 application already sent all wu's from 930M to 1,400M.

Overall Q range sieve of 2,1037- started at 20M to 1,400M.

Q range situation is this:
20M-921M (sent through 16e application, remaining wu's close to be done)
921M-930M (unsent through 16e application)
930M-1400M (sent through 16e V5 application, remaining wu's close to be done)

16e V5 application started another number (2,1049+) from q=1000M because all wu's for 2,1037- have been distributed. Only missing the left overs wu's. Also I only gave order to my CPU to do the 16e Lattice Sieve wu's instead of both 16 and 16e V5 applications respectively.

In conclusion, 2,1037- will be completely sieved by the end of the year.

Carlos Pinho

 

[pinhodecarlos]

Status of 2,1037-:

20948 wu's left to be crunched by applications 16e and 16 e V5 to finally close the 2,1037- sieve.

Status of 2,1049+:

Last 16e Lattice Sieve application wu received is at ~q=23M (goal to 1000M)
Last 16e Lattice Sieve V5 application wu received is at ~q=1046M (started at 1000M, goal to unknown, then backwards from 1000M until meet 16e in the middle)

 

[pinhodecarlos]

Soon I'll post the status of 2,1037-. Post-processing phase started.

About 2,1049+ NFS@Home sieve:

Last 16e Lattice Sieve application wu received is at ~q=129M (goal to 1000M)
Last 16e Lattice Sieve V5 application wu received is at ~q=1095M (goal to unknown, then backwards from 1000M until meet 16e in the middle)

From now on I'll update weekly.

Carlos