On Sat, 15 Dec 2001, Alexander Kruppa wrote:
> So if that person who received the three assignments you mentioned does
> extra trial factoring work, that might explain why he gets other peoples
> exponents (and maybe doesn't even know it). Did the factoring depth of
> these three exponents change over the reassignment?
All three of the exponents are now factored one level deeper than they
were on my printout.
Here are the three exponents and how they looked on my printout from Dec
7th:
4624171 D* 61 124.8 36.5 60.5 07-Dec-01 11:02 05-Aug-01 05:14
tarnold cypraea2
4668337 D* 61 52.8 -31.8 28.3 16-Oct-01 06:11
messmer amd
4696429 D* 62 87.8 -52.7 7.3 08-Oct-01 07:27 11-Sep-01 06:25
kgymnas CBA6E3613
The first exponent has been completed. There were originally two
back-to-back exponents assigned to tarnold/cypraea2, only one of them
moved over to the new account (nuutti), so this is not a matter of someone
changing the team on the machine this exponent was assigned. The machine
that was working on this assignment has now "absorbed" another exponent
from the first page, which on Dec 7th belonged to the account litbos and
was one line higher than the tarnold assignment. This is the before (from
my Dec. 7th printout) and the after (a status report pulled up just a few
minutes ago):
4606513 D* 62 41.6 -17.6 42.4 27-Oct-01 09:35 litbos
litbos
4606513 D 63 48.8 -24.8 35.2 15-Dec-01 03:04 27-Oct-01 09:35 nuutti
hima
Note that the after has a *very* recent updated timestamp, but the
expiration time hasn't been changed to match. Three of the four exponents
had very negative "days to go" (were very overdue), and none had any work
reported in the "current iteration" column. It could be that the litbos
assignment was the original target, but this person read the wrong line
and entered the tarnold assignment instead. Those three are the only
exponents from my Dec. 7th assignment that have negative "days to go" and
no iterations reported. It all looks consistent with your "factoring
ending up taking over an LL assignment" glitch. Whether it is inadvertent
or deliberate is another question. Not the ideal way to move an exponent,
but it just might work. Unless of course, the bug is fixed in the
meantime. :)
_________________________________________________________________________
Unsubscribe & list info -- http://www.ndatech.com/mersenne/signup.htm
Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers