I am attempting to create an anonymous platform at Milkyway.and
am using the Boinc documentation here

https://boinc.berkeley.edu/wiki/Anonymous_platform

Looking a the example's first 8 lines is confusing:

<app_info>
<app>
    <name>setiathome_enhanced</name>
</app>
<file_info>
    <name>setiathome_6.6_windows_intelx86.exe</name>
    <executable/>
</file_info>

"setathome_enhanced" is not really "app name". When actually coding up the app_info file one
would use "setiathome_v8" if you wanted to acquire v8 data

"setiathome_6.6_windows_intelx86.exe" is the name of the executable that is to be used to process the data.
It may or may not have the same name as an existing program at SETI.

Is the above analysis correct?

Here is the problem at Milkyway:

My app_info.xml file is recognized as an anonymous platform by milkyway

Milkyway@Home	12/27/2019 11:01:18 PM	Found app_info.xml; using anonymous platform	

I created an app that I call "test". If I rename "test.exe" to have the same name as an existing Milkyway app
" milkyway_1.46_windows_x86_64__opencl_ati_101.exe" then when the boinc client starts there is the
message "milkyway_1.46_windows_x86_64__opencl_ati_101" has size X bytes but only Y bytes was expected
That executable is then deleted and Milkyway downloads the 1.46 version to replace my app.

If just put "test.exe" at <file_info> then there is no message about the wrong length,
but test.exe is deleted anyway and nothing is downloaded.

Does not look like they support anonymous platform or I am doing something wrong.
I have not yet figured out what goes where "setiathome_v8" is.
I tried "Milkway@home separation" and have been guessing but have not
hit the right name that they call their data yet.

[edit] the download can be stopped using cc_config "don't check size" but tjhere is not reason to delete the test.exe app

"setathome_enhanced" is not really "app name". When actually coding up the app_info file one
would use "setiathome_v8" if you wanted to acquire v8 data

It's an example, and at the time of writing that piece of documentation it was correct, the Seti app was called seti_enhanced

"setiathome_6.6_windows_intelx86.exe" is the name of the executable that is to be used to process the data.
It may or may not have the same name as an existing program at SETI.

Is the above analysis correct?

Yes.

Here is the problem at Milkyway:

My app_info.xml file is recognized as an anonymous platform by milkyway

Milkyway@Home	12/27/2019 11:01:18 PM	Found app_info.xml; using anonymous platform	

Does not look like they support anonymous platform or I am doing something wrong.

There's no such thing as the project not supporting anonymous platform, it's a BOINC thing. And BOINC does support it.

I have not yet figured out what goes where "setiathome_v8" is.

That's an app name for Seti@Home, not Milkyway. Why don't you do us a favor and post the contents of your app_info.xml file?

---

It is just Milkyway for the project name in the app_info.

The project name doesn't appear in app_info - it's inferred from which project folder you put the file in.

There are application names and file names. They all appear at least twice, because you define them first, and then specify haw to use them. You really have to get a feel for the rhythm of how those components fit together.

In general, every project will accept anonymous platform once you've pieced the jigsaw together. I've found two exceptions recently:
1) One of my projects has actively disabled anonymous platform: it posts an explicit message in the Event Log to say that it's done so.
2) Shortly before Christmas, it appeared that the most recent version of the server code has a bug which causes an internal server error when you try to fetch work with an otherwise working app_info.xml file. I doubt this affects MilkyWay, and it should be fixed soon after everyone gets back from their hols.

If you're still having problems getting to grips with it, I suggest you do as Ageless suggested - post your attempt so far, and we can proofread it.

Oince I put
<dont_check_file_sizes>1</dont_check_file_sizes>

into the cc_config.xml then there was no urgency for an anonymous platform and I deleted the app_info.xml

From memory I think I had the following

<app_info>
<app>
<name>milkyway</name>
</app>
<file_info>
<name>ati_milkyway_separation.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>milkyway</app_name>
<version_num>1.46</version_num>
<platform>windows_x86_64</platform>
<plan_class>opencl_ati_101</plan_class>
</app_version>
</app_info>

I put the above (or something like it) together after looking at
https://milkyway.cs.rpi.edu/milkyway/forum_thread.php?id=3987 and comparing it to the one that Tbar released for SETI.

starting with the first <app> above the first "101" and I changed nvidia to ati
the "factory" app I have been using is milkyway_1.46_windows_x86_64__opencl_ati_101
so I guessed and broke that down in to the 4 parts name, ver, platform, class

In order to try the above xml I will have to run down my WU count from 850 to zero, set resources to "0" and exclude all but 1 gpu and only process 1 work unit at a time else I might dump a lot of good workunits due to my misconfiguration of the anonymous platform. However, I got plenty of free time and can try getting it to work.

If you have existing stock work for the application you are trying to mimic, I find the easiest way is to look inside client_state.xml for the matching <app_version> segment, and copy the string values from that as you make up your new app_info.xml file. The syntax is not exactly the same, but once you get the general shape right, it falls into place.