Siegmar Szlavik writes: >I have some bad news: I think I found a bug in Mlucas. >I also have some good news: it is not related to the test itself. :) > >I had 2 unfinished exponents with savefiles and everything. >I copied all the stuff to a directory and started Mlucas, which >continued the work on the first exponent in worktodo.ini. So far so >good, no problem. But: after finishing the first exponent it restarts >the computation of the second one, instead of continuing the previous >work :( all the work done so far was lost :( Is it possible, that you >only check the first exponent for old work? Hi, Siegmar: Thanks for the bug, er, I mean, "new feature!!", report. Indeed, Mlucas only checks for old savefiles upon program initiation- I hadn't considered the case of people concatenating worktodo files for several partially finished jobs. It just goes to show: for any program of even modest complexity, people will always find ways to use it that one didn't anticipate. For those of you using Mlucas who in future encounter this scenario, the short-term workaround is to move the savefiles for exponent #2 (or beyond) into the working directory, but don't actually add exponent #2 to the worktodo.ini file until #1 finishes. (I.e. let the current run complete and the program stop.) Alternatively, put the exponent #2 savefiles into a separate directory, create a new worktodo.ini file there, and start a second parallel run. (But that is preferable only if the two jobs don't conflict with each other too much, i.e. if the aggregate runtime needed for both LL tests run in parallel isn't significantly more than to do them sequentially would require.) I've added this to my TODO list for v2.7a - it will check for old savefiles whenever a new exponent is gotten from worktodo.ini. Sorry about the lost iterations, Siegmar. -Ernst _________________________________________________________________ Unsubscribe & list info -- http://www.scruz.net/~luke/signup.htm Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers
