P1 found a factor in stage #2, B1=500000, B2=20000000, E=12.
M15048053 has a factor: 779549271886429668067009697 (P1, B1=500000, B2=[B]20000000[/B], E=12) 2[SUP]5[/SUP]× 13× 127× 281× 174893× 15048053× [B]19952047[/B] +1 90 bit (89.33) 
that's a nice one. :whistle:

P1 found a factor in stage #2, B1=760000, B2=13680000.
UID: Jwb52z/Clay, M99367627 has a factor: 111236745363658693048154513 (P1, B1=760000, B2=13680000), 86.524 bits. 
P1 found a factor in stage #2, B1=760000, B2=13680000.
UID: Jwb52z/Clay, M99402031 has a factor: 960298973528588868089863 (P1, B1=760000, B2=13680000), 79.668 bits. 
P1 found a factor in stage #2, B1=6000000, B2=160000000, E=12.
M14005993 has a factor: 417809407686661544489263 (P1, B1=6000000, B2=160000000, E=12) 417809 407686 661544 489262 = 2 × 3^2 × 97 × 68813 × 14 005993 × 248 284483 
141.4 bits
[QUOTE]exponent factor digits bits* k min B1 min B2
40579559 3592039036873131451370283138714871190421073 43 141.366 44259217268392831121825192071639704 2^3 × 3^3 × 11 × 113 × 379 × 2579 × 5857 × 52567 × 596341 × 918555097 596,341 918,555,097[/QUOTE] I used B1=1000000, B2=20000000 Result had E=12. Brent Suyama helped, I believe 
Impressive, that's #20 on the [url=https://www.mersenne.ca/pm1user/1]alltime biggest P1 list[/url].

[QUOTE=James Heinrich;550022]Impressive, that's #20 on the [url=https://www.mersenne.ca/pm1user/1]alltime biggest P1 list[/url].[/QUOTE]
I also have the 4th. :) 
[QUOTE=petrw1;550031]I also have the 4th. :)[/QUOTE]And 35, 36, 81... But I got #117, so there! :flex:
Maybe I should extend that page to show beyond 100 so I feel special again... :down: 
P1 found a factor in stage #1, B1=760000.
UID: Jwb52z/Clay, M99621787 has a factor: 39763146304338863464275129264073 (P1, B1=760000), 104.971 bits. 
UID: storm5510/7700_Kaby_Lake, M7755521 has a factor: 105137409539055148931876353 (P1, B1=370000, B2=8140000, E=6)
86.442 bits. This is not a record here, or for me. However, it is the first I have found of any significance is a really long time. 
P1 found a factor in stage #2, B1=760000, B2=13680000.
UID: Jwb52z/Clay, M99633031 has a factor: 97905827678596252126675363231 (P1, B1=760000, B2=13680000), 96.305 bits. 
From [I]gpuOwl[/I]:
{"status":"F", "exponent":"7765781", "...":"PM1", "B1":"370000", "B2":"8140000", "...", "factors":["140468706376328182650630225863",...} 96.826 bits. {"status":"F", "exponent":"7766881", "...":"PM1", "B1":"370000", "B2":"8140000", "...", "factors":["14786058658810602089190892018393"...} 103.544 bits. I shortened these a little for readability. 
332283361 Factored
297034017173995954820063 77 bits The exponent has previously had a total about 60% of a first time check run (3 different users). What a waste of cycles when a factor was so close. I have done 7 different single bit factoring runs on this exponent (2009, 2012, 2014, 2014, 2015, 2017, 2020) 
If the exponent would have received proper P1'ing with stage 2, the same factor would long have been found, even barely with the lower GPU72 bounds.

Some I have found in recent days:
[QUOTE]{"status":"F", "exponent":"7772591", "..."factors":["217829919898848456896764649"], "..."} 27 digits. 87.493 bits. {"status":"F", "exponent":"7773749", "..."factors":["755815062954005295953743"], "..."} 24 digits. 79.322 bits. {"status":"F", "exponent":"10037099", "..."factors":["75804608324741176071997207"], "..."} 26 digits. 85.970 bits. {"status":"F", "exponent":"10039303", "..."factors":["10264737979425392203143761"], "..."} 26 digits. 83.086 bits. {"status":"F", "exponent":"7783463", "..."factors":["1348646481756687012246977831"], "..."} 28 digits. 90.124 bits. {"status":"F", "exponent":"8028799", "..."factors":["817275039261758312823819887"], "..."} 27 digits. 89.401 bits. {"status":"F", "exponent":"8030609", "..."factors":["190035152807530410451188527"], "..."} 27 digits. 87.296 bits.[/QUOTE]JSON makes these a bit tedious to prepare. 
[QUOTE=storm5510;551210]JSON makes these a bit tedious to prepare.[/QUOTE]Does this make it simpler? Now with sortable columns for exponent/bits/date.
[url]https://www.mersenne.ca/pm1user/63934/date[/url] You can copypaste with BBcode already provided:[quote][M]M8030609[/M] has a 87.296 bit factor: [url=https://www.mersenne.ca/M8030609]190035152807530410451188527[/url] [M]M8028799[/M] has a 89.401 bit factor: [url=https://www.mersenne.ca/M8028799]817275039261758312823819887[/url] [M]M8020049[/M] has a 73.671 bit factor: [url=https://www.mersenne.ca/M8020049]15041194718010883036649[/url] [M]M7783463[/M] has a 90.124 bit factor: [url=https://www.mersenne.ca/M7783463]1348646481756687012246977831[/url] [M]M10039303[/M] has a 83.086 bit factor: [url=https://www.mersenne.ca/M10039303]10264737979425392203143761[/url] [M]M10037099[/M] has a 85.971 bit factor: [url=https://www.mersenne.ca/M10037099]75804608324741176071997207[/url] [M]M7773749[/M] has a 79.322 bit factor: [url=https://www.mersenne.ca/M7773749]755815062954005295953743[/url] [M]M7772591[/M] has a 87.493 bit factor: [url=https://www.mersenne.ca/M7772591]217829919898848456896764649[/url][/quote] 
That's snazzy!

[STRIKE]Oliver[/STRIKE]Ryan must be too [STRIKE]modest[/STRIKE]busy to mention this one:
3307 has (another factor) [C]3413215452475967590824666626325289455333796024133147903[/C] 181.1 bits Found on [STRIKE]April 17[/STRIKE]July 19. The kicker is that the remaining cofactor is...... a PRP prime. Here it is in all of its 895 digits of glory [code]4353524133827611408574208775478589622111831317341613312984483361937010301205675662770047321087657048773241272664969392649718635926074520045281026910770712314524181933285227032125890659729016386069176693616914507334697422980860732777622339397522425721336605336658097363439448188753603624197638404803872825913098432275237874692169933508441748813480413682045289248409103532867732796807798694178375216208599640289769681995273685523060799468166287838493578146083048523489321729004640944722830982540726315520246334782951056660779801812979132998107387817802450037638989678012221564659671646755919013676548232993387587588481088712201127163199334146273445861473198777280904858096693010663932570520300269384917851688798854877340668001753453962945664051594771519075317923436346650061743281400127677733596528217642970792987250908618113230982353461817488308071861173968794875263418257665630917664743895435713[/code] Dario's ECM site confirms it. 
[QUOTE=Uncwilly;551258]Oliver must be too modest to mention this one: 3307 has (another factor).[/QUOTE]
That's because Ryan found it, I only appear in another result line (if you were thinking about me). :razz: 
[QUOTE=James Heinrich;551218]Does this make it simpler? Now with sortable columns for exponent/bits/date.
[URL]https://www.mersenne.ca/pm1user/63934/date[/URL] You can copypaste with BBcode already provided:[/QUOTE] Wow! That is a lot simpler. Some of the older programs, like [I]CUDAPm1[/I] and [I]CUDALucas[/I] could migrate to JSON. On the other hand is [I]gpuOwl[/I]. It does those jobs and generates JSON. Perhaps there is no point in update the older ones afterall. [I]mfaktc[/I] would be a good candidate though. Just some ideas... 
[QUOTE=kruoli;551266]That's because Ryan found it, I only appear in another result line (if you were thinking about me). :razz:[/QUOTE]:doh!::doh!:
Need more sleep. :picard: Yes, it was Ryan. 
[QUOTE=storm5510;551279]Wow! That is a lot simpler. ... JSON[/QUOTE]There is now a generalpurpose JSON factor results line to BBcode converter:
[url]https://www.mersenne.ca/json2bbcode.php[/url] 
My biggest factor yet.
[M]M10464319[/M] has a 100.251 bit factor: [url=https://www.mersenne.ca/M10464319]1508190451550803761680015597777[/url]
I had this assigned for PRPCF. When I found the factor, I quickly assigned it back, because for some reason, when a new factor is found, AID changes on server, resulting in unassignment in Prime95. When I tried further, I found nothing. But apparently I was too slow with reassigning because another user got it assigned before me. :cry: If I hadn't done another P1, I would still have it assigned to me... That's what I get for being greedy on factors. 
[QUOTE=Viliam Furik;551474][M]M10464319[/M] has a 100.251 bit factor: [URL="https://www.mersenne.ca/M10464319"]1508190451550803761680015597777[/URL]
I had this assigned for PRPCF. When I found the factor, I quickly assigned it back, because for some reason, when a new factor is found, AID changes on server, resulting in unassignment in Prime95. When I tried further, I found nothing. But apparently I was too slow with reassigning because another user got it assigned before me. :cry: If I hadn't done another P1, I would still have it assigned to me... That's what I get for being greedy on factors.[/QUOTE] 31 digits, if I counted correctly. My largest ever is 39. I found it running an ECM. I find more larger factors with P1 than any other test. 
P1 found a factor in stage #2, B1=765000, B2=13770000.
UID: Jwb52z/Clay, M99722053 has a factor: 10512338016344446590255974311 (P1, B1=765000, B2=13770000), 93.086 bits. 
I will match you:
107,841,991 has a factor 12730778224029936496678206809 93.4 bits 
[M]M7819481[/M] has a 82.157bit factor: [URL="https://www.mersenne.ca/M7819481"]5390575845470371528047137[/URL] (P1,B1=375000,B2=8250000)
[B]James Heinrich[/B] made these really easy to trim down. 
P1 found a factor in stage #2, B1=725000, B2=12506250.
UID: Jwb52z/Clay, M99840353 has a factor: 5932727665521459357484273 (P1, B1=725000, B2=12506250), 82.295 bits. 
M14085161 has a factor: 32832537809579740360129 (ECM curve 3, B1=51000, B2=5000000)
P1 = 32832 537809 579740 360128 = 2^6 × 3 × 7 × 11 × 13 × 6599 × 1 837931 × 14 085161 Not that interesting at first glance. However, it appears that an earlier P1 effort (from December 2001) should have found this factor: [URL="https://www.mersenne.org/report_exponent/?exp_lo=14085161&full=1"]M14085161[/URL] 
P1 found a factor in stage #1, B1=765000.
UID: Jwb52z/Clay, M99768083 has a factor: 384441743608822713047911 (P1, B1=765000), 78.347 bits. 
This was for GPUto72. I rarely get anything this size from [I]mfaktc[/I].
[QUOTE]M109296301 has a factor: 10598526822311362603927 [TF:73:74:mfaktc 0.21 barrett76_mul32_gs][/QUOTE]"Inane." I thought this was a typo which should have been "insane." Not the case. Google said, "Silly, Stupid." 
[QUOTE=storm5510;552450]"Inane." I thought this was a typo which should have been "insane." Not the case. Google said, "Silly, Stupid."[/QUOTE]
FYI the previous thread titles are as follows: [CODE]found a factor? say it found a factor? say it backwards... fast found a factor? say it backwards then fast for a week found a factor? say it backwards for a week found a factor? pay it back found a factor? play it again, Sam found a factor? pat yourself on the back found a factor? Get a cowpat on your back found a factor? Don't have a cow, man! found a factor? Join the club... found a factor? Man the lifeboat... found a factor? Person the lifeboat... found a factor? Draw a star on starboard... found a factor? Draw a straw and hope it's a long one found a factor? Draw a strawman and hope it's a long one found a factor? Draw a lawman and hope it's a strong one found a factor? Talk to a layman and hope it's a patient one found a factor? Talk to a caiman and hope it's a patient one found a factor? Go to a caiman and have a good break! You deserve it found a factor? Go to Caimans and have a good break! You deserve it found a factor? Go to Caymans and have a good break! You deserve it found a factor? Go to Caymans and break a leg! You deserve it found a factor? Turn it in at the lost property office found a factor? Turn it in at the lost prosperity office found a factor? Turn it in for the world to admire found a factor? Turn it in to become instantly famous! fondled a factor? Turn it in to become instantly famous! fondled a factor? Turn yourself in to become instantly famous! fondled a factor? Turn yourself in to become insanely famous! fondled a factor? Turn yourself in to become inanely famous! fond of a factor? Turn yourself in to become inanely famous! fond of a factor? Turn yourself in to become insane. [/CODE] 
[QUOTE=Uncwilly;552460]FYI the previous thread titles are as follows:...[/QUOTE]
Wow! I had no idea there had been so many. I remember "instantly famous!" None before. :smile: 
[URL="https://www.mersenne.org/report_exponent/?exp_lo=53297821&full=1"]53297821[/URL]
P1 found a factor: 369952925606532942373603199517480717271799 in stage 2. B1=5 000 000, B2=200 000 000 138.086 bits 
Congratulations! :smile: That's place 33 in the [URL="http://www.mersenne.ca/pm1user/1"]alltimebiggestMersennenumberfactorlist[/URL] using P1.

P1 found a factor in stage #2, B1=725000, B2=12506250.
UID: Jwb52z/Clay, M99867301 has a factor: 1258963263490729826198657 (P1, B1=725000, B2=12506250), 80.059 bits. 
UID: Jwb52z/Clay, M99786779 has a factor: 5811971107148547657342833 (P1, B1=765000)
82.265 bits. 
[CODE]P1 found a factor in stage #2, B1=30000000, B2=600000000, E=12.
UID: axn/R5, M3640333 has a factor: 75280105019644427503116372295759257424213063 (P1, B1=30000000, B2=600000000, E=12) [/CODE] 44 digits / 146 bits. Should be in Top 20. This needed a BS assist. 
Ends in a 7 digit Palindrome
41130281 Factor: 33095143150868303223223

[QUOTE=axn;554389]44 digits / 146 bits.[/QUOTE]
Nice, congratulations! :party: 
[QUOTE=axn;554389]44 digits / 146 bits. Should be in Top 20. This needed a BS assist.[/QUOTE]Indeed, it's [url=https://www.mersenne.ca/pm1user/1]#16 of all time[/url], and #1 on [url=https://www.mersenne.ca/pm1user/1077]your list[/url]. Well done! :smile:

Recently:
[QUOTE]{"status":"F", "exponent":"7765781", "worktype":"PM1", "B1":"370000", "B2":"8140000", "fftlength":"524288", "factors":["140468706376328182650630225863"]...} 30 digits. 96.826 bits. M7743221 has a factor: 1949670033377397597594276583567 (P1, B1=370000, B2=8140000, E=6) 31 digits. 100.621 bits. {"status":"F", "exponent":"7766881", "worktype":"PM1", "B1":"370000", "B2":"8140000", "fftlength":"524288", "factors":["14786058658810602089190892018393"]...} 32 digits. 103.544 bits.[/QUOTE]These are from [B]James Heinrich's[/B] "Poorly factored P1's" list. 
I updated the [url=https://www.mersenne.ca/json2bbcode.php]BBcode results encoder[/url] to also handle nonJSON results for your convenience:[QUOTE=storm5510;554600][M]M7765781[/M] has a 96.826bit (30digit) factor: [url=https://www.mersenne.ca/M7765781]140468706376328182650630225863[/url] (P1,B1=370000,B2=8140000)
[M]M7743221[/M] has a 100.621bit (31digit) factor: [url=https://www.mersenne.ca/M7743221]1949670033377397597594276583567[/url] (P1,B1=370000,B2=8140000,E=6) [M]M7766881[/M] has a 103.544bit (32digit) factor: [url=https://www.mersenne.ca/M7766881]14786058658810602089190892018393[/url] (P1,B1=370000,B2=8140000)[/quote] 
[QUOTE=James Heinrich;554606]I updated the [URL="https://www.mersenne.ca/json2bbcode.php"]BBcode results encoder[/URL] to also handle nonJSON results for your convenience:[/QUOTE]
That's right. You did and I had forgotten. Shame on me. :blush: I keep all my results. I wrote a quickanddirty little program which will read through a results file and pick out lines with factor information and write them to another text file. It is a workinprogress, but good enough that I may have missed the three above without it. :smile: 
From July:
[QUOTE]UID: storm5510/7700_Kaby_Lake, M7743221 has a factor: 1949670033377397597594276583567 (P1, B1=370000, B2=8140000, E=6), AID: 0C70DF7EE62E9F9A34F8DE8387A2F292 31 digits. 100.621 bits.[/QUOTE][B]James Heinrich[/B]: This is a [I]Prime95 result[/I]. Your BBCode convertor did not want to work with it. 
[M]M100091029[/M] has a 101.349bit (31digit) factor: [URL="https://www.mersenne.ca/M100091029"]3228091182977790599237506837961[/URL] (P1,B1=650000,B2=22000000)

[B][U]A correction to post #1598 :[/U][/B]
v30 of [I]Prime95[/I] creates dual results entries in two different files. I made a false assumption that JSON only happened with PRP work. :blush: 
[QUOTE=storm5510;554714][B]James Heinrich[/B]: This is a [I]Prime95 result[/I]. Your [url=https://www.mersenne.ca/json2bbcode.php]BBCode convertor[/url] did not want to work with it.[/QUOTE]It accepts it now.
[QUOTE=storm5510;554726]v30 of [I]Prime95[/I] creates dual results entries in two different files.[/QUOTE]That's not new to v30:[code]New features in Version 29.8 of prime95.exe 6) JSON results are now available for all work performed. JSON results are written to results.json.txt.[/code] 
[QUOTE=James Heinrich;554758]It accepts it now.
That's not new to v30:[code]New features in Version 29.8 of prime95.exe 6) JSON results are now available for all work performed. JSON results are written to results.json.txt.[/code][/QUOTE] I remember seeing [I]results.json.txt[/I] files prior to v30, now that you mention it. Looking at them, wordwrapped in Notepad, they did not seem to make a lot of sense. Turning off wordwrap, they appeared as very long lines of text. Perhaps in the future, the old forms will cease, at least in [I]Prime95[/I]. Other programs, like [I]mfakt(x)[/I] will need some revision to comply. [U]I appreciate your efforts[/U]. 
:davar55: Me and my precious 122 bit factor even won't appear in that Top200.
James, you [B][U]must[/U][/B] extend that top to 300 or 500 :rant: 
[QUOTE=LaurV;554794]:davar55: Me and my precious 122 bit factor even won't appear in that Top200.
James, you [B][U]must[/U][/B] extend that top to 300 or 500 :rant:[/QUOTE]Your "precious" would be #256 on the [URL="https://www.mersenne.ca/pm1user/1"]list[/URL] if I would extend it that far. 
[QUOTE=James Heinrich;554804]Your "precious" would be #256 on the [URL="https://www.mersenne.ca/pm1user/1"]list[/URL] if I would extend it that far.[/QUOTE]
Yay! Power of two! I knew it that's something important with it! :razz: Thanks! BTW just today I just found a 116 bits factor, so now you have to extend it further. Haha, just kidding man. But I [U]did[/U] just found a [URL="https://www.mersenne.ca/exponent/105890809"]116 bits factor[/URL], and anyhow, it is funny to see how you take it so serious every time. Kudos and kutgw! :bow: (P.S.: the best part of it is that now I can click on my name and see my factors! Before, as I was not in the table, and could never remember my "jail number", it was more complicate  bookmarks, search, saved link, etc, hihi) 
[QUOTE=LaurV;554794]...Me and my precious 122 bit factor even won't appear in that Top200. ..[/QUOTE]
35digits. That is really good. I have a 39digit but it would not appear on this list. It is ECM. I do not know if anyone in this group has noticed, ECM assignments are now 7 curves. I run a few on my antique machine on occasion. Anyway, I have always believed larger factors are more commonly found with P1. 
[QUOTE=James Heinrich;554804]Your "precious"...[/QUOTE]
Told you I'll bring luck if you put me on that list :razz: This beauty popped up (62 digits, 202 bits): :shock: Factor: 11357797528017579440065902285366253196028688791738880200930167 / (P1, B1=1500000, B2=75000000) Unfortunately, not prime, grrr... :sad: it would have been a nice "absolute ever" record. It splits into 122+81 bits, the larger of which is just a pinch smaller that my former record, and now I have two positions in top300, (yay!), at 257 and 281. BloodIce, I come for you! :razz: One odd thing worth mentioning: when I reported it, the server recorded it two times (once for each factor) and it gave me a double amount of credit (one full credit, for each factor). 
[QUOTE=LaurV;555439]One odd thing worth mentioning: when I reported it, the server recorded it two times (once for each factor) and it gave me a double amount of credit (one full credit, for each factor).[/QUOTE]It's a known thing. Once the server receives your factor it's checked and (if necessary) split into prime factors, and then processed as if you had submitted each prime factor separately. If both happen to be new factors then you get a "bonus". Consider it an incentive to find more composite factors. :smile:

[QUOTE=LaurV;555439]Factor: 11357797528017579440065902285366253196028688791738880200930167 / (P1, B1=1500000, B2=75000000)...[/QUOTE]
Wow! That's big. How would you go about breaking this down into smaller factors, like "w = x * y * z?" I've seen this done before. 
[QUOTE=storm5510;555464]Wow! That's big. How would you go about breaking this down into smaller factors, like "w = x * y * z?" I've seen this done before.[/QUOTE]
Feed it to yafu, or msieve, or CADO; you know, any of the factoring programs used by other parts of this forum. Try the "factoring" subforum for more info. 
[QUOTE=VBCurtis;555466]Feed it to yafu, or msieve, or CADO; you know, any of the factoring programs used by other parts of this forum.
Try the "factoring" subforum for more info.[/QUOTE] or use [url]https://www.alpertron.com.ar/ECM.HTM[/url] 
[QUOTE=storm5510;555464]Wow! That's big. How would you go about breaking this down into smaller factors, like "w = x * y * z?" I've seen this done before.[/QUOTE]
Dario Alpern has a good online factorization tool: [url]https://www.alpertron.com.ar/ECM.HTM[/url] (tool is online, calculations are done on your machine in the browser) [url]https://www.mersenne.ca/factor.php[/url] can also be used to factor [I]small[/I] numbers (up to 45 digits, but also larger numbers that are Mersenne factors). If you have [URL="https://www.mersenneforum.org/forumdisplay.php?f=96"]YAFU[/URL] installed, just open it and type [COLOR="DarkSlateBlue"][FONT="Courier New"]factor(11357797528017579440065902285366253196028688791738880200930167)[/FONT][/COLOR] and you'll get your answer. This is what mersenne.ca does internally when it encounters a composite factor, and if it can't get the answer quickly (within a few seconds) then I can run that manually on my morepowerful home computer. Most numbers can be factored quickly, some can take forever (just ask M1277). 
Ryan found a 208 bit factor:
[M]2137[/M] has a factor 434527865148151913428610180914321766584011558417928142522774921 :fusion::party: :faf: 
[QUOTE=Uncwilly;555649]Ryan found a 208 bit factor:
[M]2137[/M] has a factor 434527865148151913428610180914321766584011558417928142522774921 :fusion::party: :faf:[/QUOTE] My GPU could TF that in less than 4 times the age of the universe. 
Can I ask how long did the curve take? And would it be advisable to repeat one or two curves with the same bound to find similar sized other factor? ( atm the cofactor has been Prp'ed and show not prime).
edit: I realise it should have been a T65 curve, my apologies. 
[QUOTE=firejuggler;555665]Can I ask how long did the curve take?[/QUOTE]By my calculations a single curve of those bounds should be in the order of 12 GHzdays. It's all the [i]other[/i] curves that didn't find a factor that make it such a long/hard process. :smile:

[QUOTE=firejuggler;555665]Can I ask how long did the curve take? And would it be advisable to repeat one or two curves with the same bound to find similar sized other factor? ( atm the cofactor has been Prp'ed and show not prime).
edit: I realise it should have been a T65 curve, my apologies.[/QUOTE] If you click on the exponent report linked in the post above yours, you'll see that B1 is 2.9G. That's T70 standard. I don't think you understand ECM at all if you think an extra curve or two has any nontrivial probability to find another factor; never mind that there's no reason at all to think there's another one of the same size lurking just because one was found at this size. 
[QUOTE=James Heinrich;555666]By my calculations a single curve of those bounds should be in the order of 12 GHzdays. It's all the [i]other[/i] curves that didn't find a factor that make it such a long/hard process. :smile:[/QUOTE]
True. I wonder why that effort was not reported to Primenet and only one curve is mentioned. 
[QUOTE=lycorn;555709]True. I wonder why that effort was not reported to Primenet and only one curve is mentioned.[/QUOTE]On this current effort I'm not sure. It's not impossible that he just got lucky and found the factor in the first curve he attempted at those bounds. Ryan has previously run a large number of curves on M2137, most recently reported on 20191119:[code]M2137 completed 8596 ECM curves, B1=110000000, B2=776278396540
M2137 completed 19664 ECM curves, B1=260000000, B2=3178559884516 M2137 completed 348 ECM curves, B1=850000000, B2=14899382397918[/code]Remember that NFECM results are hidden on the exponent report page by default, you need to check the checkbox if you want to [url=https://www.mersenne.org/report_exponent/?exp_lo=2137&exp_hi=&full=1&ecmhist=1]see them[/url]. 
[QUOTE=lycorn;555709]True. I wonder why that effort was not reported to Primenet and only one curve is mentioned.[/QUOTE]
Probably an artifact of his batch methods whereby prime95 does stage 1 and GMPECM does stage 2. This big factor was found in stage 1! 
[QUOTE=Prime95;555723]Probably an artifact of his batch methods whereby prime95 does stage 1 and GMPECM does stage 2. This big factor was found in stage 1![/QUOTE]
I actually use just GMPECM, but with gwnum compiled/linked in, which makes stage 1 faster for b^n1 numbers... Actually, this factor was found in stage 2: [CODE]GMPECM 7.0.5dev [configured with GMP 6.2.0, GWNUM 29.8, enableasmredc, enableassert] [ECM] Due to incompatible licenses, this binary file must not be distributed. Input number is 2^21371 (644 digits) Using B1=2900000000, B2=81712898767516, polynomial Dickson(30), sigma=0:8561132775016161148 Step 1 took 20559097ms Step 2 took 12655697ms ********** Factor found in step 2: 434527865148151913428610180914321766584011558417928142522774921 Found prime factor of 63 digits: 434527865148151913428610180914321766584011558417928142522774921 Composite cofactor (2^21371)/434527865148151913428610180914321766584011558417928142522774921 has 581 digits[/CODE] 
[QUOTE=ryanp;555737]Actually, this factor was found in stage 2[/QUOTE]How do you generate the result line you submitted from that? Do you just handcraft those when you find a factor?[quote]M2137 has a factor: 434527865148151913428610180914321766584011558417928142522774921 (ECM curve 1, B1=2900000000)[/quote]I have adjusted the mersenne.ca record to include B2 and Sigma, perhaps if there are future similar factors found you could ensure the B2 and Sigma are included in the submitted result line, like this:[quote]M2137 has a factor: 434527865148151913428610180914321766584011558417928142522774921 (ECM curve 1, B1=2900000000, B2=81712898767516, Sigma=8561132775016161148)[/quote]

So it actually looks like only one curve was run.
It´s an amazing strike of luck to find a factor this size on curve #1... 
Another member of 9factor community
[M]M9532331[/M] has a 87.885 bit factor: [url=https://www.mersenne.ca/M9532331]285749678795460545168553689[/url]
I will try to push it to 10 factors. 
[QUOTE=lycorn;555796]So it actually looks like only one curve was run.
It´s an amazing strike of luck to find a factor this size on curve #1...[/QUOTE] No, there were many more curves run. I just report them separately (offline) to George, from time to time... 
[QUOTE=James Heinrich;555756]perhaps if there are future similar factors found you could ensure the B2 and Sigma are included in the submitted result line, like this:[/QUOTE]Thank you Ryan! :smile:
[quote][m]M1999[/m] has a factor: 7452018296729329082588085050101877014364039300287 (ECM curve 1, B1=850000000, B2=15892628251516, Sigma=3085684570545921953)[/quote] 
[QUOTE=James Heinrich;555804]Thank you Ryan! :smile:
[QUOTE][M]1999[/M] has a factor:[/QUOTE][/QUOTE] So, we have factors now totaling ~1/3 the total number of digits of the number (197/602). Very nice. 
and factordb tell us it is FF [url]http://factordb.com/index.php?query=M1999[/url]

2 big P1 factors found recently by the same CPU
[CODE]Speck 41033441 FPM1 20200831 06:41 Factor: 12701256943476787953365441980792492997353 / (P1, B1=1000000, B2=20000000, E=12) === 133.222 bits
Speck 41029441 FPM1 20200824 10:42 Factor: 145135143123598692565245877677438002712525001 / (P1, B1=1000000, B2=20000000, E=12) === 146.702 bits[/CODE] 
That's an impressive [url=https://www.mersenne.ca/pm1user/1221]Speck[/url]!
[M]M41029441[/M] has a 146.702 bit factor: [url=https://www.mersenne.ca/M41029441]145135143123598692565245877677438002712525001[/url] [M]M41033441[/M] has a 133.222 bit factor: [url=https://www.mersenne.ca/M41033441]12701256943476787953365441980792492997353[/url] I guess we just need to look at exponents in the form 410xx441 to find big P1 factors? :) 
I am still continuing to beat you all with.... [URL="https://www.mersenne.org/report_exponent/?exp_lo=103901689&full=1"]composite factors[/URL], haha.
But I won't be picky about the double amount of credit :razz: 
[QUOTE=LaurV;555902]I am still continuing to beat you all with.... [URL="https://www.mersenne.org/report_exponent/?exp_lo=103901689&full=1"]composite factors[/URL], haha.
But I won't be picky about the double amount of credit :razz:[/QUOTE] Feel free to come back to "the dark side" when you get bored. 
[URL="https://www.mersenne.org/report_exponent/?exp_lo=107930453"][COLOR=black]M107930453[/COLOR][/URL] has a 77.779 bit factor : [URL="http://www.mersenne.ca/factor/259365338128498517663353"]259365338128498517663353[/URL] (note: found with P1 with Colab)
The k is very low. it would have been found with a B1 @ 35111 
UID: Jwb52z/Clay, M100111807 has a factor: 5497876794406428536190503 (P1, B1=820000),
82.185 bits. 
[QUOTE=Uncwilly;555649]Ryan found a 208 bit factor:[/QUOTE]
And another 200+ digit factor has arrived thanks to Ryan: M[M]2083[/M] has a factor: [C]4188332412064506725391133958916461731585439326430544722593471[/C] That brings it to 199 digits of known factors out of 628 digits. A known forumite is doing the PRPCF. 
But but but... factordb would quasi instantly tell you , for a Mp of this size. up to about M(8k) or M(9k)

PrimeNet assigns it out anyway. The PRP will get done and a cert will get run soon.

[QUOTE=Uncwilly;556292]PrimeNet assigns it out anyway. The PRP will get done and a cert will get run soon.[/QUOTE]And PrimeNet user "atrench" was impatient and did a PRP run that looks to be lacking in a VDF. So it will still need to be rerun.

[QUOTE=Uncwilly;556336]And PrimeNet user "atrench" was impatient and did a PRP run that looks to be lacking in a VDF. So it will still need to be rerun.[/QUOTE]What is "VDF"?

VDF = Verifiable Delay Function. It is the PRP thing that generates the certs.
[url]https://www.mersenneforum.org/showthread.php?t=24654[/url] 
[QUOTE=Uncwilly;556336]And PrimeNet user "atrench" was impatient and did a PRP run that looks to be lacking in a VDF. So it will still need to be rerun.[/QUOTE]
VDF only kicks in for "larger" exponents. I think it is 100,000 or more. 
[URL="https://mersenneforum.org/showthread.php?t=25638"]https://mersenneforum.org/showthread.php?t=25638 [/URL]
it is where I would start 
2 Factors in same bit level.....
I believe this is my 7th in the last 6 years.
29060401 Factored 20200909 Sid & Andy Factor: 4333636239825805123801 / TF: 7172 20200909 Sid & Andy Factor: 2773219337689395056809 / TF: 7172 
[QUOTE=petrw1;556519]I believe this is my 7th in the last 6 years.
29060401 Factored 20200909 Sid & Andy Factor: 4333636239825805123801 / TF: 7172 20200909 Sid & Andy Factor: 2773219337689395056809 / TF: 7172[/QUOTE] I'm fed up with a lot of double factors like that: [URL="https://www.mersenne.org/report_exponent/?exp_lo=880000153&exp_hi=&full=1"]M880000153[/URL] (TF 7879) [URL="https://www.mersenne.org/report_exponent/?exp_lo=989000567&exp_hi=&full=1"]M989000567[/URL] (TF 7778) 
[M]M3349033[/M] has a 201.952 bit composite factor: [url=https://www.mersenne.ca/M3349033]6217575158069946300914632364196267867798278947818161061977999[/url]
This is my second largest double factor. 
[QUOTE=Miszka;556705][M]M3349033[/M] has a 201.952 bit composite factor: [URL="https://www.mersenne.ca/M3349033"]6217575158069946300914632364196267867798278947818161061977999[/URL]
This is my second largest double factor.[/QUOTE] 61 digits. That's remarkable. :shock: 
[FONT=Arial]M105006619 has a factor: 3114311268814618461112972838321 (P1, B1=830000)
101.297 bits. I think it is one of my largest one found [/FONT] 
[QUOTE=firejuggler;556899][M]M105006619[/M] has a 101.297bit (31digit) factor: [url=https://www.mersenne.ca/M105006619]3114311268814618461112972838321[/url] (P1,B1=830000)
101.297 bits. I think it is one of my largest one found[/QUOTE]It hasn't shown up in the nightly data sync yet, but it would currently be [URL="https://www.mersenne.ca/pm1user/9092"]your biggest ever[/URL]. Congrats :smile: 
P1 found a factor in stage #1, B1=820000.
UID: Jwb52z/Clay, M100140233 has a factor: 390077835803264014215583 (P1, B1=820000), 78.368 bits. With that new 201 bit composite factor recently found, this one seems a bit paltry. 
All times are UTC. The time now is 17:03. 
Powered by vBulletin® Version 3.8.11
Copyright ©2000  2023, Jelsoft Enterprises Ltd.