anybody would have... don't worry about it... it does not have a driver yet

[QUOTE=frmky;265248]I ruined it. It became 2^2 at 2692 and remains so at 2696.[/QUOTE]
E = mc[SUP]2[/SUP] = :poop:, where m=2 and c=7...

Preliminary poly for line 2696:
[code][color=green]# sieve with ggnfs siever 14e on alg side from Q=12M to ??? (TBD)[/color]
# aq4788:2696
n: 8755586957647299753989940018066954131853563140628725006016461530329394193683073655733471708006846371139255974755721298957099259657401475696647916915828783
# norm 5.645726e-15 alpha -8.072274 e 3.033e-12 rroots 5
skew: 5249963.52
c0: -46345271813152906243625561305975391919
c1: 315851147445769179340289495399705
c2: 285281660006640392120520145
c3: -1154498250914466025
c4: -8963811002586
c5: 367080
Y0: -473707895443070147940141714680
Y1: 1276292379120039143
rlim: 24000000
alim: 24000000
lpbr: 29
lpba: 29
mfbr: 58
mfba: 58
rlambda: 2.5
alambda: 2.5
[/code]

ECM found a 48-digit factor overnight for line 2696. Now at 2703 with a c142. It grew a bit with 2^2 * 5, but just lost the 5 in this last step. No 3 or 7 in sight yet, so hope is alive...

[QUOTE=Mini-Geek;264033]I realized I made a rather large mistake in that math: it ignores that 3 can not be a cofactor of a downdriver, since otherwise it would be the 2*3 perfect driver. ... The new and improved script is attached. :smile:
More trivia: there is a [B]5.01% chance of it ending by 163.6 digits,[/B] and a 95.05% chance of it ending by 66.2 digits.[/QUOTE]

(the first line without the downdriver was ~10^165.0; from the time of that posting we only had a ~2.55% chance of breaking by then) Either we were [I]very[/I] unlucky, (i.e. about 1 in 39 such runs would end so soon) or my numbers are [I]very[/I] off. But anyway, with the breaking being 2*7^2*p, I noticed one more thing that made it a little more inaccurate: I didn't take into account that 2*n^2*p can break it, too! I accounted for this by multiplying the probability of each line breaking by [URL="http://www.wolframalpha.com/input/?i=1+%2B+%28sum+1%2Fprime%28k%29^2%2C+k%3D3+to+infinity%29"]1 + (sum 1/prime(k)^2, k=3 to infinity)[/URL] (about 1.091). I was looking around a little for more accurate calculations than mine, and only found the [URL="http://www.mersenneforum.org/showthread.php?t=12682"]Losing Downdriver thread[/URL], which seems to have last settled on numbers very different from mine: 1/420 for 100 digits. I calculate 1.09113630893*3/2/log(10)/100~=1/141. To simply state each, they (mainly Greebley post #6 with modifications for squares by CRGreathouse post #12) say about 1/(4.2*digits) I say 1/(1.4*digits). A factor of 3 different. I think it's because I'm accounting for the fact that the downdriver's cofactor can't have a factor of 2 or 3 by definition.
Does anyone have an automated way to look through many downdrivers and see if my numbers hold up to real test data? Just looking at this one, it'd seem I'm way off, and my memory seems to also say it's lost far easier, but I'd like something far more concrete.

The new script, taking into account the squares, is attached.

[QUOTE=jrk;265283]Preliminary poly for line 2696:[/QUOTE]
It's obsolete now, but in case anyone happens to collect these, here's the best one I found:
[code]# sieve with ggnfs siever 14e on alg side from Q=12M to ??? (TBD)
# aq4788:2696
n: 8755586957647299753989940018066954131853563140628725006016461530329394193683073655733471708006846371139255974755721298957099259657401475696647916915828783
# norm 6.055972e-15 alpha -7.175530 e 3.223e-12 rroots 3
skew: 2748791.27
c0: 22518556851938655674731450005532544565
c1: 49007811576301845607236669717695
c2: 12280205727986637086832355
c3: -20291335212629008203
c4: -848640062100
c5: 765072
Y0: -408993941175622024607029493362
Y1: 1200827227936261913
rlim: 24000000
alim: 24000000
lpbr: 29
lpba: 29
mfbr: 58
mfba: 58
rlambda: 2.5
alambda: 2.5
[/code]

+400 curves @ 8e7 for line 2703

I did the c142 from 2703, and four more terms. Now at 2708 with a c157. Except for one 2^2*5 it continues to decrease...

I've run 1000 @ 1M and 3000 at 10M so far. I'll keep running curves but this one is too big for me to sieve on my own.

I'll start poly selection on line 2708 as usual.

Done:

[CODE]
prp64 factor: 4038843625314075842900554513884322322635236034496696017887771851
prp93 factor: 288180620682225170824303650548350247409615780738733199886385422296800168275435704019909533659
[/CODE]

Sequence still decreasing... I've done 1000 curves at 1e6 on the C153 at iteration 2709.

I've done 3k curves at 10M and 1800 curves at 100M on the C153 of iteration 2709. I'm run with it a while longer and do the nfs.

+960 curves @ B1=8e7

[QUOTE=bsquared;269049]Done:

[CODE]
prp64 factor: 4038843625314075842900554513884322322635236034496696017887771851
prp93 factor: 288180620682225170824303650548350247409615780738733199886385422296800168275435704019909533659
[/CODE]

Sequence still decreasing... I've done 1000 curves at 1e6 on the C153 at iteration 2709.[/QUOTE]At least it's still alive in terms of not getting a driver or an upwardly increasing guide!

[QUOTE=Batalov;265252]E = mc[SUP]2[/SUP] = :poop:, where m=2 and c=7...[/QUOTE]

No need to worry about a 2 · 7^2 ... :cat:

[QUOTE=biwema;269103]No need to worry about a 2 · 7^2 ... :cat:[/QUOTE]

There [I]is[/I] a need to worry - it killed the downdriver.

How much ECM has been done on the c162?

Would have been nice to know that 2709 had been factored. Guess I'll kill that GNFS job.

[QUOTE=bsquared;269722]Would have been nice to know that 2709 had been factored. Guess I'll kill that GNFS job.[/QUOTE]
When I saw the factors posted to factordb, I assumed you were the one that finished it. The smaller factor was a p58 so it was probably done via GNFS.

[QUOTE=jrk;269729]When I saw the factors posted to factordb, I assumed you were the one that finished it. The smaller factor was a p58 so it was probably done via GNFS.[/QUOTE]

I was maybe 80% done, but got scooped by someone. It wasn't my electricity though, so I can't be too upset.

[QUOTE=jrk;269729]When I saw the factors posted to factordb, I assumed you were the one that finished it. The smaller factor was a p58 so it was probably done via GNFS.[/QUOTE][QUOTE=bsquared;269742]I was maybe 80% done, but got scooped by someone. It wasn't my electricity though, so I can't be too upset.[/QUOTE]Interesting....so if it wasn't either of you, who was it?

I'm sure we all appreciate the assist; but, as bsquared said, it would be nice to know ahead of time....

I did 3200@43e6 on the c162 - no factors.

+1920@11e7
How much ECM we need?

+2160@11e7

+200@11e7

3200@43e6 + 4380@11e7 is a bit less than 2t50, should we go further ?

[QUOTE=debrouxl;271613]+200@11e7

3200@43e6 + 4380@11e7 is a bit less than 2t50, should we go further ?[/QUOTE]Would someone like to run a poly search?

[QUOTE=schickel;272377]Would someone like to run a poly search?[/QUOTE]
I posted a poly for this composite earlier in this thread. On August 21.

[QUOTE=jrk;272404]I posted a poly for this composite earlier in this thread. On August 21.[/QUOTE]Oh.....sorry, I missed it (it has been >30 days after all; I probably saw it but forgot it by now.)

Then, as to the question by debrouxl, do we have enough ECM yet?

That's about half as much ECM as we needed, but if people are willing to sieve already then it's probably OK.

[QUOTE=jrk;272404]I posted a poly for this composite earlier in this thread. On August 21.[/QUOTE]I did see it, but it has been so long I didn't remember seeing it in connection with the current line....[QUOTE=jrk;272449]That's about half as much ECM as we needed, but if people are willing to sieve already then it's probably OK.[/QUOTE]I'll start some curves @ 110M, but even with my fastest machine it's only ~100 curves a day......

I have just queued some curves @110M too.

600@11e7, no factor.

[QUOTE=Andi47;272929]600@11e7, no factor.[/QUOTE]+200 curves at 110M.

Sorry, I stopped after a couple of days so I could concentrate on a c144 for one of my sequences....

Hmmm.... ECM anyone? If I do the remaining ~4000 curves @11e7 alone, it will take me at least a month or so.

I think you have already wasted longer on ECM than it will take to do the sieving; it'll be about six thousand hours on a 64-bit Linux system, so two weeks on three hex-cores. My machines are busy or I would do it myself.

[QUOTE=henryzz;275248]I have reached the sqrts without a problem. Reducing the memory speed didn't improve things. Should I be altering the settings for the nb(not certain I have access on my rubbish motherboard)? It is a Q6600 in case you haven't realized.
Fortunately Prime95 stability is what I am worried about not msieve stability.

Factors should hopefully be available when I come back from uni today.[/QUOTE]
I have the factors:
prp58 factor: 6154716799577446885023090856129309198086450129268256055737
prp104 factor: 27073317568454671115447910049600122939037137794629195952679986797162648298087899683780597042901407700459

The filtering and postprocessing log is attached. After the first error cost me the first 25% I stopped and restarted creating a checkpoint 2-3 times a day(~8%). Only the one of the restarts had an error on the second attempt and it had somehow created a checkpoint just before.

[QUOTE=fivemack;275506]No factors after 10000@3e7; another 10000@3e7 is running, but I think it's nearing time to start sieving.[/QUOTE]

That's close to a t50. In addition to these, I've done nearly 2/3 of t55 (4857 curves at 26e7). I agree that it's time to sieve.

Ugh. ABORT!
4788.8_2.log:********** Factor found in step 2: 97638666289321937759157257447922535245262746322381397384147

Is anyone doing ECM on the c152? I'll run some curves at 3e6.

I've just started 8000@3e7

I ran 1000@11e6 with no luck.

A nice little surprise lurking in step 2721...

[QUOTE=frmky;276087]A nice little surprise lurking in step 2721...[/QUOTE]

:w00t: :party::party::party: :banana:

[QUOTE=Andi47;276088]:w00t::party::party::party:[/QUOTE]Yeehaw!!!

Let's hope this sucker lasts a little longer!

[QUOTE=schickel;276089]Yeehaw!!!

Let's hope this sucker lasts a little longer![/QUOTE]

I [URL="http://www.mersenneforum.org/showpost.php?p=265319&postcount=1266"]calculate[/URL] that it has a 50% chance of breaking by ~135 digits. I still have a "gut feeling" that that's far too optimistic and that we'd be lucky for this single run to make it below 150, but I can't see that I'm missing anything else in the math.

[QUOTE=frmky;265248]I ruined it. It became 2^2 at 2692 and remains so at 2696.[/QUOTE]
Greg broke it, Greg fixed it! You da man!

c141 is ready for gnfs (a t50 is done). Anyone? My comp is busy with a c169 for a couple days more.

[QUOTE=Batalov;276281]c141 is ready for gnfs (a t50 is done). Anyone? My comp is busy with a c169 for a couple days more.[/QUOTE]

Done.

[QUOTE=frmky;276286]Done.[/QUOTE]Man, that was quick work!

:bow::bow::bow:

How much ecm had the c144 of iteration 2730?

starting 6 threads ECMing at B1=11e6...

C144 already factored: [URL]http://factordb.com/sequences.php?se=1&eff=2&aq=4788&action=last20&fr=0&to=100[/URL]

Looks like someone already GNFS'd it. It's a 69/76 split. No wonder it was so hard to factor.

[QUOTE=Stargate38;276612]C144 already factored: [URL]http://factordb.com/sequences.php?se=1&eff=2&aq=4788&action=last20&fr=0&to=100[/URL]
[/QUOTE]
Didn't take long to notice. :) Yes, I ran ECM for a day without luck, and decided to be impatient and do it with GNFS. It took about 1.5 days to run. I'm being particularly impatient with the C122. I have ECM and GNFS both running. Whichever finishes first... :smile:

1164@11e6 at the c141 of i2734, no factor

I know 4788 is past this line, but my query is based on future value.

I recently started playing with 4788:2734 via aliqueit to see what it would do with the c141 and wondered if in the future this approach could allow me to submit anything of value towards the ECM level with the data written to the log.

I actually started it several times, so the log shows multiple tests for the same value. Each of the following lines from the log has been followed by the next aliqueit step, so all of them have been completed. These are the log lines:
[code]
[Nov 01 2011, 22:17:15] c141: running 74 ecm curves at B1=11e3...
[Nov 01 2011, 22:17:33] c141: running 214 ecm curves at B1=5e4...
[Nov 01 2011, 22:23:29] c141: running 74 ecm curves at B1=11e3...
[Nov 01 2011, 22:23:46] c141: running 214 ecm curves at B1=5e4...
[Nov 01 2011, 22:24:23] c141: running 430 ecm curves at B1=25e4...
[Nov 01 2011, 22:29:47] c141: running 904 ecm curves at B1=1e6...
[Nov 01 2011, 23:12:05] c141: running 2350 ecm curves at B1=3e6...
[Nov 02 2011, 00:10:05] c141: running 2271 ecm curves at B1=11e6...
[Nov 03 2011, 10:01:57] c141: running 74 ecm curves at B1=11e3...
[Nov 03 2011, 10:02:15] c141: running 214 ecm curves at B1=5e4...
[Nov 03 2011, 10:02:52] c141: running 430 ecm curves at B1=25e4...
[Nov 03 2011, 10:07:29] c141: running 904 ecm curves at B1=1e6...
[Nov 03 2011, 10:44:55] c141: running 2350 ecm curves at B1=3e6...
[/code]If I compile the preceeding lines:

222 curves @ 11e3
642 curves @ 5e4
860 curves @ 25e4
1808 curves @ 1e6
4700 curves @ 3e6
2271 curves @ 11e6

Is this correct, and is it of use in the overall determination of ECM level? Should I provide this type of information for future ECM runs, if I'm inclined to participate or should I leave 4788 to the "big guys?"

[QUOTE=EdH;277023]should I leave 4788 to the "big guys?"[/QUOTE]
No. I happen to have free time on the small cluster right now so I've been throwing it at 4788, but that won't continue. Anyway, it seems stuck with a C158 right now. If ECM doesn't break it, it will be the next team sieve.

[QUOTE=frmky;277032]If ECM doesn't break it, it will be the next team sieve.[/QUOTE]
I have started polynomial selection on the c158

2400@3e6 at the c157 of 4788.2741, no factor.

Here's a poly for line 2741 c157:

[code][color=blue]# sieve with ggnfs siever 14e on alg side from Q=15M to 60M[/color]
# aq4788:2741
n: 1481920007172920321632684015692625609805984206540054444446952577396822360888953735158614084520196754869149889450540343135300182389495199905198697311390505007
# norm 4.111812e-15 alpha -7.532730 e 2.589e-12 rroots 1
skew: 1482966.09
c0: -5257854309105137028176287630689322269
c1: -11610693825698014790914425706848
c2: 15578263422883256843111696
c3: 33624011889155565220
c4: -7221188786619
c5: 970596
Y0: -1088322150509666538306440783662
Y1: 363038661537230021
rlim: 30000000
alim: 30000000
lpbr: 29
lpba: 29
mfbr: 58
mfba: 58
rlambda: 2.5
alambda: 2.5
[/code]

[QUOTE=jrk;277716]Here's a poly for line 2741 c157:[/QUOTE]
ecm cracked it. :smile:

[QUOTE=jrk;277716]Here's a poly for line 2741 c157:

[snip][/QUOTE]

[QUOTE=frmky;277727]ecm cracked it. :smile:[/QUOTE]Nice catch:[quote=FactorDB]28187367500116204879687812105802743791802250189[SUB]<47>[/SUB] · 5257390592...3[SUB]<110>[/SUB][/quote]

poly for line 2758 c156:
[code][color=blue]# sieve with ggnfs siever 14e on alg side from Q=14M to 56M[/color]
# aq4788:2758
n: 144739887039821320412433904800918245955511689135419840521482770289830592456260477974502851830058996429275572891157738219546086713066293094069539959116497151
# norm 4.635619e-15 alpha -6.675641 e 2.770e-12 rroots 5
skew: 2314414.85
c0: -12536100420029886137216006042549543445
c1: 25835581821167904558496560478159
c2: 17699237376342619033080495
c3: -12607847003375816379
c4: -3878171451830
c5: 762600
Y0: -717229768080719056896876193562
Y1: 33524333511886151
rlim: 28000000
alim: 28000000
lpbr: 29
lpba: 29
mfbr: 58
mfba: 58
rlambda: 2.5
alambda: 2.5
[/code]

[QUOTE=jrk;277933]poly for line 2758 c156:
[/QUOTE]

How much ECM has been done on this one?

[QUOTE=Andi47;277941]How much ECM has been done on this one?[/QUOTE]
I have done 300 curves @ B1=6e7

[QUOTE=Andi47;277941]How much ECM has been done on this one?[/QUOTE]

I've almost completed a t50. We should do 2-3 * t50 if we're patient enough.

I have done 400@11e6 and 355@43e6 so far.

179 @ 43e6

I've done 4221 curves at B1=26e7. By my numbers, we have 2.87*t50. I think it's time to start sieving.

Sorry, I just realized I probably should have posted here, too.

Factors for i2758:[code]Tue Nov 22 05:27:47 2011 prp57 factor: 102790717129223843417803050429410108782301549107512023917
Tue Nov 22 05:27:47 2011 prp100 factor: 1408102706958069732039126528126569998510672288334591298669907765961909775816097444970846771711426203[/code]The next line has a c139. I can start some ECM later today if no one else cracks it first.

Thanks to frmky and bsquared for the sieving on this!

I've run 200@3e6 and 250@11e6 with no factor.

+3000 @ 3e6
+3000 @ 11e6

I started it out with the standard ECMNet progression, then jumped it to 43M when I saw the counts here. As soon as my c144 finishes sieving, I can turn up the heat a little....135 curves as of right now.

Running poly selection overnight yielded
[code]# norm 2.429692e-013 alpha -8.005815 e 2.648e-011 rroots 5
skew: 5888761.30
c0: 1687889403675766759343125546201640280
c1: 2398948750046935264483215852992
c2: -97631157945253165093374
c3: -501606506533732426
c4: 9078185861
c5: 1092
Y0: -1021991101564638366966532381
Y1: 1199160448660049[/code]

[CODE]n: 1217481712681662771825109692643535592816957835317259585599247670000232140841359105657319736289241044863040845079199448868877948796757789681
# norm 2.590028e-13 alpha -7.598676 e 2.806e-11 rroots 5
skew: 2525337.84
c0: 240771216400135547934164990820558525
c1: 531035425904972804460211115511
c2: -212400247580094586549691
c3: -235436525480653559
c4: 42295628374
c5: 10200
Y0: -653690021993883049018840324
Y1: 1087289483840201
[/CODE]

1930@44m. Should be ready for sieving.

[QUOTE=akruppa;279692]1930@44m. Should be ready for sieving.[/QUOTE]Wow....I only managed ~400 @ 43M and ~60 @ 110M. Thanks for that!

Do we want to do a group job or is one of us willing to take it on solo?

My ressources are currently tied up with a GNFS-145 from sequence 10212 (not yet in the factordb), so I will not join this one.

I can take this one if no one else wants to.

Edit: Sieving. Edit: Filtering. Edit: LA.

The cluster here is tied up with NFS@Home stuff, so take it.

[QUOTE=akruppa;279703]I can take this one if no one else wants to.

Edit: Sieving.[/QUOTE]Thank you!

[QUOTE=frmky;279760]The cluster here is tied up with NFS@Home stuff, so take it.[/QUOTE]No problem, you did a lot of the last line, so no since having to do another one right away....

Probable prime factor 1 has 85 digits:
3404540906123474411316363722443607027674989081142569513493978852526718134888725154971
Probable prime factor 2 has 54 digits:
357605253175802985551082760434451534908397764660135011

Finished p40 for the c157. Found a p47, a c110 remains. I'll sieve it.

The c110 is done but by the time I finished, someone else already checked the factors into factordb.

The next line has a c139. I've run 400@3e6 with no factor.

I'm almost done with p40 on the c139. Found a p52. Next step has a c131.

[QUOTE=akruppa;280080]Probable prime factor 1 has 85 digits:
3404540906123474411316363722443607027674989081142569513493978852526718134888725154971
Probable prime factor 2 has 54 digits:
357605253175802985551082760434451534908397764660135011

Finished p40 for the c157. Found a p47, a c110 remains. I'll sieve it.[/QUOTE]

[QUOTE=akruppa;280124]The c110 is done but by the time I finished, someone else already checked the factors into factordb.[/QUOTE]

[QUOTE=akruppa;280134]I'm almost done with p40 on the c139. Found a p52. Next step has a c131.[/QUOTE]Lucky hits on those. I was not looking forward to another c15x GNFS job. Thanks for all the ECM and GNFS work on this!

Looks like we might get just such a GNFS job. Did 4000@44M, no factor yet. EDIT: on the current c154.

[QUOTE=akruppa;280183]Looks like we might get just such a GNFS job. Did 1600@44M, no factor yet. EDIT: on the current c154.[/QUOTE]I'll run some ECM until we decide different....

starting polynomial selection on c154 (line 2764)

[code][color=blue]# sieve with ggnfs siever 14e on alg side from Q=10M to 40M[/color]
# aq4788:2764
n: 1566995182284290084552061351701731286158584419729523776503441142820300208568705908650143119696309631508397253178597013710075243911171394358266029728845823
# norm 9.543221e-15 alpha -7.409829 e 4.239e-12 rroots 5
skew: 4651649.62
c0: 51051556980151412770346722598733836877
c1: 63112572000896956954660071934161
c2: 6723391780590826967760721
c3: -7015861282295435665
c4: -7929641070
c5: 97776
Y0: -437488941713715648011445883282
Y1: 61125925743039029
rlim: 20000000
alim: 20000000
lpbr: 29
lpba: 29
mfbr: 58
mfba: 58
rlambda: 2.5
alambda: 2.5
[/code]

I've completed a t50 so far. Nothing yet.

Add:

1200@3e6
1300@43e6

Did about 3500@110M. Looks like a GNFS job.

[QUOTE=frmky;280293]I've completed a t50 so far. Nothing yet.[/QUOTE]

[QUOTE=EdH;280349]Add:

1200@3e6
1300@43e6[/QUOTE]

[QUOTE=akruppa;280358]Did about 3500@110M. Looks like a GNFS job.[/QUOTE]Plus:

850 @ 11M
175 @ 110M

As [URL="http://www.mersenneforum.org/showpost.php?p=281469&postcount=23"]reported[/URL]:[code]prp62 factor: 20634753487937621334296309336069486043601573832158278690150677
prp92 factor: 75939612421360034434396399144301505736137685593066413285259017792902632706691893472452354499[/code]And just a reminder: if you're in the colder parts of the country and you're on a private well, make sure that the heater in the pump house is actually making contact with the outlet, otherwise you might have trouble when the temp gets below 32F....

[SIZE="1"]No pipes lost, thank goodness, just a couple of nail-biting hours waiting until everything thawed out.[/SIZE]

It's done
 

87015491 relations, 71928202 unique

Matrix 5460887x5461067 with weight 519487306 before the tidying-up and MPI-splitting step

Linear algebra took 32125 seconds over 48 MPI threads

Ran eight sqrt jobs in parallel: the first to finish took 4864 seconds.

Factors:

[code]
Sat Dec 17 08:19:27 2011 prp74 factor: 46491131460318302100667853604969125999833946975188994819138005259573336249
Sat Dec 17 08:19:27 2011 prp86 factor: 60540054526512543948070644083618121838194243448058579707245074941266171173299153581767
[/code]

[QUOTE=fivemack;282593]87015491 relations, 71928202 unique

Matrix 5460887x5461067 with weight 519487306 before the tidying-up and MPI-splitting step

Linear algebra took 32125 seconds over 48 MPI threads

Ran eight sqrt jobs in parallel: the first to finish took 4864 seconds.

Factors:

[code]
Sat Dec 17 08:19:27 2011 prp74 factor: 46491131460318302100667853604969125999833946975188994819138005259573336249
Sat Dec 17 08:19:27 2011 prp86 factor: 60540054526512543948070644083618121838194243448058579707245074941266171173299153581767
[/code][/QUOTE]That was some heavy lifting there. :flex: Thanks for the enormous boost!

And so with that, another 17 lines added very quickly and the 160 digit line has been breached! (And there's a c136 -- almost a yawner!)
:party: :party:

Done 4800@1e7 on the C136, which I think is about enough (it took about 83 CPU-hours and the sieving should take about 200 on same hardware).

Am leaving the sieving to someone else.

[QUOTE=fivemack;282612]Done 4800@1e7 on the C136, which I think is about enough (it took about 83 CPU-hours and the sieving should take about 200 on same hardware).

Am leaving the sieving to someone else.[/QUOTE]Thank you for the curves on this line and the NFS on the last line.

I can do this if no one else does. I'll have to put my current job on hold....(I'll start it tomorrow if no one says they're going to....)

OK, I ran a poly search while I was at work today, and since no one else has said anything, I just kicked off the job for this. ETA is maybe 3 days? (It's been a while since I did one this size, so I'll know more for sure tomorrow....)