mersenneforum.org

mersenneforum.org (https://www.mersenneforum.org/index.php)
-   Lone Mersenne Hunters (https://www.mersenneforum.org/forumdisplay.php?f=12)
-   -   fond of a factor? Urn yourself to become remains (https://www.mersenneforum.org/showthread.php?t=13977)

gLauss 2021-04-15 18:55

Finally, after hundreds of attempts (and thousands of curves) found my first factor with ECM :smile: Even if it is only 71bits, it shows that it is possible! [M]3255283[/M]

masser 2021-04-15 20:13

[QUOTE=gLauss;575975]Finally, after hundreds of attempts (and thousands of curves) found my first factor with ECM :smile: Even if it is only 71bits, it shows that it is possible! [M]3255283[/M][/QUOTE]

Congrats! Nice find - may it be the first of many!

James Heinrich 2021-04-16 01:19

Ryan strikes again. #11 on the all time biggest Mersenne factors [url=https://www.mersenne.ca/userfactors/any/1/bits]list[/url].

[M]M4283[/M] has a 219.268-bit (67-digit) factor: [url=https://www.mersenne.ca/M4283]1014581894481062086635266411284139009925301539055947709872564246847[/url] (ECM,B1=260000000,B2=3142865025316,Sigma=6655636513802850625)

petrw1 2021-04-16 14:14

Almost....Laurv
 
[QUOTE=LaurV;574333]Congrats, triple 59, next one you will find will start with a quadruple 69... :razz:[/QUOTE]

Factor ends with ... let's see 1, 2, 3: 69.
Exponent ends with 369; and starts with 396.
Exponent has 5 out of 8 digits 6 or 9: 40%
Factor has 9 out of 23 digits 6 or 9: 39%.
Time found contains a 6 and a 9.

[CODE]39626369 F-PM1 2021-04-16 06:19 Factor: 35172309356636629912369[/CODE]

Viliam Furik 2021-04-16 15:31

[QUOTE=petrw1;576000]Factor ends with ... let's see 1, 2, 3: 69.
Exponent ends with 369; and starts with 396.
Exponent has 5 out of 8 digits 6 or 9: [B]40%[/B]
Factor has 9 out of 23 digits 6 or 9: 39%.
Time found contains a 6 and a 9.

[CODE]39626369 F-PM1 2021-04-16 06:19 Factor: 35172309356636629912369[/CODE][/QUOTE]

I'm pretty sure that's supposed to be 62.5%

James Heinrich 2021-04-16 15:37

[QUOTE=LaurV;574333]Congrats, triple 59, next one you will find will start with a quadruple 69... :razz:[/QUOTE]TJAOI did that 7 years ago: [M]M926969327[/M] has a 49.308-bit (15-digit) factor: [url=https://www.mersenne.ca/M926969327]696969697584761[/url]

slandrum 2021-04-16 15:40

[QUOTE=James Heinrich;576004]TJAOI did that 7 years ago: [M]M926969327[/M] has a 49.308-bit (15-digit) factor: [url=https://www.mersenne.ca/M926969327]696969697584761[/url][/QUOTE]

As well as double 69 in the exponent!

ATH 2021-04-16 16:46

[QUOTE=James Heinrich;576004]TJAOI did that 7 years ago: [M]M926969327[/M] has a 49.308-bit (15-digit) factor: [url=https://www.mersenne.ca/M926969327]696969697584761[/url][/QUOTE]

[M]345495211[/M]: Factored 1163[B]69696969[/B]03
[M]608055197[/M]: Factored 23981[B]69696969[/B]

petrw1 2021-04-28 04:39

Consecutive P-1 factors with repeated ending digits

Magic_8_Ball 39629561 F-PM1 2021-04-27 14:21 Factor: 63762133812827843899999
Magic_8_Ball 39605273 F-PM1 2021-04-28 03:00 Factor: 204171204894399516952237777

James Heinrich 2021-04-30 17:49

Another impressive one from Ryan (#14 on the overall biggest [url=https://www.mersenne.ca/userfactors/ecm/1/bits]list[/url], and he also got #11, #12 spots in the last 2 weeks)
[M]M4001[/M] has a 212.771-bit (65-digit) factor: [url=https://www.mersenne.ca/M4001]11228234992112410011165597181282604695853195021678012695442609737[/url] (ECM,B1=850000000,B2=14182957708936,Sigma=15234304705639590802)

petrw1 2021-05-04 17:27

9/63
 
9 P-1 factors in 63 (14.28%) attempts working on assignments with an expected success rate of 3%.

firejuggler 2021-05-05 15:55

[M]M23516089[/M] has a 70.456-bit (22-digit) factor: [url=https://www.mersenne.ca/M23516089]1619450690983460996873[/url] (P-1,B1=1200000,B2=76800000)


This is almost frustrating, as it was TF'ed to 70bit. But I really like it because the B1 is almost perfect.

k= 2^2*1 175 411 *7 323 571

firejuggler 2021-05-06 02:39

Well, I decided to run a PP1 curse on my old already factored exponent.
This is my first pp1 factor

P+1 found a factor in stage #2, B1=500000, B2=26500000.
UID: firejuggler/Maison, M8805827 has a factor: 4175293398605056163377 (P+1, B1=500000, B2=26500000)

Jwb52z 2021-05-06 18:45

P-1 found a factor in stage #2, B1=740000, B2=20264000.
UID: Jwb52z/Clay, M103695649 has a factor: 2004109083829816426995592903 (P-1, B1=740000, B2=20264000).

90.695 bits.

firejuggler 2021-05-07 15:17

Sadly, a composite
[M]M23517601[/M] has a 195.647-bit (59-digit) [b]composite[/b] (P27+P33) factor: [url=https://www.mersenne.ca/M23517601]78650091603029033018091227770166444001988216065464577593033[/url] (P-1,B1=1200000,B2=79200000)

Jwb52z 2021-05-12 14:55

UID: Jwb52z/Clay, M103808857 has a factor: 1401232317330993509639727923687 (P-1, B1=740000),

100.145 bits.

kruoli 2021-05-17 08:20

[M]M103830131[/M] has a 157.127-bit (48-digit) [b]composite[/b] (P24+P24) factor: [url=https://www.mersenne.ca/M103830131]199531333730879095999006796725214407904194653871[/url] (P-1,B1=1708000)

While the composite factor itself it not extremely interesting by itself, I find it interesting because:
- it was found in stage 1.
- the prime factors are very similar in size (78.460 and 78.667 bits).

The prime factors are 415767534785818078323247 and 479910808412848576977793.

axn 2021-05-17 08:56

Nice!

LaurV 2021-05-29 14:38

M106722533 has an 110 bits factor 771972811871697820846912678000249.

Albeit 110 bits is not a joke, the factor is not a record in itself, but it is quite large and nice, considering the fact that was found in stage 1 (yes, it is [URL="https://www.mersenne.ca/exponent/106722533"]sooo smooth[/URL], like ice cream!)

Viliam Furik 2021-05-29 15:00

[QUOTE=LaurV;579389]M106722533 has an [STRIKE]110[/STRIKE] bits factor 771972811871697820846912678000249. [/QUOTE]

Liar! Only 109 bits, 109.25 to be more exact. :razz:

James Heinrich 2021-05-29 15:17

[QUOTE=Viliam Furik;579393]Liar! Only 109 bits, 109.25 to be more exact. :razz:[/QUOTE]Why stop there? 109.25024907447 :whee:

But LaurV isn't wrong, the factor does take 110 bits to represent. You don't say it's 32.8876 decimal digits long. :smile:

Dr Sardonicus 2021-05-30 13:41

[QUOTE=Viliam Furik;579393][QUOTE=LaurV;579389]M106722533 has an [STRIKE]110[/STRIKE] bits factor 771972811871697820846912678000249. [/QUOTE]Liar! Only 109 bits, 109.25 to be more exact. :razz:[/QUOTE]Oops.

From my "I can't count" liturgy:

[b]Versicle:[/b] How many bits in two to the first power?

[b]Responsory:[/b] Two, two.

[b]Versicle:[/b] How many decimal digits in ten to the first power?

[b]Responsory:[/b] Two, two.

From the output of Pari-GP:
[code]? v=binary(771972811871697820846912678000249)
%1 = [1, 0, 0, 1, 1, 0, 0, 0, 0, 0, 1, 1, 1, 1, 1, 0, 1, 0, 1, 0, 1, 0, 1, 0, 1, 0, 1, 1, 1, 1, 0, 1, 1, 0, 0, 1, 0, 1, 1, 1, 1, 1, 0, 1, 1, 1, 1, 1, 1, 0, 1, 0, 1, 1, 0, 1, 0, 1, 0, 1, 1, 0, 1, 0, 0, 0, 1, 0, 1, 1, 1, 1, 0, 1, 0, 0, 1, 0, 1, 1, 1, 0, 0, 0, 0, 1, 1, 1, 0, 0, 1, 0, 0, 1, 1, 1, 1, 1, 0, 1, 1, 0, 0, 1, 1, 1, 1, 0, 0, 1]
? #v
%2 = 110
?[/code]

Uncwilly 2021-05-30 16:17

A nice run of the mill 79 bit factor: 1025757166134493292294953
But, it was found when I poached (not sorry) a stalled P-1 that was in the lowest 25 exponents for FTC.
[M]103547179[/M]
There are others down there that have zero check ins since assigned and are more than a month old and thus have violated the rules for Cat 0 (but the rules do seem to apply to P-1 assignments down in the low FTC's)[LIST][*]Must be completed in 30 days[*]Assignments are recycled if assignment is not started with 7 days or when assignment is more than 30 days old.[/LIST]

chalsall 2021-05-30 16:41

[QUOTE=Uncwilly;579496]There are others down there that have zero check ins since assigned and are more than a month old and thus have violated the rules for Cat 0 (but the rules do seem to apply to P-1 assignments down in the low FTC's)[/QUOTE]

Just so you know, I'm working on those held by ANONYMOUS and Kas. Should all be done in about three days (assuming Colab cooperates).

Uncwilly 2021-05-30 18:26

[QUOTE=chalsall;579497]Just so you know, I'm working on those held by ANONYMOUS and Kas. Should all be done in about three days (assuming Colab cooperates).[/QUOTE]
I have been working bottom up getting about 9 every 5 days.

chalsall 2021-05-30 22:22

[QUOTE=Uncwilly;579503]I have been working bottom up getting about 9 every 5 days.[/QUOTE]

Yeah. I am aware you are on a certain team... :tu:

Just wanted to declare intentions, so we didn't duplicate efforts. A Compute Cycle is a terrible thing to waste! :wink:

Viliam Furik 2021-05-30 22:34

[QUOTE=James Heinrich;579396]Why stop there? 109.25024907447 :whee:

But LaurV isn't wrong, [B]the factor does take 110 bits to represent[/B]. You don't say it's 32.8876 decimal digits long. :smile:[/QUOTE]

Oh, didn't realize that. Sorry, LaurV.

Uncwilly 2021-06-01 14:42

[QUOTE=Uncwilly;579496]A nice run of the mill 79 bit factor: 1025757166134493292294953
But, it was found when I poached (not sorry) a stalled P-1 that was in the lowest 25 exponents for FTC.
[M]103547179[/M][/QUOTE]
Just got me another like it: [URL="https://www.mersenne.org/report_exponent/?exp_lo=103566409&full=1"]312854885986074648542201 [/URL]
78 bits
The old P-1 assignment had been sitting on this low Cat 0 assignment since April 18. Hadn't checked in since then. P-1 is the wild west. No expiry after 30 days, no expiry after not starting in 7 days. (This was in the bottom 25 again).

Jwb52z 2021-06-02 01:58

P-1 found a factor in stage #1, B1=736000.
UID: Jwb52z/Clay, M104224103 has a factor: 457222887848673747662129713 (P-1, B1=736000)

88.563 bits.

Viliam Furik 2021-06-08 19:43

Yay, I found my first top-500 factor. Not even on the list yet, but soon. Albeit only at 495th place.

[M]M2315107[/M] has a 118.475-bit (36-digit) factor: [url=https://www.mersenne.ca/M2315107]461896913357939229136479311870224273[/url] (P-1,B1=5000000,B2=505000000)

461896913357939229136479311870224273 = 2 * (2^3 * 3 * 7 * 59 * 13381 * 412537 * [B]3,978,523[/B] * [B]458,257,259[/B]) * 2315107

Also a relatively tight fit in the bounds.

James Heinrich 2021-06-08 19:47

[QUOTE=Viliam Furik;580379]Yay, I found my first top-500 factor[/QUOTE]:party:

Viliam Furik 2021-06-09 09:50

[QUOTE=Viliam Furik;580379]Yay, I found my first top-500 factor. Not even on the list yet, but soon. Albeit only at 495th place.

[M]M2315107[/M] has a 118.475-bit (36-digit) factor: [url=https://www.mersenne.ca/M2315107]461896913357939229136479311870224273[/url] (P-1,B1=5000000,B2=505000000)

461896913357939229136479311870224273 = 2 * (2^3 * 3 * 7 * 59 * 13381 * 412537 * [B]3,978,523[/B] * [B]458,257,259[/B]) * 2315107

Also a relatively tight fit in the bounds.[/QUOTE]

And the last fun fact to add is that it almost went unnoticed. I have run out of my worktodo, and that triggered the setting in the prime.txt that turned off the PrimeNet usage, so the factor, being found after these events, has not been reported immediately. If I didn't notice that nothing was being reported, I wouldn't have found it, and it would have been buried in the results files until deletion.

Is there a way to not get work from PrimeNet but not quit the PrimeNet after work is done? Basically, I want a monologue relationship with PrimeNet; I talk to him, but he doesn't reply :grin:.

firejuggler 2021-06-09 10:01

On prime95, Advanced, manual communication, Do not contact Primenet server automatically (a box to be checked). just below there is an already checked box for 'contact now'

Viliam Furik 2021-06-09 10:52

[QUOTE=firejuggler;580424]On prime95, Advanced, manual communication, Do not contact Primenet server automatically (a box to be checked). just below there is an already checked box for 'contact now'[/QUOTE]

I believe this would mean I'd have to manually upload every once in a while, and when I would upload, it would, in the process of contacting the PrimeNet, get some assignments back, which I don't want. Or not?

kruoli 2021-06-09 10:58

[QUOTE=Viliam Furik;580423]Is there a way to not get work from PrimeNet but not quit the PrimeNet after work is done?[/QUOTE]

What about manually setting [C]DaysOfWork=0[/C]? That way, you'll never get automatic work and the results still will be reported normally.

Uncwilly 2021-06-09 12:37

[QUOTE=Viliam Furik;580423]Is there a way to not get work from PrimeNet but not quit the PrimeNet after work is done? Basically, I want a monologue relationship with PrimeNet; I talk to him, but he doesn't reply :grin:.[/QUOTE]
NoMoreWork=1 in prime.txt

sweety439 2021-06-09 13:59

[QUOTE=Jwb52z;577821]P-1 found a factor in stage #2, B1=740000, B2=20264000.
UID: Jwb52z/Clay, M103695649 has a factor: 2004109083829816426995592903 (P-1, B1=740000, B2=20264000).

90.695 bits.[/QUOTE]

When I add the P-1 method with B1=740000, B2=20264000 for [URL="http://factordb.com/index.php?id=1100000002602478101"]this prime in factordb[/URL], it says "Err: Calculated grouporder 2004109083829816426995592902<28> is not within B1/B2 bounds (B1=740000, B2=20264000). Please check your result!"

Viliam Furik 2021-06-09 14:01

[QUOTE=Uncwilly;580431]NoMoreWork=1 in prime.txt[/QUOTE]

That is the setting I am using, but it turns off the PrimeNet connection when out of work. It prints out "Successfully quit GIMPS" in the Comm thread.

Viliam Furik 2021-06-09 14:03

[QUOTE=kruoli;580427]What about manually setting [C]DaysOfWork=0[/C]? That way, you'll never get automatic work and the results still will be reported normally.[/QUOTE]

That may help. I'll try it.

Viliam Furik 2021-06-09 14:08

[QUOTE=sweety439;580439]When I add the P-1 method with B1=740000, B2=20264000 for [URL="http://factordb.com/index.php?id=1100000002602478101"]this prime in factordb[/URL], it says "Err: Calculated grouporder 2004109083829816426995592902<28> is not within B1/B2 bounds (B1=740000, B2=20264000). Please check your result!"[/QUOTE]

Maybe it's got a problem with the exponent P=103695649.

2004109083829816426995592902 = 2 * 3 * 281 * 29917 * 47269 * 8106041 * 103695649, so the biggest factor is 103695649, the exponent, which is bigger than B2=20264000.

Is it possible it's not accounting for the special form of Mersenne factors, which allows ignoring P as a factor of Q-1 (Q is the factor found) and only using the general rules for factors found by the P-1 method?

axn 2021-06-09 14:20

[QUOTE=Viliam Furik;580442]Is it possible it's not accounting for the special form of Mersenne factors, which allows ignoring P as a factor of Q-1 (Q is the factor found) and only using the general rules for factors found by the P-1 method?[/QUOTE]
That's probably it.

Viliam Furik 2021-06-10 09:11

[M]M1001159[/M] has a 120.912-bit (37-digit) factor: [url=https://www.mersenne.ca/M1001159]2500439903769890259112379635985290039[/url] (P-1,B1=10000000,B2=1110000000)

Is it Christmas already? This one should come in at about 365th place.

firejuggler 2021-06-10 10:30

No, no, no, I have no budget for christmass right now. So it is NOT christmass. At least for another 6 month.

Uncwilly 2021-06-10 13:51

[QUOTE=Viliam Furik;580523][M]M1001159[/M] has a 120.912-bit (37-digit) factor: [url=https://www.mersenne.ca/M1001159]2500439903769890259112379635985290039[/url] (P-1,B1=10000000,B2=1110000000)

Is it Christmas already? This one should come in at about 365th place.[/QUOTE]
You have bet my best. I am in the 120 bit club too. Very nice catch.
:faf:

firejuggler 2021-06-12 19:01

M[M]23554211[/M] has a 114.027-bit (35-digit) factor: [URL="https://www.mersenne.ca/M23554211"]21164767805799094411604254592575543[/URL] (P-1,B1=1200000,B2=79200000)
I also have a near Christmass time

LaurV 2021-06-13 04:28

We found both an [URL="https://www.mersenne.ca/exponent/35124833"]98.x[/URL] and [URL="https://www.mersenne.ca/exponent/35123269"]101.x[/URL] bits factors in 35.1M range, [STRIKE]what's worth mentioning them is the fact they were both found in a row, one after the other, and both found [U]in stage 1[/U] (!)
They are not sync'd on James' site yet, but they are indeed very smooth![/STRIKE]

Viliam Furik 2021-06-13 09:33

[QUOTE=LaurV;580844]We found both an [URL="https://www.mersenne.org/report_exponent/?exp_lo=35120669&full=1"]98.x[/URL] and [URL="https://www.mersenne.org/report_exponent/?exp_lo=35124833&full=1"]101.x[/URL] bits factors in 35.1M range, what's worth mentioning them is the fact they were both found in a row, one after the other, and both found [U]in stage 1[/U] (!)
They are not sync'd on James' site yet, but they are indeed very smooth![/QUOTE]

Your 98.x factor directs to 83.x factor and 101.x factor directs to 98.x factor.

LaurV 2021-06-13 10:06

Fixed, thank you very much! (I didn't edit the quote in your post, only my post). I got lost in so many factors and links. But in this case, the 101 is not anymore "smooth". My mistake. As they were not yet on mersenne.ca at the time, I wrongly remembered their size (which is displayed when reporting), and I assumed the 101 was the smooth one (the "smoothness" is deduced from the amount of credit given, you don't need to do any calculation or to see the k value to know your factor is very smooth, hehe).

Therefore, to repair the damage, take this new [URL="https://www.mersenne.ca/exponent/35126153"]115 bits[/URL] guy here... :razz:

Jwb52z 2021-06-14 23:57

[QUOTE=sweety439;580439]When I add the P-1 method with B1=740000, B2=20264000 for [URL="http://factordb.com/index.php?id=1100000002602478101"]this prime in factordb[/URL], it says "Err: Calculated grouporder 2004109083829816426995592902<28> is not within B1/B2 bounds (B1=740000, B2=20264000). Please check your result!"[/QUOTE]Um, I don't know how to check the result. I just report what the screen and results file shows me.

Jwb52z 2021-06-15 00:00

P-1 found a factor in stage #2, B1=737000, B2=20466000.
UID: Jwb52z/Clay, M104363929 has a factor: 12877212261710761007261993 (P-1, B1=737000, B2=20466000),

83.413 bits.

Jwb52z 2021-07-01 16:29

P-1 found a factor in stage #1, B1=739000.
UID: Jwb52z/Clay, M104656151 has a factor: 179821323726211482179833 (P-1, B1=739000)

77.251 bits.

firejuggler 2021-07-01 20:36

one of my biggest find
[M]M35821609[/M] has a 114.854-bit (35-digit) factor: [url=https://www.mersenne.ca/M35821609]37533512686961073352872057770174521[/url] (P-1,B1=1200000,B2=73200000)

Jwb52z 2021-07-02 19:40

P-1 found a factor in stage #1, B1=739000.
UID: Jwb52z/Clay, M104679433 has a factor: 7144991229022485833889497 (P-1, B1=739000)

82.563 bits.

Jwb52z 2021-07-04 03:58

P-1 found a factor in stage #2, B1=739000, B2=20534000.
UID: Jwb52z/Clay, M104710483 has a factor: 2087604414043709000130191 (P-1, B1=739000, B2=20534000)

80.788 bits.

Happy5214 2021-07-04 10:58

P-1 found a factor in stage #1, B1=10000000.
M524351 has a factor: 210100758636629488891459910447 (P-1, B1=10000000)

This 97.407-bit factor is notable because it's my first P-1 Mersenne factor.

James Heinrich 2021-07-04 13:26

[QUOTE=Happy5214;582582]This 97.407-bit factor is notable because it's my first P-1 Mersenne factor.[/QUOTE]Congrats, and may you find many more! :smile:

firejuggler 2021-07-08 17:29

M23851277 has a factor: 2172095945184050340167 [TF:70:71*:mfaktc 0.21 barrett76_mul32_gs]
found 1 factor for M23851277 from 2^70 to 2^71 (partially tested) [mfaktc 0.21 barrett76_mul32_gs]
k=3 989 × 11 414 932 211


A not at all smooth k ( found with mfaktc)

Jwb52z 2021-07-10 05:56

P-1 found a factor in stage #2, B1=755000, B2=20983000.
UID: Jwb52z/Clay, M104819381 has a factor: 574983783644612576435518337 (P-1, B1=755000, B2=20983000)

88.894 bits.

Jwb52z 2021-07-14 00:26

P-1 found a factor in stage #1, B1=756000.
UID: Jwb52z/Clay, M104890637 has a factor: 126027633778180756401977 (P-1, B1=756000)

76.738 bits.


All times are UTC. The time now is 20:13.

Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2021, Jelsoft Enterprises Ltd.