[QUOTE=chalsall;396199]Or stupid... Never give the full result!

I'll run the DC on this; will take about three days.[/QUOTE]

I've already logged my result in, remind me again what good does the full residue do anyone?

79299719 was chosen as it was the largest exponent that the software could test at that time.

[QUOTE=Prime95;396191]I'd say wait, there is no hurry. Look at it this way, 5 years from now will you care if the M45 milestone was completed in March 2015 or September 2015?[/QUOTE]

I guess I'm fine with waiting... I don't mean to but I know I'm just stirring the pot... I shouldn't do that. :smile:

[QUOTE=Prime95;396191]By my understanding of the expiration rules, that exponent should already have been recycled. Do you want to investigate why, or would you like me to investigate?[/QUOTE]

I poked around at a few of the expiration sprocs... looks like there's the one that runs and specifically takes care of non LL work which is pretty straightforward. The other one that puts exponents back into the "available" pool is the one I spent a little time today noodling at, but I haven't quite nailed down the different things involved.

I did notice that it won't expire an assignment if it matches all of the other requirements for expiration, but the exponent itself is still pretty high up there (40M higher than the latest critical range, like 51M for a first time LL test). I get the reason for that, since exponents that much higher up aren't really good candidates for reassignment anyway since they're not going to be handed out soon even if they were available.

My guess was that 58,998,341 was still making progress and being regularly checked in, so the section that applies to grandfathered work is allowing it to progress. That was the part I need to stare at longer, with the various date limits (@lim1 - @lim3) and exponent limits (@exp1) going on and then figure out just where the thresholds would be for a given day.

I suppose the exponent is just beyond where that latest critical limit is... is that meant to avoid expiring assignments that are being worked on but are still outside the current range of new assignments? After all, I think there are still a few available exponents smaller than that one, so it's just giving that computer a little extra chance to pick up the pace?

EDIT: Ah, yes... I just let that sproc run the section in question to see what values it came up with for @exp1... it's 58857158. So I guess anything higher than that wouldn't necessarily be expired since they're not in that 'critical' range as of this moment. If the exponent hadn't checked in for > 180 days or hadn't even started yet, it would be expired, but that particular one is still (slowly) doing things.

That's some inside baseball stuff there, but for everyone else, let it be known that even under the grandfathered rules, there are still some allowances made where expiration won't happen until those exponents are actually going to be reassigned to someone else in the short term. Otherwise that computer gets to hang on and hopefully get it done.

[QUOTE=Madpoo;396203]I don't mean to but I know I'm just stirring the pot... I shouldn't do that. :smile:[/QUOTE]

ALWAYS do that! That's how progress happens!

[QUOTE=Gordon;396202]I've already logged my result in, remind me again what good does the full residue do [/QUOTE]

It's a little complicated. No worries, this is being managed.

[QUOTE=Gordon;396202]I've already logged my result in, remind me again what good does the full residue do anyone?[/QUOTE]Yay, free credits. With the residue I don't have to bother with running the whole test, I'll just post a DC immediately.

[size=1][color=grey]Credits (i.e. arbitrary numbers stored in a database) are very important and must be sought after no matter who it hurts or what it costs.[/color][/size]

[QUOTE=retina;396206]Yay, free credits. With the residue I don't have to bother with running the whole test, I'll just post a DC immediately.

[size=1][color=grey]Credits (i.e. arbitrary numbers stored in a database) are very important and must be sought after no matter who it hurts or what it costs.[/color][/size][/QUOTE]

Ah...good job I have all the interim residue files that you can submit yours for comparison with :tu:

[QUOTE=chalsall;396199][QUOTE=Gordon;396195][Wed Aug 23 06:53:27 2006]
UID: nitro/m79299719, M79299719 is not prime. Res64: B2C51947EEBD3B__. Wc1: 30EAA708,54176722,[B]01000100[/B]
[/QUOTE]Or stupid... Never give the full result!

I'll run the DC on this; will take about three days.[/QUOTE]
Maybe it's a good thing, because at least the error code is clearly visible, which for some reason [URL="http://www.mersenne.org/report_ll/?exp_lo=79299719"]was not recorded[/URL] to the database.

[QUOTE=Batalov;396209]Maybe it's a good thing, because at least the error code is clearly visible, which for some reason [URL="http://www.mersenne.org/report_ll/?exp_lo=79299719"]was not recorded[/URL] to the database.[/QUOTE]

Hmm...not sure why it doesn't show up there, but in the database itself it does show that error code. Must be some parsing thing to look at later on.

[QUOTE=Batalov;396209]Maybe it's a good thing, because at least the error code is clearly visible, which for some reason [URL="http://www.mersenne.org/report_ll/?exp_lo=79299719"]was not recorded[/URL] to the database.[/QUOTE]Nor was the date of 2006.

[QUOTE=retina;396218]Nor was the date of 2006.[/QUOTE]

That's because it took me "a while" to check it in :redface:

"A while" - an undetermined period of time, to cover up a multitude of things, usually forgetting to get around to doing something...

Check them in. Just my twopence.