From line 2431:

[code]Using B1=250000, B2=128992510, polynomial Dickson(3), sigma=3423068688
Step 1 took 805ms
Step 2 took 482ms
********** Factor found in step 2: 70421951056571174298407161
Found probable prime factor of 26 digits: 70421951056571174298407161
Composite cofactor 101604430095248107007562678598950397409062296407427396953273974341582170484206305218451473255594781352991727576633457 has 117 digits
[/code]

Who wants to do the c117?

Should i be surprised that you got to 2*t25 and missed a 26 digit factor?

[QUOTE=henryzz;185580]Should i be surprised that you got to 2*t25 and missed a 26 digit factor?[/QUOTE]

Not too surprised - I once did t25 and t30 and missed a p25.

jrk, have you fully ECM'd the c117? (Just in case you haven't, I'll run a few curves myself)

Edit: seen Serge's post, aborted.

I've run more than enough 3e6 curves. Do go ahead. Anyone?
(I am bound with 552150.)

About how long would that c117 take on two cores of my Athlon 2.5 GHz? (using factMsieve.pl, since I don't know enough to do it manually) If it's not too long, (either for my or this forum's patience) I'll take it. :smile: For comparison, a c109 with the same setup took about 7.5 hours for the GNFS.

Ah, why not. I'm starting the GNFS now.

status update: poly selection took 2:46:46 (h:mm:ss), first q=100k chunk (started at 1.8M) took about 66 minutes and found 772526 relations, and it wants at least 5737340 before filtering. (this is factMsieve.pl with the MINRELS factor changed from 0.2 to 0.4) If I find this many relations each time, it'll take about 8 hours before the first factoring run. I doubt it'll work with that few relations, though. A c109 I ran the other day took 7168224 before being solvable. I'll guestimate that it'll need 10M relations (anyone got a better approximation?). This puts it at 13 runs, or about 13 hours. Plus an hour or two for finishing. So maybe 15 hours total.
So I should have the factors when I wake up tomorrow morning, (about 6 AM CDT / 11 AM GMT) unless I'm grossly wrong about anything. (I'm safe by about 3 hours, by my estimates)

[code]prp48 factor: 101787819775835948918733316910809569438934603559
prp69 factor: 998198314091099356256123369104680179895991846742675659120420684192423
[/code]It took 29 hours according to the computed timescale, just under 19 hours realtime (is the discrepancy due to the partial dual-threaded work or something?). I had 9602817 rels, which filtered down to 2292292 rels (if I understand the log correctly). The sieving was finished at about 3 AM my time, and the factors appeared at 4:47 AM.
Line 2432 is 2^5*3*p32*p128 and was already known as of when I put in the factors for the c117. Did someone beat me to the c117 and the next line without reporting the c117?
Anyway, now we're on Line 2433 and we lost a power of 2! :w00t: And gained a digit. :sad:
Cofactor is [URL="http://factordb.com/search.php?id=68093978"]c145[/URL]. Not much ECM has been done yet, (AFAIK, but the one who found that p32 may have worked on this c145 as well) but I'm keeping my status updated in the DB. :smile: Currently running 430@25e4. Just in case the DB has any more problems, here is the status:[code]2431. 41315209076258805980822819038600045201318969211789936794591428435375396599518680455218805759776349083356322831874886489751735221707037749030973936818492662199712 = 2^5 * 3 * 17 * 29 * 12641 * 33107 * 291521 * 70421951056571174298407161 * 101787819775835948918733316910809569438934603559 * 998198314091099356256123369104680179895991846742675659120420684192423
2432. 77489885742951318531011281537865398594576052855381059201245310474765450507848421490566102008207088378549525045932279226875927249701083945747558616485194709781088 = 2^5 * 3 * 28280105441052726736468878788089 * 28542549514354358893458915993662819655625753028398499312865912186369663866315908702072428978933749287812332066919759250319256377
2433. 125921064332295892612893332499038465438663703188435372848854032552047074765016841343996757973207483770437289808632875995776073092711376690665933668709679310599952 = 2^4 * 3 * 263 * 348407 * 6799769 * c145
c145 = 4210371029436746497837158825490947314990186258843761539738301861157299913528382593744449951063933548780440298195483979139600003150433674869074931
[/code]Edit: I finished 430@25e4 (t30) and some P-1 and P+1 (each with the highest B1 that Syd's DB would've assigned) unsuccessfully.

That must be the highest ever escape from 2^5 * 3! (161 digits)

[QUOTE=Mini-Geek;185765]
Line 2432 is 2^5*3*p32*p128 and was already known as of when I put in the factors for the c117. Did someone beat me to the c117 and the next line without reporting the c117?
[/QUOTE]
Ok, I confess. I put it on the cluster to see where it would get overnight. The C117 GNFS took less than an hour, but since you were well into completing it yourself I couldn't bear to submit it. :ermm: Of course it got stuck on the C145. Overnight, the C145 survived 4500 curves at B1=3M. It automatically started the GNFS. If you want to do it as a team effort, I'll stop. Otherwise, I'll finish it by tomorrow.