![]() |
[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 general-purpose 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 PRP-CF. 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 re-assigning because another user got it assigned before me. :cry: If I hadn't done another P-1, 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 PRP-CF. 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 re-assigning because another user got it assigned before me. :cry: If I hadn't done another P-1, 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 P-1 than any other test. |
P-1 found a factor in stage #2, B1=765000, B2=13770000.
UID: Jwb52z/Clay, M99722053 has a factor: 10512338016344446590255974311 (P-1, 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.157-bit factor: [URL="https://www.mersenne.ca/M7819481"]5390575845470371528047137[/URL] (P-1,B1=375000,B2=8250000)
[B]James Heinrich[/B] made these really easy to trim down. |
P-1 found a factor in stage #2, B1=725000, B2=12506250.
UID: Jwb52z/Clay, M99840353 has a factor: 5932727665521459357484273 (P-1, B1=725000, B2=12506250), 82.295 bits. |
M14085161 has a factor: 32832537809579740360129 (ECM curve 3, B1=51000, B2=5000000)
P-1 = 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 P-1 effort (from December 2001) should have found this factor: [URL="https://www.mersenne.org/report_exponent/?exp_lo=14085161&full=1"]M14085161[/URL] |
P-1 found a factor in stage #1, B1=765000.
UID: Jwb52z/Clay, M99768083 has a factor: 384441743608822713047911 (P-1, 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." |
| All times are UTC. The time now is 22:46. |
Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2021, Jelsoft Enterprises Ltd.