Newer milestone thread

[Dubslow]

Originally Posted by cheesehead

Poaching is knowingly or carelessly starting or resuming work on an exponent that's assigned to someone else but not to you.

And there is where we must agree to disagree.

Originally Posted by cheesehead

Paying for an item at a store is a hassle. It's much more minimal to just walk out of a store after pocketing some item than it is to go through all the hassle of standing in line at a cashier and actually paying for the item.

Ah, but the difference is that the store doesn't advertise that you can walk out without paying. GIMPS primarily advertises itself on "fire and forget" -- not how stores advertise. Stores expect you to pay, but GIMPS does not expect you to be an active participant. Having an assignment unreserved when it was perfectly within the advertised bounds/rules of GIMPS means that a typical user will continue the work so as to not have wasted any CPU time.

Personally, if a DC was unreserved in such a fashion, I would do my best to contact George, post here, and contact the new assignee, etc. However, since my only personal experience was an LL, the work would have needed to be done anyways, so I have no particular qualms about finishing the work. I see your point about the thrill, but if this sort of thing happens more than a few times, then we've got bigger problems on our hands. (No one, not even your former wife, will die if one exponent already had a test. As you said, "No one will go broke. The insurance company will reimburse the store.")

(Note that accidental unreservations aside, I agree with you on the poaching topic.)

[Dubslow]

Originally Posted by ATH

Here is George view on when assignments are too old, from the previous milestone thread: http://www.mersenneforum.org/showpos...&postcount=443

So if assignment is more than 365 days old and progress<50% or if assignment is more than 548 days old.

Apparently these recycling rules are still not implemented or not working properly, or your example M24077267 would have been reassigned 312 days ago.

I think the conclusion from this and the whole thread in general is that PrimeNet is in need of some serious upgrades, both with a more robust trust system and a more robust recycling system.

[Dubslow]

http://www.mersenne.org/report_milestones/

Less than 1000 tests to the next DC milestone.

[davieddy]

Originally Posted by Dubslow

http://www.mersenne.org/report_milestones/

Less than 1000 tests to the next DC milestone.

Made my day.

The less us slow working class pheasant pluckers have to do, the better.

David

[garo]

I have about 50 of those and 5 cores on the job.

[petrw1]

Originally Posted by garo

I have about 50 of those and 5 cores on the job.

85 here and about a dozen cores. Will be done in 2 months.

[petrw1]

Originally Posted by garo

I have about 50 of those and 5 cores on the job.

I see more than double that?

http://mersenne.org/assignments/?exp...et+Assignments

[garo]

Yeah I am catching some small ones and running TF on them before releasing them back. Found four factors in the last couple of days.

M25355903 has a factor: 367974475315822860271
M25366421 has a factor: 442195223317661712271
M25567897 has a factor: 159095036720797333279
M25462741 has a factor: 534418120347514884329

[Dubslow]

I'm willing to take some of them to DC, speed up the milestone.

[petrw1]

Originally Posted by Dubslow

I'm willing to take some of them to DC, speed up the milestone.

Ditto here....I've got some DC-milestone hungry cores here too.

Mind you, I still have 76 to go....6 weeks worth.

[Dubslow]

Originally Posted by petrw1

Ditto here....I've got some DC-milestone hungry cores here too.

Mind you, I still have 76 to go....6 weeks worth.

You could queue up three months' worth and somehow I doubt you'd be holding up the milestone