Hi,
I just installed mprime v20 for Linux on the P3 box I use (perhaps it's
relevant here that the filesystem mprime is on is NFS-mounted from a server
somewhere completely different); and it's gone completely mad.
When I installed it, I was about half-way through completing M10540451.
First, it stopped working on M10540451, and did 21059 iterations of
M10725553. *Then* it conducted a complete P1 factorisation of M10725553,
finding a factor.
Rather than going back to M10540451, it collected M5290331, performed a P-1
test on it, and ran 1638401 LL iterations, before stopping work on that and
starting a P-1 factorisation of M9728591.
This is the same process running constantly, so it's not a matter of
stopping and restarting it at peculiar times.
I'm left with qA540451, pA540451, q5290331, p5290331 and m9728591 as
checkpoint files; my worktodo.ini reads
DoubleCheck=5290331,63,1
Test=9728591,64,0
I can understand starting the P-1 factorisation before finishing the
double-check, but I don't see where M10540451 has gone, or why the computer
did 21059 LL iterations on 10725553 before doing the factorisation.
Tom
_________________________________________________________________________
Unsubscribe & list info -- http://www.scruz.net/~luke/signup.htm
Mersenne Prime FAQ -- http://www.exu.ilstu.edu/mersenne/faq-mers.txt
