Ok, I'll head back over to beta for the next 12 hours thou I think you've already see these machines. Who's going to join me??

Yep, I saw your results. What about mastering offline benches and promote to alpha from beta? ;)

SSP:

Data Distribution State        SETI@home #     Astropulse #    As of*
Results ready to send          331,529         0               0m
Current result creation rate   34.0774/sec     -0.3333/sec     5m

Interesting creation rate for AP WUs... ;-)

---

...Happens when a task is returned (and validates) after its deadline, but before the next version of the task is created.

---

Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

MB splitters output have improved, but still off the pace.
If not for all the VLARs going through we'd be out of ready-to-send work by now.

---

Grant
Darwin NT

NX-01 wrote:

(...) I think there's just a rescheduler for windows and even that seems to be hard to find.

The developer of this rescheduler tool took his tool offline, because of CreditNew.

AFAIK, also the SETI admins were 'not pleased' about this tool since CreditNew.

A rescheduler tool screw up the correct calculation of the Credits/results (your own - and your wingmen get the same wrong Credits granted).
The SETI server think e.g. it's calculated on CPU (as it is marked online), but after rescheduling it was calculated on GPU. The SETI server does not notice it and grant wrong (not accurate) Credits.

jason_gee wrote:

Yeah, there seems to be more in play than just the GPU, as when wider distribution was tried some reported extreme problems (with anger). Maybe the next generation of OpenCL and Cuda applications will handle these more to everyone's liking.

TBar wrote:

Yes, as in VLARS take more GPU resources, so, all those cards set to run more than 1 or 2 at a time would start choking...and then the complaints would roll in.

ATI cards receive VLARs at Beta, as do nVidias. Neither receive VLARs on Main.

For 2 or 3 years someone said to me that the ATI/AMD VGA cards (Windows) get .vlar WUs (@ SETI-Main)...

When that was changed?

---

AFAIK, also the SETI admins were 'not pleased' about this tool since CreditNew.

Link, please.

Well, Credit New is screwed anyway, no idea if it really matters if somebody screws it even more ;-) But as Hal said, it may not work for V7 anyway.

---

I myself wrote:

AFAIK, also the SETI admins were 'not pleased' about this tool since CreditNew.

Raistmer wrote:

Link, please.

I was in E-Mail contact with David, Eric, Matt and Jeff.
I asked why they don't write it on the homepage - that not to use a rescheduler tool.

Eric answered: I could make such a statement, but I doubt it would do much good. We have no way of verifying who is using the tool. (...)

So they will not make an officially statement about 'not to use a rescheduler tool'.

---

Well, Credit New is screwed anyway, no idea if it really matters if somebody screws it even more ;-) But as Hal said, it may not work for V7 anyway.

Well from Engineering standpoints it's merely got a number of instabilities. Hard to explain, but it can be a case of 'The straw that broke the camel's back.'

---

"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.

I myself wrote:

AFAIK, also the SETI admins were 'not pleased' about this tool since CreditNew.

Raistmer wrote:

Link, please.

I was in E-Mail contact with David, Eric, Matt and Jeff.
I asked why they don't write it on the homepage - that not to use a rescheduler tool.

Eric answered: I could make such a statement, but I doubt it would do much good. We have no way of verifying who is using the tool. (...)

So they will not make an officially statement about 'not to use a rescheduler tool'.

So that's better keep clear. All that buzz over re-sheduler comes from forums and forums only.

But as Hal said, it may not work for V7 anyway.

Well, again. It works. Personally veryfied. Period.

But as Hal said, it may not work for V7 anyway.

Well, again. It works. Personally veryfied. Period.

Ah, ok. Didn't see that, sorry Raistmer.

---

I myself wrote:

AFAIK, also the SETI admins were 'not pleased' about this tool since CreditNew.

Raistmer wrote:

Link, please.

I myself wrote:

I was in E-Mail contact with David, Eric, Matt and Jeff.
I asked why they don't write it on the homepage - that not to use a rescheduler tool.

Eric answered: I could make such a statement, but I doubt it would do much good. We have no way of verifying who is using the tool. (...)

So they will not make an officially statement about 'not to use a rescheduler tool'.

Raistmer wrote:

So that's better keep clear. All that buzz over re-sheduler comes from forums and forums only.

I don't understand you well...

So you (and maybe others also) will still use the rescheduler until the SETI admins post in the News: 'please don't use the rescheduler' ?

---

So you will still use the rescheduler until the SETI admins post in the News: 'please don't use the rescheduler' ?

I will use it while and when see to appropriate and beneficent for the project.
All objections regarding its usage come from quite few SETI forums members and all based on its possible influence on CreditNew credit awarding scheme that has quite a little connection with things that can be considered as positive for the SETI@home project. It was discussed many times already, I don't see any reason to start new round. Just don't deceive public with from where roots of buzz grow.

I myself wrote:

So you will still use the rescheduler until the SETI admins post in the News: 'please don't use the rescheduler' ?

Raistmer wrote:

I will use it while and when see to appropriate and beneficent for the project.
All objections regarding its usage come from quite few SETI forums members and all based on its possible influence on CreditNew credit awarding scheme that has quite a little connection with things that can be considered as positive for the SETI@home project. It was discussed many times already, I don't see any reason to start new round. Just don't deceive public with from where roots of buzz grow.

You use the rescheduler and you know it will screw up CreditNew.
Wrong granted Credits for the (your) results.

But, your wingmen can't do anything against it, they must accept it that they get wrong Credits, because you use a rescheduler tool.

You don't need to answer... - it's just an ascertainment. ;-)

---

So you will still use the rescheduler until the SETI admins post in the News: 'please don't use the rescheduler' ?

I will use it while and when see to appropriate and beneficent for the project.
All objections regarding its usage come from quite few SETI forums members and all based on its possible influence on CreditNew credit awarding scheme that has quite a little connection with things that can be considered as positive for the SETI@home project. It was discussed many times already, I don't see any reason to start new round. Just don't deceive public with from where roots of buzz grow.

I can see that. On a technical level, well you won't find the problems/weaknesses if you don't push the mechanism beyond its limits either. It's tough though IMO. Which is better ? to push a system to the point it collapses, or try to prop it up by good behaviour. Maybe it isn't black and white.

---

"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.

So you will still use the rescheduler until the SETI admins post in the News: 'please don't use the rescheduler' ?

I will use it while and when see to appropriate and beneficent for the project.
All objections regarding its usage come from quite few SETI forums members and all based on its possible influence on CreditNew credit awarding scheme that has quite a little connection with things that can be considered as positive for the SETI@home project. It was discussed many times already, I don't see any reason to start new round. Just don't deceive public with from where roots of buzz grow.

I can see that. On a technical level, well you won't find the problems/weaknesses if you don't push the mechanism beyond its limits either. It's tough though IMO. Which is better ? to push a system to the point it collapses, or try to prop it up by good behaviour. Maybe it isn't black and white.

Yep, exactly.

Credits? what credits?

You not only screw up credits, you also mess with a few server side held personal and global variables that are in turn used for runtime estimates.
Messed up credit is just a secondary effect.

These days a few people moving work across devices will not influence the bigger picture much - the impact is on your own APR and on credit (for you and your wingmate) of course.
The latter makes it an ethical decision ;)

I would discourage from rescheduling in general - you don't want to rock the boat more than you absolutely have to.

I live by the principle 'there are no rules, only guidelines'
That makes you responsible for your actions.
If you can stand before the angry mob and say 'yes I did it, I had my reasons' - well. But don't be amazed if you get lynched before you managed to explain your reasons.

---

A person who won't read has no advantage over one who can't read. (Mark Twain)

But don't be amazed if you get lynched before you managed to explain your reasons.

When I do that on occasion, I still tend to only get some stern tellings off. Hasn't reached lynchmob status yet, but still opportunities to get into the history of the seti@home witch trials.

---

"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.