Missed Factors (TF)

[Dobri]

Due to the issue described in post #10 at https://mersenneforum.org/showpost.p...5&postcount=10 and some subsequent measures taken at the GIMPS server,
now when LordJulius partially repeats some of his own TF tests (without skipping the composite factor generated by mfaktc), a double TF miss occurs.
For example see the TF: 67-68 tests of M15941603.

[LordJulius]

Originally Posted by Dobri

Due to the issue described in post #10 at https://mersenneforum.org/showpost.p...5&postcount=10 and some subsequent measures taken at the GIMPS server,
now when LordJulius partially repeats some of his own TF tests (without skipping the composite factor generated by mfaktc), a double TF miss occurs.
For example see the TF: 67-68 tests of M15941603.

But if you look at that exponent on mersenne.ca, you see that the 67-68 factor was caught, but that a 'glitch' on the server side resulted in unnecessary second result lines.
This 'glitch' was previously pointed out concerning the Factors Missed by TF page (https://www.mersenne.ca/tfmissed.php?u=173981), where the reults are all separated by 0-1 second.

[Dobri]

The matter is now resolved for new submissions of TF tests with the inclusion of the notification "Redundant composite factor".
For example, see M16897861 for which one more composite factor (TF:1:64) was generated by mfaktc but it was skipped manually and does not appear in the PrimeNet exponent status at the GIMPS server.

M16897861 has a factor: 2096988918560585239 [TF:1:64:mfaktc 0.21 75bit_mul32_gs]

[chalsall]

Originally Posted by kriesel

Hardware fails.

Geeks often don't get out often... No one notices our work until something /doesn't/ work (which we work hard not to have ever happened).

It's not easy being us. But most of those who do the job actually enjoy it.

It can be fun never being seen. But always there when needed.

I am not alone in that solution space.