sb client continue to crunch after it found a P-1 factor

[Aillas]

Hi,

I was looking at my result.txt and prime.log files and found this:

On december 10, sb found a factor for 22699*2^17456374

In Result.txt
[Thu Dec 10 01:11:26 2009]
P-1 found a factor in stage #2, B1=40000, B2=170000.
UID: Ludovic, 22699*2^17456374+1 has a factor: 2449061290113623401, AID: 000000000000000000000000000F7A93

In prime.log
[Thu Dec 10 01:11:26 2009 - ver 25.11]
Sending result to server: UID: Ludovic, 22699*2^17456374+1 has a factor: 2449061290113623401, AID: 000000000000000000000000000F7A93

So the result was sent to the server.

and then I found this:

In Result.txt
[Sun Jan 3 03:41:46 2010]
UID: Ludovic, 22699*2^17456374+1 is not prime. Wd2: D1BA2149,00000000, AID: 000000000000000000000000000F7A93

In prime.log
[Sun Jan 3 03:41:46 2010 - ver 25.11]
Sending result to server: UID: Ludovic, 22699*2^17456374+1 is not prime. Wd2: D1BA2149,00000000, AID: 000000000000000000000000000F7A93



Hopefully, it occurs only on 1 of my exponents, but what a waste of time.
I hope there are not a lot of cases like this one.

Hope this help

Regards

[opyrt]

Hi.

I have no answer to your post, but I would like to remind you that you should not post the residues (RES64) to the public.

[Aillas]

Hi.

I have no answer to your post, but I would like to remind you that you should not post the residues (RES64) to the public.

I was not aware of this.
Removed.

[Frodo42]

I sure hope this gets fixed ... I haven't seen it on my cruncher here (Linux 64bit) but I haven't found any factors ... if everyone could check their result.txt files so that we can see if this is a general problem and Louie will be able to fix it fast when he finds the time.

Hi.

I have no answer to your post, but I would like to remind you that you should not post the residues (RES64) to the public.

Completely of topic ... but why?

[imwithid]

I've checked my results.txt (prior to this thread I've never really looked through it). I was surprised to see several round off errors recently (in the last two months, I've seen six "ERROR: ROUND OFF (0.5) > 0.40"). Again, not to detract from the current thread, but:

1. What does this error mean? If I get this error should I turn the "Round off checking" feature on (even though the readme.txt states that there is no good reason for having this feature) or do I have a hardware problem?
2. Like the above user had mentioned, what's with the RES64 output? Why is this to be kept confidential?

Regards,
Dan.

[philmoore]

The RES64 output would enable another user to fraudulently claim that they had double-checked this number and therefore receive credit for it. Masking the last 2 characters (8 bits) would in all likelihood prevent this. So for example: 7AE52134B5669A__ reveals most of the residue, but not the entire thing.

By the way, the round-off error > 0.4 probably indicates a problem with your computer hardware, and needs to be investigated. Turning off round off checking is not a good idea!

[imwithid]

By the way, the round-off error > 0.4 probably indicates a problem with your computer hardware, and needs to be investigated. Turning off round off checking is not a good idea!

I've turned round off checking on to see what would happen.

[Work thread Jan 29 02:51] Iteration: 15181500 / 17450262 [86.99%]. Round off: 0.0000000000 to 0.0937500000. Per iteration time: 0.046 sec.

I now get the above in addition to the "per iteration" time. Is this within norms or should it be 0?

[prime95]

On december 10, sb found a factor for 22699*2^17456374

In Result.txt
[Thu Dec 10 01:11:26 2009]
P-1 found a factor in stage #2, B1=40000, B2=170000.
UID: Ludovic, 22699*2^17456374+1 has a factor: 2449061290113623401, AID: 000000000000000000000000000F7A93

and then I found this:

In Result.txt
[Sun Jan 3 03:41:46 2010]
UID: Ludovic, 22699*2^17456374+1 is not prime. Wd2: D1BA2149,00000000, AID: 000000000000000000000000000F7A93

Has anyone else noticed this problem? I just tried replicating the problem and couldn't. Please check your results.txt files and let me know if this was a one time occurrence or if finding P-1 factors is not then skipping the PRP test.