processed dc and tc posts

[kriesel]

Doublecheck=126745771,80,1
Prime95 or mprime with Jacobi check, random offset is recommended for triple check.

https://www.mersenne.org/report_expo...6745771&full=1

Second run was on my generally very reliable GTX1080. Selected interim residues for check against triple check run follow. The log file contains such lines at 50,000-iteration intervals. Offset for the run: offset = 63381765.

|   Date     Time    |   Test Num     Iter        Residue        |    FFT   Error     ms/It     Time  |       ETA      Done   |
|  Mar 19  20:38:52  | M126745771   1000000  0x15edf96ca917718e  |  6912K  0.25000   6.5481  327.40s  |   9:12:49:49   0.78%  |
|  Mar 20  03:56:31  | M126745771   5000000  0xb051d166bd0d4b77  |  6912K  0.26367   6.5451  327.25s  |   9:05:54:55   3.94%  |
|  Mar 20  13:03:25  | M126745771  10000000  0xc78694fe47a6c290  |  6912K  0.26563   6.6095  330.47s  |   8:20:48:43   7.88%  |
|  Mar 21  07:19:05  | M126745771  20000000  0xe8b99fde161b0dc9  |  6912K  0.25627   6.5234  326.17s  |   8:02:45:13  15.77%  |
|  Mar 22  01:36:06  | M126745771  30000000  0x8086b6a513e02681  |  6912K  0.26563   6.5931  329.65s  |   7:08:36:49  23.66%  |
|  Mar 22  19:54:40  | M126745771  40000000  0xdb678d3e24b74ed8  |  6912K  0.25000   6.5796  328.98s  |   6:14:28:29  31.55%  |
|  Mar 23  14:14:22  | M126745771  50000000  0x0487c8c933f3b472  |  6912K  0.26563   6.6038  330.19s  |   5:20:17:48  39.44%  |
|  Mar 24  08:31:55  | M126745771  60000000  0x602d363d22b19738  |  6912K  0.26563   6.5840  329.20s  |   5:02:01:43  47.33%  |
|  Mar 25  12:33:21  | M126745771  70000000  0xeb8cda315394d739  |  6912K  0.28125   6.5855  329.27s  |   4:07:43:28  55.22%  |
|  Mar 26  06:46:58  | M126745771  80000000  0x15755ff86e6e458a  |  6912K  0.26563   6.5379  326.89s  |   3:13:24:54  63.11%  |
|  Mar 27  23:45:57  | M126745771  90000000  0x0754d138fd03932a  |  6912K  0.25000   6.5502  327.51s  |   2:19:07:16  71.00%  |
|  Mar 28  17:57:45  | M126745771 100000000  0x9adb1773be482891  |  6912K  0.25781   6.5468  327.34s  |   2:00:50:10  78.89%  |
|  Mar 29  12:07:57  | M126745771 110000000  0xbcb72ec2eb415862  |  6912K  0.26563   6.5203  326.01s  |   1:06:33:46  86.78%  |
|  Mar 30  06:20:06  | M126745771 120000000  0x78dfe475a7ee035a  |  6912K  0.26563   6.5534  327.67s  |     12:18:32  94.67%  |
|  Mar 30  15:25:57  | M126745771 125000000  0x128cef69ca9d362a  |  6912K  0.26172   6.5461  327.30s  |      3:11:06  98.62%  |
|  Mar 30  17:15:07  | M126745771 126000000  0x88825c2169f7f431  |  6912K  0.26563   6.5485  327.42s  |      1:21:38  99.41%  |
M( 126745771 )C, 0x86e0ae7fee07db__, 6912K, CUDALucas v2.06beta, estimated total time = 231:14:17

max error logged 0.29688
No separate error messages appear in the log file for this primality test.

[kriesel]

Originally Posted by Uncwilly

This is not a commentary thread. If you want to add info to the quoted post, send me a pm with the specific changes or an new version of that post. Your post that I have quoted will be moved or wished away into the cornfield.

Hmm. See also posts 6 thru 8 by others.

[Uncwilly]

Originally Posted by kriesel

Hmm. See also posts 6 thru 8 by others.

7-8 are in context to a current is and will be moved after a sufficient time. If you gander at the processed thread, you will see many such things over there. It is closed and so all of the posts were here.

6 is important for those that may claim PRP-DC's. I have thought about extracting content and moving it to post 4.

[Runtime Error]

Hi, I can take this one. Running it with manual testing in mprime on linux, but I've registered it with Prime95 on windows.

Doublecheck=126745771,80,1

Edit: it says "mPrime95 please"... thought it was either mprime in linux or Prime95 on windows. Let me know if I should stop the test. Should be done in ~4 days

[Uncwilly]

Originally Posted by Runtime Error

Edit: it says "mPrime95 please"... thought it was either mprime in linux or Prime95 on windows. Let me know if I should stop the test. Should be done in ~4 days

Just my either/or shorthand. Your good. Note Ken's list above. You can see how your run is matching.

[Runtime Error]

Originally Posted by Uncwilly

Note Ken's list above. You can see how your run is matching.

Noob question: How do I see these residuals? I'm running headless. Is there an option in mprime to write interim residuals to the results.txt or results.json.txt file?

Follow up: When manual testing, can we submit interim residuals to the server on the manual result turn in page somehow?

Thanks!

[ATH]

Use this in prime.txt to display residues in results.txt every 1M iterations, or how often you want:

InterimResidues=1000000

[Runtime Error]

Thank you, ATH. Residuals @ 40m are:

M126745771 interim LL residue 5FAC61D44C636740 at iteration 40000000
M126745771 interim LL residue F41348BCAF00B2D7 at iteration 40000001
M126745771 interim LL residue DB678D3E24B74ED8 at iteration 40000002

Which unfortunately does not match Kriesel's, unless it needs to be adjusted by offset somehow?

M126745771 40000000 0xdb678d3e24b74ed8

I also reran the first million iters for this:

M126745771 interim LL residue C92BE3EE0729DDBC at iteration 1000000
M126745771 interim LL residue 70230187AD96E7C9 at iteration 1000001
M126745771 interim LL residue 15EDF96CA917718E at iteration 1000002

Which does not match Kriesel's either:

M126745771 1000000 0x15edf96ca917718e

[Prime95]

Originally Posted by Runtime Error

Which unfortunately does not match Kriesel's, unless it needs to be adjusted by offset somehow?:

you match. prim95 is off by 2 iterations -- my bad

[Runtime Error]

Originally Posted by Prime95

you match. prim95 is off by 2 iterations -- my bad

Oh I see now, thank you!

[kriesel]

Originally Posted by Prime95

you match. prim95 is off by 2 iterations -- my bad

Perhaps for v30, mprime and prime95 could be changed to compatible iteration numbering, and single-iteration-output rather than 3-successive, to reduce future confusion when comparing to the various other programs.