Team sieve for line 2382 has completed, producing a C131=P46*P86 factorization:

[code]2382. 864588558624620116627174028234248024151284530600967959183428254564562985214447829513189546277657276453005513317875838138485737430006182150439221712 = 2^4 * 3 * 438849012817399 * 3792916848543091297685310362301268600678979567 * 10821309017625776539139453112614668327856417769647239432607699746391699462546166162743[/code]

Next line (C138 cofactor as of this writing) is currently undergoing small ECM at Syd's DB. Guys, how do you think we should proceed for ECM on this one? With the worker queue in such a mess as it is right now, it would be like heck trying to get any work done on a very high limits job. So, unless someone is willing to babysit it and make sure it stays at the top, it might actually be quicker to do it as a distributed job ourselves.

(In the meantime, I have put it up for ECM very high limits, but we can stop that run if we decide to do it ourselves.)

[quote=mdettweiler;172082]Team sieve for line 2382 has completed, producing a C131=P46*P86 factorization:

[code]2382. 864588558624620116627174028234248024151284530600967959183428254564562985214447829513189546277657276453005513317875838138485737430006182150439221712 = 2^4 * 3 * 438849012817399 * 3792916848543091297685310362301268600678979567 * 10821309017625776539139453112614668327856417769647239432607699746391699462546166162743[/code]

Next line (C138 cofactor as of this writing) is currently undergoing small ECM at Syd's DB. Guys, how do you think we should proceed for ECM on this one? With the worker queue in such a mess as it is right now, it would be like heck trying to get any work done on a very high limits job. So, unless someone is willing to babysit it and make sure it stays at the top, it might actually be quicker to do it as a distributed job ourselves.

(In the meantime, I have put it up for ECM very high limits, but we can stop that run if we decide to do it ourselves.)[/quote]

I'll do as much babysitting as possible, but don't expect any of my resources until the downdriver run on 130396 is over. Currently at 90 digits, c86 cofactor.

[QUOTE=mdettweiler;172082]Next line (C138 cofactor as of this writing) is currently undergoing small ECM at Syd's DB. Guys, how do you think we should proceed for ECM on this one? With the worker queue in such a mess as it is right now, it would be like heck trying to get any work done on a very high limits job. So, unless someone is willing to babysit it and make sure it stays at the top, it might actually be quicker to do it as a distributed job ourselves.

(In the meantime, I have put it up for ECM very high limits, but we can stop that run if we decide to do it ourselves.)[/QUOTE]I'll run some curves on it, in fact I've got it loaded in my server right now, but I'm off to work, so I won't know until after 7PM local what happens.

I'll run some curves too.

ECM needed: at least t40, incorporating 1000 curves at the 45-digit level would be an idea too.

ECM done so far: only 1/3 of t35. [strike]Let's hope my downdriver run ends and I get a driver![/strike] No, I hope it does terminate, but as long as it has the downdriver, I will not be doing any other factorizations or parts of factorizations.

I am running 750 curves at B1=1e7, using three-eighths of a core i7 machine.

I did 415 curves @ 11e6.

750@1e7 found no factor; proceed to GNFS

Okay--line 2383 has completed group GNFS factorization (factors [url=http://www.mersenneforum.org/showpost.php?p=173461&postcount=112]here[/url] and at [url=http://factorization.ath.cx/search.php?id=35442665]Syd's DB[/url]). The next line is stuck at the moment since the TF to 1e7 worker appears to be frozen.

I'm doing some manual work on this with yafu at the moment... getting a few more iterations with easy factorizations.

Are you doing the c107 from line 2386?
[code]13426250388422857716699557092184500820449568993222904193889997607988206118731638115457299967722713612190661[/code]
If not, I can run it, unless someone else wants to take it first.