I just figured out how to view my own PRPNet stats, and saw that I have a PRP on the GFN262144 project.

Is this PRP automatically tested somewhere for primality? Or am I supposed to do something on my own now?
____________

Proud member of Team Aggie the Pew

"Wir müssen wissen. Wir werden wissen."
"We must know, we shall know."
- David Hilbert, 1930

This is listed as being found back in December '11, when I was using PRPNet 4.3.7. But PFGW wasn't enabled in that configuration.

The log file has since been overwritten. I do remember, though, that when I was first configuring PRPNet for running GFN on CUDA I was getting jobs that would abort after about 30 seconds with a false positive result. This may have been one of those false alarms?

Digging back through my email I found this notification email:

Subject: Candidate 406306^262144+1 was found to be PRP by PRPNet!
From: sm5ymt@sm5ymt.se

12/12/11

This number is approximately 1470328 digits long. It was found on machine 90031 using the program . Since the test performed as only a PRP test, another program, such as PFGW must be used to prove primality. If the number is prime and is large enough for the Prime Pages, please include the program in the credits. If adding to the Prime Pages don't forget to include project "PrimeGrid" in the credits.

This is listed as being found back in December '11, when I was using PRPNet 4.3.7. But PFGW wasn't enabled in that configuration.

The log file has since been overwritten. I do remember, though, that when I was first configuring PRPNet for running GFN on CUDA I was getting jobs that would abort after about 30 seconds with a false positive result. This may have been one of those false alarms?

Digging back through my email I found this notification email:

Subject: Candidate 406306^262144+1 was found to be PRP by PRPNet!
From: sm5ymt@sm5ymt.se

12/12/11

This number is approximately 1470328 digits long. It was found on machine 90031 using the program . Since the test performed as only a PRP test, another program, such as PFGW must be used to prove primality. If the number is prime and is large enough for the Prime Pages, please include the program in the credits. If adding to the Prime Pages don't forget to include project "PrimeGrid" in the credits.

It arrived in a cluster of other emails that announced actual prime discoveries through PRPNet, and I think all of them were false alarms.

Can't hurt to run it through PFGW, though, just to be sure.

I would suggest you run it manually with genefercuda first (or at the same time). If it is a false positive, you could abort pfgw teste and save a lot of hours. Good luck, anyway.

I would suggest you run it manually with genefercuda first (or at the same time). If it is a false positive, you could abort pfgw teste and save a lot of hours. Good luck, anyway.

I can see that is a good idea. 1 hour vs. approx 25 days (and that's with the fastest CPU I have!)

geneferCUDA test is underway now and I should have an answer in 1:09. PFGW still running as well, just in case, but much more slowly :)

/genefercuda -q "40>genefercuda -q "406306^262144+1"
genefercuda 2.3.0-0 (Windows x86 CUDA 3.2)
Copyright 2001-2003, Yves Gallot
Copyright 2009, Mark Rodenkirch, David Underbakke
Copyright 2010-2012, Shoichiro Yamada, Ken Brazier
Copyright 2011-2012, Iain Bethune, Michael Goetz, Ronald Schneider

Command line: genefercuda -q 406306^262144+1

Using default SHIFT value=7

Starting initialization...
maxErr during b^N initialization = 0.0000 (0.103 seconds).
Estimated total run time for 406306^262144+1 is 1:27:40
406306^262144+1 is a probable composite. (RES=77594a620c2e8e6b) (1470328 digits)
(err = 0.0703) (time = 1:28:46) 00:11:40

Command line: genefercuda.exe -q 406306^262144+1

Using default SHIFT value=7

Starting initialization...
maxErr during b^N initialization = 0.0000 (0.330 seconds).
Estimated total run time for 406306^262144+1 is 1:11:38
406306^262144+1 is a probable composite. (RES=77594a620c2e8e6b) (1470328 digits)
(err = 0.0703) (time = 1:13:17) 17:17:10