3381863410579^19-1 factored
 

226M total relations - 191M unique relations built a 5.9M matrix using TD=128.
[CODE]p74 factor: 70447738103044046265402101002783384230759655161833776518411774857295178219
p90 factor: 551626815738739430462075655548040459968689233568387776104952782250110880383972668934397617[/CODE]
[url]https://pastebin.com/yW7hGqJm[/url]

[QUOTE=richs;481955]Reserving Phi_3(Phi_29(14401)/59/523/3065713912035839) on 14d. I searched the thread so hopefully I'm not stepping on anyone's toes as I did last time reserving.[/QUOTE]

Would someone please advise what the data filename is for this number? Thanks!

Check here, QUEUED AS C163_287xxx323_3.

[url]http://www.mersenneforum.org/showpost.php?p=481543&postcount=1362[/url]

[QUOTE=pinhodecarlos;482540]Check here, QUEUED AS C163_287xxx323_3.

[url]http://www.mersenneforum.org/showpost.php?p=481543&postcount=1362[/url][/QUOTE]

Thanks, Carlos.

I'll take C209_96656723_29?

It also looks like there's a bunch of completed assignments still listed on 14e, hopefully those can be cleaned up soon?

Reserving C159_112xx041_17 ( Phi_17(Phi_5(8970971)/5/11/811/12926572181)).

L3095B done
 

[code]
p69 factor: 200616174261045380953621201426386272677157528816538376326238169331061
p121 factor: 1778492715631515922914765757230309139024813430686801919766975780249661754913993641823995604337751591968366572504523817911
[/code]

339.7 hours for 21.49M density-150 matrix (152 didn't work) on 6 cores i7/5820K.

Log attached and at [url]https://pastebin.com/3VpzCWRn[/url]. Marin informed.

C180_144_55

[code]
prp77 factor: 90441663540371126567171186663549836803322333932255096803454492125356946403917
prp103 factor: 1300118608837904116911153981020833608617283780543085127305468219720558953367555366260695652382331157701[/code]

460M raw / 378 unique with TD=130.

I'll take L1474 from the 15e queue.

[QUOTE=richs;481955]Reserving Phi_3(Phi_29(14401)/59/523/3065713912035839) on 14d. I searched the thread so hopefully I'm not stepping on anyone's toes as I did last time reserving.[/QUOTE]

aka C163_287xxx323_3

[CODE]p73 factor: 8944395035504412195363202429602893157674179352698250145641615784216359557
p90 factor: 591611906376559950021898338640249645342108156939855733434266266209559708200076815130760157[/CODE]

Approximately 81.5 hours on 2 threads Core i3-2310M with 4 GB memory for a 7.06M matrix at TD = 70 (didn't bother to try any higher densities).
Log attached and at [URL="https://pastebin.com/MhfDmKnz"]https://pastebin.com/MhfDmKnz[/URL] .

I had an interesting time getting the square root phase to work. Dependency 2 kept shutting down msieve without any error message. I had to use the option dep_first=3 to skip the offending dependency and the factors were found on dependency 7.

140^67+67^140 C234
 

[code]
p100 factor: 2393343733451590722259482493678734131523597811223818103668668041580319264769891398226604621573704267
p134 factor: 97320272295827767175291574901990492386000852701752891451088007424570901938689120564462838933427372271751383795175708848355960475140837[/code]

217M unique relations (had to run remdups and raw data not recorded)

C237_136_71 done
 

[code]
Wed Mar 21 08:35:50 2018 p92 factor: 14262898211782331411245660962786399464632888536608100707086951288573864282757203176651215249
Wed Mar 21 08:35:50 2018 p146 factor: 15906102574164088787823317716585575941681355581161063536784424112861552843488713180273746081037738362183650525609870661365092348166885420461993877
[/code]

About 237.1 hours on seven cores E5-2650v2 for 20.99M matrix at density 120 (122 doesn't work); log attached and at [url]https://pastebin.com/YmsWcvGV[/url]

Taking L2088 (bother, I forgot to specify sieving on the algebraic side, so this is going to need a lot more sieving :( ) ETA 15 April

I ought to have some quite exciting hardware arriving in the next week or so, so:

Taking C195_3366_2180

Taking C205_924xx521_5

Taking [B]C163_151_45[/B]

C166_11040_10075 completed - 67 hours for 8.6M matrix with TD=130 (8 threads on heavily loaded Xeon E5-2620).

[CODE]prp79 factor: 2473884612399644129627016832668714711326346419680862876245348902160039604158417
prp88 factor: 1031522037589097740137924533983344395641777997938994569813928453373730557023684074534471[/CODE]

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

I’ll take 131^98+98^131 C253 cofactor from the 15e queue.

C163_151_45 factors
 

[B]C163_151_45[/B]

[code]Sat Mar 24 18:50:36 2018 p51 factor: 348010296756513495867714654936424379370686801942773
Sat Mar 24 18:50:36 2018 p112 factor: 7183207721805977218696163044312195192711577852021127362209575912953870472360267091994509183354814160849368652793[/code]reported to factordb
log attached and at [URL]https://pastebin.com/5dwGxxhv[/URL]

Taking [B]C184_2561074343_23[/B]

[QUOTE=VictordeHolland;483293][B]C163_151_45[/B]

[code]Sat Mar 24 18:50:36 2018 p51 factor: 348010296756513495867714654936424379370686801942773
Sat Mar 24 18:50:36 2018 p112 factor: 7183207721805977218696163044312195192711577852021127362209575912953870472360267091994509183354814160849368652793[/code]reported to factordb
log attached and at [URL]https://pastebin.com/5dwGxxhv[/URL][/QUOTE]

Thanks for postprocessing this. For the record, this composite survived a full t50 and a few thousand curves at B1=11e7. Just an ECM miss.

Well, that was quick (C205_924xx521_5)
 

Checked this morning to see no msieve process running, and worried that something had gone wrong over the weekend.

No: just a smaller calculation than usual

[code]
Sun Mar 25 08:50:58 2018 p81 factor: 117068787300033044736428424227985090707910880617997445489570318815773167686484011
Sun Mar 25 08:50:58 2018 p125 factor: 11307777485970671098596844039701033355042156352707480587614217626888132952922108745150575335996885242429349447562228265253451
[/code]

22.6 hours on 7 threads E5-2650v2 for a 7.45M matrix at density 118 (120 didn't work); log attached and at [url]https://pastebin.com/iwcSYLUP[/url]

[QUOTE=richs;482729]Reserving C159_112xx041_17 ( Phi_17(Phi_5(8970971)/5/11/811/12926572181)).[/QUOTE]

[CODE]p73 factor: 2377229501564202380185377402029843680790840853443429674992790329433103753
p87 factor: 238526856148433848590038165723401372269102319949840516175967217826620328021495986904979[/CODE]

Approximately 48.3 hours on 2 threads Core i3-2310M with 4 GB memory for a 5.16M matrix at TD = 70 (didn't bother to try any higher densities since this one was way overseived).
Log attached and at [URL="https://pastebin.com/HqWcSKrp"]https://pastebin.com/HqWcSKrp[/URL]

Factors reported to Factor Database.

Reserving Phi_13(largest factor of Phi_11(307))

Taking Phi_3(Phi_5(Phi_5(Phi_3(Phi_5(3169)... or as C166_755xx481_3.

F1361 done
 

[code]
Tue Mar 27 00:23:19 2018 p113 factor: 20995139466312587159317938366832384654914653183905279911839059366287714413182875106049817053859820646711395390373
Tue Mar 27 00:23:19 2018 p145 factor: 3205171737571430555197104058100472762459683617423402162591435679651063298594747598473493591620758556786285116856829106209696515488224765308651337
[/code]

751.4 hours for a 39.15M density-116 matrix on 16 cores E5-2650v1

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

134^85+85^134 (15e) factored
 

248M total relations - 187M unique relations built a 16.66M matrix using TD=124.
[CODE]p89 factor: 58498023260379625816458590300541278712900707832147331880123129936097760386669321608432039
p160 factor: 5868540836099251731112430920085226483660721540868821472337790065494737498389359310736548783220721687783748119496948762613329888969861679474112382217073005186819[/CODE]
[url]https://pastebin.com/Dpj5xkwB[/url]

C166_755xx481_3 factored
 

273M total relations - 221M unique relations built a 6.2M matrix using TD=132.
Solve time a little over 25 hours on i5-2500K. (-t 4)
[CODE]p57 factor: 908948203090395578692532810260830174569923051851734370823
p109 factor: 1548912886477388999504122855235366357473723632034188260317526398862262976215754539938905149699658549058724469[/CODE]
[url]https://pastebin.com/Dfk29xi6[/url]

131^98+98^131 C253 cofactor seems stuck. All columns up to “Pending” keep increasing but nothing received.

Not sure what needs kicking but something seems not quite right. Greg issue?

Taking C175_142_130

[QUOTE=swellman;483718]131^98+98^131 C253 cofactor seems stuck. All columns up to “Pending” keep increasing but nothing received.

Not sure what needs kicking but something seems not quite right. Greg issue?[/QUOTE]

Looks like a missing space in the polynomial file has caused the .ini file not to be constructed. Resubmitted.

[QUOTE=fivemack;483746]Looks like a missing space in the polynomial file has caused the .ini file not to be constructed. Resubmitted.[/QUOTE]

Odd that space but thank you for correcting it.

[QUOTE=swellman;470027]Houston, we have a problem. Acting on Fivemack’s expert advice, I finally got the above procedure to work on my Win 7 box (via Cygwin) and it chewed on the file for less than 10 minutes. The uncompressed “dirty” file was 72Gb, the new clean data file was 2.4 Gb. Feeding it into msieve revealed barely 20M relations residing in the data file, and filtering quickly terminated. :max:

Either I need something else in my egrep syntax, or that data file is in bad shape.

Where to go from here?[/QUOTE]

You need the -a parameter on egrep, otherwise it will stop as soon as it notices obviously non-textual data in the file and the output will end simply 'binary file msieve.dat matches'. Discovered that just now when filtering 3366.2180

C184_2561074343_23
 

[B]C184_2561074343_23[/B]

[code]Fri Mar 30 16:44:41 2018 p53 factor: 36823751901299849981177338945600920395238140969108603
Fri Mar 30 16:44:41 2018 p131 factor: 35913260077952154026013589282451074388808485347910818505391897536081058218127695406981615933226593632444124941260920655311461857637[/code]Factors uploaded to factordb, log attached and at [URL]https://pastebin.com/rB0Upy8q[/URL]

Taking [B]C191 from Phi_5(largest_factor(Phi_23(1009)))[/B]

C195_3366_2180 progress
 

[code]
weight of 64591916 cycles is about 4521521435 (70.00/cycle)
[/code]

:busy:

I've thrown it back for another two hundred million raw relations

Taking L2675A

Reserving 134^73+73^134 C177 cofactor (corrected run) on 15e

C191 from Phi_5(largest_factor(Phi_23(1009))) update
 

Filtering with TD=120, 110 and 100 failed (I might have been a bit too optimistic)
But TD=90 produced a very do-able matrix:
[code]linear algebra completed 298470 of 13431670 dimensions (2.2%, ETA 125h42m)[/code]So it should be done in about a week.

Taking L2675B.

[QUOTE=richs;483487]Reserving Phi_13(largest factor of Phi_11(307))[/QUOTE]

Would someone advise the file name for this number?

[QUOTE=richs;484077]Would someone advise the file name for this number?[/QUOTE]

C160_121xx489_13

[url]http://factordb.com/index.php?id=1100000000438409779[/url]

[QUOTE=Dubslow;484078]C160_121xx489_13

[url]http://factordb.com/index.php?id=1100000000438409779[/url][/QUOTE]

Thanks!

C175_142_130 done
 

[code]
Sat Mar 31 20:01:27 2018 p74 factor: 31385354670252938118137178159977347002159115861342009985929607668205148337
Sat Mar 31 20:01:27 2018 p102 factor: 101041274711379918015388649284935418065955210203057095077048646066189525639242071747471956420250856973
[/code]

33.1 hours on 7 threads E5-2650v2 for 7.97M matrix at density 146 (148 didn't work).

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

Taking C191_139017523_29, ETA morning of Thursday 12 April

C217_67411_47
 

As long as nobody has previously asked for C217_67411_47 & It's not going to run for hundreds of hours on a 5960 X with 16 gig of RAM I also use for other things so it would probably need to fit in 9 gig tops I would be interested in taking. Thanks

[QUOTE=fivemack;484119]Taking C191_139017523_29[/QUOTE]
Isn't that the same as?:
C191 from Phi_5(largest_factor(Phi_23(1009)))
Which I reserved on the previous page?

[QUOTE=VictordeHolland;484142]Isn't that the same as?:
C191 from Phi_5(largest_factor(Phi_23(1009)))
Which I reserved on the previous page?[/QUOTE]

Not really, your number doesn't have a Phi_29 in the chain.

[QUOTE=VictordeHolland;484142]Isn't that the same as?:
C191 from Phi_5(largest_factor(Phi_23(1009)))
Which I reserved on the previous page?[/QUOTE]

No, that number is C191_279xx283_5

[QUOTE=Speedy51;484124]As long as nobody has previously asked for C217_67411_47 & It's not going to run for hundreds of hours on a 5960 X with 16 gig of RAM I also use for other things so it would probably need to fit in 9 gig tops I would be interested in taking. Thanks[/QUOTE]

Anything from the 14e queue should fit in 10GB and finish in less than 2 weeks. If you dodge the candidates with the largest assigned Q-range, you should be under a week and under 8GB. Matrix difficulty on 14e roughly correlates to Q-range sieved.

For example, I'm doing a GNFS-186 from the 15e queue, which fits in 9GB and will take 400hr running on half a 6-core i7. That's bigger than any job you should encounter on 14e.

Phi_3(Phi_5(Phi_5(Phi_3(Phi_5(3169)/5)/78049/22216443433)/1404522989938741)/5)/4052089 has been completed. I inadvertently used the file name in the title instead of the longer queue name [url=http://www.mersenneforum.org/showpost.php?p=483706&postcount=2549]here[/url].

[QUOTE=fivemack;484151]No, that number is C191_279xx283_5[/QUOTE]
Sorry for the confusion!

The filename after the Cxxx for the Phi numbers confused me (I didn't make the connection with the digit representation). I now realise they refer to the first and last digits and the exponent is after the underscore...

So [B]279[/B]45714132675033142899109225439212386442031501005140[B]283[/B]^[B]5[/B]-1
becomes
279...283_5

I admit it, I'm a morron :bangheadonwall:

[QUOTE=VictordeHolland;484168]Sorry for the confusion!

The filename after the Cxxx for the Phi numbers confused me (I didn't make the connection with the digit representation). I now realise they refer to the first and last digits and the exponent is after the underscore...

So [B]279[/B]45714132675033142899109225439212386442031501005140[B]283[/B]^[B]5[/B]-1
becomes
279...283_5

I admit it, I'm a morron :bangheadonwall:[/QUOTE]

Don't feel bad, I also ask what the file name is each time.

[QUOTE=VBCurtis;484164]Anything from the 14e queue should fit in 10GB and finish in less than 2 weeks. If you dodge the candidates with the largest assigned Q-range, you should be under a week and under 8GB. Matrix difficulty on 14e roughly correlates to Q-range sieved.

For example, I'm doing a GNFS-186 from the 15e queue, which fits in 9GB and will take 400hr running on half a 6-core i7. That's bigger than any job you should encounter on 14e.[/QUOTE]
Thanks for the insight. How long do you think a 20 – 100 M will take say on 8 cores?

I would just like to correct my above post it is 20 – 110 M

3 days? Perhaps less. Try it and report back:
1. The number of relations and target density you used.
2. The size of the matrix (you can round to nearest 100k, or not)
3. The number of hours the solution took.

If you look through this thread (e.g. post #2565), you'll get a pretty good idea of what some previous 30-bit or small 31-bit projects took to solve. With an 8-core, you might break 50 hours for the matrix-solve step.

L2675A done
 

[code]
Wed Apr 4 10:45:54 2018 p58 factor: 1155978240967059981545236794906098102147329427908865568601
Wed Apr 4 10:45:54 2018 p150 factor: 103914941017585432569807404537280209718564853033928931580814904984029336379068716559184041945595873614118964758599832464919670696456300942029189406901
[/code]

47.4 hours for a 13.44M density-112 (114 didn't work) matrix on 14 cores i9-7940X. Maximum reported memory use 7403.5MB.

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

[QUOTE=fivemack;483855][code]
weight of 64591916 cycles is about 4521521435 (70.00/cycle)
[/code]

:busy:

I've thrown it back for another two hundred million raw relations[/QUOTE]

[code]
Wed Apr 4 20:11:00 2018 weight of 47012938 cycles is about 3291067733 (70.00/cycle)
[/code]

So once I've found the largest working density, that should be a matrix at least reasonably tractable on excessive hardware.

C184 from Lucas(3865) second Aurifeuillian factor

[code]
p56 factor: 11650548468013607480636572444551824125879428408390406561
p129 factor: 107421293507746607930099795638622153254964830031896106394841885992088863386544251790675380303933540799807850243915748690952737701[/code]

(Releases primal scream)

533M raw / 409M unique, log attached

C233_133_86 factored

[code]
prp53 factor: 48123005051671884100596570627622910027934285907981289
prp180 factor: 220961970465109701680862878060671110534178284477988742932023352385881799781006963132654422483371568642550168863830804058261022202461328997384502687247398959971962088052635841973157[/code]

(silently stares at screen)

459M raw / 360M unique

lol

[QUOTE=swellman;484329]C233_133_86 factored
(silently stares at screen)
[/QUOTE]

Who ECMs these days, anyway?

Thanks to you, I'll finish that t55 on my next 14e submission...

:unhappyme:

I ran 15k curves @B1=43e6, then another 12k curves @B1=3e8 on the L3865 composite. Unlucky seems a fair assessment, but I’m a bit biased. Reported this result to Marin M.

Yoyo@Home ran a full t55 on C233_133_86, i.e. 18000 curves @B1=11e7. Plus I ran a touch more (~800 curves @B1=3e8). A p53?! Really?

Them’s the breaks...

[QUOTE=Dubslow;482627]I'll take C209_96656723_29[/QUOTE]

[code]matrix is 19883667 x 19883915 (6153.1 MB) with weight 1520507965 (76.47/col)
sparse part has weight 1414151927 (71.12/col)
using block size 8192 and superblock size 589824 for processor cache size 6144 kB
commencing Lanczos iteration (4 threads)
memory use: 5194.7 MB
linear algebra at 0.0%, ETA 400h28m883915 dimensions (0.0%, ETA 400h28m)
checkpointing every 50000 dimensions83915 dimensions (0.0%, ETA 406h33m)
linear algebra completed 19883509 of 19883915 dimensions (100.0%, ETA 0h 0m)
lanczos halted after 314436 iterations (dim = 19883640)
recovered 22 nontrivial dependencies
BLanczosTime: 1433833

commencing square root phase
handling dependencies 1 to 64
reading relations for dependency 1
read 9941909 cycles
cycles contain 27874064 unique relations
read 27874064 relations
multiplying 27874064 relations
multiply complete, coefficients have about 765.64 million bits
initial square root is modulo 7395469
GCD is 1, no factor found
reading relations for dependency 2
read 9940716 cycles
cycles contain 27871564 unique relations
read 27871564 relations
multiplying 27871564 relations
multiply complete, coefficients have about 765.58 million bits
initial square root is modulo 7386667
GCD is N, no factor found
reading relations for dependency 3
read 9941408 cycles
cycles contain 27880866 unique relations
read 27880866 relations
multiplying 27880866 relations
multiply complete, coefficients have about 765.83 million bits
initial square root is modulo 7424887
sqrtTime: 10099
p58 factor: 6772755222280762934306144869239832781600209926161442442841
p151 factor: 5633673172606053749567341300705965212594925381326504811982365282795063601234344646337559626043606810943430235730154306584910699812115366158348985111879
elapsed time 403:50:31[/code]

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

C160_121xx489_13 factored
 

[QUOTE=richs;483487]Reserving Phi_13(largest factor of Phi_11(307))[/QUOTE]

aka C160_121xx489_13

[CODE]p74 factor: 40296988577962720918778837216475233936098364133694147779271378412110285807
p87 factor: 113373741268416831940959085643890665810786731129173626268521043208548880276648969964901[/CODE]

Approximately 57.2 hours on 2 threads Core i3-2310M with 4 GB memory for a 5.94M matrix at TD = 70 (didn't bother to try any higher densities since this one was overseived).
Log attached and redacted log at [URL="https://pastebin.com/p3egGzBF"]https://pastebin.com/p3egGzBF[/URL].

Factors reported to Factor Database.

5869^71-1 (15e) factored
 

342M unique relations built a 20.3M matrix using TD=140.
[CODE]p71 factor: 62024235665618512576697536008160378267767304477600170952967411606022181
p194 factor: 10162492759851711215493338717881735277578039728702372316780593354149076259491935013397148761745499930774000238458300561871390485611797222247270821447217601901195219140452404515714784497438061271[/CODE]
[url]https://pastebin.com/mRGjTwdB[/url]

Taking C169_15428908531_23b

Reserving C186_134_77 (15e)

C220_148xx049_19 remains unreserved right? I'll start downloading relations.

Looks unreserved to me; I have reserved it for you

factors
 

[B]C191 from Phi_5(largest_factor(Phi_23(1009)))[/B]
a.k.a.C191_279xx283_5
or as I like to call it, the C191 from (27945714132675033142899109225439212386442031501005140283^5-1)/smallfactors
[code]Sun Apr 08 14:28:16 2018 p74 factor: 15626382775384692333419535084750741838727764681892018560625375689328636741
Sun Apr 08 14:28:16 2018 p118 factor: 1060927068363295920843997922057755434493742112717640472074895235538641668893476337366547906110082591116941822410140471[/code]Factors uploaded to factordb, log attached and at [URL]https://pastebin.com/sFjptRab[/URL]

Taking [B]C217_67411_47[/B]

L2675B factored
 

259 total relations - 194 unique relations built a 12.9M matrix using TD=108. (TD=112 failed)
Solve time about 123 hours (-t 4 on a 2500K).
[CODE]p59 factor: 27081003959745788371641070659237582329168108955795178637351
p160 factor: 2827183399078790611460579560319638331041745663997165970594154348690207033200975504887442210911860865396570903272894059148496758654638949663676512964994806385651[/CODE]
[url]https://pastebin.com/JQMU6UQu[/url]

C169_15428908531_23 done
 

[code]
Tue Apr 10 06:39:02 2018 p66 factor: 717295347633318030342138976627507745788709012271600790244007994387
Tue Apr 10 06:39:02 2018 p103 factor: 3354958610042892724493175589472265351495313262855580529260919733753185179472372450834182896479673536199
[/code]

20.3 hours for 8.84M density-138 (140 didn't work) matrix on 14 cores i9-7920X.

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

C217_67411_47 Factored
 

Took slightly over 12 hours using 8 cores On a 5960 X at 3 GHz

[code]
Tue Apr 10 16:06:16 2018 p97 factor: 1207342092151075727707215357353817141146116403942416973022741060854755523813117118109775613292399
Tue Apr 10 16:06:16 2018 p121 factor: 1174715423960493259963020896063093474393448277791261021723195996307474999056670584903862166390359725881230476653103802093
[/code]

Taking C210_401173_41

[QUOTE=VictordeHolland;484855]Taking [B]C217_67411_47[/B][/QUOTE]

[QUOTE=Speedy51;484921]Took slightly over 12 hours using 8 cores On a 5960 X at 3 GHz

[code]
Tue Apr 10 16:06:16 2018 p97 factor: 1207342092151075727707215357353817141146116403942416973022741060854755523813117118109775613292399
Tue Apr 10 16:06:16 2018 p121 factor: 1174715423960493259963020896063093474393448277791261021723195996307474999056670584903862166390359725881230476653103802093
[/code][/QUOTE]

Slight cross up here. I think Speedy first reserved it 3 pages ago

[QUOTE=Dubslow;484924]Slight cross up here. I think Speedy first reserved it 3 pages ago[/QUOTE]
Whoopsie! :redface:

[QUOTE=VictordeHolland;484933]Whoopsie! :redface:[/QUOTE]

[QUOTE]As long as nobody has previously asked for C217_67411_47 & It's not going to run for hundreds of hours on a 5960 X with 16 gig of RAM I also use for other things so it would probably need to fit in 9 gig tops I would be interested in taking. Thanks[/QUOTE]
Sorry about the mixup if you would like the credit I can email Greg

[QUOTE=Dubslow;484924]Slight cross up here. I think Speedy first reserved it 3 pages ago[/QUOTE]

Thanks for noticing and bringing it to our attention Dubslow

[QUOTE=Speedy51;484983]Sorry about the mixup if you would like the credit I can email Greg[/QUOTE]
No need, it's fine, you reserved it first.

L1474 results
 

[code]prp69 factor: 530010756799991862504700015103425063177876194726676079788591415311627
prp116 factor: 49705535924015297084179633858969703513587573940987667489365584769803458613586336857624442493891992355464275507235369[/code]
419M unique relations netted 337M unique. Filtering with TD set to 130 produced a 19.38M matrix, which took roughly 230hr to solve on half a 6-core i7-5820 (6 threads msieve, 5-6 other tasks).

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

Factors have been reported to factordb.

C210_401173_41 done
 

[code]
Thu Apr 12 03:50:29 2018 p88 factor: 1841201444665293479393381404264287891977583719549878256713771017683442793965920692607893
Thu Apr 12 03:50:29 2018 p123 factor: 118336242172607142043906738829640700949209377139907712641412223561977220424619329855357880592424422538389118788954759397897
[/code]

22.5 hours for 9.38M density-132 (134 didn't work) matrix on 14 cores i9-7940X

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

C191_139017523_29 done
 

[code]
Wed Apr 11 19:04:41 2018 p88 factor: 1976402875460645046622070313675867024506139087254573462104016004262758754108335871098697
Wed Apr 11 19:04:41 2018 p104 factor: 33619520683334443614668735273752153940382075972247186704772810559856498563630403639344861263481942369233
[/code]

115.6 hours for 14.40M matrix at density 134 (136 didn't work) on 7 cores E5-2650v2. Log attached and at [url]https://pastebin.com/cbu4mg30[/url]

Reserving C183_424xx571 (14e).

C195_3366_2180 now running the matrix, ETA end of first week in May.

Taking C192_2311333_37.

[QUOTE=Dubslow;484840]C220_148xx049_19[/QUOTE]

I'm having some [URL="https://pastebin.com/iJWttywi"]problems[/URL] with this. There were roughly 150M unique relations, for a 25% duplication rate. I think it's undersieved? Been a while since I've tried to discern under- from over-, I'd appreciate a second opinion from the log file above.

[QUOTE=Dubslow;485178]I'm having some [URL="https://pastebin.com/iJWttywi"]problems[/URL] with this. There were roughly 150M unique relations, for a 25% duplication rate. I think it's undersieved? Been a while since I've tried to discern under- from over-, I'd appreciate a second opinion from the log file above.[/QUOTE]

Definitely under-sieved. Borderline cases result in "too few cycles, matrix probably cannot build", but this fails well before that part. You need more relations.

[QUOTE=VBCurtis;485185]Definitely under-sieved. Borderline cases result in "too few cycles, matrix probably cannot build", but this fails well before that part. You need more relations.[/QUOTE]

Well I seem to recall seeing the "filtering wants x more relations" in cases of oversieved too.

Anyways, fivemack? The other similar size/bit jobs have another 50M spq beyond what this one had. (I guess that should have been my other clue :razz:)

Piling on, I think C186_134_77 in the 15e queue is also undersieved.

I queued a couple of numbers with the anticipation of putting up the Q count once I saw realistic yield figures; I missed that stage and am doing it now.

+30MQ on C220_148xx049_19
+30MQ on C186_134_77
+10MQ on C240_127_111

147^55+55^147 C245 cofactor
 

[code]
prp83 factor: 26502625453137480645487691854977701613689526564685207176565718800349228553851097407
prp162 factor: 568480166171097362679332074354225456780908201469985208424014194940686570899130644096121326827230535449825104055489832572451678930067096926762441095012298077545211
[/code]

524M raw rels / 410M unique

L2088 complete
 

[code]
Sun Apr 15 13:39:48 2018 p64 factor: 1023875573507897534143644332201796020100965328487934687048757263
Sun Apr 15 13:39:48 2018 p124 factor: 8347691614234730245566143532041577681711573687577155482207361751647831320114838959175868241409736413865129857732261682748303
[/code]

382.2 hours for 22.78M matrix at density 146 (148 didn't work) on 6 cores i7-5820K.

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

Marin informed

Taking C240_127_111

ETA May 3

Taking [B]QUEUED AS C220_126xx371_13 [/B]
C220 from the OPN t600 file.
a.k.a. Phi_13(Phi_3(Phi_17(127)/527532101/115512048133057)/3/151)/3819325511

Reserving L2735B on 14e.

I’ll take QUEUED AS C160_117xx351_3
C160 from the OPN t600 file.
[ a.k.a. Phi_3(Phi_11(861235321)/11/89/19559)/3/7/3037 ]
P83^3-1 next.