[QUOTE=Madpoo;521052]So far we've been doing pretty good with the new assignment rules. My memory may be faulty on this, but for the last few milestones, I think we've avoided having any "stalled" assignments holding things up. Those were generally being expired well ahead of when we actually got down to the last few in the queue. If I remember right.

In other words, it wouldn't have changed when we reached a particular milestone if we tried to be more aggressive on expiring those assignments that were obviously not running... the system took care of them as designed.

It was more common under the old rules to have some milestone waiting on a handful or more of assignments that were clearly not being worked on.[/QUOTE]I like your optimism. End of 2018 for example there were some stagnant assignments slow to expire that were holding up the show, and there was a bit of poaching involved in reaching a milestone before the new year. More recently an email reminder got 10 stalled exponents resumed. Usually there's no contact email available, at least to us peons, to send a reminder to.

[QUOTE=kriesel;521056]I like your optimism. End of 2018 for example there were some stagnant assignments slow to expire that were holding up the show, and there was a bit of poaching involved in reaching a milestone before the new year. More recently an email reminder got 10 stalled exponents resumed. Usually there's no contact email available, at least to us peons, to send a reminder to.[/QUOTE]

I'm either optimistic, or forgetful. Either way, it's nice and cozy here in my head. :smile:

two first primality tests left to 85M milestone
 

[URL]https://www.mersenne.org/assignments/?exp_lo=84944207&exp_hi=85000000&execm=1&exp1=1&extf=1&exdchk=1[/URL]
Next milestone at ~ August 6.

[QUOTE=kriesel;522842][URL]https://www.mersenne.org/assignments/?exp_lo=84944207&exp_hi=85000000&execm=1&exp1=1&extf=1&exdchk=1[/URL]
Next milestone at ~ August 6.[/QUOTE]

Well that's weird lol I thought it was only a double check. Ooops :grin:

Edit: Just checked it says 3 days 20 hours.

[QUOTE=dcheuk;522845]Well that's weird lol I thought it was only a double check. Ooops :grin:

Edit: Just checked it says 3 days 20 hours.[/QUOTE]Could it have gotten promoted somehow because the first was flagged as suspect?

[QUOTE=kriesel;522856]Could it have gotten promoted somehow because the first was flagged as suspect?[/QUOTE]

Yep it sure look like it.

85M milestone
 

M84944207 finished - the first result was suspect (it had one non-repeatable roundoff error) so it was being treated as a first time check. It matched though, so the "first time" test wound up being a successful double-check after all.

I marked the date of the 85M milestone as being the day that verification came in, although it does present an interesting question. Since it matched, the first test was in fact correct. Does that mean the milestone completion date shouldn't take that exponent into account, and we'd use the previous one to mark the date? Which I think was M84980339 on August 2nd. :smile:

My gut instinct says "just use the date when we got the verification for that last one", but the more I thought about it, the more I wonder if that's right. LOL Because technically that exponent was successfully tested the first time, on July 31, we just didn't have confidence in it. In general, suspect results are wrong about half the time.

Since for Mersenne Primes we use the date any human learns the result from the database the same thing could apply here. We cannot say a milestone is completed until we know it is completed, which was when the verification came in that the suspect result was correct.

[QUOTE=ATH;523152]Since for Mersenne Primes we use the date any human learns the result from the database the same thing could apply here. We cannot say a milestone is completed until we know it is completed, which was when the verification came in that the suspect result was correct.[/QUOTE] Either way, it looks fine to me. Perhaps we should put an asterisk on the date.
Something like 08-05-19 [B]*[/B]

[B]*[/B]The previous exponent was completed on 08-02-19 see [URL="https://mersenneforum.org/showpost.php?p=523149&postcount=3153"]here[/URL]

Next up
 

Only 131 to go to 48M DC milestone (current latest estimated completion 2019-08-30, will likely change with assignment expirations and reissue);
478 to go to 86M first-test milestone (current latest estimated completion 2019-09-16, will likely change)

[QUOTE=kriesel;523164]Only 131 to go to 48M DC milestone (current latest estimated completion 2019-08-30, will likely change with assignment expirations and reissue);
478 to go to 86M first-test milestone (current latest estimated completion 2019-09-16, will likely change)[/QUOTE]

We've really been going through the first-time milestones at a pretty good rate, I think. As usual, double-checks are still not quite keeping the same pace (they're just not as "sexy" for people to devote CPU time to), but they're also getting done at a decent rate.