C250_51119
 

Reserving C250_51119 for postprocessing.

[QUOTE=VBCurtis;454830]I'll take C204_19xx41_11 next from the 14e queue.[/QUOTE]

[url]http://pastebin.com/idNyTnjH[/url]

[code]prp96 factor: 270892972436863301491088297560979089306896792704053757187310273750945188048996014955337256552731
prp109 factor: 7398110844213426351156178245176066325401844989748252418726848842312135868770348721366318901478787377099591309[/code]
Density 120 failed to build, "too few cycles". 104 went fine, matrix was 6.4M.

[QUOTE=VBCurtis;455054][code]prp96 factor: 270892972436863301491088297560979089306896792704053757187310273750945188048996014955337256552731
prp109 factor: 7398110844213426351156178245176066325401844989748252418726848842312135868770348721366318901478787377099591309[/code][/QUOTE]

Oops, I posted the factors to FDB. I thought you forgot to but now I see you are just now posting your results. Not to worry because it wasn't already factored. I just posted your results.

RichD.

That would be my whoops- I haven't been posting factors to factorDB when I do LA for these. I just assumed that whomever posted the number for NFS@home would make use of the factors (posting to factordb, etc).
When I take care of that next time, do I just enter the composite and its factors? Am I supposed to enter it by its special form?
Thanks for fixing my oversight!

Reserving 98999_231.

Reserving C203_131_73

ETA morning of Wed 29 March

C201_142_80 done
 

[code]
Sat Mar 18 16:02:01 2017 p56 factor: 76781812120260810423674407357181398062050651121199975133
Sat Mar 18 16:02:01 2017 p145 factor: 1575832044789185624917451058628545230528037894576360337313677484823795502771030156103294778517895978910641633739908978700612507400990426935780317
[/code]

77 hours on 7 threads E5-2650v2 for a 13.1M matrix. Log attached and at [url]http://pastebin.com/ftSGyXDq[/url]

(fx: bites bullet; grimaces)

Taking C193_143_93. Anticipating it will take a couple of months.

[QUOTE=fivemack;455020]The last 33-bit job I did took nine weeks on a 32GB i7/5820K, which has two more cores and a significantly better memory subsystem, and is in a water-cooled desktop machine that ran unattended 24/7. It used more than 20GB of memory for the nine weeks.

I think probably you'd be biting off more than you can chew.[/QUOTE]

How long would you expect these to take on the Knight's Landing system?

[QUOTE=swellman;454831]I'll take C172_327668647153_19 once sieving is complete.[/QUOTE]

[code]
prp73 factor: 6054725637139677465720575881783390450522419160557268492512016879544214461
prp99 factor: 890014372026059848287884564136243757498233449579710863544205700586905490716551126205371524104139949
[/code]

Taking 50009_239.

98999_231 completed - 57 hours for 8M matrix (TD=100).

[CODE]prp68 factor: 50548077638013050674449920334613826410478457550085766773313566314799
prp164 factor: 19585314541328915857037914790116248844145263732064431396496806380255205386818063123590196977425504913668736401670190676558449880863734626182440940047477465657354801
[/CODE]

[URL]http://pastebin.com/Ghk4jKiv[/URL]

C250_51119
 

Would it be possible to run some additional sieving on C250_51119? I'm struggling to get the matrix to build. Than you.

[QUOTE=swellman;455430]Would it be possible to run some additional sieving on C250_51119? I'm struggling to get the matrix to build. Than you.[/QUOTE]

Another 25% queued up for C250_51119; should be a nice small matrix when that's done.

Thank you!

[QUOTE=fivemack;455171](fx: bites bullet; grimaces)

Taking C193_143_93. Anticipating it will take a couple of months.[/QUOTE]

There's some odd data corruption going on with C193_143_93; if I just use gunzip then it stops after 1126400417 decompressed bytes with

[code]
gzip: C193_143_93.dat.gz: invalid compressed data--crc error

gzip: C193_143_93.dat.gz: invalid compressed data--length error
[/code]

Thankfully gzrecover exists; the result from it is quite full of corrupt patches, but
[code]
egrep -a -e "^[0-9-]+,[0-9]+:[0-9a-fA-F,:]+$" msieve.dat > msieve.dat.clean
[/code]

cleans it up a bit. I don't think it can be getting damaged in transmission - I'm downloading over https, after all. Should be able to proceed regardless, it looks as if there are a billion clean relations there.

971403653 relations extracted from the mess, which ought to be at least enough.

[code]
-rw------- 1 butternut butternut 116913675673 Mar 25 19:21 msieve.dat.dirty
drwxrwxr-x 2 butternut butternut 4096 Mar 25 19:54 .
-rw-rw-r-- 1 butternut butternut 116427382571 Mar 25 22:09 msieve.dat
[/code]

C171_829332_3638 done
 

[CODE]Sun Mar 26 14:30:20 2017 p79 factor: 4843685974169739632744910538567557927140860815267546192531496599003306551398993
Sun Mar 26 14:30:20 2017 p92 factor: 29539171749160844389761491293297705439756128125719051613577858674887627806536615737860576393[/CODE]

235 hours on 6 threads i7-5500U with 8 GB memory for a 12.2M matrix. Log attached and at [URL="http://pastebin.com/KRyU70gW"]http://pastebin.com/KRyU70gW[/URL]

Total linear algebra time in log is not correct since Windows 10 rebooted my laptop without notice and I had to resume LA.

[QUOTE=richs;455539][CODE]Sun Mar 26 14:30:20 2017 p79 factor: 4843685974169739632744910538567557927140860815267546192531496599003306551398993
Sun Mar 26 14:30:20 2017 p92 factor: 29539171749160844389761491293297705439756128125719051613577858674887627806536615737860576393[/CODE]

235 hours on 6 threads i7-5500U with 8 GB memory for a 12.2M matrix. Log attached and at [URL="http://pastebin.com/KRyU70gW"]http://pastebin.com/KRyU70gW[/URL]

Total linear algebra time in log is not correct since Windows 10 rebooted my laptop without notice and I had to resume LA.[/QUOTE]

I forgot to attach the log.

Taking C184_128493601339_19 (should be done morning of 30 March)

Apologies: I clearly queued much too long a range for these smaller numbers. My trial sieving for this one gave
[code]
total yield: 8763, q=67003007 (0.06473 sec/rel)
[/code]

so I submitted a 75M range because that's about 2.9 relations per Q, but in reality we're getting something more like 4.1 per Q. Should sieve wider and in more places; algebraic-side trial sieving tends to be a lot noisier because you have the distribution of number of factors of the polynomial mod the special-Q in there.

Am redoing the trial sieving for C186_290770486991_19 while there's still time.

In fact it looks as if I significantly underestimated for 290770486991_19:

[code]
total yield: 17862, q=20010017 (0.10909 sec/rel)
total yield: 15093, q=55010003 (0.14041 sec/rel)
total yield: 14095, q=90010001 (0.17114 sec/rel)
total yield: 12512, q=125010001 (0.18693 sec/rel)
total yield: 10248, q=160010017 (0.20706 sec/rel)
[/code]

so I've extended the range to Qmax = 200M

12119^59-1 factored
 

[CODE]p107 factor: 10329208212582399634808891595944836113335489674780840247213091032845864562719921554023138577244641331712171
p131 factor: 67149435014392876508467707186162955093682179712591315153822029813642280539201757023866266261058839230988863188717489138620951052251[/CODE][URL]https://pastebin.com/fgDqDGTx[/URL]

C203_131_73 done
 

[code]
p81 factor: 965722132867000950989699789748993364385596290489044053288147123870874663340499939
p122 factor: 11194609567164978652776262818053528467161821996401069106470040114751282840768941961597440111421754078962194625450730490707
[/code]

104.2 hours on 7 threads E5-2650v2 for 14.4M matrix at density 120 (not enough relations for density 125). Log attached and at [url]https://pastebin.com/k6hjvC5U[/url]

50009_239 completed - 95 hours for 10.6M matrix (TD=100).

[CODE]prp55 factor: 2663984116560283462723906287447909666071595033259154603
prp75 factor: 202257618857795192716689629824310560603735718078120890663551311812708712347
prp110 factor: 92796903175073991321555147968618241117717774771484946314878796558802615590903089266791593290401437884164453249[/CODE]

[url]https://pastebin.com/HGSCp9xB[/url]

125!+1
 

[URL="http://www.factordb.com/index.php?id=1000000000002850149"]125!+1[/URL] is fully factored.
[CODE]Wed Mar 29 08:33:07 2017 p65 factor: 12486125316891001428616702841115249206283344899084647430865206483
Wed Mar 29 08:33:07 2017 p120 factor: 400092108180598088561349278715129263247581750427829472797160401223959480591482644480979572126457996424971659568976357919
[/CODE]LA for a 20.75e6 matrix took 390.8h using 6 threads on Core i7-5820K.
Log attached and at [URL]https://pastebin.com/ihcJtiJe[/URL].

Good job!

C184_128493601339_19 completed
 

[code]
Wed Mar 29 23:42:16 2017 p81 factor: 302821701457903907358879006011114703979279525778157198492208138552158071693867537
Wed Mar 29 23:42:16 2017 p103 factor: 7331773724102037673883839726243565072141926194854919299688976071380695991419314373169252628607790572307
[/code]

11.7 hours for 4.83M density-140 (145 didn't work) matrix on seven cores E5-2650v2. Log attached and at [url]https://pastebin.com/HsCarrxB[/url]

Taking C178_187039475551_19

Reserving C186_290770486991_19.

[QUOTE=fivemack;455769]Good job![/QUOTE]

Thanks. I was expecting a smaller matrix though; I thought I would be able to
build a matrix with a much higher target density given the 460M+ relations for
a 32-bit job but even 132 failed, I had to lower it to 128.

I'll take 127^95 + 95^127 cofactor from the 14e queue.

C178_187039475551_19 done
 

[code]
Sat Apr 1 11:45:02 2017 p86 factor: 59969606437825471092748609807267089171442385775453880240834192297102407276550682363249
Sat Apr 1 11:45:02 2017 p92 factor: 28161118831265144175724429817967381635120122727242283196157680376868720112151713622855853951
[/code]

13 hours for 5.75M density-120 matrix on 8 threads E5-2650v3

Log at [url]https://pastebin.com/iaTHLyUC[/url] or attached

Taking C203_125_96 (ETA Monday morning, since the linear algebra should finish just after going-home time on Friday)

Taking C202_134_87 (15e)

22.8M density-120 matrix, ETA sometime in the week after Easter

Reserving C237_12161_59 (14e)

[QUOTE=VBCurtis;456003]I'll take 127^95 + 95^127 cofactor from the 14e queue.[/QUOTE]

I forgot to add target_density to the command line, and produced a 21.8M matrix at default density. I re-ran the filtering with TD = 140, and produced the identical matrix!

I realized that meant the dataset was oversieved, so I reduced to 470M relations (from initial 495M) and ran again. This produced a 20.4M matrix at density around 100; reducing to 450M rels produced 19.7M matrix at density 125. This matrix is forecast to take 80-100 hr longer than the original matrix, so I'm solving a 21.8M matrix at density 67, forecast to take 25 days or so.

Matrix-building took 8005MB, while the solving step is logged at 6500MB while top claims 7.6g used.

[QUOTE=fivemack;455171](fx: bites bullet; grimaces)

Taking C193_143_93. Anticipating it will take a couple of months.[/QUOTE]

39.06M matrix at density=128 started on 6 threads i7-5820K, ETA about six and a half weeks from now (second half of May)

C203_125_96 done
 

[code]
Fri Apr 7 10:30:05 2017 p60 factor: 262140789711545872971063685147422871988451144802929070574027
Fri Apr 7 10:30:05 2017 p71 factor: 56035791901525658273230054058046999996742343570248151591987937037637071
Fri Apr 7 10:30:05 2017 p73 factor: 1202663914264836729954659180323840975151179663082897780688670921683426083
[/code]

63 hours on 7 threads E5-2650v2 for 11.1M density-120 matrix (not enough relations for density-125)

Log attached and at [url]https://pastebin.com/1tVttxqP[/url]

[QUOTE=VBCurtis;456280]I forgot to add target_density to the command line, and produced a 21.8M matrix at default density. I re-ran the filtering with TD = 140, and produced the identical matrix![/quote]

That distinctly surprises me; can I see the relevant bits of the log? Remember that
[code]
msieve -v -nc1 -t 6 target_density=140
[/code]
runs with target density [b]70[/b]; the target_density needs to be right after the -nc1

Attached is the log from TD=136; I deleted the log from the original no-density-set run, but the matrix was the same size to 4 sigfigs. (I forgot the TD = 140 runs were with the relations file truncated, not sure why I tried 136 first)

Interesting: so much over-sieving that the remaining cycles were very light. I didn't know that could happen. Thank you.

Taking C203_132_83

[QUOTE=richs;456183]Reserving C237_12161_59 (14e)[/QUOTE]

Since my reservation has not shown up on the 14e status page, just a reminder that I will be downloading the relations when they complete soon.

[b]fivemack[/b]: sorry for the omission, the reservation has been inserted

C186_290770486991_19 completed - 61 hours for 8.7M matrix (TD=140).


[CODE]prp93 factor: 150439732626969761986330690056970259714353117122410952773267829152146312696348867088231317079
prp93 factor: 740845168441870684384902125736351384779286997262301911427594857947914931324509223013796294481
[/CODE]

[url]https://pastebin.com/aBxDAWaL[/url]

I'll take C238_12301_19 next.
Which is really 12301^59-1.

137^62+62^137 factored
 

[code]
prp92 factor: 59915134378056696732367932276503084510388450809160673947455647072742315394579939431345569751
prp109 factor: 4726536549082114298263832049813671703961650884878966776267592873481393429447689989176410105408788931466415019
[/code]

13*2^793-1 factored
 

[code]prp84 factor: 218733177161231832966771125073991586700926578295329737721842253100215814271723769489
prp109 factor: 1122189132526495094389696806443711604583514165950135489327269050120777398921647097444353689166948241335034811[/code]
I test-sieved with the incorrect skew, so actual yield was well over my estimate, leading to oversieving. I filtered with 406M rels and TD =140, and "matrix not dense enough, retrying" led to a 9.96M matrix of density 67.

Log at [url]https://pastebin.com/iVdp0JtX[/url]

For once, I remembered to post factors to factordb.

142^67+67^142 (15e)
 

Reserving 142^67+67^142. I'll download in a few days.

Does it appear to have enough relations to build a matrix?

C238_12301_19 (aka 12301^59-1) factored
 

84 hours to solve a 10.8M matrix, -t 4, w/ TD=128.
[CODE]p66 factor: 306429441119212982842160094679500662234521592175004993998537169117
p172 factor: 5373399008907437443111523249428629587116534769141955817762052772664564995799203197079637125948336534748396015219065752233860621512112226157563812238766474000931184842407627[/CODE]
[url]https://pastebin.com/C6qLf5fM[/url]

I ran msieve on C237_12161_59 (log attached) and when the full merge process is reached, msieve goes dormant. By dormant, task scheduler shows about 0.3% cpu usage with 5+ Gb memory with the amount of memory varying every refresh. With the prior number that I ran, full merge took less than 10 minutes. Perhaps not enough memory? Running Windows 10 with 8 Gb memory.

Any advice would be appreciated.

I've had this same thing happen and it seemed to be insufficient memory. Going to another machine with more memory solved the problem, though you could try to rerun with TD=100 or 110 just to try to build the matrix. Or sieve more relations(?).

When this happened to me, I let msieve run for well over a week until full merge finally completed. The time to sieve estimate was measured in years!

C203_132_83 done
 

[code]
Fri Apr 21 13:23:57 2017 p68 factor: 69850751451692983626652885615515723472011733874399458655606950777087
Fri Apr 21 13:23:57 2017 p135 factor: 653748673101791536278347326477209219516452170215871376896498224735082845923886366677483702388290438325532576068540665597626205444877929
[/code]

91.8 hours on 6 threads i7/4930K for a 13.85M matrix at density 108 (120 didn't work).

Log attached and at [url]https://pastebin.com/nLdwpBdB[/url]

I had to run the linear algebra twice - on the first attempt it solved the matrix but every relation produced an 'error: relation 166785513 corrupt' or 'error: relation 185807891 corrupt' message at the square root phase, except one that produced the error 'algebraic side is not a square'. I did delete lines 166785513 and 185807891 from the file before repeating, but neither had anything visibly odd about it.

[QUOTE=richs;457186]I ran msieve on C237_12161_59 (log attached) and when the full merge process is reached, msieve goes dormant. By dormant, task scheduler shows about 0.3% cpu usage with 5+ Gb memory with the amount of memory varying every refresh. With the prior number that I ran, full merge took less than 10 minutes. Perhaps not enough memory? Running Windows 10 with 8 Gb memory.

Any advice would be appreciated.[/QUOTE]

The good news is that booting Windows 10 in safe mode to a command prompt and setting target density = 70 allowed the full merge to proceed. The bad news is that the linear algebra ETA is 18+ days.

I'll take C206_149xx041_13 next.

I will be relocating this box so the post-processing might be piecemeal.

C202_134_87 done
 

[code]
Tue Apr 18 19:55:53 2017 p87 factor: 298893797632505694369365366807674889411602696800624949866982229091912376171341334516301
Tue Apr 18 19:55:53 2017 p115 factor: 4095794635032719428105910461099175067710721384082052133754787896001385421174172773504078872241406037617843306535607
[/code]

(but I was on a training course last week and only got to see this computer again today)

271.1 hours for 22.8M density-120 matrix on 7 cores E5-2650v2.

Log attached and at [url]https://pastebin.com/Rze8g393[/url]

Taking C187_142_67
 

Taking C187_142_67

C250_51119
 

[code]
p54 factor: 159790103673140365135029060471459644167485842180777189
p197 factor: 31986405876337473667915871421471627616138122756251708646798873692125179282754424937563555845773902840234802484347893904745362282712769989163180104828654450774930325076753204879388780056993644766371
[/code]

Please report it to near-repdigit project here: [URL]http://stdkmd.com/nrr/c.cgi?q=51119_249[/URL]

[QUOTE=unconnected;457385]Please report it to near-repdigit project here: [URL]http://stdkmd.com/nrr/c.cgi?q=51119_249[/URL][/QUOTE]

Done. Also reported it to factirdb earlier.

[QUOTE=fivemack;457377]Taking C187_142_67[/QUOTE]

I had [url=http://www.mersenneforum.org/showpost.php?p=456861&postcount=1891]reserved this a few days ago[/url], but I haven't downloaded it yet so I'll just grab another.

Reserving C207_128_91.

I'll take C209_122_107 next. See if I can get it to fit in 14GB.

C206_149xx041_13 factored
 

66 hours to solve a 9.0M matrix, -t 4 w/ TD=116.

[CODE] p90 factor: 103289100927226855348651712368271260727605651089053239229403895613327326629616950612527039
p117 factor: 867129439516689623417853225773293001126804579977825603457611201858794195583226993604648808331467328679296069406587861[/CODE][URL]https://pastebin.com/N4u3szXx[/URL]

I'll try a 15e task: Taking C187_141_61.

[QUOTE=RichD;457543]I'll take C209_122_107 next. See if I can get it to fit in 14GB.[/QUOTE]

By reducing the rels I finally got a matrix build (20M) with TD=140. ETA is 400 hours which sounds about right on a Core-i5.

C191 from 3408:1668
 

What happened to C191 from aliquot sequence 3408 step 1668 in the 15e queue? Something seems amiss - the server appears to have stopped sending out work units.

[QUOTE=swellman;457838]What happened to C191 from aliquot sequence 3408 step 1668 in the 15e queue? Something seems amiss - the server appears to have stopped sending out work units.[/QUOTE]

Both 14e & 15e queues have stopped "pushing" out new WUs. No new WUs are being generated for some unknown reason.

Reserving 'C191 from aliquot sequence 3408 step 1668' on 15e, once it is fully sieved.

xyyx_127_95:

[code]prp91 factor: 3039948264272288301611029524578747829969639925202742966513963342037706755626693142894045237
prp106 factor: 1004824826460417603761298005812200243156572714036012054906241114361139425496143334279583118653306006054191[/code]
21.8M matrix of density 70; target-density was set to 130, but oversieving meant this was the best I could do. I tried reducing relations in the file to get a higher density, but longer expected-solving-times resulted.

Log: [url]https://pastebin.com/RZVRCh7j[/url]

Also, post #1890 contains the factors for 13_2_793m; it can be removed from the 14e queue list.

[QUOTE=RichD;457913]Both 14e & 15e queues have stopped "pushing" out new WUs. No new WUs are being generated for some unknown reason.[/QUOTE]

It's a problem with stats or work generator is broken? There are no "Unsent" WU's and only few hundrends "Pending".

Reserving C209_125_122.

C187_142_67 done
 

[code]
Fri May 5 17:37:03 2017 p74 factor: 58945606651182881158177609712621497713164795987881317683830327995837024053
Fri May 5 17:37:03 2017 p114 factor: 120931152532234170860142533632955923113194434000312645802634590708268559862072303329218061824356746123179353778241
[/code]

About 204.8 hours for 19.56M matrix with density 134 (not enough relations for density 142) on 7 cores E5-2650v2.

Log attached and at [url]https://pastebin.com/QDkkKNZv[/url]

C207_128_91
 

[code]
p76 factor: 2104400641638418732161148213874935246503471151069131875331519904774093542083
p132 factor: 381258622689269270014940251648100228906098113021530710463135832777112161682637662164232535448658411292505423097441595867599495626361
[/code]


ETA - C198_144_122 should be factored in another week.

It looks like the following (in 14e) could use a little touch up.
#5 C209_127_91
#6 C185_86353_47
Perhaps adding a few more relations might knock the pushing process free...

xyyx_141_61:
[code]prp51 factor: 103581129954480715888284312134975059043823167842387
prp93 factor: 465441408610195152978409573368582899565889795855005284538006576682006326753270532082937121363
prp95 factor: 10924015260586771894003417327483390507891781363086866127690026847348444793280618826615416068671[/code]

Matrix was 11.95M at TD 136. Log at [url]https://pastebin.com/Jfqwub0z[/url]

C237_12161_59 done
 

[CODE]p102 factor: 212521180579312214923777011904149185984152106900688611330639560978673699348260297453655753707038451597
p136 factor: 3988891517097975428705878952376639961424601247357370668721511377719041062415508159449541471386037063789488561095673680410486242600340327[/CODE]

394 hours on 8 threads i7-5500U with 8 GB memory (booted in Windows 10 safe mode for max memory) for a 13.9M matrix at TD = 120. Log attached and at [URL="https://pastebin.com/bvxEy5mg"]https://pastebin.com/bvxEy5mg[/URL]

Taking C209_127_91 (ETA probably 18th May)

It looks as if the pipes are unblocked and the relations are flowing again

C185_86353_47
 

Any chance the number of relations for C185_86353_47 could bumped a touch? I'll reserve the number now, just not sure a matrix can be built under current conditions.

C198_144_122 Factored
 

[code]
prp85 factor: 1127813795918176938063649634490900657837795126452856579311732051911454407486004045809
prp114 factor: 422754548237181745790644622950147691920227435009652673860949250131038033136404953384819260829690966102622207188721
[/code]

C209_122_107
 

[QUOTE=RichD;457717]By reducing the rels I finally got a matrix build (20M) with TD=140. ETA is 400 hours which sounds about right on a Core-i5.[/QUOTE]

Sometime during the first week I encountered a data corruption issue in LA. Unbeknownst to me the machine sat idle for several days. Luckily I was able to resume from a backup copy.

Now it looks like it will finish the day after I leave town. Therefore, I won't get the factors posted until I get back on 21 May. Less than 100 hours remaining and everything seems OK.

Can i reserve 252^79-1 and 252^83-1?
Pre-thanks

[QUOTE=vasyannyasha;458830]Can i reserve 252^79-1 and 252^83-1?
Pre-thanks[/QUOTE]


You're welcome to, but I'm a bit unsure why you're asking here ... they don't seem to be being sieved by NFS@home.

C183_705670360649_19
 

Reserving C183_705670360649_19. Thank you.

[QUOTE=fivemack;458847]You're welcome to, but I'm a bit unsure why you're asking here ... they don't seem to be being sieved by NFS@home.[/QUOTE]
Sorry i didn't understand at first time.
Sorry for my offtopic

Status update of reservations
 

144^122+122^144 C198 factors were reported in [url=http://www.mersenneforum.org/showpost.php?p=458811&postcount=1921]post 1921[/url]

C207_128_91 factors were reported in [url=http://www.mersenneforum.org/showpost.php?p=458396&postcount=1915]post 1915[/url]

My other 3 reservations should finish in the next 2-15 days.

And just repeating [url=http://www.mersenneforum.org/showpost.php?p=457931&postcount=1910]my reservation[/url] for C198_3408_1668 (15e). Thank you.

C185_86353_47
 

[code]
prp76 factor: 1102975017312984001136928782423493604379731321904835019203011609215082493101
prp110 factor: 25792914579154324770957097063633149074250390336972563340984862069746114775053653953490248295701584547610789083
[/code]

C209_127_91 complete
 

[code]
Fri May 19 04:54:43 2017 p57 factor: 956257561729453200409167605453187777865060270080835682657
Fri May 19 04:54:43 2017 p152 factor: 28173367133049314855263237494718485895578329861091925462979568706643502909839770588123678982802052916886528695118505759234965658975616787096537668536969
[/code]

155.3 hours for 17.6M density-114 matrix on 7 cores E5-2650v2

Log attached and at [url]https://pastebin.com/Xj5txg4C[/url]

Reserving C210_135_71 (eta morning of Monday 29 May)

Reserving 131^69+69^131 C202 cofactor (15e).


The C191 from aliquot sequence 3408 (step 1668) must wait for my big machine to finish its current task, around June 1st.

C209_122_107 factored
 

After a couple interruptions and a little over 400 hours to solve a 20.7M matrix, -t 4 w/ TD=140, we have the factors.
[CODE]p57 factor: 319438772661490666285422689359960796594107863047504979977
p73 factor: 8033621205469315346952222695812930747566951306504432271961628575244213559
p80 factor: 17766529723764173728868700659919679984113284354527699251818521136703580914646207[/CODE][URL]https://pastebin.com/f2jWVt0R[/URL]

C193_143_93 finally done
 

[code]
p65 factor: 19689114812096575020410808275022771112267200142919345821782522589
p129 factor: 100709446869075805052224236705696112233958098610845255888252287228214441381874886498464034990758653729011776134762119677093496783
[/code]

1137.8 hours for 39.06M matrix at density 128 on 6 threads i7/5820K; about 20 gigabytes memory used. The largest GNFS matrix I've done.

Log attached and at [url]https://pastebin.com/fC0E5T0z[/url]

I'll take 134^116+116^134 next.

Taking C208_147_50 (ETA now morning of 1 June)

I'll take C211_125_112 though it could probably use a few million more relations. It's actually a 32-bit job (the 14e status page erroneously lists 30-bit).

I've pushed another 32MQ for C211_125_112 and put Sean's name on it, also updated the difficulty and the LP number.

Thank you!

I'll take C197_128341_47 next, when my other job finishes.

[QUOTE=swellman;459064]Reserving C183_705670360649_19. Thank you.[/QUOTE]

[code]
prp84 factor: 161052706284719650329996902963864740993552991595503166339196904235547165596571760941
prp100 factor: 2186356753015951430721449081038862987022989669440943368066698955647372529211053449065269623342365527
[/code]