There hasn't been any recent activity. Any ECM work? Perhaps yoyo can help get things started.

[QUOTE=RichD;467630]There hasn't been any recent activity. [/QUOTE]
Hmmm. I'd say factoring a c210 was a pretty damn good activity. ...and sort of recent, too. (Dated [URL="http://factordb.com/index.php?id=1100000000968464113"]Sep. 12[/URL].) 
[QUOTE=Batalov;467665]Hmmm. I'd say factoring a c210 was a pretty damn good activity.
...and sort of recent, too. (Dated [URL="http://factordb.com/index.php?id=1100000000968464113"]Sep. 12[/URL].)[/QUOTE] I was referring to [url=http://www.factordb.com/sequences.php?se=1&aq=4788&action=range&fr=12501&to=12501]AS 4788:12501[/url] which has a C195 blocker and a total size of 199. Unless there is something wrong with FDB I am not aware of. 
[QUOTE=RichD;467676]I was referring to [url=http://www.factordb.com/sequences.php?se=1&aq=4788&action=range&fr=12501&to=12501]AS 4788:12501[/url] which has a C195 blocker and a total size of 199.
Unless there is something wrong with FDB I am not aware of.[/QUOTE] Create time April 20th. Certainly seems like a while. 
Ah, my mistake.
[SPOILER]That old sequence is certainly worthy of moving from one 2^2 · 3 · 7 iteration to another 2^2 · 3 · 7 iteration. Just like the other one is worthy of moving from one 2 · 3 iteration to another 2 · 3. Both equally worthy, for sure.[/SPOILER] 
ok, in the first step I'll run all curves up to 43e6.

[QUOTE=yoyo;467686]ok, in the first step I'll run all curves up to 43e6.[/QUOTE]
it is quite possible that ryanp has already run the necessary ecm before abandoning the sequence. 
[QUOTE=yoyo;467686]ok, in the first step I'll run all curves up to 43e6.[/QUOTE]
As second step I'll run all 110e6 curves. 
[QUOTE=yoyo;467893]As second step I'll run all 110e6 curves.[/QUOTE]
I run now all 260e6 curves. Is afterwards more needed? 
[QUOTE=yoyo;468440]I run now all 260e6 curves.
Is afterwards more needed?[/QUOTE] Bayesian says, given 18000 curves @ 110e6: [CODE]3400 curves with B1 = 850.0e6 4800 curves with B1 = 2.9e9[/CODE] 
And what does it say after 42000 curves @260e6?
Where can I see what it say? 
[QUOTE=yoyo;468473]And what does it say after 42000 curves @260e6?
Where can I see what it say?[/QUOTE] After 42000 @ 260e6, it wants:[CODE]2800 curves with B1 = 2.9e9[/CODE] It's a script that was put up on the forum by someone (Xilman, maybe?). If you search around for Bayesian or ecmtoy, you should find it. Make sure you also get the ecmtimes generating script as well. It'll produce the timings needed for the ecmtoy script to do calculations properly. 
I believe it was fivemack's creation.

[url]http://www.mersenneforum.org/showthread.php?t=21420[/url]
This should be the correct thread. And yes, it was Fivemack's creation. My apologies. :smile: 
Allow me to lend a hand.
[CODE]********** Factor found in step 2: 182357912893988503627254174005712015671586296929600556279774513 Found prime factor of 63 digits: 182357912893988503627254174005712015671586296929600556279774513 Prime cofactor 3437983098198847465432715554453716156167883161078675410143054569773009704002951049321643443408470436997896703479610434558233530978921 has 133 digits[/CODE] 
Ok, So I wasted the time of my Minions :(

[QUOTE=yoyo;468533]Ok, So I wasted the time of my Minions :([/QUOTE]
Well, not really it's likely Ryan wouldn't pay attention or have a go at it until something near t55 was done. If you don't want to use the Bayesian tool each time you queue curves, you can still improve on the old methods by doing half the usual number of curves at a B1 level before moving to the next B1. Once you've done half a t50, move to B1 = 110M, etc. The second half of the effort for t50 is then completed by the 110Mbound curves,while improving chances to find bigger factors. 
I were running all curves up to B1=110e6 for the current C167.
More curves required? 
[QUOTE=yoyo;469308]I were running all curves up to B1=110e6 for the current C167.
More curves required?[/QUOTE] ~2*t50 is enough for C167, so t55 is more than enough. 
С167 splits as P81*P87, next blocker is C157, ECM'ed to t40 by me.

[QUOTE=unconnected;472239]С167 splits as P81*P87, next blocker is C157, ECM'ed to t40 by me.[/QUOTE]
I'll help out here: [CODE]********** Factor found in step 2: 429703755622418749195461202672606685434385383452642849506855188546787 Found probable prime factor of 69 digits: 429703755622418749195461202672606685434385383452642849506855188546787 Probable prime cofactor 16506221423962903401572546600437748119934273038133738581822300715727493794731141539898483 has 89 digits[/CODE] 
Curtis, seems that 4788 is waiting on a C146 that showed up a few lines and a few days after the most recent post here, do you want to CADOize it?

Yes, please! I'll start this morning. Should be 4 days or so.

[QUOTE=VBCurtis;473851]Should be 4 days or so.[/QUOTE]
4 days for a c146. <===> 4000 days for a c197. (Just to keep things in perspective.) 
Ye assume he has nothing in his Q.

Factors, reported to FactorDB this time:
[code]5549197341624338233523401594270651210469419943578860543352095617937601 1811457164989861608083111991415393667057176845661763189253626073324202259447[/code] CADO took 1.7 megathreadseconds for the C146 factorization. That includes 10 hrs wall clock time for the linear algebra. 
C135 @ i12513
[B]yoyo[/B] found a p43 leaving a C135 at this step.
Anyone interested at finishing it off? (I am over committed right now and can't do it for a while.) 
I got it.

The following C185 has had at least t45 with continuing (if extremely slow) ECM by me. Looks like a likely GNFS target. It would take me 90 hours to complete ECM to t50, but I'm letting it run now while my computer access is intermittent. Either yoyo@home or someone else can complete ECM (to ~t55 level I would think) and begin a poly search.

Dubslow  any hits? You mention intermittent computer access, but let us know when you can about progress.
Maybe yoyo can take on ECM to t55 if necessary? I don’t have the resources available currently. 
A P46 popped out right after I PM'd yoyo@home, and the C140 residual will be done in a few hours (Sandy Bridge quad core isn't very fast these days, but at least I'm back home after the holidays now)

[URL="http://factordb.com/sequences.php?se=1&aq=4788&action=last20&fr=0&to=100"]Index 12515[/URL] has a C197. t40 complete, 12 hours on my box to completing t45. 4/13s ECM rule suggests a t60 be completed. I think we'd definitely need yoyo@home for this.
Perhaps two runs for yoyo@home: a hybrid t50/t55  perhaps 12K@75M, with the second round being a standard t60 42K@260M? 
yoyo@home seems to have completed ECM to at least the t60 level. I believe poly select can now begin, although perhaps some further ECM is warranted  or perhaps not.

C197 @ i12515
yoyo is completing 10K @ 850e6. This is surely enough ECM. A C197 can also be added to the poly select/generation queue.

C174 @ i12516
It looks like yoyo completed a full t55 plus 8000 @ t60 on the remaining C174. Should be ready for poly selection.

C153 @ i12518
Anybody running ECM on the C153? After the C174 was split, it has advanced a couple terms but nothing recently. It stands at:
2^2 * 3^2 * 7^2 * ... * C153 
I can do GNFS on the C153 if it has received enough ECM.

C153
yoyo@home has 7800 @ 43e6 in the input queue but it hasn't gone active yet.

I am doing it, it will finish quite soon, so it's not necessary that yoyo@home does it.

The C153 factors as
[CODE] p74 factor: 19928638114143557639348319790409168695610012346109977780982024608631375087 p79 factor: 7798641889897770108922816559374634253586927781674138840644647051053991265389963 [/CODE] I have added some more term to the sequence (and currently doing ECM on a C194). 
I've ECMed the C194 with 14716 curves at B1=110M (yafu's default for t=55), without luck. I'm stopping working on it.

I'll run the t=60.

A p57 found. Now it is a C165.

Nice hit!
Unfortunately, the D2 is difficult to lose, especially at this size. On the bright side, if it does not get a 3, then it is steady (i.e. it doesn't grow much), and 5 is not sticky. But unless we double the seven, there is no much hope... Maybe we could find a "better" sequence to tickle? :wonder: 
Great! I am doing the C165.

It's now a C167. I've ECMed it with 7553 curves at B1=43M without luck and I'm dropping it.

I'll run all B1=110M curves.

17030 curves done so far without factor. I run up to 18000 curves.
What is needed next? 
2t50 was probably enough, so your curves are more than sufficient. We'll do poly select soon and get it fed to the 14e queue.

I can do the linear algebra if you need it.

The c167 is factored and reported to factordb. I did zero ECM on the new line.
Go, Ricky, go! 
The latest composite is a C154 (ECMed to t25) after three easy lines.
Edit: C126 at t30. 
I'm working on it!

The C126 factors very nicely as p63*p63! :smile:

It's now a C196... I've ECMed it to t=50. I think yoyo@home may be interested to go to t=55 at least... or perhaps even to t=60.

[QUOTE=ricky;507714]It's now a C196... I've ECMed it to t=50. I think yoyo@home may be interested to go to t=55 at least... or perhaps even to t=60.[/QUOTE]
Anybody still working on this? Has yoyo been contacted about ECM? 
C196 @ i12534
I see [B]yoyo[/B] has completed t55 + 20K @ 26e7 and is nearing 12K @ 85e7. That should be plenty to start GNFS poly selection.

about 600 threadhours on CADO poly select yielded this:
[code]n: 1702810278506124393622905886419417373727833799255920336877918870350397583189521830994382118639550712786413448936290016013396498804612664118174179978449082129699734624314982852315442373887230082927 skew: 53530918.291 c0: 14138230899246094225865032544701492909383604820 c1: 93571871123367745680754273625163957009 c2: 37510656767740839089260370637202 c3: 475303574396348223775899 c4: 8150194247457752 c5: 4386480 Y0: 88526646710138023135509930133068454122 Y1: 21051283668116650162091989 # MurphyE (Bf=4.000e+08,Bg=2.680e+08,area=2.147e+17) = 2.67e11[/code] I don't recall a good way to run this through msieve to find the usual score; if someone could do so we can compare it to the C196 record and decide how much msieveGPU poly select to continue with. 
[QUOTE=VBCurtis;511291]
[code]# MurphyE (Bf=4.000e+08,Bg=2.680e+08,area=2.147e+17) = 2.67e11[/code] I don't recall a good way to run this through msieve to find the usual score; if someone could do so we can compare it to the C196 record and decide how much msieveGPU poly select to continue with.[/QUOTE] [C]Msieve v. 1.52 (SVN 883 prerelease)[/C] [CODE]commencing number field sieve (196digit input) R0: 88526646710138023135509930133068454122 R1: 21051283668116650162091989 A0: 14138230899246094225865032544701492909383604820 A1: 93571871123367745680754273625163957009 A2: 37510656767740839089260370637202 A3: 475303574396348223775899 A4: 8150194247457752 A5: 4386480 skew 53530918.29, size 3.836e019, alpha 8.143, combined = 9.505e015 rroots = 5[/CODE] 
The [url=http://myfactors.mooo.com]skew optimizer[/url] suggests it can be improved even further:
skew: 76499475.66494 Escore: 9.56202965e15 
The previous C196 record was 8.16e15. This beats the C195 record too (which was lower than C196).
Seems the CADO polyselect is very effective on large inputs! The C206 last week in the poly select thread also found CADO highly effective. Let's give Max a bit of time to appear and try his magic before we queue to 15e? 
C196 and C195
[QUOTE=VBCurtis;511334]The previous C196 record was 8.16e15. [B] This beats the C195 record too (which was lower than C196).
[/B] Seems the CADO polyselect is very effective on large inputs! The C206 last week in the poly select thread also found CADO highly effective. Let's give Max a bit of time to appear and try his magic before we queue to 15e?[/QUOTE] Well, no, it doesn't (and it wasn't). [URL]https://www.mersenneforum.org/showpost.php?p=503952&postcount=134[/URL] and [URL]https://www.mersenneforum.org/showpost.php?p=481656&postcount=101[/URL] I got swellman's PM, I'm on it but so far it doesn't look too promising. 
Thanks for the 2018 table; I've updated my copy of the chart to correct the outofdate records.

C196 poly
[QUOTE=Max0526;511365]Well, no, it doesn't (and it wasn't).
[URL]https://www.mersenneforum.org/showpost.php?p=503952&postcount=134[/URL] and [URL]https://www.mersenneforum.org/showpost.php?p=481656&postcount=101[/URL] I got swellman's PM, I'm on it but so far it doesn't look too promising.[/QUOTE] It was a bit ahead of myself. It's better by now. I'll post it finalized before going to bed. 
C196 poly  new record
Crossed 1e14! :stirpot:
They might not sieve the same, please testsieve. from CADO:[code]Y0: 88526593606906636872832313995490222337 Y1: 21051283668116650162091989 c0: 16963157469344920969930575255084128666463471380 c1: 104226072109715053258553301087375190176 c2: 40797138907888738018707441706807 c3: 393345121770100035860379 c4: 8094868342851752 c5: 4386480 skew: 76011430.42456 # lognorm 61.32, E 53.00, alpha 8.31 (proj 2.17), 5 real roots # MurphyE(Bf=1.000e+07,Bg=5.000e+06,area=1.000e+16) = 1.00222868e14[/code]from msieve:[code]Y0: 88526652402994562936959400167280855414 Y1: 21051283668116650162091989 c0: 16945072822861140163957622147315197462146382800 c1: 113754137212796358973399404221053058157 c2: 37121473509227882514071277769078 c3: 484122945206142149130523 c4: 8156125382524952 c5: 4386480 skew: 75049313.58 # size 4.185e19, alpha 8.314, combined = 1.002e14 rroots = 5[/code] 
I test sieved both polys and found the first to be slightly better
[code] n: 1702810278506124393622905886419417373727833799255920336877918870350397583189521830994382118639550712786413448936290016013396498804612664118174179978449082129699734624314982852315442373887230082927 skew: 76011430.42456 c0: 16963157469344920969930575255084128666463471380 c1: 104226072109715053258553301087375190176 c2: 40797138907888738018707441706807 c3: 393345121770100035860379 c4: 8094868342851752 c5: 4386480 Y0: 88526593606906636872832313995490222337 Y1: 21051283668116650162091989 type: gnfs # lognorm 61.32, E 53.00, alpha 8.31 (proj 2.17), 5 real roots # MurphyE(Bf=1.000e+07,Bg=5.000e+06,area=1.000e+16) = 1.00222868e14 rlim: 268000000 alim: 400000000 lpbr: 33 lpba: 33 mfbr: 65 mfba: 94 rlambda: 3.0 alambda: 3.6 [/code] Test sieving on the a side with Q in blocks of 2K using some advice from VBCurtis (mfbr=64 performed horribly): [code] Q0=50M 5285 rels Q0=100M 4644 rels Q0=200M 5113 rels Q0=300M 3800 rels Q0=400M 3234 rels Q0=500M 3513 rels Q0=600M 2580 rels [/code] The big unknown to me is how many relations are needed? I would typically aim for 850900M on a 33 bit job but that seems like overkill considering some of the parameters. Should I initially aim for 600M and slowly increase the Q range until a matrix can be built? Advice welcome. Once a consensus is reached, I'll enqueue it in 15e. 
I'd go for 900M to start, and then we can decide how many more to request once we see how many unique relations we have.
You can reserve the postprocessing for me when you queue it. 
The c196 is finished, factors posted. i12535 has a c187, I'm running 3000 curves at B1=2e7 overnight. If no factor, I'll run curves at 6e7 tomorrow until a t50 is complete.

t50 complete. I've scheduled 3000 curves at 15e7.
I lack the patience to go past a t55; if a GPUer or yoyo could do half a t60, that should be about enough. 
[QUOTE=VBCurtis;526956]t50 complete. I've scheduled 3000 curves at 15e7.
I lack the patience to go past a t55; if a GPUer or yoyo could do half a t60, that should be about enough.[/QUOTE] I’ll put it in Yoyo’s queue. 
i12537
I just went to enqueue this series and see that it has progressed. Current on i12537 with a C177. Is anyone actively working this series right now?

Wasn't me! I'll run some curves at 6e7 on the C177; that's small enough we won't need yoyo's help for ECM.

Ryan must be at it again. :smile:

[strike]I'll run some ECM at 11e7 overnight as well.[/strike]
Might that step on your toes? 
[QUOTE=EdH;527485][strike]I'll run some ECM at 11e7 overnight as well.[/strike]
Might that step on your toes?[/QUOTE] Step right ahead! I don't have free cores till tomorrow anyway, so I'll run some at 15e7 instead if you don't crack it. We should sum to half a t55, give or take, when we finish. 
[QUOTE=VBCurtis;527492]Step right ahead! I don't have free cores till tomorrow anyway, so I'll run some at 15e7 instead if you don't crack it. We should sum to half a t55, give or take, when we finish.[/QUOTE]
I'll let you know how many I ran in the morning. I just queued it into my ecmpi script, so it's supposed to run a few smaller curves and then lots of 11e7 before passing it to NFS (which is inhibited ATM). 
[QUOTE=EdH;527494]I'll let you know how many I ran in the morning. . .[/QUOTE]Darn it! I ran a crippled version of my script and it only did 496 curves @11e7 and quit.

I did 4480 curves @11e7 and i'm currently at 1952 of 7584 @43e7 ETA 14h

7584 curves on C177, B1=43M completed. Now doing B1=110M 4544 of 12800 completed.

[QUOTE=vebis;527642]7584 curves on C177, B1=43M completed. Now doing B1=110M 4544 of 12800 completed.[/QUOTE]
If I'd known you meant 43e6 instead of 43e7, I could have saved you the time. 11e7 was the level to work at! Oh well. 
[QUOTE=VBCurtis;527646]If I'd known you meant 43e6 instead of 43e7, I could have saved you the time. 11e7 was the level to work at! Oh well.[/QUOTE]
Oh yeah, one digits which matters. Anyway now i'm on track with 11e7 as stated above. 
I'm going to polyselect this C177 (i12546) and submit to the 14e queue.

[QUOTE=VBCurtis;533393]I'm going to polyselect this C177 (i12546) and submit to the 14e queue.[/QUOTE]
Sorry, I'm already working on this c177  it's in LA and should be done sometime tomorrow. (Should I have reserved the sequence somewhere?) 
Nice timing, sir. After two months of no posts, a reservation doesn't seem necessary; if you did report your work plans, please use this thread.
Thanks for the help! 
[QUOTE=ryanp;533408]Sorry, I'm already working on this c177  it's in LA and should be done sometime tomorrow. (Should I have reserved the sequence somewhere?)[/QUOTE]
Correction, CADONFS has only completed the first stage of LA (krylov). Looks like we'll have the factors on Wednesday. 
This series seems to have stalled at i12553 (C169). Anyone still working it?

[QUOTE=swellman;533754]This series seems to have stalled at i12553 (C169). Anyone still working it?[/QUOTE]
I'm still on it. :smile: I'll post a note if/when I release it. 
And, we're going again...

Finally, with 12562 known terms, this sequence has become the longest sequence below 1e6 for the moment.
However it will be impossible to beat 2005020 without a downdriver. 
index 12566
Bad news: the c205 at index 12566 (1905316801...) has thus far failed to yield to ECM.
I've run 83K curves at B1=29e8, but no hits. May continue on at B1=76e8 after. Could this be a good GNFS target for the forum? I may not have the time/resources to devote to it. 
[QUOTE=ryanp;534357]Bad news: the c205 at index 12566 (1905316801...) has thus far failed to yield to ECM.
I've run 83K curves at B1=29e8, but no hits. May continue on at B1=76e8 after. Could this be a good GNFS target for the forum? I may not have the time/resources to devote to it.[/QUOTE] Yes, yes it could. We'd appreciate it if you could aim a couple of CADO clients at the forum server if we do take it on; I'd run it on I=15, so each client would be ~3GB memory. Sieve time would be on the order of 75 [hyper]threadyears. Those who donate clientcycles may prefer to tackle the c204 GNFS cunningham target first, or either of these might just get sent to Greg's 16e queue at NFS@home. 
Hello A4788 my old friend
I've come to unblock you again..
[CODE]Msieve v. 1.54 (SVN 1030M) GMP: 6.2.0 Thu Nov 5 15:15:39 2020 random seeds: b2118e58 790b70c1 factoring 1905316801900227776940740392824424737989728747169726258280714634792948493247829252120845527350847484333154257861780256228486021326259811811322794867063747268414450756262259879962628547123420929973114919411 (205 digits) no P1/P+1/ECM available, skipping commencing number field sieve (205digit input) R0: 644385218268975855216257270717655 R1: 7554842833428957692911 A0: 968459661759956978335434484607254900640 A1: 84216134837203272920647028519575602 A2: 2272015212039749459863221804895 A3: 46966005229435841480877792 A4: 215405822583844424753 A5: 3185898266006400 A6: 8516121600 skew 1.00, size 9.339e15, alpha 8.029, combined = 2.424e16 rroots = 6 commencing linear algebra read 53676482 cycles cycles contain 173114391 unique relations read 173114391 relations using 20 quadratic characters above 4294917295 building initial matrix memory use: 24824.7 MB read 53676482 cycles matrix is 53676304 x 53676482 (27077.6 MB) with weight 8147585062 (151.79/col) sparse part has weight 6454113870 (120.24/col) filtering completed in 2 passes matrix is 53675530 x 53675708 (27077.5 MB) with weight 8147552115 (151.79/col) sparse part has weight 6454105192 (120.24/col) matrix starts at (0, 0) matrix is 53675530 x 53675708 (27077.5 MB) with weight 8147552115 (151.79/col) sparse part has weight 6454105192 (120.24/col) saving the first 240 matrix rows for later matrix includes 256 packed rows matrix is 53675290 x 53675708 (24980.0 MB) with weight 5995587872 (111.70/col) sparse part has weight 5689533400 (106.00/col) using block size 8192 and superblock size 608256 for processor cache size 25344 kB commencing Lanczos iteration (64 threads) memory use: 34200.5 MB linear algebra at 0.0%, ETA 438h13m675708 dimensions (0.0%, ETA 438h13m) checkpointing every 130000 dimensions5708 dimensions (0.0%, ETA 430h34m) linear algebra completed 213115 of 53675708 dimensions (0.4%, ETA 471h49m)[/CODE] 
LA on the c205 blocker done, onto the sqrt phase...
[CODE]Fri Nov 20 19:53:24 2020 Msieve v. 1.54 (SVN 1030M) Fri Nov 20 19:53:24 2020 GMP: 6.2.0 Fri Nov 20 19:53:24 2020 random seeds: f0d0fbab d4c8c7cc Fri Nov 20 19:53:24 2020 factoring 1905316801900227776940740392824424737989728747169726258280714634792948493247829252120845527350847484333154257861780256228486021326259811811322794867063747268414450756262259879962628547123420929973114919411 (205 digits) Fri Nov 20 19:53:25 2020 no P1/P+1/ECM available, skipping Fri Nov 20 19:53:25 2020 commencing number field sieve (205digit input) Fri Nov 20 19:53:25 2020 R0: 644385218268975855216257270717655 Fri Nov 20 19:53:25 2020 R1: 7554842833428957692911 Fri Nov 20 19:53:25 2020 A0: 968459661759956978335434484607254900640 Fri Nov 20 19:53:25 2020 A1: 84216134837203272920647028519575602 Fri Nov 20 19:53:25 2020 A2: 2272015212039749459863221804895 Fri Nov 20 19:53:25 2020 A3: 46966005229435841480877792 Fri Nov 20 19:53:25 2020 A4: 215405822583844424753 Fri Nov 20 19:53:25 2020 A5: 3185898266006400 Fri Nov 20 19:53:25 2020 A6: 8516121600 Fri Nov 20 19:53:25 2020 skew 1.00, size 9.339e15, alpha 8.029, combined = 2.424e16 rroots = 6 Fri Nov 20 19:53:25 2020 Fri Nov 20 19:53:25 2020 commencing square root phase Fri Nov 20 19:53:25 2020 reading relations for dependency 1 Fri Nov 20 19:53:29 2020 read 26081206 cycles Fri Nov 20 19:54:15 2020 cycles contain 85819134 unique relations Fri Nov 20 20:00:30 2020 read 85819134 relations Fri Nov 20 20:08:59 2020 multiplying 85819134 relations Sat Nov 21 00:25:42 2020 multiply complete, coefficients have about 6070.54 million bits Sat Nov 21 00:27:12 2020 initial square root is modulo 6421997 Sat Nov 21 05:03:35 2020 GCD is N, no factor found Sat Nov 21 05:03:35 2020 reading relations for dependency 2 Sat Nov 21 05:03:42 2020 read 26076816 cycles Sat Nov 21 05:05:50 2020 cycles contain 85808718 unique relations Sat Nov 21 05:13:23 2020 read 85808718 relations Sat Nov 21 05:29:42 2020 multiplying 85808718 relations Sat Nov 21 10:06:16 2020 multiply complete, coefficients have about 6069.83 million bits Sat Nov 21 10:07:51 2020 initial square root is modulo 6410059 Sat Nov 21 15:01:19 2020 GCD is 1, no factor found Sat Nov 21 15:01:19 2020 reading relations for dependency 3 Sat Nov 21 15:01:27 2020 read 26077136 cycles Sat Nov 21 15:03:40 2020 cycles contain 85804702 unique relations Sat Nov 21 15:11:34 2020 read 85804702 relations Sat Nov 21 15:28:11 2020 multiplying 85804702 relations[/CODE] 
[QUOTE=ryanp;563981]LA on the c205 blocker done, onto the sqrt phase...
[CODE]... Sat Nov 21 10:07:51 2020 initial square root is modulo 6410059 Sat Nov 21 15:01:19 2020 GCD is 1, no factor found Sat Nov 21 15:01:19 2020 reading relations for dependency 3 Sat Nov 21 15:01:27 2020 read 26077136 cycles Sat Nov 21 15:03:40 2020 cycles contain 85804702 unique relations Sat Nov 21 15:11:34 2020 read 85804702 relations Sat Nov 21 15:28:11 2020 multiplying 85804702 relations[/CODE][/QUOTE] :popcorn: 
A4788 i12566 factored
Cracked it on the 4th dep.
[CODE]Sun Nov 22 01:22:50 2020 reading relations for dependency 4 Sun Nov 22 01:22:57 2020 read 26077789 cycles Sun Nov 22 01:25:15 2020 cycles contain 85796244 unique relations Sun Nov 22 01:33:14 2020 read 85796244 relations Sun Nov 22 01:49:31 2020 multiplying 85796244 relations Sun Nov 22 06:47:42 2020 multiply complete, coefficients have about 6068.95 million bits Sun Nov 22 06:49:21 2020 initial square root is modulo 6395869 Sun Nov 22 11:43:36 2020 sqrtTime: 143411 Sun Nov 22 11:43:36 2020 p84 factor: 612727101216841212852838132931420183159227670481704836048413322760603770006744226207 Sun Nov 22 11:43:36 2020 p121 factor: 3109568351255194772600345239390001448995931316250320993654548823052509790679152109713793122115796159590511967310967260973 Sun Nov 22 11:43:36 2020 elapsed time 39:50:12[/CODE] 
Is anyone working on the c165? If not I'm happy to give it a go.

[QUOTE=charybdis;564146]Is anyone working on the c165? If not I'm happy to give it a go.[/QUOTE]
Already on it :smile: It didn't yield with a good bit of ECM (B1=26e7), so just going straight to msieve now. 
All times are UTC. The time now is 06:12. 
Powered by vBulletin® Version 3.8.11
Copyright ©2000  2022, Jelsoft Enterprises Ltd.