View Single Post
Old 2020-10-19, 12:34   #3367
kriesel
 
kriesel's Avatar
 
"TF79LL86GIMPS96gpu17"
Mar 2017
US midwest

29·167 Posts
Default

Quote:
Originally Posted by LaurV View Post
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).
A) what are you talking about? "edit the asterisk"?
B) shouldn't be necessary to manually intervene. What about people who use Misfit or mfloop etc.?
C) ... especially since completing the bit level is the mfaktc default configuration. (But not mfakto)
mfaktc ini file as distributed in zip file:
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
mfakto ini file as distributed in zip file:
Code:
# Allows you to split an assignment into multiple bit ranges.
# Note that many mfakto-kernels can handle only one bit level at a time,
# i.e. in order to use them, Stages needs to be enabled.
# 0 = disabled
# 1 = enabled
# Enabled Stages make only sense when StopAfterFactor is 1 or 2.
#
# 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=2

StopAfterFactor=2
D) Finishing the bit level makes more sense to me, because it leaves the database cleaner, with completed bit levels, not partially completed, so the folks that like to overfactor or completely factor Mersenne numbers don't need to either repeat trial factoring work already performed, or gamble by skipping part of a bit level.
E) The assignment is by bit level. Finish the assignment seems like the right thing to do.
F) The first factor found is not necessarily the smallest, since factoring on gpus is done class by class, not in ascending k order.
Attached Thumbnails
Click image for larger version

Name:	TF factor submission.png
Views:	26
Size:	75.7 KB
ID:	23565   Click image for larger version

Name:	TF factor resulting credit.png
Views:	31
Size:	101.4 KB
ID:	23566  

Last fiddled with by kriesel on 2020-10-19 at 13:27
kriesel is offline   Reply With Quote