2,1037- sieve

[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 user will run both, windows users only lasievef.

Carlos Pinho

[Mumps]

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 user will run both, windows users only lasievef.

Carlos Pinho

Just curious, did we actually finish the 11,301- Sieving during these challenges? I see what looks like the number listed as Sieving, but Detailed status indicates it's moved to Post Processing.

Also, 2,1037- doesn't match up to anything I can find on the Detailed status pages for sieve_d or sieve_e. Do they not show all the numbers in the Detailed status pages?

EDIT: Yeah, there it is. 5 days ago in the Project News. Which I don't remember seeing in our RSS feed here...

[pinhodecarlos]

Just curious, did we actually finish the 11,301- Sieving during these challenges? I see what looks like the number listed as Sieving, but Detailed status indicates it's moved to Post Processing.

Also, 2,1037- doesn't match up to anything I can find on the Detailed status pages for sieve_d or sieve_e. Do they not show all the numbers in the Detailed status pages?

EDIT: Yeah, there it is. 5 days ago in the Project News. Which I don't remember seeing in our RSS feed here...

Post-processing of 11,301+ was started before the challenges 1st of December, check attach with log file. Application used was lasievee (44 points per wu, less than 1GB necessary).
11,301- sieve was ended during the challenges. Currently being post-processed by M. Vang on a core i7 with 16 GB of memory. Relation file zipped is 19 GB. Last wu's gathered entered it at 22nd of December.

For integers being sieved by applications lasievef and lasieve5f it is very difficult to estimate how much wu's are necessary so there's no progress or detailed page as are for applications lasieved and lasievee. Here we are working on advancing the state of the art of factoring. As I said before, more wu's for 2,1037- can be necessary to generate if a matrix, for the linear algebra phase, is not built.

Carlos Pinho

S11p301.zip

[pinhodecarlos]

Last 16e Lattice Sieve application wu received is at ~q=910M.
Last 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-910M (sent through 16e application, remaining wu's close to be done)
910M-930M (unsent throgh 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.

Carlos Pinho

[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.
After next phase (post-processing) finishes by using the 512 core cluster, Greg usually writes a simple 2-3 pages article about the factorization with final figures. Hope I can give you guys a little surprise. Thank you all for this month of full crunching.

Carlos Pinho

[pinhodecarlos]

This is the number, 31376, the number of wu's still left to be done on 2,1037- sieving. This number represents the aborted ones, the left ones, etc.
Let's point to 7-8 days to fully complete the 2,1037- sieve due to the increase of the wu's deadline from 4 days to 7 days.

Carlos

[pinhodecarlos]

It's down to 20948 wu's left (16e+16e V5).

[STE\/E]

the S2m1037 are the ones Greg wants run ???

[pinhodecarlos]

the S2m1037 are the ones Greg wants run ???

Yes. You might already have a few ones in your queue. I also had a few, didn't abort them, only the S2p1047 ones.

[STE\/E]

Yes. You might already have a few ones in your queue. I also had a few, didn't abort them, only the S2p1047 ones.

Yes I see some on at least 1 Box, will check them all ...