This matter was resolved on or about 14 December at SETI Beta.

Issue(s) still persist at SETI Main.

Details here...http://setiathome.berkeley.edu/forum_thread.php?id=73525


Keifer

---

Important Note: It is on the opencl_nvidia_100 planclass where ATI work fetch doesn't work,

the ati_opencl_100 planclass for pre-Boinc 7 clients does get work, for example: All AstroPulse v6 tasks for computer 7042346

Claggy

Important Note: It is on the opencl_nvidia_100 planclass where ATI work fetch doesn't work,

the ati_opencl_100 planclass for pre-Boinc 7 clients does get work, for example: All AstroPulse v6 tasks for computer 7042346

Claggy

Just to claify, I am currently running Boinc 7.2.33(x64). I was running Boinc 7.0.64(x64) and CCC v 13.4 when I stopped receiving WU's. I have not received any stock AP v 6.06 WU's (be they ati_opencl_100 or opencl_ati_100) from SETI main since 26 November.

After 26 November (about the time I upgraded to Boinc 7.2.33) I began to receive AP v 6.08 (cal_ati) from SETI Beta. That issue was resolved on or about 14 December and I now correctly receive opencl_ati_100 from the beta site (although the server won't allow more than a 50 WU cache, but that is a minor issue for some other day).

By the way I have downgraded to CCC v 12.10 as I have noticed much less kernel usage and faster CPU times when compared to CCC 13.4/13.9.


Keifer

---

Greetings,

I have a dumb question.
Since 24Dec2013, I'm not getting opencl_ati_100 work and I'm not sure how to read the server status to see if what GPU WU are available..
Is this possible? Am I flogging a dead horse?

Previously, I have been able to get and process AstroPulse v6 v6.07 (opencl_ati_100) WU.
(Earlier (15Dec2013) was also able to get SETI@home v7 v7.04 (opencl_ati5_cat132).)

The last opencl_ati_100 was on Dec. 23rd.http://setiweb.ssl.berkeley.edu/beta/workunit.php?wuid=5910366
(I was the one with AstroPulse v6 v6.07 (opencl_ati_100) .)
So I guess that the easiest explanation is that the server ran out of that type of WU over the Holidays.

The server status shows

Program-----------------Host----Status
data-driven web pages---bruno---Running
upload/download server--bruno---Disabled
scheduler---------------bruno---Disabled
db_purge.el6.x86_64-----synergy-Disabled
beta_feeder.el6.x86_64--synergy-Not Running
          [...  programs either disabled or not running  ...]
vote_monitor------------bruno---Running
splitter_throttle-------bruno---Running

But, I can get 'CPU' work - SETI@home v7 v7.00 .
http://setiweb.ssl.berkeley.edu/beta/results.php?userid=19165

I suppose I really should wait and see if the work resumes in a few days.

Best wishes for all at SETI and SETI-Beta for a happy holiday with friends and family.
Jay

The last Astropulse WU split was WU 5928305, created Dec. 21 and sent Dec. 23 UTC time. That one was the end of the beam 5 polarity 1 channel, normally the beam 6 polarity 0 channel would have followed, but that didn't automatically happen this time. So the only AP tasks since then have been reissues sent because of an error or inconclusive validation.

(Earlier (15Dec2013) was also able to get SETI@home v7 v7.04 (opencl_ati5_cat132).

Neither of the hosts shown on your jay_e account show that work and the supply of Sah v7 work has been plentiful. Was that on a different account?

                                                                   Joe

Good Morning.

Josef, it is the same account. Probably I just didn't get that work while it is/was available.

http://setiweb.ssl.berkeley.edu/beta/forum_thread.php?id=2067 asks for another AP tape to be split. This might be related.

I just can't get A WU for my ATI gpu.

Here is my BOINC log from yesterday (showing CPU work and no ATI work fetched):

Wed 25 Dec 2013 11:34:59 PM EST | SETI@home Beta Test | Sending scheduler request: Requested by user.
Wed 25 Dec 2013 11:34:59 PM EST | SETI@home Beta Test | Requesting new tasks for ATI
Wed 25 Dec 2013 11:35:00 PM EST | SETI@home Beta Test | Scheduler request completed: got 0 new tasks
Wed 25 Dec 2013 11:35:10 PM EST | SETI@home Beta Test | Sending scheduler request: To fetch work.
Wed 25 Dec 2013 11:35:10 PM EST | SETI@home Beta Test | Requesting new tasks for CPU
Wed 25 Dec 2013 11:35:12 PM EST | SETI@home Beta Test | Scheduler request completed: got 18 new tasks
Wed 25 Dec 2013 11:35:14 PM EST | SETI@home Beta Test | Started download of 16au08aa.1136.23794.438086664197.16.40
...
and today (No CPU work needed.):
Thu 26 Dec 2013 09:00:34 AM EST | SETI@home Beta Test | update requested by user
Thu 26 Dec 2013 09:00:37 AM EST | SETI@home Beta Test | Sending scheduler request: Requested by user.
Thu 26 Dec 2013 09:00:37 AM EST | SETI@home Beta Test | Requesting new tasks for ATI
Thu 26 Dec 2013 09:00:39 AM EST | SETI@home Beta Test | Scheduler request completed: got 0 new tasks

Other projects, like LHC@home run out of work all of the time -that is their nature.
I suppose the same could happen for SETI, and especially SETI/Beta.

Which points back to the original question of reading the server status.
I 'assume' that CPU, CUDA, Intel_CL, opencl_ati_mac, opencl_nvidia_100, opencl_ati_100 WU are created and placed into 'ready-to-be-sent' queues on the server. I don't know all of the types - like opencl_ati5_cat132 - and how they are processed at the server. So, I expect that showing a server status for each type/queue may not be worth the effort.

Or, maybe I'm missing something on how to read the existing server status.
Is there a way to read GPU items on the server status?

Thanks,
Jay

There are only 2 types of actual work units. Multibeam and Astropulse.

Both of them can be sent to any device that asks for work and are then tagged for that device.

Greetings,
Thanks for the reply.
I'm still stumped.
The code for CPU and GPU is different and the log message (still) says:

Fri 27 Dec 2013 02:35:44 PM EST | SETI@home Beta Test | Sending scheduler request: Requested by user.
Fri 27 Dec 2013 02:35:44 PM EST | SETI@home Beta Test | Requesting new tasks for ATI
Fri 27 Dec 2013 02:35:45 PM EST | SETI@home Beta Test | Scheduler request completed: got 0 new tasks

And I can get CPU code - if I change my preference to allow CPU and GPU code.

Thanks,
Jay

As Joe as already replied, the Astropulse work as already been split and sent out, now you have to wait for a new tapes.

For Multibeam v7 there are two apps, with two planclasses for Windows and two for Linux, for drivers below Cat 13.1/APP runtime 1084.4, and for drivers above Cat 13.1/APP runtime 1084.4, since you're running Cat 13.1/APP runtime 1084.4 won't get any MB v7 ATI GPU work until you upgrade or downgrade your drivers.

Claggy

Hi there

Thanks for the reply.
I guess I asked the wrong question.
I now understand that there is no work for my configuration.

Wish list: A way for the server status to explain suitablity of a client's configuration to receive the 'ready to send' WU.

Sorry for the bother,
Jay