Yes, for example

[CODE]./CUDAPm1 -b1 value -b2 value exponent[/CODE]

When submitting results from cuda p-1, I'm getting this:

Found 1 lines to process.
processing: P-1 no-factor for M68xxxxxx (B1=645,000, B2=15,802,500, E=4)
Error: Missing checksum. Correct the problem or email results to [email]woltman@alum.mit.edu[/email].

Is there anything we can do to fix this?

-- Craig

[QUOTE=nucleon;382377]Error: Missing checksum.
Is there anything we can do to fix this?[/QUOTE]I have fixed the manual results form to accept CUDAPm1 results without checksum, as it was supposed to be.

I guess there's potentially also the possibility that George could share his checksum-generating code with the CUDAPm1 authors (either explicitly or wrapped inside a closed-source DLL or similar) in which case CUDAPm1 could generate the correct checksums on its own, but that's a whole other area of discussion.

Thanks.

I have my titan working on P-1, I'd hate to stop it. :)

Still no good.

Submitting:
M67xxxxxx found no factor (P-1, B1=635000, B2=14446250, e=2, n=4096K CUDAPm1 v0.20)

And I get:

Found 1 lines to process.
processing: P-1 no-factor for M67xxxxxx (B1=635,000, B2=14,446,250, E=2)
Error: Missing checksum. Correct the problem or email results to [email]woltman@alum.mit.edu[/email].

-- Craig

[QUOTE=nucleon;382390]Still no good.[/QUOTE]Sorry, I put the checksum code in the wrong place. Please try again?

Its working for me now. Thanks.

It is not working for me. When a factor is found I get the answer:
[COLOR=darkgreen]processing: P-1 factor 888024044817831733817 for [URL="http://www.mersenne.org/report_exponent/?exp_lo=2297327&full=1"][COLOR=#000080]M2297327[/COLOR][/URL] (B1=615,000, B2=12,000,000, E=12)[/COLOR]
[COLOR=red]Insufficient information for accurate CPU credit. For stats purposes, assuming factor was found using ECM with B1 = 50000. CPU credit is 0.0908 GHz-days. [/COLOR]
[COLOR=red] [/COLOR]
[COLOR=red] [/COLOR]
[COLOR=red] [/COLOR]

[QUOTE=ugonabuj;382395]It is not working for me. When a factor is found I get the answer:
[COLOR=darkgreen]processing: P-1 factor 888024044817831733817 for [URL="http://www.mersenne.org/report_exponent/?exp_lo=2297327&full=1"][COLOR=#000080]M2297327[/COLOR][/URL] (B1=615,000, B2=12,000,000, E=12)[/COLOR]
[COLOR=red]Insufficient information for accurate CPU credit. For stats purposes, assuming factor was found using ECM with B1 = 50000. CPU credit is 0.0908 GHz-days.[/COLOR][/QUOTE]That's very interesting. That shouldn't happen. Investigating...

edit: and found the problem. Turns out I was still calling the method-unknown factor recording function rather than the found-by-PM1 function. Sorry about that.

When I send it to your site it is working perfectly. In fact it has never
worked for CUDAPm1 from the start in May 2013.


Userid:Hbendtz

It's a long-standing problem with mersenne.org's manual results parser which was just upgraded within the past 48 hours. Apparently I'm still finding a few bugs.

The old code ignored anything on the result line other than the exponent+factor, then made some broad assumptions about how factors were found. In this example, the rule that applied was "exponent < 16M, therefore must be ECM".

But, the bug should be fixed now, please let me know if you see that message again, because you shouldn't. :smile:

[i]edit: There is a probable plan to update the previously-recorded factor results that were falsely recorded as ECM or P-1 when in fact they were P-1 or TF, but that won't happen for a few days at the earliest.[/i]