New AstroPulse for GPU ( ATi & NV) released (r1316)

New AstroPulse binaries are available here: http://lunatics.kwsn.net/12-gpu-crunching/ap6-for-nv-ati-gpus-r1316-released.msg49053.html#msg49053

Please, report noticed issues in this thread.

New AstroPulse binaries are available here: http://lunatics.kwsn.net/12-gpu-crunching/ap6-for-nv-ati-gpus-r1316-released.msg49053.html#msg49053

Please, report noticed issues in this thread.

On hosts with BOINC supporting OpenCL app will use device supplied by BOINC. With older BOINC versions own enumeration ability will be used.

I notice that the current offerings are all win-x86, are there plans for win-64 versions?
____________
Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

Here is an example for ATI cards.
Just use ap_cmdline.txt instead of comand line in appinfo.
So you can edit params without restarting Boinc.

Type has to be uppercase.

ATI or CUDA

<app>
<name>astropulse_v6</name>
</app>
<file_info>
<name>AP6_win_x86_SSE2_OpenCL_ATI_r1316.exe</name>
<executable/>
</file_info>
<file_info>
<name>ap_cmdline.txt</name>
</file_info>
<app_version>
<app_name>astropulse_v6</app_name>
<version_num>601</version_num>
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.2</max_ncpus>
<plan_class>ati13ati</plan_class>
<coproc>
<type>ATI</type>
<count>0.5</count>
</coproc>
<file_ref>
<file_name>AP6_win_x86_SSE2_OpenCL_ATI_r1316.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>ap_cmdline.txt</file_name>
</file_ref>
</app_version>

@ Fred E.

You dont need to do anything for 6.12 version.
Just check you appinfo with mine.

Mike
____________

I notice that the current offerings are all win-x86, are there plans for win-64 versions?

Question:
Is this new release still affected by the high cpu usage on newer drivers?

Second big change - there is ap_cmdline.txt file that can be used to add command line parameters to app.
Put params there as you would put them in corresponding tag in app_info.
App_info tag supported too so use a way that more convenient to you.

Which one will be used if they contradict?

(e.g.
* in app_info.xml
<cmdline>-unroll 3 -ffa_block 2048 -ffa_block_fetch 1024</cmdline>

* in ap_cmdline.txt
-unroll 6 -ffa_block 2048 -ffa_block_fetch 1024
)


Will this erase AP ATI 601 tasks on-board?:
<version_num>604</version_num>

I think I need second 'copy' section with:
<version_num>601</version_num>


P.S.
It will be good to supply APATI.aistub (two of them - for 32 and 64 bit) in the .7z

If cmdline.txt is not mentioned in appinfo it will be untouched on most hosts.

____________

[quote]New AstroPulse binaries are available here: Not sure what this means - what do I need to do for 6.12.34?

Regarding what to mention in app_info file: for stock users upgrading to this release it would be better to include libfftw3f-3.dll in app_info.
That's because stock version could mention it already. If you have this file in project dir then you need to mention it to save it from deletion. It's BOINC's paranoid "kill all I know" approach - quite useless cause nothing prevents to accumulate not known to BOINC trash in that folders.

In general, upgrading with big cache of tasks is not recommended cause chances to lost all accumulated work and work in progress quite big (the same "wipe all" approach in action). I would recommend to finish current GPU AP work, set to "no new task", do update then enable work fetch. In this case errors in app_info will cause minimal damage.

Question:
Is this new release still affected by the high cpu usage on newer drivers?

Yes, cause nothing was done in drivers still. They still use busy-wait loop.

Since there's been many driver updates since the last working version, I've been wondering if that driver bug is a bug or just the way the drivers work now?

Question:
Is this new release still affected by the high cpu usage on newer drivers?

Yes, cause nothing was done in drivers still. They still use busy-wait loop.

Since there's been many driver updates since the last working version, I've been wondering if that driver bug is a bug or just the way the drivers work now?

It is a bug.
It was the same with ATI drivers.

AMD fixed it.

Thanks, who will kick NV in the butt then? ;)

Question:
Is this new release still affected by the high cpu usage on newer drivers?

Yes, cause nothing was done in drivers still. They still use busy-wait loop.

Since there's been many driver updates since the last working version, I've been wondering if that driver bug is a bug or just the way the drivers work now?

It is a bug.
It was the same with ATI drivers.

AMD fixed it.

Thanks, who will kick NV in the butt then? ;)

I think it more depends on their strategy in particular.

Completed my first Task. It ran very fast - was on track for about an hour running with 2 MB 6.10 tasks at the same time, but exited early at the 35 minute mark with "Found 30 single pulses and 30 repeating pulses, exiting." Was only split tonight so it won't validate for a long time. CPU use was high - about 21% with driver 301.42 (I'm not currently reserving a CPU core for the GPU).

There are several warnings in the StdErr you might want to review. One seems to be about the BOINC version I'm using, and I'm not concerned after your earlier comments. The other has to do with inability to open a file:

"INFO: can't open binary kernel file: C:\BoincData/projects/setiathome.berkeley.edu\AstroPulse_Kernels_r1316.cl_GeForceGTX670.bin_V6, continue with recompile..." and another similar message labeled "Warning". Maybe because it's the first time? Or my non=standard data directory location?

Guess my app_info.xml section is okay. Anyone looking at that earlier in this thread needs to make the fix that Mike pointed out - CUDA needs to be upper case on the Type line.


____________
Another Fred
Support SETI@home when you search the Web or shop online with GoodSearch and GoodShop

Question:
Is this new release still affected by the high cpu usage on newer drivers?

Yes, cause nothing was done in drivers still. They still use busy-wait loop.

Since there's been many driver updates since the last working version, I've been wondering if that driver bug is a bug or just the way the drivers work now?

"INFO: can't open binary kernel file: C:\BoincData/projects/setiathome.berkeley.edu\AstroPulse_Kernels_r1316.cl_GeForceGTX670.bin_V6, continue with recompile..." and another similar message labeled "Warning". Maybe because it's the first time?