[QUOTE=heliosh;492408]Undefined index: timing in 0.95_cpu_credit.inc.php on line 72[/QUOTE]I put a debug line in to see what's not showing up, once someone else reports a similar result that generates that error.
@George if you spot the problem first feel free to clobber my debug.

edit: George I think we cross-uploaded, please re-upload your fix

huge GHzD result
 

i recall one a few years ago
i think someone adjusted that credit downward.

[url]https://www.mersenne.org/report_exponent/?exp_lo=32077&full=1[/url]

[url]https://www.mersenne.org/primenet/graphs.php[/url]

Mersenne.org is down.

[url]https://downforeveryoneorjustme.com/www.mersenne.org[/url]

[QUOTE=Uncwilly;493197]Mersenne.org is down.

[url]https://downforeveryoneorjustme.com/www.mersenne.org[/url][/QUOTE]

Sorry, I put up a late notice on the official maintenance thread, but not until I was already underway.

Just routine stuff, shouldn't be too much longer.

Duplicate PRP was not logged as a DC
 

On July 31, I completed and reported a manual run of a PRP in gpuOwL, for an exponent which already had a completed PRP test in the database.
Instead of counting and logging my submitted result as a PRP-DC, it generated an error code 40. Computing credit was issued, but the result was not logged in the database for the exponent. I emailed a couple people who often fix such things, on July 31, but there appears to have been no response and no change yet. See [URL]https://www.mersenne.org/report_exponent/?exp_lo=153000031&exp_hi=&full=1[/URL]
These are runs to completion, of exponents started to probe the exponent limits of fft transforms in gpuOwL, and many of them have already been separately run from start to completion by someone else. My runs of them are being completed sequentially on a slow gpu with a different transform and so are essentially guaranteed to not complete in time to be poached first tests.

I know PrimeNet is not crediting me with any PRP-DC for any such result, because the total given in my status is still zero.

I'm expecting to submit more such instances in the near future. It would be nice if the results did get recorded into the database, and counted in user status. Ideally the PrimeNet server would handle the error and treat the duplicate PRP as a PRP-DC.
Failing that, would it accept an unassigned result, manually edited from PRP to PRP-DC before submission?


edit: moderator please move this post to the [url]http://www.mersenneforum.org/showthread.php?t=5758[/url] [B]OFFICIAL "SERVER PROBLEMS" THREAD [/B]

[QUOTE=kriesel;493221]On July 31, I completed and reported a manual run of a PRP in gpuOwL, for an exponent which already had a completed PRP test in the database.
Instead of counting and logging my submitted result as a PRP-DC, it generated an error code 40. Computing credit was issued, but the result was not logged in the database for the exponent. I emailed a couple people who often fix such things, on July 31, but there appears to have been no response and no change yet. See [URL]https://www.mersenne.org/report_exponent/?exp_lo=153000031&exp_hi=&full=1[/URL]
These are runs to completion, of exponents started to probe the exponent limits of fft transforms in gpuOwL, and many of them have already been separately run from start to completion by someone else. My runs of them are being completed sequentially on a slow gpu with a different transform and so are essentially guaranteed to not complete in time to be poached first tests.

I know PrimeNet is not crediting me with any PRP-DC for any such result, because the total given in my status is still zero.

I'm expecting to submit more such instances in the near future. It would be nice if the results did get recorded into the database, and counted in user status. Ideally the PrimeNet server would handle the error and treat the duplicate PRP as a PRP-DC.
Failing that, would it accept an unassigned result, manually edited from PRP to PRP-DC before submission?


edit: moderator please move this post to the [URL]http://www.mersenneforum.org/showthread.php?t=5758[/URL] [B]OFFICIAL "SERVER PROBLEMS" THREAD [/B][/QUOTE]




This happened to me also, this is weird that the double PRP results are not recognized as double-checks. If one computes the same number twice the second time is wasted.

Are you by any chance submitting the second PRP result with the same shift-count of zero as the first PRP test?

If so, best to update to a recent version of Prime95/mprime.

[QUOTE=GP2;493241]Are you by any chance submitting the second PRP result with the same shift-count of zero as the first PRP test?

If so, best to update to a recent version of Prime95/mprime.[/QUOTE]




I am using gpuOwl.

The server is picky. It will not accept as a DC any result that is performed with the same software and same shift count.

[QUOTE=Prime95;493254]The server is picky. It will not accept as a DC any result that is performed with the same software and same shift count.[/QUOTE]




So, what to do about it ?

[QUOTE=SELROC;493258]So, what to do about it ?[/QUOTE]

Do you have a recent version of gpuOwL? I think recent versions have non-zero shift counts, but the earliest versions didn't.