[QUOTE=kriesel;551044]
Running first-time PRP without -proof, or even worse, first-time LL, by CUDALucas, prime95/mprime, Mlucas, etc is haste creating waste, by requiring more future DC, that is quite avoidable. (PRP with proof is possible on Gpuowl now, not yet released for prime95/mprime, not yet developed for Mlucas.)
Needed DC is currently a very good use of cycles, while we wait for PRP proof capability to expand.[/QUOTE]

We need to make a serious effort to get curtisc to convert to PRP.

[QUOTE=Chuck;551046]We need to make a serious effort to get curtisc to convert to PRP.[/QUOTE]

1. George needs to email curtisc.
2. curtisc needs to get access to the Uni machines.

[QUOTE=kriesel;551023]Then, on to 53M in October. (Looks like Fan Ming did cleanup of expired DC for 51M.:thumbs-up:)[/QUOTE]You mean poached active assignments.
The last 51M exponent was progressing. And the 52 exponent was a few days off, but progressing. That got poached. Waiting 10 days for between milestones in no big issue. Even a month between them is nothing.

Now that the squatter is off the other exponents, the next million milestone should be achieved soon enough too.

[QUOTE=Chuck;551046]We need to make a serious effort to get curtisc to convert to PRP.[/QUOTE]Given the number of machines involved, he may want to wait until a PRP-proof-enabled version of prime95/mprime is released for general use. Update the herd once for version and preferred work, rather than two rounds.

[QUOTE=Uncwilly;551051]You mean poached active assignments.[/QUOTE]I wrote what I meant. See [url]https://mersenneforum.org/showpost.php?p=550809&postcount=3274[/url] Both the exponents listed there were seen to have been stalled since ~12 June then, and since.

[QUOTE=Uncwilly;551051]You mean poached active assignments.
The last 51M exponent was progressing. And the 52 exponent was a few days off, but progressing. That got poached. Waiting 10 days for between milestones in no big issue. Even a month between them is nothing.[/QUOTE]
[QUOTE=kriesel;551063]I wrote what I meant. See [url]https://mersenneforum.org/showpost.php?p=550809&postcount=3274[/url] Both the exponents listed there were seen to have been stalled since ~12 June then, and since.[/QUOTE]
[QUOTE=kriesel;550809]As of now, 1 left to 51M DC milestone (estimated 3 days), and 3 more to 52M DC, one of which is checking in regularly; two seem stalled.
docustompc has been contacted for [M]51931577[/M]
And someone who may or may not be William P Wilkey about the other. [M]51791717[/M][/QUOTE]
The last hold out for the 51M finished naturally.
One of the last 2 in the 51-52 range completed naturally.
There are no manual assignments allowed in the Cat 1 or Cat 0 range.
So Fan Ming, went outside of the PrimeNet assignment rules. If a user turns in 'manual assignment' work in a range where there are no manual assignments, they are poaching. When the assignments expired, they get sent out again. So some well meaning person that has been turning in Cat 1 and 0 assignments consistently got handed out an assignment that Fan Ming poached before the person put a single cycle to. If I recall correctly, that last assignment vaporizes once a matching DC is turned in (thus does not show up on the exponent report), I think that this happened to me once.
With the assignment rules and recycling of assignments, we should have had 52 achieved by the end of July. Again, waiting 10 or 12 days for a milestone is nothing.

Makes me wonder if poaching results could be held in a different table to be processed when an active assignment expires.

[QUOTE=Uncwilly;551097]If a user turns in 'manual assignment' work in a range where there are no manual assignments, they are poaching. [/QUOTE]

This may result in poaching but it is not the definition of poaching. You can also turn in manual results in Cat0/1 which had no current assignment, I do this all the time. All Cat 0/1 exponents are not assigned at once.

Poaching is turning in a result, manually or otherwise, while another person has an active assignment that has not expired.

You can poach without manual results, if you add a line to worktodo.txt you get N/A instead of assignment ID, and when Prime95/mprime finishes you will have poached the exponent.
(unless the current assignment expired before this and no new assignment was made).

AFAIK, the server records "Manual Assignment" for any result without an AID. The problem with doing these turning in of work between the moment it expires and when it gets assigned is that it is the wild west. People might be working behind the scenes on the same exponent. There is also cases like what happened to me recently. There was an exponent running close to expiration. I contacted the normally responsible user. The machine was not going to be able to do the work. They agreed to drop the exponent. As soon as they did, I did the self-assignment trick and got a valid AID from PrimeNet, all legit. My machine started to work on it. Some person came in after the exponent would have expired and turned in the DC (done on a GPU). So, I lost several days of time. Letting the system work saves cycles.

Not everyone who poaches cares to be the most useful to the project. I think some are not on the forum.

If we tried coordinate who would spearfish the tail-end DC's that might help. Or have a user or 5 that get all of the expired Cat 0 assigned to them the instant that they expire. The server could email them the their assignment and any known interim residues.

I try to grab assignments just when they expire so I get an AID like [URL="mersenne.org/assignments/?exp_lo=91550000&exp_hi=91620000&execm=1&exdchk=1&exp1=1&extf=1"]these[/URL], and then it is no longer poaching. If I turn in results without AID, I make sure there is no active assignments to someone else.

Exceptions recently was the endless "patgie" assignments for 6+/12+ months without progress and the unneeded TF assignments in the DC range. Both of which most of us agreed was "borderline ok" to poach.

[QUOTE=Mark Rose;551100]Makes me wonder if poaching results could be held in a different table to be processed when an active assignment expires.[/QUOTE]
It wouldn't be beneficial. Poacher's mind is twisted (don't ask me how I know! :razz:), if he doesn't see his result displayed, he will assume something went wrong (or just forget the history, and spot the same candidate again) and he will try again and again, wasting even more resources, when he would be better "contributing" to different "assignments". So, let them have at it, display the results, but don't credit it, and don't display the name (or say "poacher" with lower case, hihi). That should deter most of them.

On the other hand, the summary of the last posts, is that in Ken's world, the poaching is bad only when is done by me :razz: