![]() |
![]() |
#1 |
1976 Toyota Corona years forever!
"Wayne"
Nov 2006
Saskatchewan, Canada
11B916 Posts |
![]() Code:
storm5510 Manual testing 186326311 F 2017-10-24 15:13 0.0 0.0748 Factor: 639998333042400862489 / TF: 69-70 Dominik Radler Manual testing 189914267 F 2017-10-21 08:49 0.0 0.2034 Factor: 738480182799319135169 / TF: 69-70* Both are first (ONLY) factors from TF Neither has any LL/DC results. |
![]() |
![]() |
![]() |
#2 |
"/X\(‘-‘)/X\"
Jan 2013
B7116 Posts |
![]()
It means the factoring program stopped without finishing the bit level. It indicates incomplete work if someone in the future is trying to find more factors.
|
![]() |
![]() |
![]() |
#3 |
Oct 2015
2·7·19 Posts |
![]()
I'll enable that flag in mfaktc if I'm working at higher bit levels for instance. I don't want to spend a long time working through and entire 80+ bit level if there is a factor discovered close to the start. Unless I'm looking for all factors, it's counter productive to eliminating the non-primes as fast as possible.
|
![]() |
![]() |
![]() |
#4 |
Random Account
Aug 2009
U.S.A.
111000100112 Posts |
![]()
An excerpt from mfaktc.ini:
Code:
# 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=0 StopAfterFactor=0 |
![]() |
![]() |
![]() |
#5 |
Oct 2015
2×7×19 Posts |
![]() |
![]() |
![]() |
![]() |
#6 |
1976 Toyota Corona years forever!
"Wayne"
Nov 2006
Saskatchewan, Canada
10001101110012 Posts |
![]()
I am using Option: 0... finish the entire bit level for the current exponent even if a factor is found.
I think that if one chooses this option then the credit given should reflect the work to complete the entire bit level; ...however I have noted that I am only getting credit equivalent to the relative size of the factor. That is, if I am testing bit levels 72-73 and find only one 72.1 bit factor I only get 10% of the credit I would get for finding a 72.99 bit factor; even though my GPU has the the same amount of work by testing the entire bit range. |
![]() |
![]() |
![]() |
Thread Tools | |
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Report Results Here | clowns789 | Operation Billion Digits | 1172 | 2020-08-06 11:12 |
Recent Results/Factoring | Primeinator | PrimeNet | 4 | 2014-10-26 00:56 |
Primenet Recent Results Request | garo | PrimeNet | 7 | 2014-02-03 02:53 |
How to report GPU results | dcorbit | Information & Answers | 4 | 2012-08-13 21:53 |
How to report P-1 results | James Heinrich | Marin's Mersenne-aries | 6 | 2004-05-27 05:47 |