Can you test 6.10.9 to see if it still does this?

Does Collatz even have Nvidia applications? I think they only have ATI apps.
But since their server is AWOL again, I can't check.

Although this may well be a scheduler problem. I think I have seen similar things at DrugDiscovery, where I would ask for CPU work and get as message that I didn't have an Nvidia GPU. That was with an older 6.10 though.

---

OK -- I will download and test on a system in the next day or so.

And yes, Collatz is a slut project <BIG GRIN>

It supports ATI processors (from the embedded 3100 on up).
It supports Nvidia processors (from the 8400GS on up).
It supports CPU only configurations.

I run Collatz on systems with embedded ATI (3200/3300) as well as Nvidia systems (8400GS, 9400GS, 9600GT, 9800GT, 250GS).

For the test you would like me to make, I'll update from 6.10.7 to 6.10.9 on one of the systems with an Nvidia video adapter.

Can you test 6.10.9 to see if it still does this?

Does Collatz even have Nvidia applications? I think they only have ATI apps.
But since their server is AWOL again, I can't check.

Although this may well be a scheduler problem. I think I have seen similar things at DrugDiscovery, where I would ask for CPU work and get as message that I didn't have an Nvidia GPU. That was with an older 6.10 though.

David Anderson has been busy over the weekend: changeset [trac]changeset:19194[/trac]

- client/scheduler/web: add per-project preferences for whether to accept CPU, NVIDIA and ATI jobs.
These prefs are shown only where relevant:
e.g., only for processor types for which the project has app versions,
and if it has versions for only one type, no pref is shown.

These prefs affect both client and scheduler.
The client won't ask for work for a device blocked by prefs,
and the scheduler won't send it.

This replaces earlier optional project-specific prefs for
"no CPU jobs" and "no GPU jobs".
(However, these prefs continue to be honored on the server side).

It's not in any downloadable version yet (unless someone is willing and able to make a private build), but it sounds good to me: I imagine the participants in this conversation will be queuing up to test it once there's an alpha build and a project with the necessary server code installed.

..and a project with the necessary server code installed.

We need that first. Not even Seti has the latest code.

[trac]changeset:19167[/trac] says: "- user web: remove "enforced by version X+" for X < 6.0"

Seti computing preferences say: "Suspend work if no mouse/keyboard activity in last
(Needed to enter low-power mode on some computers)
Enforced by version 5.10.14+

On multiprocessors, use at most
Enforced by version 5.10 and earlier

Use at most
(Can be used to reduce CPU heat)
Enforced by version 5.6+"

(Alpha project has the latest code, but it has no CUDA/CAL apps+work)

---

Agreed - this is going to be a chicken-and-egg alpha test. I'm still working my way through the double negatives, but I think the code as written will 'ping' legacy (CPU-only) BOINC servers for GPU work as before. If that checks out after more coffee, I think I may write DA to suggest no_cuda and no_ati default 'true' in the final (release) client. Can't do that yet, of course, or we'll get no work to test from current servers! But it will be easier to monitor and confirm that all the active GPU-enabled projects have updated, and change the defaults then, than to persuade dormant projects to update their server code. LHC and Orbit, anyone?

Talking of updated server code, the newest I've seen is AQUA: check out the new task listing.

Talking of updated server code, the newest I've seen is AQUA: check out the new task listing.

That's been around for a while already. We have it at H2 and DD as well. I can't find what changeset put that through, though. Something before 19109 at least.

---

Talking of updated server code, the newest I've seen is AQUA: check out the new task listing.

That's been around for a while already. We have it at H2 and DD as well. I can't find what changeset put that through, though. Something before 19109 at least.

Collatz Conjecture has that new format as well:

All tasks for computer 4178

Claggy

Interesting and encouraging stuff -- of course without an update to the project side by the project (they don't always deploy the latest stuff from BOINC either for various reasons), but those changes once they find their way into a released client and deployed updates at the project might well let users have the control they ask for AND avoid needless pings to the project servers.

David Anderson has been busy over the weekend: changeset [trac]changeset:19194[/trac]

- client/scheduler/web: add per-project preferences for whether to accept CPU, NVIDIA and ATI jobs.
These prefs are shown only where relevant:
e.g., only for processor types for which the project has app versions,
and if it has versions for only one type, no pref is shown.

These prefs affect both client and scheduler.
The client won't ask for work for a device blocked by prefs,
and the scheduler won't send it.

This replaces earlier optional project-specific prefs for
"no CPU jobs" and "no GPU jobs".
(However, these prefs continue to be honored on the server side).

It's not in any downloadable version yet (unless someone is willing and able to make a private build), but it sounds good to me: I imagine the participants in this conversation will be queuing up to test it once there's an alpha build and a project with the necessary server code installed.