Fixup Old Primo Certificate?
 

Attempting to put the primality proof for [URL="http://www.primes.viner-steward.org/andy/S/29D40BF5.html"](10708^3061-1)/10707[/URL] into the factordb requires the Primo Certificate for the [URL="http://www.primes.viner-steward.org/andy/S/29D40BF5.zip"]P3092[/URL].

When uploaded to the factordb, this certificate fails with the message "No number found in file." Comparing it to other certificates that loaded OK, I see that this was generated with an older version of Primo, Version 1.1.0. I see that this lists the number as N = , and then the decimal expansion spread over many lines with "\", whereas newer certificates have N$= and the hexadecimal expansion on a single line.

I see other differences - the new certificate has Type= lines. While both certificates have A and B lines, the same format differences as described for the N line applies.

Does anybody know how to hand edit this certificate to make it acceptable to the factordb version of Primo? I don't mind diddling with it if it is likely to work, but I don't want to waste time if we know it isn't convertible.

[QUOTE=wblipp;300405]When uploaded to the factordb, this certificate fails with the message "No number found in file." Comparing it to other certificates that loaded OK, I see that this was generated with an older version of Primo, Version 1.1.0. I see that this lists the number as N = , and then the decimal expansion spread over many lines with "\", whereas newer certificates have N$= and the hexadecimal expansion on a single line.[/QUOTE]

Hmmm, I wrote the verifier that is used by the factordb. I think I can update the verifier to accept this new (old?) format. I didn't realize there was more than one format out there. I wonder if there are others that we haven't seen yet. I'll be busy for the next few days, but I should be able to get this working by next weekend. I'll report back here when I make some progress on this.