having some issues.
After fiddling with various app_info.xml's I finally got the program to download nbody wu's and ati gpu wu's. However now the gpu wu's are going to 100% after 2 secs and they are not reporting properly (obviously, as they are not being computed)

help?

here's a copy of my app_info

<app_info>
<app>
<name>milkyway</name>
<user_friendly_name>MilkyWay@Home</user_friendly_name>
</app>
<file_info>
<name>milkyway_0.23_windows_intelx86__ati13ati.exe</name>
<executable/>
</file_info>
<file_info>
<name>brook32a_ati.dll</name>
<executable/>
</file_info>
<app_version>
<app_name>milkyway</app_name>
<version_num>23</version_num>
<file_ref>
<file_name>milkyway_0.23_windows_intelx86__ati13ati.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>brook32a_ati.dll</file_name>
<open_name>brook32a_ati.dll</open_name>
<copy_file/>
</file_ref>
<platform>windows_intelx86</platform>
<plan_class>ati13ati</plan_class>
<avg_ncpus>0.050000</avg_ncpus>
<max_ncpus>1.00000</max_ncpus>
<coproc>
<type>ATI</type>
<count>1.000000</count>
</coproc>
</app_version>

<app>
<name>milkyway_nbody</name>
<user_friendly_name>MilkyWay@Home nbody Simulation</user_friendly_name>
</app>
<file_info>
<name>milkyway_nbody_0.03_windows_intelx86.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>milkyway_nbody</app_name>
<version_num>3</version_num>
<file_ref>
<file_name>milkyway_nbody_0.03_windows_intelx86.exe</file_name>
<main_program/>
</file_ref>
<platform>windows_intelx86</platform>
</app_version>
</app_info>

Is it possible you used the wrong brook dll file? There are several and i think it depends on your videodriver version which one to use.

*Also i think you should leave open name at brook32.dll

If that doesn't work you can try different brook dlls from here:
http://milkyway.cs.rpi.edu/milkyway/download/ but i think you have the right one because i also have catalyst 10.7

so how can I determine which is the right one?
I'm running catalyst 10.7

Hi all,

well, its up and running fine.

@ Benzini: I checked my MW-folder. I have only the brook64a_ati.dll available and it works with the setting from Arjan.

Regards,
Alexander

Just wanted to inform all:
since I started nbody, 24 wu's succesfully completed, 12 ended in errors and some are pending.


One more info: before I switched over to use an app_info, I had ~24 ati-wu's ready. Now I have only 3 or 4 of them ready and 5 nbody-wu's.

Alexander

Thanks for the info Arjan and Werkstatt

this is what my app_info.xml looks like atm...

<app_info>
<app>
<name>milkyway</name>
<user_friendly_name>MilkyWay@Home</user_friendly_name>
</app>
<file_info>
<name>milkyway_0.23_windows_intelx86__ati13ati.exe</name>
<executable/>
</file_info>
<file_info>
<name>brook32a_ati.dll</name>
<executable/>
</file_info>
<app_version>
<app_name>milkyway</app_name>
<version_num>23</version_num>
<file_ref>
<file_name>milkyway_0.23_windows_intelx86__ati13ati.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>brook32a_ati.dll</file_name>
<open_name>brook32.dll</open_name>
<copy_file/>
</file_ref>
<platform>windows_intelx86</platform>
<plan_class>ati13ati</plan_class>
<avg_ncpus>0.050000</avg_ncpus>
<max_ncpus>1.00000</max_ncpus>
<coproc>
<type>ATI</type>
<count>1.000000</count>
</coproc>
</app_version>

<app>
<name>milkyway_nbody</name>
<user_friendly_name>MilkyWay@Home nbody Simulation</user_friendly_name>
</app>
<file_info>
<name>milkyway_nbody_0.03_windows_intelx86.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>milkyway_nbody</app_name>
<version_num>3</version_num>
<file_ref>
<file_name>milkyway_nbody_0.03_windows_intelx86.exe</file_name>
<main_program/>
</file_ref>
<platform>windows_intelx86</platform>
</app_version>
</app_info>

Please, look at dis:
http://milkyway.cs.rpi.edu/milkyway/forum_thread.php?id=1887

Arjan, thanks for that App_Info. It works great for running both at the same time.

I've only wound up with one error so far and it seems that the WU is messed up (I'm the 2nd error). If anyone cares to look at the computer it's http://milkyway.cs.rpi.edu/milkyway/results.php?hostid=201146.

I have to admit I'm liking the short run times, but assume they'll have to unfortunately get longer to get any good data. :P


My only real complaint is that it keeps on downloading 4 nbody WU's and only 2 ATI WU's. (0.02 day buffer just to keep from having to wait on downloads). But this seems to be more of a factor of for some reason BOINC thinks the ATI WU's will take like 4.5 hours. And it just so happens that it does an upload / download right before the task finishes so it works out perfectly.

---

Hello everyone,

I ran a single task of this nbody simulations on an i7880@3.07GHz and it errored out: error task.

Thought it might help to let you know, as this app is still in the development stage?

Have deactivated the use of CPU though, as my team and me are crunching other things atm.

Cheers,
CH

I've just had three show Computation Error

Task ID : 182869744 Work Unit ID : 141027959

27/08/2010 14:47:11 Milkyway@home Aborting task de_nbody_test_10_8452_1282324624_3: exceeded elapsed time limit 869.170273


Task ID : 182923223 Work Unit ID : 140119009

27/08/2010 17:36:04 Milkyway@home Aborting task de_nbody_test_10_25535_1282162623_4: exceeded elapsed time limit 869.170273


Task ID : 182923341 Work Unit ID : 140221542

27/08/2010 17:51:21 Milkyway@home Aborting task de_nbody_test_10_16002_1282143148_2: exceeded elapsed time limit 869.170273