Some of our users have said that they're having problems using the ATI application on an anonymous platform; when they have settings that specify no cpu, and no nvidia gpu work, and only ATI gpu work. If anyone is having this problem please post your app_info.xml so I can send it to the boinc_dev mailing list to get it debugged. thanks!

--Travis

---

This is pretty much the standard one, with the command line option included that I use and a change to the count if I want to run a Astropulse unit at SETI Beta.

<app_info>
 <app>
 <name>milkyway</name>
 </app>
 <file_info>
  <name>astronomy_0.20b_ATI_x64_ati.exe</name>
  <executable/>
 </file_info>
 <file_info>
  <name>brook64.dll</name>
  <executable/>
 </file_info>

 <app_version>
  <app_name>milkyway</app_name>
  <version_num>21</version_num>
    <plan_class>ati13ati</plan_class>
    <flops>1.0e11</flops>
    <avg_ncpus>0.05</avg_ncpus>
    <max_ncpus>1</max_ncpus>
    <coproc>
      <type>ATI</type>
      <count>0.90</count>
    </coproc>
    <cmdline>b-1</cmdline>
  <file_ref>
   <file_name>astronomy_0.20b_ATI_x64_ati.exe</file_name>
   <main_program/>
  </file_ref>
  <file_ref>
   <file_name>brook64.dll</file_name>
  </file_ref>
 </app_version>

</app_info>

---

I've tried several modifications on my own since the problem started - none of them helped.

I started out with:

<app_info>
 <app>
 <name>milkyway</name>
 <user_friendly_name>Milkyway@Home</user_friendly_name>
 </app>
 <file_info>
  <name>astronomy_0.20b_ATI_x64_ati.exe</name>
  <executable/>
 </file_info>
 <file_info>
  <name>brook64.dll</name>
  <executable/>
 </file_info>

 <app_version>
  <app_name>milkyway</app_name>
  <version_num>20</version_num>
    <flops>1.0e11</flops>
    <avg_ncpus>0.05</avg_ncpus>
    <max_ncpus>1</max_ncpus>
    <coproc>
      <type>ATI</type>
      <count>0.32</count>
    </coproc>
    <cmdline>w1.3</cmdline>
  <file_ref>
   <file_name>astronomy_0.20b_ATI_x64_ati.exe</file_name>
   <main_program/>
  </file_ref>
  <file_ref>
   <file_name>brook64.dll</file_name>
  </file_ref>
 </app_version>

</app_info>

In the first attempt I changed the version to 21. When that didn't help I manually added the planclass without success.
This is what I'm using now:

<app_info>
 <app>
 <name>milkyway</name>
 <user_friendly_name>Milkyway@Home</user_friendly_name>
 </app>
 <file_info>
  <name>astronomy_0.20b_ATI_x64_ati.exe</name>
  <executable/>
 </file_info>
 <file_info>
  <name>brook64.dll</name>
  <executable/>
 </file_info>

 <app_version>
  <app_name>milkyway</app_name>
  <version_num>21</version_num>
  <plan_class>ati13ati</plan_class>
    <flops>1.0e11</flops>
    <avg_ncpus>0.05</avg_ncpus>
    <max_ncpus>1</max_ncpus>
    <coproc>
      <type>ATI</type>
      <count>0.32</count>
    </coproc>
    <cmdline>w1.3</cmdline>
  <file_ref>
   <file_name>astronomy_0.20b_ATI_x64_ati.exe</file_name>
   <main_program/>
  </file_ref>
  <file_ref>
   <file_name>brook64.dll</file_name>
  </file_ref>
 </app_version>

</app_info>

Apart from some minor differences (filenames, cpu-proc-count, version number) there are identically to the ones I use for Collatz, where they strangely work.

---

Starfire

I am not having this problem.


I have the switches set to CPU=No, nVidia=No, and ATI=Yes, on WinXP Pro (32b), Catalyst 8.12, all machines are using the same app_info file...

<app_info>
<app>
<name>milkyway</name>
</app>
<file_info>
<name>astronomy_0.20b_ATI_SSE2_amd.exe</name>
<executable/>
</file_info>
<file_info>
<name>brook32.dll</name>
<executable/>
</file_info>

<app_version>
<app_name>milkyway</app_name>
<version_num>20</version_num>
<flops>1.0e11</flops>
<avg_ncpus>0.05</avg_ncpus>
<max_ncpus>1</max_ncpus>
<coproc>
<type>ATI</type>
<count>1</count>
</coproc>
<cmdline>w0.9</cmdline>
<file_ref>
<file_name>astronomy_0.20b_ATI_SSE2_amd.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>brook32.dll</file_name>
</file_ref>
</app_version>

</app_info>

I think the only change I made was setting the "w0.9", I have no problems getting/requesting work, every minute or two it asks and receives work.

My computers.

I hope this helps someone!!!

---

Calm Chaos Forum...Join Calm Chaos Now

I know now what's causing the problems. It's NOT anonymous platform!


The scheduler can't handle <count>0.5</count> in the coproc section

This one works:
<coproc>
<type>ATI</type>
<count>1</count>
</coproc>

This one will get you the "no work send" message!

<coproc>
<type>ATI</type>
<count>0.5</count>
</coproc>

The bug is somewhere in sched_send.cpp and is related to the changeset 19529

---

Join Support science! Joinc Team BOINC United now!

Yay, it's working - thank you very much.

That was one of the only differences between my Milkyway and Collatz setup (the only one I didn't change because I never suspected it). I've disabled the fractional GPU jobs on Milkyway (coproc_count=1) for the time being. Now everything is working like it used to be.
I guess we'll have to wait until it's fixed by the BOINC devs in the next server version.

---

Starfire

I guess we'll have to wait until it's fixed by the BOINC devs in the next server version.

Fix -> http://boinc.berkeley.edu/trac/changeset/20189

---

Join Support science! Joinc Team BOINC United now!

I have found that my RAC stays the same no matter how many I do at a time.

1 at a time is fine as that was what I was doing anyway, I was just leaving a little room in case I wanted to do some ATI AP work.

---

Excellent. Thanks very much for finding out what was causing it.

I couldn't work out why it was affecting me and some others but not everyone.
I don't run 2 tasks concurrently for the extra credit but mainly for the more even loading on the GPU. Stops the fan slowing down and speeding up too. I was only running one task concurrently until the shorter tasks were reintroduced. The shortest ones take about 13.7 seconds on my 5870 and I prefer the the GPU load not going up and down so often.

I updated with Dave Anderson's fix for this. Let me know if it works ;)

---