I've just completed a WCG Beta Test - FAH2 task.

I got credited for World Community Grid: Beta Test.

However I also have entries for:
World Community Grid Beta - FightAIDS@Home - VINA
World Community Grid Beta - The Clean Energy Project - Phase 2

This seems inconsistent to me. Either all the beta tasks should be lumped together or all the apps are split out. I prefer lumping because that matches the project but one could similarly argue that many other apps should be lumped together (SETI for example)

Please can we have some consistency?

For here it makes sense to group the WCG beta's into one Beta Test app because you are very unlikely to get enough beta's to reach 100h if you split them into their individual sub-project and even sub-app groupings. I think it used to be done like that and didn't work - these are the WCG Beta's I have:

World Community Grid Beta Test 658.73 0.00
World Community Grid Beta - FightAIDS@Home 224.78 0.00
World Community Grid Beta - FightAIDS@Home - VINA 56.45 0.00
World Community Grid Beta - FightAIDS@Home - AutoDock 37.08 0.00
World Community Grid Beta - The Clean Energy Project - Phase 2 31.22 0.00
World Community Grid Beta - Say No to Schistosoma 1.63 0.00

As you can see, with the old way 4/5 sub-project apps (that I actually received any betas for) didn't reach 100h.
Also, WCG groups the Beta's into one badge, so it makes sense to reflect their approach here. Maybe this could be done for some of the other projects too, but each would need to be justified with some rational.

World Community Grid Beta Test 658.73 0.00
World Community Grid Beta - FightAIDS@Home 224.78 0.00
World Community Grid Beta - FightAIDS@Home - VINA 108.95 0.00
World Community Grid Beta - FightAIDS@Home - AutoDock 37.08 0.00
World Community Grid Beta - The Clean Energy Project - Phase 2 31.22 0.00
World Community Grid Beta - Say No to Schistosoma 1.63 0.00
World Community Grid Beta 1.03 1.03

Complain at WCG, not here. WUProp is just reporting the app name as it comes in. As soon as I saw the app name show up in my task list I knew someone was gonna complain about it here.

Why 'complain' anywhere? Reporting an issue isn't complaining! I've identified a limitation of the app/system here, explained why it's limited and I'm suggesting how it could be improved.

WCG uses different beta app names to differentiate between their numerous apps & different sub-projects, its multi project. Doing so facilitates the researchers and their servers. However, they have a single Beta badge - they pool all their Beta apps to make it. That should be done here IMO. Most people don't get any Beta tasks, those that do only get the odd task. I've probably missed most of their beta runs over the last few years. It's not likely that you will get 100h of beta tasks for a specific app test run; and some beta app names could differ despite being the same application (just a different version).

Complain at WCG, not here. WUProp is just reporting the app name as it comes in. As soon as I saw the app name show up in my task list I knew someone was gonna complain about it here.

When a Beta test is run at WCG, it seems to be random as to whether it gets assigned to "Beta Testing" here or under its own name. If you read the original post you'll see the inconsistency. Ergo WUProp isn't "just reporting the app name as it comes in".

This is a WUProp issue and not a WCG issue. This isn't the only time there have been inconsistencies especially if a project changes its name. Most of the time Sebastien takes action. This time it seems not.

The apps clearly show up as Beta, Beta Test, etc in Boinc Manager. This is the APP name that is different, not a project name change and the app is different. It's just like running Zika vs MCM or FAAH vs FAAH Phase 2.

Project badges are completely separate from WUProp. PrimeGrid has a single GFN badge but many applications for it. The same applies here.

Couldn't it just be scripted in that any app 'Beta' from WCG just gets dumped into the same field in the database?

I think it's actually more inconsistency in naming on their end than any one beta app is to a specific beta name. It seems anything Beta is just called Beta work rather than a specific Beta project. It's quite possible you could get beta for a project that previously had beta but the only difference is the inconsistent naming.

The only real load on the server would be a one-off merging of all existing records. After that, beta releases are infrequent and rather limited. Short of all the WUs bombing out the load should be negligible (and that's no different than other new app/work, WCG or otherwise, bombing out.

Besides, a rose by any other name is still a rose...

Just my two-pence of thoughts. ~Y

I tried to google a bit and found many medical-related terms which contains word beta. Here are few examples: beta hcg, beta alanine, beta carotene, beta blockers, beta endorphins, beta glucan. So this is not so easy, any of these names may be part of non-beta WCG project name. Automatic classification would not work here.

---

Beta means they are 'testing' an application (or the servers) for a project (sub-project/campaign). I doubt they would ever release an application for a new live project called 'Beta' anything, and I certainly don't expect to see a project/app called beta alanine (amino acid/supplement), vitamin or similar.

I tried to google a bit and found many medical-related terms which contains word beta. Here are few examples: beta hcg, beta alanine, beta carotene, beta blockers, beta endorphins, beta glucan. So this is not so easy, any of these names may be part of non-beta WCG project name. Automatic classification would not work here.

Hence why I said specifically a script >FOR WCG<, e.g. it only triggers if there's work reported from running WCG.

Else next time it could be 'Beta Testing' and we would have a 3rd listing for the same thing.

Incidentally, DuChamp released a new app version but fortunately it's dumping into the existing entry instead of starting all over. Got a new star, yea. :)