inconsistencies between results.txt and results.json.txt

[ixfd64]

I've noticed two inconsistencies between the results file and the JSON version:

1. PRP certification results appear in prime.log and results.json.txt but not the results.txt file. Is this intentional?

2. I know that Prime95 by default doesn't add a new timestamp if the previous result is less than 300 seconds old. One of my computers recently completed two LL double check assignments within two minutes of each other, so there was only a single timestamp as expected.

[Fri Jul 16 14:23:53 2021]
UID: ixfd64/dt-lab-26, M63547579 is not prime. Res64: 8A7E4245DDCBDD13. Wh4: 939A7956,38250151,00000000, AID: E043DABADE17E04CACFD88E2A4436941
UID: ixfd64/dt-lab-26, M63547591 is not prime. Res64: 40BCA7C1304FADB4. Wh4: 881EF8D6,3206818,00000000, AID: B6ECE4964C3A2B319CAF6C247C6D8EBA
[Fri Jul 16 15:13:42 2021]
UID: ixfd64/dt-lab-26, M63547487 is not prime. Res64: 32A3DCE0CF0B145B. Wh4: FD478EA4,56968218,00000000, AID: 90846CFE9114F401D145B772BF0AEF38
[Fri Jul 16 15:25:08 2021]
UID: ixfd64/dt-lab-26, M63547501 is not prime. Res64: 6D56700C65C5B28D. Wh4: 2D3BE683,37238773,00000000, AID: 3ADA228A63F1E318F33B486BE44DF6FA

However, results.json.txt grouped the first three results together:

[Fri Jul 16 14:23:53 2021]
{"status":"C", "exponent":63547579, "worktype":"LL", "res64":"8A7E4245DDCBDD13", "fft-length":3440640, "shift-count":38250151, "error-code":"00000000", "security-code":"939A7956", "program":{"name":"Prime95", "version":"30.3", "build":6, "port":4}, "timestamp":"2021-07-16 21:23:53", "user":"ixfd64", "computer":"dt-lab-26", "aid":"E043DABADE17E04CACFD88E2A4436941"}
{"status":"C", "exponent":63547591, "worktype":"LL", "res64":"40BCA7C1304FADB4", "fft-length":3440640, "shift-count":3206818, "error-code":"00000000", "security-code":"881EF8D6", "program":{"name":"Prime95", "version":"30.3", "build":6, "port":4}, "timestamp":"2021-07-16 21:25:57", "user":"ixfd64", "computer":"dt-lab-26", "aid":"B6ECE4964C3A2B319CAF6C247C6D8EBA"}
{"status":"C", "exponent":63547487, "worktype":"LL", "res64":"32A3DCE0CF0B145B", "fft-length":3440640, "shift-count":56968218, "error-code":"00000000", "security-code":"FD478EA4", "program":{"name":"Prime95", "version":"30.3", "build":6, "port":4}, "timestamp":"2021-07-16 22:13:42", "user":"ixfd64", "computer":"dt-lab-26", "aid":"90846CFE9114F401D145B772BF0AEF38"}
[Fri Jul 16 15:25:08 2021]
{"status":"C", "exponent":63547501, "worktype":"LL", "res64":"6D56700C65C5B28D", "fft-length":3440640, "shift-count":37238773, "error-code":"00000000", "security-code":"2D3BE683", "program":{"name":"Prime95", "version":"30.3", "build":6, "port":4}, "timestamp":"2021-07-16 22:25:08", "user":"ixfd64", "computer":"dt-lab-26", "aid":"3ADA228A63F1E318F33B486BE44DF6FA"}

Is there a reason for this?

Don't worry about the assignment keys and residues as these are completed double checks.

[Zhangrc]

Originally Posted by ixfd64

AID: XXXXXXXXX

Do not post your assignment ID!

[ixfd64]

These are completed assignments, so the AIDs are no longer useful.

[axn]

1. results.json.txt supersedes results.txt, so i believe this is intentional.
2. The standalone timestamp is a relic. The actual result timestamp is present in the json itself.