Clarifying:
I never run HCC CPU, so I had no one running.
I had running 2 SIMAP's and 2 HCC GPU's.
Then new WCG HCC GPU tasks arrived and immediately 1 of the running HCC GPU-tasks changed to 'WtR' and a 3rd SIMAP started.
No reason to prioritize SIMAP, because it has the highest <rec> and no deadline panic.

No horse needed. Only a simple BOINC restart and again 2 HCC GPU-tasks were running concurrently.

This is because a bug was fixed in the BOINC client. World Community Grid has never supported the anonymous platform mechanism. However, because of two bugs, one in the client and one in the server, volunteers were able to fetch work using the anonymous platform at WCG.

The bug that is fixed in the BOINC client is that before 7.0.40, if you were using the app_info.xml file & your client supported an 'alt-platform', then the client would send 'anonymous' as the primary platform but also report an 'alt-platform' (which it should not have been sent).

The issue on the server side is as follows. When the server receives a request, it adds the primary platform and any alt-platforms that the project supports to an 'allowed platform' list. If the first platform on the allowed platform list is the anonymous platform, then the server code handles the request using the anonymous platform code path. If the list size is 0 then a message is reported back to the client that the platforms reported are not supported.

The server bug is that if the primary platform is the anonymous platform, then any alt-platforms should not be considered. Instead, the server code added the alt-platforms to the list anyway.

This is an issue for us because since we do not support the anonymous platform, that is discarded during processing and not added to the allowed platform list. However, the alt-platforms are added to the list. Since the list size is > 0, processing continues down the normal server side logic. It is this that caused the generation of the 'ignored app version' message. It also meant that if I user only specified hcc1 in their app_info.xml file, but they had opted into receiving work for more than hcc1, then they would be assigned work from those other projects and the client would immediately discard that work (and not report that fact to the server).

After discussing with BOINC, the decision was that volunteers should be able to have fine grain control over how many instances of a job are run on their GPU and that the anonymous platform mechanism is not the way that should be done. The decision was made to create the app_config.xml file so that volunteers could have control over this by making changes to the file which has been added in the 7.0.40 client. Volunteers at World Community Grid should be looking as this is stabilized as the way to run multiple copies of HCC1 GPU on your graphics card at one time.

Once the changes for the app_config.xml file are in a stable BOINC client release, we will disable the anonymous platform on the server side. We will provide warning in this forum before we do that and we will allow time for volunteers to upgrade to the stable client build before we disable the feature.

Saw a check-in note to reapply the config after each RPC. Fix could be in the just released test client 7.0.41.

David  10 Dec 2012
5235	    - client: re-apply app configuration after each scheduler RPC;
5236	        otherwise the changes get overwritten
5237	    client/
5238	        cs_scheduler.cpp

then a little later:

Rom    10 Dec 2012
5266	    - Tag for 7.0.41 release, all platforms
5267	      client_release_7.0.41
5268	
5269	    /
5270	        configure.ac
5271	        version.h

The official change note list will tell if it got included. Loaded the x86_64 version anyhow to see what else breaks/or does not. :D

Exactly!

edit: With the added "major" gain that we can now control how many of a science run concurrent. I've been playing as have a few others, and now have 1 exclusive core that seamlessly processes CEP2 24/7 on an octo. There's a learning curve to go with it... searching the sweat-spot how big to set the buffer, how much to allow being buffered of CEP2. FTM, 4 "in progress" on a 1 day cache, with max_concurrent 1 in app_config. Works a treat... no more step 1 through 7 or whatever to make the slightest chance in mix selection. Client restart is though still required FAIK.

Confirmed: Fixed in BOINC client version 7.0.41