For the past 36 hours, my wingman and I have been pounding away on this SR5 task on my 3930k:

http://www.primegrid.com/workunit.php?wuid=386276075

From the sticky thread, I know finding a prime is supposed to take 10x as long to crunch as a regular workunit, which take around 2:15 on my computer (6 threads active). This particular one was at about 44% at the 2 hour mark, and the percentage per hour completion rate steadily decreased and seems to be asymptotic with 0. To speed the crunching and get that coveted #1 spot (since I am against an Ivy i5) I suspended the other tasks and have just the 1 core running on this guy. Yesterday afternoon at 25 hours it was 98%, this morning at 36 hours when I left for work it was at 99.994%. Based on the other SR5 prime times on a 3930k, that seems a bit long, yes?

So, I'm curious, considering my wingman is still working on this as well, is it likely that we are close to finding the next SR5 or is something off here?
____________
Eating more cheese on Thursdays.

It's certainly possible that it's prime, but the only way I could answer this is to test that candidate myself. I don't know how the boinc client displays progress on an SR5 prime as I've never had one myself. I've triplechecked quite a few, but we generally do so manually using the pfgw program.

Your wingman could be running any number of projects simultaneously, so you can't really conclude anything from how long he/she is taking to return that candidate.

I've started checking it on this machine. I'll let you know in about 90 minutes.
____________
My lucky number is 75898⁵²⁴²⁸⁸+1

Your wingman could be running any number of projects simultaneously, so you can't really conclude anything from how long he/she is taking to return that candidate.

Result sent via PM.

In the future, it's best to ask these questions via PM rather than publicly. It's possible (although unlikely) that an unscrupulous person could figure out what number you're testing and attempt to report the prime as their discovery to the top 5000 prime list before you and your wingman complete the testing.

In general, if a task appears to be "stuck", the best approach is:

1) In the BOINC manager, "Suspend Activity" to stop all running tasks.
2) Reboot your computer.
3) In the BOINC manager, change back to "Run according to preferences."

In most cases, that should unstick the task.

Although I've never personally seen it, on an SGS or SR5 prime, what you should see if a prime is found is a normal progression from 0 to 99% followed by the percentage resetting back to 0, and then progressing a second time up to 100%. In the case of an SR5 test on a Reisel number (i.e., c = -1), this will occur about 5 times.
____________
My lucky number is 75898⁵²⁴²⁸⁸+1

Is it my imagination or did the OP abort his task ?!

EDIT:- That means it is not prime? :-(

Not this one, but another one is. (by Brown. Congrats!)

Another "K" bites the dust.

One of the primes has been reported to Top-5000: http://primes.utm.edu/primes/page.php?id=117597

Looking at the status page, it would seem that the other prime is for 207394*5^n-1

For the second one: Are we waiting on doublechecker to finish up (unlikely), or on the primary finder to report it (19 days)?

Can we at least announce the first one?

For the second one: Are we waiting on doublechecker to finish up (unlikely), or on the primary finder to report it (19 days)?

Can we at least announce the first one?

For the second one: Are we waiting on doublechecker to finish up (unlikely), or on the primary finder to report it (19 days)?

We are still waiting for a wingman to doublecheck.

1) Someone discovers a prime.

2) We see that ONE person discovered a prime, but it's still waiting for the wingman. Unless we suspect it's a false positive, we'll start verifying the prime on our own computers. Although we typically say "we're verifying it on the server...", we really mean we're verifying it on our personal computers because they're MUCH faster than the server. (The server isn't AVX.)

3) When the wingman comes in, we notify the prime finder. If he has authorized us to report on his behalf, we proceed to step 4. Otherwise, we send him an email and he either authorizes us to report for him, or he reports it himself. If he doesn't respond in 19 days, we repeat the process with the wingman.

4) Either the user reports the prime to the top 5000 website, or we report it for him or her.

5) We update the appropriate PrimeGrid webpages and publish an announcement about the prime.

6) When the prime is verified on the top 5000 website, the PrimeGrid server makes the prime visible in the prime list.

1) Someone discovers a prime.

2) We see that ONE person discovered a prime, but it's still waiting for the wingman. Unless we suspect it's a false positive, we'll start verifying the prime on our own computers. Although we typically say "we're verifying it on the server...", we really mean we're verifying it on our personal computers because they're MUCH faster than the server. (The server isn't AVX.)

3) NEW: Once we've verified that the number is indeed prime (using both LLR and PFGW), if the wingman hasn't responded yet, we modify the workunit so it only requires one task to verify. The prime number then gets validated immediately without the need for a wingman. This permits us to proceed with reporting the prime. The wingman's task is allowed to continue and he will get BOINC credit and be recognized as the double checker if he correctly returns the result.

4) Without waiting for the wingman we notify the prime finder. If he has authorized us to report on his behalf, we proceed to step 5. Otherwise, we send him an email and he either authorizes us to report for him, or he reports it himself.

5) Either the user reports the prime to the top 5000 website, or we report it for him or her.

6) We update the appropriate PrimeGrid webpages and publish an announcement about the prime.

7) When the prime is verified on the top 5000 website, the PrimeGrid server makes the prime visible in the prime list.

I would go one further. For SR5, if LLR permits it*, only do the initial part of test on the client. Skip the proving part, and report the results straightaway. The admins will be doing the rigorous proof offline, so nothing's lost. The total time to report the prime will come down. This will also obviate this thread (long running task = stuck!)

* Whether LLR can be configured for only the first part: There are three settings that I can find in the documentation
ForcePRP=1 : Do only a PRP test, even if a deterministic one is possible.
LucasPRPtest=1 : For a PRP test, use only the Lucas+Frobenius algorithm.
FermatPRPtest=1 : For a PRP test, use only the Fermat SPRP algorithm.

Here's the second SR5 prime from April 9th: http://primes.utm.edu/primes/page.php?id=117731

Congratulations Honza!

207394*5^1612573-1

We can scratch k=207394 off the Riesel base 5 list.
____________
My lucky number is 75898⁵²⁴²⁸⁸+1

This one was found on the 25th: http://primes.utm.edu/primes/page.php?id=117737

Congratulations Scott!
____________
My lucky number is 75898⁵²⁴²⁸⁸+1

Congrats Scott.

Looks like we have made TOP5000 verification process busy for a while :-)
____________
My stats
Badge score: 1*1 + 5*1 + 8*3 + 9*11 + 10*1 + 11*1 + 12*3 = 186