[QUOTE=axn;245984]Huh? It used to be that, once upon a time, p95 used to go ahead with TF even if a factor was found, just to make sure that no _smaller_ factor was missed. Then, that was removed. You mean to say that this (mis)feature has been reintroduced?![/QUOTE]
I'm afraid I followed the wrong chain of answers. The old behavior was removed. The actual Prime95 should finish its bit range even if a factor is found. Luigi 
Which raises my question, again.
Why multiply them? Isn't that sort of the opposite of what we're trying to do here? 
[QUOTE=alpertron;231757]My computer found the following results:
M120247 has a factor: 3250729890896242123679136285673 [/QUOTE] Some work effort quantification trivia complements of: [url]http://mersennearies.sili.net/credit.php?worktype=TF&exponent=120247&f_exponent=&b1=&b2=&numcurves=&factor=&frombits=1&tobits=102&submitbutton=Calculate[/url] Finding the same factor via TF would take over 8.5 quadrillion GhzDays :shock: 
[QUOTE=lorgix;246091]Which raises my question, again.
Why multiply them?[/QUOTE]Exactly which ones are you referring to, and which procedure found them? Perhaps there's some mixup. TF doesn't multiply them. (I've seen TF report two found factors from a single run; it did so on separate "has a factor" lines, not presented as the product of the two.) P1, by its nature, may find the product of two smaller factors at the conclusion of its GCD, rather than finding the two separately. Isn't that the method involved in the case you reference? [quote]Isn't that sort of the opposite of what we're trying to do here?[/quote]:smile: 
[QUOTE=cheesehead;246180]Exactly which ones are you referring to, and which procedure found them? Perhaps there's some mixup.[/QUOTE]
Post #46. [QUOTE]TF doesn't multiply them. (I've seen TF report two found factors from a single run; it did so on separate "has a factor" lines, not presented as the product of the two.)[/QUOTE]That's what I'd expect. Hence the question; why multiply? [QUOTE]P1, by its nature, may find the product of two smaller factors at the conclusion of its GCD, rather than finding the two separately. Isn't that the method involved in the case you reference?[/QUOTE]No, as you know by now; he claims it was found by TF. In post #51 I wrote that I thought it would have stopped after finding the smaller one. But that I wouldn't at all be surprised to see that factor found by P1. 
This is my largest factor so far
52526609 has a factor: 156325851414571040867100443817329068296081239222450719 Found by P1 
That's a composite; p24*p30. Still, nice find!

[QUOTE=MiniGeek;233559]These "k=2" you are talking about are really k=1. Factors are of the form 2kp+1. In other words, they're mp+1, with m always even. With these factors, m=2 and k=1, since the factor is equal to 2*p+1.
I'd bet that the factors of the k's break down, on average, like the factors of any natural number of about their size. And that the chance of any given k producing a factor is related to the equation given at [url]http://www.mersenne.org/various/math.php[/url]: "(how_far_factored1) / (exponent times [URL="http://www.utm.edu/research/primes/glossary/Gamma.html"]Euler's constant[/URL] (0.577...))".[/QUOTE] That's probably the case for other k. However it is a [url=http://en.wikipedia.org/wiki/Sophie_Germain_prime]theorem[/url] that if p is a prime congruent to 3 (mod 4) then 2p+1 divides Mp iff 2p+1 is prime. This must affect the statistics. I'm not aware of any comparable theorem for other k. 
[QUOTE=lorgix;246322]That's a composite; p24*p30. Still, nice find![/QUOTE]
Yes. I tend to view composite factors as two factors, rather than as a big factor. Still a P30 is not to be sniffed at 
M39375727 has a factor: 13698938687421045884119517033
M42516611 has a factor: 124316222847533124840651137 The second half of last year was really poor for me. I got no factors at all between 8 August and 26 November. Then three in December, and these twoinarow this month. M39787039 has a factor: 1700513525404800279754718890351 A nice p31 found back in February last year. 
I also agree that we should view composite factors as two smaller ones. Here is my 2nd largest one, also found by P1:
M51443083 has a factor: 25320591696138535897675469195834877349466521 I'm also assuming that this is composite since it is so large. I'm still very new at this, and learning. Can you tell me what you are doing, or using to tell if these numbers are composite or not? Also, maybe I'm getting more than my share, but I've been doing P1 work for 18 months now, and I've found 24 factors in 331 tests, at about a 7.25% rate. Thanks, Doug 
All times are UTC. The time now is 17:55. 
Powered by vBulletin® Version 3.8.11
Copyright ©2000  2022, Jelsoft Enterprises Ltd.