StopAfterFactor=0 for prime95/mprime

[mattmill30]

I have a low spec laptop running TF-LHM. Since it only takes a few hours to complete a bitlevel it seems pointless to not complete the bitlevel after a factor is located. Is there a similar configuration to the mfakt[co] StopAfterFactor=0 for prime95/mprime?

[Prime95]

Originally Posted by mattmill30

I have a low spec laptop running TF-LHM. Since it only takes a few hours to complete a bitlevel it seems pointless to not complete the bitlevel after a factor is located. Is there a similar configuration to the mfakt[co] StopAfterFactor=0 for prime95/mprime?

No similar feature in prime95

[rudi_m]

BTW I wonder about the exponent status page after finding a factor:

       Status    Details
625000049    Factored    945826699666557440279
History	
2017-02-21    rudimeier F    Factor: 945826699666557440279 / TF: 68-78

My original job line was Factor=625000049,68,78.

But what does "TF: 68-78" mean in the database? The Factor is between 68 and 69 bits and I stopped factoring after I found it.

[VictordeHolland]

Originally Posted by rudi_m

BTW I wonder about the exponent status page after finding a factor:

       Status    Details
625000049    Factored    945826699666557440279
History    
2017-02-21    rudimeier F    Factor: 945826699666557440279 / TF: 68-78

My original job line was Factor=625000049,68,78.

But what does "TF: 68-78" mean in the database? The Factor is between 68 and 69 bits and I stopped factoring after I found it.

I think it just means you found the factor while doing TF in the 68-78bit range. Not all programs search linearly and some TF programs (mfacto/c) can do more than 1bitlevel at the same time. In other words, if an exponent has 2 factors (one of 69bits and one of 72bits), its possible to find the 72 bits factor before the 69 bits one.

If you find a factor of an exponent, you know it's composite. So no need to factor it further if the goal is finding primes (which is the goal of GIMPS). Some people may argue against that. In their opinion you should complete the range (so 68 till 78bits) as that is what the original assignment was. But that is a whole different discussion and it is almost impossible the track in the database anyway.

[Madpoo]

Originally Posted by VictordeHolland

I think it just means you found the factor while doing TF in the 68-78bit range. Not all programs search linearly and some TF programs (mfacto/c) can do more than 1bitlevel at the same time. In other words, if an exponent has 2 factors (one of 69bits and one of 72bits), its possible to find the 72 bits factor before the 69 bits one.

If you find a factor of an exponent, you know it's composite. So no need to factor it further if the goal is finding primes (which is the goal of GIMPS). Some people may argue against that. In their opinion you should complete the range (so 68 till 78bits) as that is what the original assignment was. But that is a whole different discussion and it is almost impossible the track in the database anyway.

Depending on the client software, it may indicate whether it continued the assignment after a factor was found (it'll append an asterisk to the TF range). In this case I don't think that happened (it was an mprime client, v29.1 build 1).

There's a table that keeps track of "factoring effort" that has the highest bit level each exponent has been TF'd to and the P-1 bounds, but once a factor is found Primenet considers it "done" and that info isn't retained.