Rootfinder instead of linesiever this time
 

On running the nfsnetclient it called/launched/spawned the rootfinder.
Normally it is the linesiever.

Why did it do that ?

Has the linesiever exhausted the search space with the previous root(s) ?

Has the 2^757 - 1 entered a new stage of processing ?

Is this normal ?

I have examined the text file documentation and it mentions the rootfinder running after registration, but doesn't mention it re-occuring.

Does it automatically expire/ redo roots at the start of the month ?

Some good guesses. I like the "first of the month" hypothesis. smile

Actually, you must be in the "Texas" pool (one of five). That pool has been working on subproject 2_757M_2 while everyone else was working on 2_757M_1. Last night, we finished 2_757M_2 and so those sievers have now switched to 2_757M_1.

For those interested, let me explain the difference.
Our objective in sieving is to find "enough" relations. We want to try to be efficient in doing so.
We sieve over a two dimensional space. However, the probability of finding a relation at a particular location is not uniform. It is more like 1/(a * b). For technical reasons, we sieve rectangular regions. Since it is more efficient to search near the axes, we search a wide rectangle for small values of "b" and a narrower one for the larger values of "b". These correspond to the two subprojects, 2_757M_2 (0<b<1M) and 2_757M_1 (1M<b<24M), in this case.

The relations from both subprojects are combined, but it is easier for us to administer things by treating them as if they were different factorizations. In either case, the sievers are designed to automatically get the data and process whatever assignment they are given.