A bug or... a surprising result???...
 

You all may wish to check the status of the following exponent:
[B]26556359.[/B]
I won´t say a word, my lips are sealed, my fingers frozen...:devil:

Interesting... I will know tomorrow.

Iteration 140000 M( 26556359 )C, 0xf2c30c641c2b5556, n = 2097152
4.237 ms/iteration

If it isn't a bug, it'll be a great incentive for taking assignments currently considered unglamorous.

Maybe the residue is 0000000000000001? :geek:

[QUOTE=lycorn;264590]You all may wish to check the status of the following exponent:
[B]26556359.[/B]
I won´t say a word, my lips are sealed, my fingers frozen...:devil:[/QUOTE]
You are making a habit of spotting these things!
How do you do it?

My money is on a bug.

[QUOTE=Batalov;264594]Maybe the residue is 0000000000000001? :geek:[/QUOTE]
But chance of those 56 bits all 0 is 1/2^56.

[QUOTE]You are making a habit of spotting these things!
How do you do it? [/QUOTE]

Actually this finding was a bit different. Msomething was spotted as a "success" in the Top producers report for first time LLs. I haven´t checked that report for ages now, it´s maybe time to go and have a look :wink:...
This time I was just going to check whether there were some more of Axon´s "accomplishments" in the Recent Cleared report. Instead, amphoria´s accomplishment caught my eye. Hey, it´s rather easy to spot that bunch of 0s in the middle of hex stuff (I don´t wear glasses).
Let´s wait and see.
BTW, is GW on vacation?

He's online ATM.
Probably on the case. Has anyone told him yet?

*crosses fingers*

:whistle:

Someone with a CUDA-capable GPU could probably test the exponent in a day or so. However, it has already been assigned to someone else, and poaching it could have ethical implications.

[QUOTE=ixfd64;264605]Someone with a CUDA-capable GPU could probably test the exponent in a day or so. However, it has already been assigned to someone else, and poaching it could have ethical implications.[/QUOTE]

I did say *I* will know tomorrow. I don't have to tell anyone else... :smile:

[QUOTE=frmky;264610]I did say *I* will know tomorrow. I don't have to tell anyone else... :smile:[/QUOTE]

If it is prime, the form is to tell George, he announces a
possible new prime and gets it "verified".

Meanwhile, we all try to guess what the exponent is...
Oops!

David

Amphoria's residue is 000000000000002. This happens if the FFT data is zeroed anywhere by error during the LL test.

Shift count is zero. Probably means it wasn't prime95.

Oh well... Guess we'll just have a triple check then.

[QUOTE=frmky;264622]Oh well... Guess we'll just have a triple check then.[/QUOTE]
Male that a double!

[QUOTE=Prime95;264613]Amphoria's residue is 000000000000002. This happens if the FFT data is zeroed anywhere by error during the LL test.

Shift count is zero. Probably means it wasn't prime95.[/QUOTE]
I experienced this with an erroneous CUDALucas run. Beginning with iteration 11 million it constantly looped at 002.

The first test had the correct residue. It is not prime.

[QUOTE=frmky;264692]The first test had the correct residue. It is not prime.[/QUOTE]Proven.

Or perhaps your identical residues were down to a bug
(as yet undiscovered)?

David
Conspiracy Theorist (NOT:smile:)

[QUOTE=Prime95;264613]Amphoria's residue is 000000000000002. This happens if the FFT data is zeroed anywhere by error during the LL test.

Shift count is zero. Probably means it wasn't prime95.[/QUOTE]

It was actually CUDALucas.

I see that I am not the first person to experience this.

I've also had this kind of issue with CUDALucas 1.0, where at some point the residue is the same over all upcoming 10k iterations.
Sometimes restoring from a checkpoint file helped(If I was fast to notice the abnormal behavior).

Needless to say...
 

2^2 - 2 = 2

Or 0^2 - 2 = -2
(-2)^2 = 2^2