I recently ran a cleanup on the app_info.xml while implementing the latest MB optimized Versions for both CPU and GPU.

First of all, I found the Lunatics 0.41 installer that I had previously installed had all <platform> entries double, one for 32bit and one for 64bit.

- Running a 64bit machine, I removed all 32bit platform app_versions, cutting app_info.xml size nearly in half

But then I also ran across multiple instances of the same client <plan_class>, such as
...ati_opencl_sah
...opencl_ati_sah
...ati_opencl_100
...ati13ati
...opencl_ati5_sah
...opencl_ati5_cat132
...opencl_ati_cat132

I can only assume this will cause the client to operate in ways as to create a binary compatible result with a wingman running other/older hardware ?

Now the 1000$ question is :
Should I re-enter all those <plan_class> variations or stick only to one that should run fastest on my Tahiti GPU ? Which one would that be anyway ?

PS.
Since that app_info.xml is still rather hughe, I left only ati_opencl_sah and opencl_ati_sah in it - system is crunching along just nice.
(sorry to all wingmen for unintentionally abandoning workunits as their x86 platform got lost over my app_info.xml cleanup :p )

I must say, things have become much more complicated since the early days of optimized SETI clients. Seems best to empty the cache before modifying the app_info.xml, that rings some old memories from the past.

---

Plan class is not that critical.
I use ati_opencl_sah. Which I believe is no longer even used. Just as I still use cuda on my nvidia system instead of cuda23, cuda32, or any of the others.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

Plan class is not that critical.
I use ati_opencl_sah. Which I believe is no longer even used. Just as I still use cuda on my nvidia system instead of cuda23, cuda32, or any of the others.

The plan class name is not important. It exists for identification, not for control.

But if you use a non-standard mapping, you have to remember that you are on your own when it comes to upgrading. Users who don't follow the established patterns are liable to trash their entire cache if they update with a standards-compliant app_info.xml - such as that generated by the Lunatics installer.