mersenne.ca

[De Wandelaar]

Thanks for the check and the solution !

[James Heinrich]

Data has finished re-importing.

[lycorn]

No data as of 04/10/2020 11:45 GMT.

[James Heinrich]

Originally Posted by lycorn

No data as of 04/10/2020 11:45 GMT.

Should be back to normal now.

[lycorn]

It is, indeed.

[Ensigm]

Minimal TF effort aka "min. TF" as shown in the factor entry seems to be quite different from the efforts shown in the TF history entry. For example, for M113317913 the "min. TF" shows 8.4409 GHz.d, whereas the total effort up to 2⁷³ is already roughly 8.4409*2, and the TF effort in 73-74 bits is greater than 8.4409GHz-days too, considering the fact that the factor is close to 2^74.
This couldn't be correct, unless the GHz-days in the factor entry and in the TF history are calibrated differently (which is also confusing).

[Ensigm]

Also there‘s another thing in the TF history of M113317913 that perplexes me. Its factor 18823632331491929056447 is so close to 74 bits (73.995), but the GHz-days shown is much less than the TF effort of the whole 73-74 bits range, which should be 2 times the TF effort of 72-73 bits.

[VBCurtis]

Originally Posted by Ensigm

Minimal TF effort aka "min. TF" as shown in the factor....
This couldn't be correct, unless the GHz-days in the factor entry and in the TF history are calibrated differently (which is also confusing).

What is confusing about doing more than "minimal"? Minimal != recommended.

[James Heinrich]

Originally Posted by Ensigm

Also there‘s another thing in the TF history of M113317913 that perplexes me. Its factor 18823632331491929056447 is so close to 74 bits (73.995), but the GHz-days shown is much less than the TF effort of the whole 73-74 bits range, which should be 2 times the TF effort of 72-73 bits.

One thing that may be not immediately obvious is that TF is not done linearly from bitA to bitB, the work is divided into classes (by default mfaktx uses 4620 classes) and my calculations for how much effort is spent actually looking for a given factor take that into account. That particular factor is found in class 3651, so should be found about 79% through the factoring process from 73-74.

That said, the 8.44 number does look suspiciously low, I will take deeper look at it in the morning and check if the calculations are correct or not.

[LaurV]

Numbers look right for me. That's a tinny factor for a large exponent.

[Ensigm]

Originally Posted by James Heinrich

One thing that may be not immediately obvious is that TF is not done linearly from bitA to bitB, the work is divided into classes (by default mfaktx uses 4620 classes) and my calculations for how much effort is spent actually looking for a given factor take that into account. That particular factor is found in class 3651, so should be found about 79% through the factoring process from 73-74.

Thanks for explaining it, I really didn't know that.