manual result submission page feature request

kriesel · 2019-04-05, 19:34

If the code that interprets manual result submissions was extended to be able to recognize and process records like the following example record from CUDALucas 2.06, it would enable progress reporting for CUDALucas on gpus. This progress reporting could be optional. It would be useful for reducing expiration, reassignment, and duplicate work for tasks that are progressing on gpus. It would also increase the collection of interim residues for comparison in double checks.
Field descriptions:

Code:

|   Date     Time    |   Test Num     Iter        Residue        |    FFT   Error     ms/It     Time  |       ETA      Done   |

Example record:

Code:

|  Mar 30  07:52:38  |  M84270409  40000000  0xd6cd73de2029c850  |  4608K  0.21094   5.6984  569.84s  |   2:22:21:27  47.46%  |

This is the default console output record style.

If it worked out for CUDALucas, it could be extended to accommodate some version of gpuowl also. (Unfortunately there's a lot of variation in console or log output format for gpuowl versus version, and depending on the fft length, different versions of gpuowl are fastest.)

Please try adding this for CUDALucas (without breaking the existing functionality). I'd be happy to field test it when ready for that.

chalsall · 2019-04-05, 19:53

Quote:

Originally Posted by kriesel

Please try adding this for CUDALucas (without breaking the existing functionality). I'd be happy to field test it when ready for that.

kriesel · 2019-04-05, 21:29

A later example, with 0 days 6 hr 44 min 26 sec remaining. Eventually it gets down to minutes and seconds, and "0:00" ETA can occur, and did during my DC of M118000081.

Code:

|  Apr 01  22:35:07  |  M84270409  80000000  0x042f3884c19038dd  |  4608K  0.22070   5.6551  565.51s  |      6:44:26  94.93%  |

kriesel · 2020-04-04, 19:49

Now that so many performance improvements have been made in Gpuowl v6.11, I think previous versions of Gpuowl are of little relevance. So supporting interim residues from Gpuowl v6.11 or CUDALucas v2.06 alone would accomplish a lot.
Sample gpuowl console line:

Code:

2020-04-03 15:34:04 condorella/rx550 131500093 OK  6000000   4.56%; 29302 us/it; ETA 42d 13:30; 1ba5fe1928b87e3e (check 11.94s)

Note, could include at the right, " 1 errors"

2019-04-05, 19:34	#1
kriesel "TF79LL86GIMPS96gpu17" Mar 2017 US midwest 3·7·257 Posts	manual result submission page feature request If the code that interprets manual result submissions was extended to be able to recognize and process records like the following example record from CUDALucas 2.06, it would enable progress reporting for CUDALucas on gpus. This progress reporting could be optional. It would be useful for reducing expiration, reassignment, and duplicate work for tasks that are progressing on gpus. It would also increase the collection of interim residues for comparison in double checks. Field descriptions: Code: \| Date Time \| Test Num Iter Residue \| FFT Error ms/It Time \| ETA Done \| Example record: Code: \| Mar 30 07:52:38 \| M84270409 40000000 0xd6cd73de2029c850 \| 4608K 0.21094 5.6984 569.84s \| 2:22:21:27 47.46% \| This is the default console output record style. If it worked out for CUDALucas, it could be extended to accommodate some version of gpuowl also. (Unfortunately there's a lot of variation in console or log output format for gpuowl versus version, and depending on the fft length, different versions of gpuowl are fastest.) Please try adding this for CUDALucas (without breaking the existing functionality). I'd be happy to field test it when ready for that. Last fiddled with by kriesel on 2019-04-05 at 19:40

2019-04-05, 21:29	#3
kriesel "TF79LL86GIMPS96gpu17" Mar 2017 US midwest 3×7×257 Posts	ETA field size varies A later example, with 0 days 6 hr 44 min 26 sec remaining. Eventually it gets down to minutes and seconds, and "0:00" ETA can occur, and did during my DC of M118000081. Code: \| Apr 01 22:35:07 \| M84270409 80000000 0x042f3884c19038dd \| 4608K 0.22070 5.6551 565.51s \| 6:44:26 94.93% \|

2020-04-04, 19:49	#4
kriesel "TF79LL86GIMPS96gpu17" Mar 2017 US midwest 3×7×257 Posts	Now that so many performance improvements have been made in Gpuowl v6.11, I think previous versions of Gpuowl are of little relevance. So supporting interim residues from Gpuowl v6.11 or CUDALucas v2.06 alone would accomplish a lot. Sample gpuowl console line: Code: 2020-04-03 15:34:04 condorella/rx550 131500093 OK 6000000 4.56%; 29302 us/it; ETA 42d 13:30; 1ba5fe1928b87e3e (check 11.94s) Note, could include at the right, " 1 errors" Last fiddled with by kriesel on 2020-04-04 at 19:56

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Can't get manual page to parse a result	Siegmund	PrimeNet	6	2017-01-08 22:22
New Manual Results Submission Page	TheMawn	PrimeNet	12	2014-04-09 14:30
Manual result submission could fail	sonjohan	PrimeNet	12	2012-04-25 13:17
Manual submission of automatic assignment result	tichy	PrimeNet	4	2010-12-17 09:57
Sieve submission page available	ltd	Prime Sierpinski Project	7	2007-06-16 09:50