Thanks to the efforts of the guys on the team the "BIG app_info" is now more complete. Just HCMD to do now I think.

I suspect that some may say that a few are not pretty but I have run the complete file (less nVidia + HCCC) as a test today.

http://www.xtremesystems.org/forums/showthrea...09-Working-app_info-files

Every CPU science you wanna run should be part of the app_info.xml.
The needed files of course should be in the project folder.
An example of an app_info for an AMD-card with allowed 3 tasks concurrently on the GPU & CEP2, HPF2 and FAAH on the free CPU-cores.

<app_info>
 <app>
  <name>hcc1</name>
  <user_friendly_name>Help Conquer Cancer</user_friendly_name>
 </app>
 <file_info>
  <name>wcg_hcc1_img_7.05_windows_intelx86__ati_hcc1</name>
  <executable/>
 </file_info>
 <file_info>
  <name>hcckernel.cl.7.05</name>
  <executable/>
 </file_info>
 <app_version>
  <app_name>hcc1</app_name>
  <version_num>705</version_num>
  <platform>windows_intelx86</platform>
  <plan_class>ati_hcc1</plan_class>
  <avg_ncpus>1.0</avg_ncpus>
  <max_ncpus>1.0</max_ncpus>
  <coproc>
   <type>ATI</type>
   <count>0.330000</count>
  </coproc>
  <file_ref>
   <file_name>wcg_hcc1_img_7.05_windows_intelx86__ati_hcc1</file_name>
   <main_program/>
  </file_ref>
  <file_ref>
   <file_name>hcckernel.cl.7.05</file_name>
   <open_name>hcckernel.cl</open_name>
  </file_ref>
 </app_version>
<app>
 <name>cep2</name>
 <user_friendly_name>The Clean Energy Project - Phase 2</user_friendly_name>
</app>
<file_info>
	<name>wcgrid_cep2_6.40_windows_intelx86</name>
	<executable/>
</file_info>
<file_info>
	<name>wcgrid_cep2_qchem_6.40_windows_intelx86</name>
	<executable/>
</file_info>
<file_info>
	<name>wcgrid_cep2_graphics_6.40_windows_intelx86</name>
	<executable/>
</file_info>
<file_info>
	<name>cep2_qcaux_6.40.zip</name>
</file_info>
<file_info>
    <name>cep2_images_6.40.zip</name>
</file_info>
<app_version>
    <app_name>cep2</app_name>
    <version_num>640</version_num>
    <platform>windows_intelx86</platform>
    <avg_ncpus>1.000000</avg_ncpus>
    <max_ncpus>1.000000</max_ncpus>
    <flops>1982909446.217418</flops>
    <api_version>6.11.7</api_version>
    <file_ref>
        <file_name>wcgrid_cep2_6.40_windows_intelx86</file_name>
        <main_program/>
    </file_ref>
    <file_ref>
        <file_name>wcgrid_cep2_qchem_6.40_windows_intelx86</file_name>
        <open_name>wcgrid_cep2_qchem_prod_linux.x86</open_name>
    </file_ref>
    <file_ref>
        <file_name>wcgrid_cep2_graphics_6.40_windows_intelx86</file_name>
        <open_name>graphics_app</open_name>
    </file_ref>
    <file_ref>
        <file_name>cep2_images_6.40.zip</file_name>
        <open_name>Cep2_images.zip</open_name>
    </file_ref>
    <file_ref>
        <file_name>cep2_qcaux_6.40.zip</file_name>
        <open_name>qcaux2.zip</open_name>
    </file_ref>
</app_version>
<app>
    <name>faah</name>
    <user_friendly_name>FightAIDS@Home</user_friendly_name>
</app>
<file_info>
    <name>wcg_faah_autodock_6.40_windows_intelx86</name>
    <executable/>
</file_info>
<file_info>
    <name>wcg_faah_autodock_graphics_6.40_windows_intelx86</name>
    <executable/>
</file_info>
<file_info>
    <name>faah_protease_6.40.dat</name>
</file_info>
<file_info>
    <name>faah_image_6.40.tga</name>
</file_info>
<app_version>
    <app_name>faah</app_name>
    <version_num>640</version_num>
    <platform>windows_intelx86</platform>
    <avg_ncpus>1.000000</avg_ncpus>
    <max_ncpus>1.000000</max_ncpus>
    <flops>3894434573.022523</flops>
    <api_version>6.3.3</api_version>
    <file_ref>
        <file_name>wcg_faah_autodock_6.40_windows_intelx86</file_name>
        <main_program/>
    </file_ref>
    <file_ref>
        <file_name>wcg_faah_autodock_graphics_6.40_windows_intelx86</file_name>
        <open_name>graphics_app</open_name>
    </file_ref>
    <file_ref>
        <file_name>faah_protease_6.40.dat</file_name>
        <open_name>protease.dat</open_name>
    </file_ref>
    <file_ref>
        <file_name>faah_image_6.40.tga</file_name>
        <open_name>wc_grid_s1b2.tga</open_name>
    </file_ref>
</app_version>
<app>
    <name>hpf2</name>
    <user_friendly_name>Human Proteome Folding - Phase 2</user_friendly_name>
</app>
<file_info>
    <name>wcg_hpf2_rosetta_6.40_windows_intelx86</name>
    <executable/>
</file_info>
<file_info>
    <name>wcg_hpf2_6.40.tga</name>
    <executable/>
</file_info>
<file_info>
    <name>wcg_hpf2_rosetta_graphics_6.40_windows_intelx86</name>
    <executable/>
</file_info>
<file_info>
    <name>hpf2_6.40_win_paths.txt</name>
    <executable/>
</file_info>
<app_version>
    <app_name>hpf2</app_name>
    <version_num>640</version_num>
    <platform>windows_intelx86</platform>
    <avg_ncpus>1.000000</avg_ncpus>
    <max_ncpus>1.000000</max_ncpus>
    <flops>3570131549.238372</flops>
    <api_version>6.3.3</api_version>
    <file_ref>
        <file_name>wcg_hpf2_rosetta_6.40_windows_intelx86</file_name>
        <main_program/>
    </file_ref>
    <file_ref>
        <file_name>wcg_hpf2_6.40.tga</file_name>
        <open_name>wc_grid_hpf2.tga</open_name>
    </file_ref>
    <file_ref>
        <file_name>wcg_hpf2_rosetta_graphics_6.40_windows_intelx86</file_name>
        <open_name>graphics_app</open_name>
    </file_ref>
    <file_ref>
        <file_name>hpf2_6.40_win_paths.txt</file_name>
        <open_name>paths.txt</open_name>
    </file_ref>
</app_version>
</app_info>

The VINA's ran on a Linux box without a GPU. ;)

"Anonymous platform" was added to BOINC so users could:
1: Run on platforms the project don't have any applications for.
2: Be so concerned by security they're only running applications they've compiled themselves.

While users instead mainly uses anonymous platform to run optimized applications supplied by 3rd. party, and later on to run multiple GPU-units at once, requirement #2 must still be fulfilled. For this reason, client tells all application-name(s) & accompanying version-number(s) it's got, and scheduling-server is only allowed to send work for these applicaton(s)/version(s).

This means anyone using app_info.xml to run multiple GPU-tasks at once won't get any CPU-work for this BOINC-project except if they've also including info about CPU-applications in their app_info.xml. This also means every time a new application-version comes out anyone using app_info.xml must manually download the new application-files & update their app_info.xml

While the scheduling-server at the moment contains a bug so doesn't work correctly with both "anonymous" & "homogeneous app" and the scheduling-server incorrectly can assign tasks for applications not specified in app_info.xml, the client still knows it's running anonymous platform and therefore can't download the application-files neccessary to run the tasks. Scheduler-replies still containing this message: "[error] App version returned from anonymous platform project; ignoring" reveals the bug haven't been fixed yet, since scheduling-server should not send the version-number.

On POEM, you are relieved of some of that pain. You can specify whether to use either an Nvidia or AMD card, for example. If that could be extended to how many work units to be run at once (maybe not an easy task), and to run only GPU tasks for a given project, it would be perfect for WCG.

<Emphasis mine>

Now that would be bad news, for multi-WU loading on GPUs turned out to be the raison d'être of using an app_info.xml file.
;