Hello,

do we need a new app_config.xml for the new 1.20 application?

Thank you for your answer!

Cheers

Nowi

---

It depends. If you are currently running 'stock', no you shouldn't have to do anything other than make sure your project prefs allow it.

If you run on the anonymous platform, then yes you will have to modify your app_info to run it.

Thanks Alinator.

I know about the app_info, because I used them a long time. Here I must make an entry for every application I want to use.

By now I´m using the app_conf-feature off boinc to adjust the CPU-usage of the GPU-app. My question is: Must I do this also for every application or is it for all GPU-apps of the project?

---

You only need to do it once. As long as the app_config.xml file is in your project folder, it will work even when the app name changes. Be aware that if you reset the project or detach/reattach then you would need to insert the file again.

You only need to do it once. As long as the app_config.xml file is in your project folder, it will work even when the app name changes. Be aware that if you reset the project or detach/reattach then you would need to insert the file again.

Agreed. I only recently started taking BOINC v7 seriously, so I haven't fully explored all the possibilities app_config brings to the table. ;-)

Thanks, swiftmallard. Then I will get WU for the new app-version.

---

Now I got WU for the new app. My old app_config.xml didn´t work, because of the changed application name.

This one works:

<app_config>
<app>
<name>milkyway</name>
<max_concurrent>2</max_concurrent>
<gpu_versions>
<gpu_usage>1.0</gpu_usage>
<cpu_usage>0.05</cpu_usage>
</gpu_versions>
</app>
<app>
<name>milkyway_separation__modified_fit</name>
<max_concurrent>2</max_concurrent>
<gpu_versions>
<gpu_usage>1.0</gpu_usage>
<cpu_usage>0.05</cpu_usage>
</gpu_versions>
</app>
</app_config>

---

Now I got WU for the new app. My old app_config.xml didn´t work, because of the changed application name.

This one works:

<app_config>
<app>
<name>milkyway</name>
<max_concurrent>2</max_concurrent>
<gpu_versions>
<gpu_usage>1.0</gpu_usage>
<cpu_usage>0.05</cpu_usage>
</gpu_versions>
</app>
<app>
<name>milkyway_separation__modified_fit</name>
<max_concurrent>2</max_concurrent>
<gpu_versions>
<gpu_usage>1.0</gpu_usage>
<cpu_usage>0.05</cpu_usage>
</gpu_versions>
</app>
</app_config>

Awesome!! My dual GPU computers were only processing one GPU WU at a time since someone decided it was an amazing idea to change things. FAIL!

Sorry about the confusion. We are trying to get some new science out for you guys. We made the decision to put it in a new app for a couple of reasons. One of them being if there is a problem, you can turn it off without effecting other applications. Another is because its easier to organize and track on our end.


Thanks for sticking with us,

Jake W

LOL...

Don't worry about it. I'm totally used to trying to do the next to impossible with almost no funding and/or staffing. So I feel your pain there! ;-)

In any event, if it was easy, that would take all the sport out of it and everybody would be doing it. Right? :-D

That´s science on the leading edge. For me it is no problem to fine tune my crunching experience. :)

---

Now I got WU for the new app. My old app_config.xml didn´t work, because of the changed application name.

This one works:

<app_config>
<app>
<name>milkyway</name>
<max_concurrent>2</max_concurrent>
<gpu_versions>
<gpu_usage>1.0</gpu_usage>
<cpu_usage>0.05</cpu_usage>
</gpu_versions>
</app>
<app>
<name>milkyway_separation__modified_fit</name>
<max_concurrent>2</max_concurrent>
<gpu_versions>
<gpu_usage>1.0</gpu_usage>
<cpu_usage>0.05</cpu_usage>
</gpu_versions>
</app>
</app_config>

Yes it does, thank you!