Or at least I hope it will be released. I fully expect this release attempt to fail, or if it is released I expect it to fail to run for many of you.

Let me know how it goes.
____________

I think the scheduler it treating it as a normal ATI app with extreme requirements rather than a OpenCl apps, so I'm going to need to find the problem with the scheduler and build a new one.
____________

After much trying and at least two scheduler changes, and a recompile of the feeder, two people have gotten OpenCL/ATI Astropulse v6 work units.

Now if they come back OK.
____________

Odd. I had to turn on CPU, in order to get an ATI GPU app. This is with 7.0.25.

FWIW, it worked fine.

http://setiweb.ssl.berkeley.edu/beta/result.php?resultid=10777921
____________

I was noticing that. Even with my changes the scheduler will say "Not Looking for CPU apps" from time to time.

I may have to change some default parameters in the opencl ati planner.
____________

4/17/2012 11:09:36 PM | | OpenCL: ATI GPU 0: ATI RV770 (driver version CAL 1.4.1703, device version OpenCL 1.0 AMD-APP (898.1), 512MB, 480MB available)


As I am getting no work units shall I assume this requires a OpenCL 1.1 gpu? :-/

Or at least I hope it will be released. I fully expect this release attempt to fail, or if it is released I expect it to fail to run for many of you.

Let me know how it goes.

Odd. I had to turn on CPU, in order to get an ATI GPU app. This is with 7.0.25.

FWIW, it worked fine.

http://setiweb.ssl.berkeley.edu/beta/result.php?resultid=10777921

First task completed.

http://setiweb.ssl.berkeley.edu/beta/result.php?resultid=10778437

I'll run some more.


//TRuEQ
____________
TRuEQ & TuVaLu

Second task completed and validated.

http://setiweb.ssl.berkeley.edu/beta/result.php?resultid=10778428

I wonder why CPU is running at 0.975+1ATI GPU

This is what I use in the app_info.xml for CPU when doing ATI ap tasks.
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.2</max_ncpus>

//TRuEQ
____________
TRuEQ & TuVaLu

Odd. I had to turn on CPU, in order to get an ATI GPU app. This is with 7.0.25.

I did as I use too, detach project and then re-attach it.

... that problem lies deep in BOINC istelf and is not easy to fix.

Technically the problem is that what is presented to the user as an "opt-out" is actually implemented as an "opt-in", and thus only affects the applications known at the time when you change your preferences. Applications that are issued afterwards are basically ignored.

I think you opted out of FGRP1 before S6LV1 was issued. If so, changing your preferences on the website first to accept all apps (and save!), then disabling FGRP1 again should fix the problem.

I just switched GPU cards from my Nvidia 250 to ATI 4850 on my second computor.
I am not getting any ATI tasks for the 4850.
I am running BM 6.12.34 and using Catalyst driver 12.3

Hopefully it can run SETI Beta OpenCl ATI ap tasks soon.

So now it is running some openCl tasks on project Milkyway.
It will be ready to run a couple of ap tasks as soon. When app is ready iI'll try again.

//TRuEQ
____________
TRuEQ & TuVaLu

I am not getting any ATI tasks for the 4850.
I am running BM 6.12.34 and using Catalyst driver 12.3

This is what I use in the app_info.xml for CPU when doing ATI ap tasks.
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.2</max_ncpus>

Update: I detached, quit BOINC. Then updated my preferences to remove CPU. Then restarted BOINC and added this project. And I am getting work. So the trick worked, for whatever reason.

Also, the run time estimate is *way* off. BOINC thinks the task will take 8 days to run. (It was the same before the detach/reattach). Actual run times are either 45 minutes, or 3 seconds (two different types of tasks?). DCF will correct this over time, of course. Just FYI.

http://setiweb.ssl.berkeley.edu/beta/results.php?hostid=56750
____________

I am not getting any ATI tasks for the 4850.
I am running BM 6.12.34 and using Catalyst driver 12.3

You may need to update BOINC to v7.0.25/26, as you did on your other machine.

True OpenCL scheduling requires BOINC v7, and if Eric has followed Applications and versions carefully (it isn't completely clear from the release news), he might have set BOINC v7 as the minimum core client version for Astropulse v6.02

Update: I detached, quit BOINC. Then updated my preferences to remove CPU. Then restarted BOINC and added this project. And I am getting work. So the trick worked, for whatever reason.

Also, the run time estimate is *way* off. BOINC thinks the task will take 8 days to run. (It was the same before the detach/reattach). Actual run times are either 45 minutes, or 3 seconds (two different types of tasks?). DCF will correct this over time, of course. Just FYI.

http://setiweb.ssl.berkeley.edu/beta/results.php?hostid=56750

In ap_remove_radar.cpp: get_indices_to_randomize: num_ffts_forecast < 100. Blanking too much RFI?

I am not getting any ATI tasks for the 4850.
I am running BM 6.12.34 and using Catalyst driver 12.3

You may need to update BOINC to v7.0.25/26, as you did on your other machine.

True OpenCL scheduling requires BOINC v7, and if Eric has followed Applications and versions carefully (it isn't completely clear from the release news), he might have set BOINC v7 as the minimum core client version for Astropulse v6.02

I updated BM to 7.0.26 but no luck with "stock" ati app
So I dl Raistmers .r560 app and that one works so the ATI 4850 should be able to run ATI ap tasks.

//TRuEQ

DavidH,

Here's the log for one of your hosts... Unfortunately the reason is buried in "app_plan() returned false". Whoever wrote the OpenCL planner didn't put a whole lot of effort into diagnostic messages. I suppose I'll have to. My guess is the OpenCL version.

And what is: Couldn't open plan class spec file '../plan_class_spec.xml' ?
____________