![]() |
|
|
#67 | |
|
Sep 2002
Database er0rr
373910 Posts |
Quote:
Last fiddled with by paulunderwood on 2014-04-15 at 14:31 |
|
|
|
|
|
|
#68 | |
|
"Serge"
Mar 2008
Phi(4,2^7658614+1)/2
2·7·677 Posts |
Quote:
Let me get this straight, and in terms that you will be able to follow. You put a shirt in a washing machine and say loudly: "this is a washing machine, and here's how it works". Everyone agrees. Yes, this is a washing machine. We've seen it before. It's been known for a few centuries. You put sneakers in a washing machine and say loudly: "this is not a washing machine, it is a completely new machine, and here's how it works". Some people even gather around and start asking questions: "how does this wonderful new boldi machine works?" It is still a washing machine, the same old washing machine - its name doesn't depend on what you put in it. It makes things clean. It doesn't make them new. Even if the things look new when they come out of the washing machine, they are in reality not new. Just clean. If you proved that sneakers (exactly sneakers, but not anything else) come out of the machine not just clean, but new, then it would have been an achievement. Well? You didn't. Hence, it is still the same ol' washing machine. To your last retort ("but I was first to make this conjecture! It is mine! All that's left is to prove it"), - nope, even that is not new. It is also not faster. And just in case you don't understand the subtleties, the opposite of "faster" (>) is not "slower" (<). It is "not faster" (<=). It includes "equally fast"; ever heard of the "=" sign? The 3-PRP is exactly as fast as the LL test, when both are implemented correctly. If you don't know what this statement means, or if it is true, or what "implemented correctly" means (I'll give you a hint: it doesn't include running things in Pari, BASIC, or even in plain C) - it is a bit of a problem. Your problem, to be precise. The second post already told you that. This thread ended with the second post. Everything below it is just idle coffee room chatter. Last fiddled with by Batalov on 2014-04-15 at 17:13 |
|
|
|
|
|
|
#69 | ||
|
Apr 2014
168 Posts |
Quote:
Calm down. Please realize, that there is no counterexample. The conjecture is still valid. In the data that Mayer has posted, you will not find a counterexample. He shows only some factorizations on base 3 done in 1997. And if you read carefully, Mayer does also not claim to have a counterexample. It was only a little bit a flash grenade ;-) but it was enough, that someone was destroying the headline of the thread. You? If you are the opinion, that the conjecture is disproved, please show where it was done. Quote:
Greetings boldi |
||
|
|
|
|
|
#70 |
|
"Serge"
Mar 2008
Phi(4,2^7658614+1)/2
2×7×677 Posts |
Calm down, boldi. ;-)
boldi's Profile Total Posts: 14 Posts Per Day: 7.01 ! (and all are essentially a repetition of the first post) Stop putting your problems on others. "Calm down". You are funny. Instead, go to any shopping mall, stand next to a washing machine and tell everyone that you invented it. Do you understand the analogy? Just answer: yes or no?
|
|
|
|
|
|
#71 | |
|
Aug 2006
3×1,993 Posts |
Quote:
|
|
|
|
|
|
|
#72 |
|
"Forget I exist"
Jul 2009
Dumbassville
26·131 Posts |
We are essentially working within the mersennes completely and your conjecture is saying only the first of the following works and only for prime exponents:
you must prove this if you are going to assert it's truth over and over. Last fiddled with by science_man_88 on 2014-04-15 at 20:32 Reason: essential -> essentially |
|
|
|
|
|
#73 | |
|
Just call me Henry
"David"
Sep 2007
Cambridge (GMT/BST)
16F816 Posts |
Quote:
I was getting errors with qint so I followed the suggestion in the code. I now mostly get the following type of error: Code:
mersenne_cofactor.f90:286.60:
print'(a,i4,a,f35.0)','factor',i,'=',int(qfactor(i)/2,kind=r16) !* if your com
1
Error: Invalid kind for INTEGER at (1)
|
|
|
|
|
|
|
#74 | ||
|
∂2ω=0
Sep 2002
República de California
101101011101112 Posts |
Quote:
================= Quote:
And I have no time to try to relearn the various intricacies of F90 - just note that my old F90 stuff was all developed on one kind of platform (DEC Alpha, using the DEC F90 compiler), so if you want to get a quick idea what may be awry, your best bets are [a] Repost the gzipped source to an online Fortran board along with your errors and see if a quick fix emerges; [b] Try one or more alternate F90 compilers / hardware platforms. Sorry, wish I had time to be of more help at the moment, but don't. |
||
|
|
|
|
|
#75 | ||
|
∂2ω=0
Sep 2002
República de California
103·113 Posts |
Small clarification, since the OP first states one thing, then actually computes another, and there are several distinct classes of probable-primality tests in play:
That is just a base-3 Fermat pseudoprime test. No reason to expect it to be rigorous for M an odd-prime-exponent Mersenne number. Oddly, the OP is clearly acquainted with Fermat's "little" theorem, but despite that goes on to claim rigor for the test applied to prime-exponent Mersennes. "I only need a proof" - that assumes there *is* a proof. The only missing thing is ... a proof. And what the OP actually computes is something different: Quote:
3^(M-1)/2 == -1 (mod M) Again no reason to expect this crterion to be rigorous for Mersennes, since those lack the key property which make the test rigorous for Fermat numbers. The reason we can restrict ourselves to -1 for the Legendre symbol on the RHS is that the base 3 is a quadratic non-residue modulo the stated class of moduli (you can see the 1997 archived code I posted also uses this quadratic nonresiduacity property and tests the powering residue against -1): Quote:
3^(M+1)/2 == -3 (mod M), which works so long as 3 < M, which is true for all Mersennes with exponent p > 2. As Bob notes that last bit is actually a nice trick for the case of Mersenne moduli since it does those the same thing that occurs in the orthodox Euler test for Fermat numbers: it leads to just a single lit bit in the exponent, and thus eliminates any scalar-muls-by-base which are needed in left-to-right binary powering whenever an intermediate bit in the binary expansion of the powering exponent = 1. As I noted such scalar muls can be easily dealt with in practice by folding them into the carry step of each iteration, but it's more elegant to do the above way. Now, why am even bothering with any of this, since we know we're dealing with a criterion which has no complexity advantages over LL and has no proof of rigor for the moduli in question? The reason is that I can't help but think that had the OP done his homework and presented it in a form more like that above rather than making grand claims and evidencing that peculiar combination of ignorance and arrogance which is the classic hallmark of the crank, the resulting thread would surely have had a very different tone than the one which actually ensued. Off to bed... Last fiddled with by ewmayer on 2014-04-17 at 08:01 |
||
|
|
|
![]() |
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Fastest software for Mersenne primality test? | JonathanM | Information & Answers | 25 | 2020-06-16 02:47 |
| New Mersenne primality test | Prime95 | Miscellaneous Math | 19 | 2014-08-23 04:18 |
| LLT Cycles for Mersenne primality test: a draft | T.Rex | Math | 1 | 2010-01-03 11:34 |
| Mersenne Primality Test in Hardware | Unregistered | Information & Answers | 4 | 2007-07-09 00:32 |
| A primality test for Fermat numbers faster than Pépin's test ? | T.Rex | Math | 0 | 2004-10-26 21:37 |