View Single Post
Old 2022-05-08, 05:36   #20
Batalov
 
Batalov's Avatar
 
"Serge"
Mar 2008
Phi(4,2^7658614+1)/2

9,901 Posts
Default

Correct, primecertexport(C,1) goes 99% of the way toward FactorDB compatibility, but not all the way.
Quote:
Originally Posted by Batalov View Post
Btw, I had to "massage" their cert a little bit, but then factorDB took it. Took 3 iterations slightly reformatting the file (and to rename it into .out file)
I actually blame FactorDB implementation (it surely doesn't use Primo to validate). I suspect that Jared implemented his exported cert compatibility for back-to-Primo compatibility. I doubt he submitted any to FactorDB.

In 50001-file (which looks like Andreas also created it merely with primecertexport(C,1)), I replaced N=0x... by N=$.. (but I didn't replace any other 0x by $ in the file)
as well as created a full header of the file from some previous Primo-generated files. I added "Expression=..." row and some more as follows:
Code:
[PRIMO - Primality Certificate]
Version=4.3.2 - LX64
WebSite=http://www.ellipsa.eu/
Format=4
ID=B427A03BFE679
Created=May-4-2021 05:30:38 PM
TestCount=1645
Status=Candidate certified prime

[Comments]
...

[Candidate]
File=/tmp/D/cu1/primo432/work/ttt.in
Expression=10^50000+65859
N=$152E81DCC5CF9B751C028E9<<...>>
HexadecimalSize=41524
DecimalSize=50001
BinarySize=166096

[1]
... <<no more changes below>>
Maybe FactorDB needs some of those added rows, e.g. DecimalSize.
When FactorDB's intake validator is not happy, it reports: "1 zip file found, 0 certs added."
Then it means that you have to muck with the file some more.
Batalov is offline   Reply With Quote