![]() |
What is PM1-L?
|
[QUOTE=ckdo;223271]Pardon my ignorance, but how could an assignment possibly have an Estimated Completion prior to the last time it was Updated[/QUOTE]
I have no idea. PM1-L is P-1 factoring on large exponents. |
[QUOTE=ckdo;223271]Pardon my ignorance, but how could an assignment possibly have an Estimated Completion prior to the last time it was Updated, like [URL="http://mersenne.org/assignments/?exp_lo=34744883&exp_hi=38569603&execm=1&exdchk=1&exfirst=1&extf=1&B1=Get+Assignments"]these[/URL]? :confused:[/QUOTE]
Maybe this is because the user has their machine set up update only every so often but the exponent will be completed prior that next scheduled update. These two dates may not have to coincide- yet the result will be reported when it completes. In other words, the next update may be the date that the machine would normally report progress with the server regardless of whether an assignment was close to finishing or not. However, this is just speculation. |
[quote=Primeinator;223301]Maybe this is because the user has their machine set up update only every so often but the exponent will be completed prior that next scheduled update. These two dates may not have to coincide- yet the result will be reported when it completes. In other words, the next update may be the date that the machine would normally report progress with the server regardless of whether an assignment was close to finishing or not. However, this is just speculation.[/quote]
The case at hand is 6 exponents updated this month with completion dates in 2009... |
[QUOTE=ckdo;223309]The case at hand is 6 exponents updated this month with completion dates in 2009...[/QUOTE]
I would assume that that is because they have not been started. If there is no progress, no completion date can be established. Seems like an odd quirk. |
[quote=ckdo;223271]Pardon my ignorance, but how could an assignment possibly have an Estimated Completion prior to the last time it was Updated, like [URL="http://mersenne.org/assignments/?exp_lo=34744883&exp_hi=38569603&execm=1&exdchk=1&exfirst=1&extf=1&B1=Get+Assignments"]these[/URL]? :confused:[/quote]Perhaps it was reported without updating the completion dates. (There's a check box for that.)
|
Double checks for M41 seem to be occurring at a MUCH faster rate now.
|
[QUOTE=Primeinator;223531]Double checks for M41 seem to be occurring at a MUCH faster rate now.[/QUOTE]
If this is the case, hopefully it will be sufficient to dissuade poaching, narrow the band of work done and satisfy those who have a thing for quasi-arbitrary milestones. The only other issue that may still require some resolution is term limits. A quick look at the first 10 active assignments: 21041719 D 34.00% 639 -26 2010-07-06 2010-07-14 2010-06-16 2008-10-31 blackivory v4_computers 21065063 D 16.80% 500 22 2010-08-23 2010-08-01 2010-07-31 2009-03-19 gangho v4_computers 21076607 D 31.40% 643 281 2011-05-09 2010-07-29 2010-07-28 2008-10-27 ANONYMOUS v4_computers 21096547 D LL, 43.40% 502 16 2010-08-17 2010-07-23 2010-07-22 2009-03-17 ANONYMOUS *21128461 D 641 13 2010-08-14 2010-08-26 2010-07-29 2008-10-29 ANONYMOUS v4_computers 21131827 D LL, 80.60% 467 5 2010-08-06 2010-08-02 2010-08-01 2009-04-21 ANONYMOUS 21181877 D 85.80% 624 -6 2010-07-26 2010-08-10 2010-07-13 2008-11-15 blackivory v4_computers 21205913 D 94.50% 524 -14 2010-07-18 2010-08-14 2010-07-17 2009-02-23 ANONYMOUS v4_computers 21238873 D 27.90% 635 9 2010-08-10 2010-07-31 2010-07-28 2008-11-04 ANONYMOUS v4_computers 21253487 D 35.70% 631 -1 2010-07-31 2010-08-20 2010-07-23 2008-11-08 ANONYMOUS v4_computers 21260417 D 55.70% 460 -11 2010-07-21 2010-07-22 2010-06-24 2009-04-28 ANONYMOUS v4_computers I have no issue with slow and steady progress. I couldn't be bothered much by an assignment almost two years old as long as sufficient [subjective] regular progress was being done. However, there is one test (as well as about a half dozen within the first 1,000 assignments currently sorted from smallest to largest and almost or over a year old), 21128461, which has seemingly not started or server does not report work, as mentioned previously, due to the possibility of no network connection (although it's update reporting is current so I assume it has a network connection) or work submission restrained (I suppose forced through editing the prime.txt file or otherwise - I suppose for good reason?), hence requiring manual submission. If the latter is the case, perhaps there should be a renewal process through one's account required with approximate work_done% submitted, otherwise such assignments may remain in limbo for far too long before ultimately being reassigned. |
[QUOTE=Primeinator;223531]Double checks for M41 seem to be occurring at a MUCH faster rate now.[/QUOTE]
I haven't implemented my suggestions for unreserving 12-18 month old assignments. I've been watching how preferred assignments are handed out. I'm still seeing some go to v4_computers even though there is code in place to prevent this. |
[QUOTE=Prime95;223570]I haven't implemented my suggestions for unreserving 12-18 month old assignments. I've been watching how preferred assignments are handed out. I'm still seeing some go to v4_computers even though there is code in place to prevent this.[/QUOTE]
Even if you had implemented these changes, would it not be too soon to see the fruits? As for the server, that is a rather odd conundrum! |
Am I going spare?????
Double checks are running fine.
LLs are going backwards. David |
| All times are UTC. The time now is 11:30. |
Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2021, Jelsoft Enterprises Ltd.