Team sieve #21: c162 from 4788:2602

[jrk]

Originally Posted by bchaffin

Finished the c147, and added about 10 more terms -- happily, ecm found 45- and 48-digit factors. Now at term 2602, still with 2^4, and a c162. I've run 3400 curves at 11M so far. I'll leave it running for a few days, but if ecm doesn't come through this will probably be the end of my solo drive.

Time for another team job. After a lot of heavy lifting from bchaffin, 4788 has stalled on a c162.

A lot of sieving will be done by RSALS, but if you have some spare cycles, every little bit helps...

Originally Posted by jrk

In case it becomes a GNFS job, here is a poly for the c162:

n: 201662644625726223965504252321039229795541434802496056546534987125943330407091389007249091194783132977342010346522074086728121107031532400663175295605381304978591
# norm 1.037974e-15 alpha -8.491231 e 1.135e-12 rroots 3
skew: 11670747.10
c0: -58098198798717019126014055711399549989735
c1: -11019918536209930229435557980670531
c2:  2131349269924959161803770145
c3:  100289713633328138483
c4: -10690842992178
c5:  551880
Y0: -12958548897691078082274705009044
Y1:  1627296609596924339
rlim: 45000000
alim: 45000000
lpbr: 29
lpba: 30
mfbr: 58
mfba: 60
rlambda: 2.5
alambda: 2.5

Sieve specialq on algebraic side from 20M to 90M with siever 14e. Aim for about 84M raw relations.

Post-processing will be done by Batalov.
28 Dec 2010 Post-processing started, ETA 29 Dec 2010
30 Dec 2010 Post-processing complete! c162 = p63 * p100

Reservations:

20M - 50M   RSALS
50M - 80M   RSALS
80M - 90M   RSALS
90M - 95M   RSALS
95M -100M   RSALS

Relations so far: 78M

[debrouxl]

The poly posted by jrk yields ~1.4 relation per q value over a range of 1000 q values starting at (r&a)lim/2.
For a 30-bit large primes task, on average, RSALS clients can sieve the bulk of a range of 30-40M q values, split in WUs of 10K q values, in 3-4 days.

[schickel]

Originally Posted by debrouxl

The poly posted by jrk yields ~1.4 relation per q value over a range of 1000 q values starting at (r&a)lim/2.
For a 30-bit large primes task, on average, RSALS clients can sieve the bulk of a range of 30-40M q values, split in WUs of 10K q values, in 3-4 days.

Will you also be able to handle the post-processing?

[debrouxl]

schickel: RSALS relies on external contributors to do the post-processing. Is there somebody interested in Aliquot sequences willing to do the job ?

AFAICS, the best poly posted here so far was by jrk, indeed.

[Batalov]

Ok, count me in for finishing.

[debrouxl]

Reserving 50M-80M for the RSALS grid
At the current rate of crunching, I'll start "C162_4788_2602" by Wednesday.

[Batalov]

Pls send me a PM when needed, because I may not notice/follow specific threads. (But I'll receive a PM for sure.)

[debrouxl]

I've just added "C162_4788_2602" to the RSALS work generation infrastructure. For now, WUs will be generated from q=50M to 80M.

[debrouxl]

At the time of this writing, nearly 5/6 of the 50M-80M range have been distributed to clients, with more than 1/5 of the corresponding results returned, yielding ~6M raw relations.
I'm therefore expanding the RSALS reservation to 80M-90M

[schickel]

Originally Posted by debrouxl

Reserving 50M-80M for the RSALS grid
At the current rate of crunching, I'll start "C162_4788_2602" by Wednesday.

Originally Posted by debrouxl

I've just added "C162_4788_2602" to the RSALS work generation infrastructure. For now, WUs will be generated from q=50M to 80M.

Originally Posted by debrouxl

At the time of this writing, nearly 5/6 of the 50M-80M range have been distributed to clients, with more than 1/5 of the corresponding results returned, yielding ~6M raw relations.
I'm therefore expanding the RSALS reservation to 80M-90M

So, do we need a thread for this job to co-ordinate other contributors, or will RSALS be able to do it all?

[10metreh]

Originally Posted by schickel

So, do we need a thread for this job to co-ordinate other contributors, or will RSALS be able to do it all?

20M-90M will probably be enough, so if RSALS are willing to do it all, that's fine.