[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