Hello.
https://boinc.berkeley.edu/projects.php shows that LHC@ home uses AMD GPU.
I can not any sub-project there that uses GPUs.
Anyone know if there really is one?
Their FAQ says no GPU of any type. (last updated in 2015)
If this is true. Can the BOINC project page be updated to remove the GPU symbol?
Thanks,
Jay

Unfortunately, the project page is generated automatically from the plan class names of the project's applications.

LHC have a couple of applications they have named native_mt and native_theory.

The word native contains the letters ATI, and that's what triggers the false positive GPU report.

The same thing happens in the 'Attach to project' wizard in BOINC Manager, because that's driven from the same automatic list.

The word native contains the letters ATI, and that's what triggers the false positive GPU report.

Assuming that most search patterns are letters only, would it be reasonable to require matches to be surrounded by non-letter characters?

It's a very simple search routine. I dare say there are other cases where projects are using what they consider to be "innocent" application names that trip the "ooo, there's a ?????? application" by the BOINC processor type routine. Most of the time it is just a simple annoyance, but there are times when it gets a bit beyond that. Just be thankful the project "knows the truth" and doesn't send work out for a non-existent application.

Thank you all for your time and effort in answering.
That clears things up.

Perhaps an exception script could be developed that looks for words like 'native' that have triggered a response.
Maybe? Or something like Floyd's idea?

Thanks again,
Jay

I think all the ATI detections are made automatically, including the project preferences. In which case, it's probably best that they're consistent, driven off the same data via the same rules.

I did go into this in some detail when I was writing #2643, in an attempt to synchronise the web page here with the 'attach to project' wizard displayed in the client - they were badly out of sync. It's better now, but I've discovered that the automatic updating process has broken down: Universe@Home has added an Android application which doesn't show in BOINC Manager, for example.

I agree the outcome has become bad programming, but in defence of the BOINC programmers, they're working at the cutting edge of computer science development. When BOINC coding started, we worked on CPUs only, on the main desktop operating systems and a few legacy OSs. Since then, we've added CUDA, ATI, OpenCL, intel_gpu, Android and probably more, and the original OSs have undergone huge changes. In general, BOINC works surprisingly well, under the circumstances.

Going back to the specific ATI question: the decision on what devices to support is taken individually by each separate project. The rules for supported devices are specified in Plan class names:

Plan class names encode information as follows:

• The name includes "opencl" if and only if the app requires OpenCL libraries.
  
• The name includes "cuda" if and only if the app requires CUDA libraries.
  
• The name includes "ati" if and only if the app requires CAL libraries.
  
• The name includes "ati" or "amd" if and only if the app uses an ATI/AMD GPU.
  
• The name includes "cuda" or "nvidia" if and only if the app uses an NVIDIA GPU
  
• The name includes "intel_gpu" if and only if the app uses an Intel GPU.
  
• The name includes "vbox" if and only if the app is a VM app and requires VirtualBox.
  
• The name includes "wsl" if and only if the app uses Windows Subsystem for Linux.
  

CERN's use of 'native' breaks the "and only if" component of those rules. I pointed this out to CERN while I was working on the wizard, but it's up to them to fix it.

If you can think of a better rule which would correctly discriminate all of these, please let me know and I'll forward it.

ati_opencl
ati14
ati14_app13
BRP4G-Beta-opencl-ati
BRP4G-Beta-opencl-ati-Lion
BRP4G-opencl-ati
BRP4G-opencl-ati-lion
FGRPopencl1K-ati
FGRPopencl-ati
FGRPopencl-ati-mav
GW-opencl-ati
native_mt
native_theory
opencl_ati
opencl_ati_100
opencl_ati_101
opencl_ati_AP27
opencl_ati_cat132
opencl_ati_gpu
opencl_ati_mac
opencl_ati_nocal
opencl_ati_sah
opencl_ati5_cat132
opencl_ati5_mac
opencl_ati5_nocal
opencl_ati5_sah
opencl_ati5_SoG
opencl_ati5_SoG_cat132
opencl_ati5_SoG_mac
opencl_ati5_SoG_nocal
opencl_atiapu_sah
openclatiGFN15
openclatiGFN16
openclatiGFN17LOW
openclatiGFN17MEGA
openclatiGFN18
openclatiGFN19
openclatiGFN20
openclatiGFN21
openclatiGFN22
openclatiGFNEXTREME
openclatiPPSsieve