[QUOTE=guido72;393710]That sounds weird... Nothing to say about new rules, but what if a client is regularly communicating with the server telling it: "Hey Buddy, I'm just a bit late, not dead! Wait for me, OK?" ?
Nothin' can ovveride the rules? It does sound silly!
If it is like this, should be more efficient for the whole gimps project that Primenet told immediately the out of scheduling client: "that's it! Do something else, bud!"...[/QUOTE]

The idea is that clients unable to complete in time shouldn't get the assignments in the first place. This is problematic when clients slow down for some reason.

I'll have a look, THKS!

[QUOTE=petrw1;393708]Welcome back...
However since no one else seems to have it you could simply assign it again through normal (not Manual) channels.[/QUOTE]
In other words?

How it comes that M63667837 is listed in my personal extension list ([url]http://www.mersenne.org/manual_extension/[/url]) and in my cpus list ([url]http://www.mersenne.org/cpus/)?[/url] I mean: dear Primenet, if M63... is no longer assigned to me, why do you list it with my cpus list and moreover let me extend his expiring date?

[QUOTE=guido72;393716]In other words?[/QUOTE]

Add the line to worktodo.txt

test=63667837,74,1

Humbly: may be rational to think about an integration of the rules.
If (and only if!) I'm honestly and reliably (and you decide if I am) telling you what I'm doing and at what pace, the thresholds should be more flexible... 3.333% of deviation (that's my case: 6 days out of 180) should be manageable... What about implementing some "italian/latin" fuzzy logic? :)

[QUOTE=petrw1;393719]Add the line to worktodo.txt

test=63667837,74,1[/QUOTE]
Why? It is already in my wortodo.txt file....

[QUOTE=guido72;393720]Humbly: may be rational to think about an integration of the rules.
If (and only if!) I'm honestly and reliably (and you decide if I am) telling you what I'm doing and at what pace, the thresholds should be more flexible... 3.333% of deviation (that's my case: 6 days out of 180) should be manageable... What about implementing some "italian/latin" fuzzy logic? :)[/QUOTE]

That's exactly the same thing as arguing for a longer deadline. Which might make more sense, but that's not for me to decide.

[QUOTE=Mark Rose;393723]That's exactly the same thing as arguing for a longer deadline. Which might make more sense, but that's not for me to decide.[/QUOTE]
Hi Mark! thanks for quoting! Did anyone suggest something like this?
[QUOTE=guido72;393718]How it comes that M63667837 is listed in my personal extension list ([URL]http://www.mersenne.org/manual_extension/[/URL]) and in my cpus list ([URL="http://www.mersenne.org/cpus/%29?"]http://www.mersenne.org/cpus/)?[/URL] I mean: dear Primenet, if M63... is no longer assigned to me, why do you list it with my cpus list and moreover let me extend his expiring date?[/QUOTE]
any idea about this apparently self conflicting behavior of Primenet?

[QUOTE=guido72;393721]Why? It is already in my wortodo.txt file....[/QUOTE]

oh ok....then I believe the next time you communicate with the server it will assign it to you (Fingers Crossed)

[QUOTE=petrw1;393725]oh ok....then I believe the next time you communicate with the server it will assign it to you (Fingers Crossed)[/QUOTE]
The problem is not my specific case (after all we're speaking about 150 ghz/d...Even if when I joned the project in late 90s that meant a huge leap forward in top producers list!!) but the efiiciency of GIMPS...

"During February 2014, new [URL="http://www.mersenne.org/thresholds/"]assignment and recycling policies[/URL] were put in place to help GIMPS make steady progress on milestones by detecting assignments that [U][B]are proceeding extremely slowly or not at all."
[/B][/U]
It seems to me we're missing the target... Better: we're getting closer to it but not the "most close"...
What's better than giving some weight to the communications between clients and server? After this you may apply all the rules you prefer...

Anyway: finger crossed! ;-)