20201018, 12:15  #3356  
"Marv"
May 2009
near the Tannhäuser Gate
2×293 Posts 
Quote:
It is from the latest Cuda toolkit ( 11.x ) and shows how to run the Cuda toolkit from WSL2. https://docs.nvidia.com/cuda/wsluserguide/index.html 

20201018, 13:55  #3357  
"TF79LL86GIMPS96gpu17"
Mar 2017
US midwest
12EF_{16} Posts 
odds
Quote:
in the same bit level, (bitlevel1)/bitlevel * (ln(bitlevel/(bitlevel1)))^{2 }/ 2 = 78/79 * (ln(79/78))^{2} / 2 = 8.03E5. In the same class c of the same bit level, (bitlevel1)/bitlevel * (ln(bitlevel/(bitlevel1)))^{2} / 2 / c = 78/79 * (ln(79/78))^{2}/2/c. Assuming moreclasses, c=960; 8.35E8 Make enough TF runs (tens of thousands or more), and finding two factors in the same bit level occurring at least once becomes almost inevitable. https://www.mersenneforum.org/showpo...82&postcount=5 I hit these recently: Code:
Manual testing 104615629 F 20201016 14:48 0.0 Factor: 75292655729231867474113 / TF: 7576 72.7737 Manual testing 104615629 F 20201016 14:48 0.0 Factor: 52035700039723086976271 / TF: 7576 33.7870 

20201018, 14:01  #3358 
"James Heinrich"
May 2004
exNorthern Ontario
2^{2}·811 Posts 
It's harder to see from the data since many people (most?) will stop factoring immediately after finding a factor, so unless the factor pair is in the same class the second factor wouldn't be discovered.

20201018, 15:00  #3359  
"TF79LL86GIMPS96gpu17"
Mar 2017
US midwest
37×131 Posts 
Quote:
Code:
# Allow to split an assignment into multiple bit ranges. # 0 = disabled # 1 = enabled # Enabled Stages make only sense when StopAfterFactor is 1 or 2. # Do not change this in the middle of a run which spans over multiple # bitlevels, in this case mfaktc will ignore the checkpoint file and # restarts from the beginning. # # Default: Stages=1 Stages=1 # possible values for StopAfterFactor: # 0: Do not stop the current assignment after a factor was found. # 1: When a factor was found for the current assignment stop after the # current bitlevel. This makes only sense when Stages is enabled. # 2: When a factor was found for the current assignment stop after the # current class. # # Default: StopAfterFactor=1 StopAfterFactor=1 

20201018, 15:04  #3360 
"James Heinrich"
May 2004
exNorthern Ontario
2^{2}×811 Posts 
I believe credit should be given appropriately depending whether the bit level was finished or not. If this is not the case please email/PM me a note/reminder with a screenshot of manual form output and I'll look into it.

20201018, 16:26  #3361  
"TF79LL86GIMPS96gpu17"
Mar 2017
US midwest
4847_{10} Posts 
Quote:
Will email you next time I (a) hit a factor, and (b) remember to do the screen capture(s) and email. Forum PM does not support attachments IIRC. Last fiddled with by kriesel on 20201018 at 16:27 

20201018, 16:37  #3362 
"James Heinrich"
May 2004
exNorthern Ontario
CAC_{16} Posts 
If you complete the bit level after finding factor it should give full credit, if you stop after factor found then scaled credit is appropriate. I'm out of town for 2 days but can double check the code when you email me.

20201018, 16:41  #3363 
"Viliam Furík"
Jul 2018
Martin, Slovakia
2·167 Posts 
I can confirm, mersenne.org gives credit only for work done before the factor is found if it's found. But neither I have a fresh factor, so I can't provide evidence immediately.

20201019, 10:27  #3364 
Romulan Interpreter
Jun 2011
Thailand
23C1_{16} Posts 
Yep, it works as expected. See discussion around, where somebody complained the given credit for factor was only 70% or so. I have many factors which got lower credit than completing full bitlevel. Which is normal, as the work done to find the factor was less than the full bitlevel, sometimes very low if the factor was found in first classes.

20201019, 11:24  #3365 
"Oliver"
Sep 2017
Porta Westfalica, DE
11×37 Posts 

20201019, 11:44  #3366 
Romulan Interpreter
Jun 2011
Thailand
21701_{8} Posts 
Oh, you mean the other way around... Never tried that, because I always stop after class, but it should be easy to try, just take a factor line already reported and edit the asterisk. I will try when I reach home in about one hour (still at job).

Thread Tools  
Similar Threads  
Thread  Thread Starter  Forum  Replies  Last Post 
mfakto: an OpenCL program for Mersenne prefactoring  Bdot  GPU Computing  1668  20201222 15:38 
The P1 factoring CUDA program  firejuggler  GPU Computing  753  20201212 18:07 
grmfaktc: a CUDA program for generalized repunits prefactoring  MrRepunit  GPU Computing  32  20201111 19:56 
mfaktc 0.21  CUDA runtime wrong  keisentraut  Software  2  20200818 07:03 
World's seconddumbest CUDA program  fivemack  Programming  112  20150212 22:51 