And a big reason on my side:

I'm checking [b]all[/b] resultfile from LLRnet/PRPnet for all drives and it's highly automated to save me time instead of checking things by hand.
One script takes the big sievefile and extracts the recommended candidates for a 1k or 10k range beginning with xxx001.
Doing the same only at the beginning of a new sieverange like 1M-2M will pop up errors like pair is not in that automaticly created sieverange, so i have to check why by hand.
That's what I want to avoid.

OK. I'll make a mental note to sieve only xxxx001 to xxxx000 on various drives in the future -IF- NPLB originally sieved the range immediately below it. Afaik, that should be the case on all drives at this point.

395, 397 and 399 at n=1.2M, continuing

Status report
 

k=337 tested till n=2.62M

There's about 3 days work left at port 3500 for me!

[quote=kar_bon;224515]There's about 3 days work left at port 3500 for me![/quote]

We went through that quicker than expected. n=1.1M-1.2M will be loaded within the next few hours.

To make it official: Reserving n=1.1M-1.2M for port 3500.

[QUOTE=gd_barnes;224657]We went through that quicker than expected. n=1.1M-1.2M will be loaded within the next few hours.
[/QUOTE]

In about 3 hours I'm sending back 356 tested pairs, so I can't reserve this amount again!
Currently 571 pairs untested minus the 356 -> Server is out of work!

[quote=kar_bon;224786]In about 3 hours I'm sending back 356 tested pairs, so I can't reserve this amount again!
Currently 571 pairs untested minus the 356 -> Server is out of work![/quote]

Done. Sorry about the delay.

[QUOTE=gd_barnes;224814]Done. Sorry about the delay.[/QUOTE]

Just want to submit and receive more!

Reserving k's 389, 391 and 393 to n=1.3M

395, 397 and 399 will be finished in a few days to n=1.3M

Status report
 

k=337 tested till n=2.67M