20201018, 10:01  #100 
"Mihai Preda"
Apr 2015
10100110110_{2} Posts 

20201018, 19:40  #101 
Jul 2003
So Cal
806_{16} Posts 
Yes, that fixed it.
20201018 12:36:19 Tesla K20c0 6972649 P2(1.5M,10M) Setup 1024 P2 buffers in 3.7s ... 20201018 12:38:35 Tesla K20c0 6972649 GCD: 11352967935560261207067499316137 
20201018, 20:16  #102 
"Viliam Furík"
Jul 2018
Martin, Slovakia
2^{3}×41 Posts 
P1 on known factors
Now with the new version, removing the standalone P1, could you fulfil last wish from version 6.x, that being, implement the functionality, that when you write known factor(s) in the worktodo line, it will not stop P1 when finding the already known factor(s) after the first stage? I don't know as much about C and OpenCL as you, but I think you will agree, it can be solved with a simple condition and some extension of parsing script. (If the factor found in P1 consists of only the known factor(s), ignore it, and let the P2 run  or something similar)
And to the new version, do you plan to make PRPCF available? 
20201018, 21:49  #103  
"Mihai Preda"
Apr 2015
2·23·29 Posts 
Quote:
Could you explain a bit more about what you're trying to do by not stopping P1 when it finds a factor? About accepting a factor in the worktodo line, that was the case before (the factor was completly ignored), but it turned out that was a problem because some users assumed that PRPCF must be supported because the worktodo line with a factor is not rejected. Now it's rejected for hopefully less confusion. 

20201018, 22:26  #104  
"Viliam Furík"
Jul 2018
Martin, Slovakia
2^{3}×41 Posts 
Quote:
Simply the same mechanics as in Prime95/mprime. When you create a line in worktodo.txt for P1, and you include the known factors at the end like this > Pminus1=AID,1,2,prime,1,99,0,"factor,factor" , it will ignore the factors if they are found. gpuOwl 6.x doesn't accept the factors, so it will always stop after first stage if a factor is found. 

20201018, 22:31  #105  
"Viliam Furík"
Jul 2018
Martin, Slovakia
148_{16} Posts 
Quote:


20201018, 22:49  #106 
"Mihai Preda"
Apr 2015
2·23·29 Posts 
I think any v6.x accepts factors at the end of the assignment, and completely *ignores* them. Does not read them, does not handle them in any way, as if they weren't there. Does not continue P1 past them, P1 works in the same way as if the factors were not there. Not very useful IMO.

20201018, 23:09  #107  
"Viliam Furík"
Jul 2018
Martin, Slovakia
510_{8} Posts 
Quote:


20201018, 23:15  #108 
"Mihai Preda"
Apr 2015
2×23×29 Posts 
I don't know, maybe only works for PRP. Anyway I consider that (not rejecting factors at the end) a bug.
Last fiddled with by preda on 20201018 at 23:15 
20201019, 01:58  #109  
"TF79LL86GIMPS96gpu17"
Mar 2017
US midwest
11353_{8} Posts 
Quote:
https://www.mersenneforum.org/showth...tor#post558573 https://www.mersenneforum.org/showth...tor#post556524 Gpuowl does a lot, but not everything that mprime/prime95 do, or that we users wish it would do. Last fiddled with by kriesel on 20201019 at 02:18 

20201023, 04:18  #110 
"Mihai Preda"
Apr 2015
2×23×29 Posts 
Proof v2
In a recent commit (tagged v7.1), GpuOwl switched to "Proof v2".
This is a change in the way the proof is generated  slightly different residues are used. Not much changes clientside, except that the transition between proof versions *can't* be done halfway through the PRP test (because: different residues are used for the two versions). So finish the PRP test with the old version, and start a new one with the new version. The "Proof v2" is already accepted (and preferred) by the server, and is the same format Prime95 uses. 
Thread Tools  
Similar Threads  
Thread  Thread Starter  Forum  Replies  Last Post 
GpuOwl PRPProof changes  preda  GpuOwl  20  20201017 06:51 
gpuowl: runtime error  SELROC  GpuOwl  59  20201002 03:56 
gpuOWL for Wagstaff  GP2  GpuOwl  22  20200613 16:57 
gpuowl tuning  M344587487  GpuOwl  14  20181229 08:11 
How to interface gpuOwl with PrimeNet  preda  PrimeNet  2  20171007 21:32 