Hi there,

I usually use my app_info.xml file to select AVX512 workunits among some other well performing CPU extensions.

The only thing I did not manage to get to work so far is AMD GPU related work units.
If I add the GPU related stuff to the app_ifo file, no GPU workunits are downloaded anymore.

Here is my app_info file, does anyone spot mistakes in the last part, which is the GPU part?

<app_info>
    <app>
        <name>period_search</name>
        <user_friendly_name>Period Search Application</user_friendly_name>
    </app>
    <file_info>
        <name>period_search_10213_windows_x86_64__fma_win10.exe</name>
        <executable/>
    </file_info>
    <app_version>
        <app_name>period_search</app_name>
        <version_num>10213</version_num>
        <api_version>7.14.0</api_version>
        <plan_class>fma_win10</plan_class>
        <avg_ncpus>1.000000</avg_ncpus>
        <file_ref>
            <file_name>period_search_10213_windows_x86_64__fma_win10.exe</file_name>
            <main_program/>
        </file_ref>
    </app_version>



    <app>
        <name>period_search</name>
        <user_friendly_name>Period Search Application</user_friendly_name>
    </app>
    <file_info>
        <name>period_search_10215_windows_x86_64__avx512_win10.exe</name>
        <executable/>
    </file_info>
    <app_version>
        <app_name>period_search</app_name>
        <version_num>10213</version_num>
        <api_version>7.14.0</api_version>
        <plan_class>avx512_win10</plan_class>
        <avg_ncpus>1.000000</avg_ncpus>
        <file_ref>
            <file_name>period_search_10215_windows_x86_64__avx512_win10.exe</file_name>
            <main_program/>
        </file_ref>
    </app_version>
	



    <app>
        <name>period_search</name>
        <user_friendly_name>Period Search Application</user_friendly_name>
    </app>
    <file_info>
        <name>period_search_10214_windows_x86_64__sse2_win10.exe</name>
        <executable/>
    </file_info>
    <app_version>
        <app_name>period_search</app_name>
        <version_num>10214</version_num>
        <api_version>7.14.0</api_version>
        <plan_class>sse2_win10</plan_class>
        <avg_ncpus>1.000000</avg_ncpus>
        <file_ref>
            <file_name>period_search_10214_windows_x86_64__sse2_win10.exe</file_name>
            <main_program/>
        </file_ref>
    </app_version>



	<app>
		<name>period_search</name>
		<user_friendly_name>Asteroids</user_friendly_name>
	</app>

	<file_info>
		<name>period_search_10220_windows_x86_64__opencl_102_amd_win.exe</name>
		<executable/>	
	</file_info>
	
	<app_version>
		<app_name>period_search</app_name>
		<version_num>10220</version_num>
		<avg_ncpus>1.00</avg_ncpus>
		<max_ncpus>1.00</max_ncpus>
		<plan_class>opencl_102_amd_win</plan_class>
		<file_ref>
			<file_name>period_search_10220_windows_x86_64__opencl_102_amd_win.exe</file_name>
			<main_program/>
		</file_ref>
		<coproc>
		<type>AMD</type>
		<count>1</count>
		</coproc>
	</app_version>
	
	
	
	
	
	
	
	
	
	
	
	
</app_info>

I don't see anything wrong with your gpu app_version section. Rudimentary question. Is the app present in the asteroids directory? You normally have to run the stock client to download the app and tasks and get its download location installed into the client state file before converting everything over to an app_info installation.

Common issues is that upon launch of an app_info installation is the client will delete an application it does not have a record of in the client state file.

Best practice is to keep a copy of any executables outside of the Boinc project folders so you can replace them if they get deleted by the client somehow.

So check for the presence of the gpu app first. Second, what kind of messages are present in the Event Log at startup. Does the client detect the gpu by finding the drivers for AMD?

Should have an entry listing the gpu found and the OpenCL drivers loaded for it.

---

A proud member of the OFA (Old Farts Association)

I was able to locate the problem. It was the app_info file.

It was:

		<coproc>
		<type>AMD</type>
		<count>0.5</count>
		</coproc>

But "AMD" is not known, and "ATI" has to be used, otherwise the card is missing.

<coproc>
		<type>ATI</type>
		<count>1</count>
		</coproc>
	</app_version>

For someone who wants to run specific apps, here is the working app_info.xml file which works with AMD/ATI cards.

<app_info>
    <app>
        <name>period_search</name>
        <user_friendly_name>Period Search Application</user_friendly_name>
    </app>
    <file_info>
        <name>period_search_10213_windows_x86_64__fma_win10.exe</name>
        <executable/>
    </file_info>
    <app_version>
        <app_name>period_search</app_name>
        <version_num>10215</version_num>
        <api_version>7.14.0</api_version>
        <plan_class>fma_win10</plan_class>
        <avg_ncpus>1.000000</avg_ncpus>
        <file_ref>
            <file_name>period_search_10213_windows_x86_64__fma_win10.exe</file_name>
            <main_program/>
        </file_ref>
    </app_version>



    <app>
        <name>period_search</name>
        <user_friendly_name>Period Search Application</user_friendly_name>
    </app>
    <file_info>
        <name>period_search_10215_windows_x86_64__avx512_win10.exe</name>
        <executable/>
    </file_info>
    <app_version>
        <app_name>period_search</app_name>
        <version_num>10215</version_num>
        <api_version>7.14.0</api_version>
        <plan_class>avx512_win10</plan_class>
        <avg_ncpus>1.000000</avg_ncpus>
        <file_ref>
            <file_name>period_search_10215_windows_x86_64__avx512_win10.exe</file_name>
            <main_program/>
        </file_ref>
    </app_version>
	


    <app>
        <name>period_search</name>
        <user_friendly_name>Period Search Application</user_friendly_name>
    </app>
    <file_info>
        <name>period_search_10214_windows_x86_64__sse2_win10.exe</name>
        <executable/>
    </file_info>
    <app_version>
        <app_name>period_search</app_name>
        <version_num>10214</version_num>
        <api_version>7.14.0</api_version>
        <plan_class>sse2_win10</plan_class>
        <avg_ncpus>1.000000</avg_ncpus>
        <file_ref>
            <file_name>period_search_10214_windows_x86_64__sse2_win10.exe</file_name>
            <main_program/>
        </file_ref>
    </app_version>


	<app>
		<name>period_search</name>
		<user_friendly_name>Asteroids</user_friendly_name>
	</app>

	<file_info>
		<name>period_search_10220_windows_x86_64__opencl_102_amd_win.exe</name>
		<executable/>	
	</file_info>
	
	<app_version>
		<app_name>period_search</app_name>
		<version_num>10220</version_num>
		<avg_ncpus>1.00</avg_ncpus>
		<max_ncpus>1.00</max_ncpus>
		<plan_class>opencl_102_amd_win</plan_class>
		<file_ref>
			<file_name>period_search_10220_windows_x86_64__opencl_102_amd_win.exe</file_name>
			<main_program/>
		</file_ref>
		<coproc>
		<type>ATI</type>
		<count>0.5</count>
		</coproc>
	</app_version>
	

	
</app_info>

Good catch, I'm so used to seeing AMD as card definition that I forgot how ancient the client is with still labeling AMD cards as their predecessor ATI.

---

A proud member of the OFA (Old Farts Association)

btw, the new app automatically selects the optimal optimization level for your CPU at runtime. This eliminates the need for specific versions to take advantage of features like AVX512.