Since the project does not offer the possibility to choose which type of n-Body application we want to run, I was thinking about how this can be done. The only way I found here in the forums was using app-info.xml (anonymous platform), which works great, however that means no automatic updates of the application.

Now I looked at the Project-level configuration and wondered if that could be used. Something like setting <avg_ncpus> for the single core application above whats actually there. Has anybody tried that? Other ideas?

---

While I'm waiting for the computer to finish all cached tasks, ist that something that is worth trying on a 4 core CPU?

<app_config>
<app>
<name>milkyway_nbody</name>
<max_concurrent>1</max_concurrent>
</app>
<app_version>
<app_name>milkyway_nbody</app_name>
<avg_ncpus>8.000000</avg_ncpus>
</app_version>
<app_version>
<app_name>milkyway_nbody</app_name>
<plan_class>mt</plan_class>
<avg_ncpus>4.000000</avg_ncpus>
<cmdline>--nthreads 4</cmdline>
</app_version>
</app_config>

What's the plan_class of the single thread application?
And do I need the <cmdline> tag at all if I want to use all cores?

---

Since the project does not offer the possibility to choose which type of n-Body application we want to run, I was thinking about how this can be done.

Thanks for looking into this. I think it is very strange that they would send both multi-core and single core. That makes it very difficult to run. I think it is a good project, but wonder about how they are doing it.

I think I will choose another project until they can figure out how they want to run this one.

I will post the result when I know if it works or not. After removing app_info.xml I first had to get some single core tasks before BOINC will accept anything about that in the app_config.xml. So now I have to complete them, than change the avg_ncpus value to 8, and than we will see what the server thinks about that. The BOINC client doesn't really care about it, it runs the tasks anyway, even if I don't allow it to use that many CPU cores in preferences.

---

OK, so this isn't working at all, the firts thing I got were two single core tasks. Apparenty the server thought it is a great idea to send tasks to my computer, which will use 4x more CPUs than BOINC is allowed to use...

Back to app_info.xml I guess...

There really schould be some <disable_app_version> tag in the app_config.xml file.

---