LHC@home

LHC@home: Notice from BOINC
Your app_config.xml file refers to an unknown application 'ATLAS'. Known applications: None


What? This is crazy.
This is like the second or third time I have had this happen.

I reset the project, no change.
Repaired BOINC, no change.


What now? Because of this error I get: | LHC@home | No tasks are available for ATLAS Simulation

I see in preferences on the project that it does limit the total cpu's to 4, so in theory I do not need app_config.xml anymore? Going to test this.

This usually happens after a project reset:
Your BOINC client tries to overwrite some values regarding ATLAS with values from your app_config.xml
before you got the default ATLAS values from the project server.
Hence, ATLAS is not yet known to your BOINC client.

What now? Because of this error...

Not because of this.
You don't get ATLAS tasks because the project runs more than 1 project server for load balancing and it's only the server your request is connected to that has no ATLAS tasks.
Wait until the DNS record needs an update and then try to get work again.
Be aware that DNS delivers the server IPs in random order. Hence, you may get the "wrong" server again.
:-(

Why have WCG a normal flow of tasks?
There must be a problem, to get more tasks. Seeing this now since a few days.
20k, 30k or 36k of credits, with the same PC's for me.
Sixtrack is coming back next time. We will see this more and more...., sorry.

This usually happens after a project reset:
Your BOINC client tries to overwrite some values regarding ATLAS with values from your app_config.xml
before you got the default ATLAS values from the project server.
Hence, ATLAS is not yet known to your BOINC client.
Interesting, does not happen all the time

What now? Because of this error...

Not because of this.
You don't get ATLAS tasks because the project runs more than 1 project server for load balancing and it's only the server your request is connected to that has no ATLAS tasks.
Wait until the DNS record needs an update and then try to get work again.
Be aware that DNS delivers the server IPs in random order. Hence, you may get the "wrong" server again.
:-(

So I guess I need to select another project within LHC to keep getting some kind of credit if this is going to happen alot?

You can ignore that message or as you say just skip app config and make changes on site instead. Simple solution is to not app config and run default

This how boinc-client works and has nothing with to do which project how handle applications. It would be unknown at start.
Reset project or repair would only wipe master files and make client to download it again.

You can ignore that message or as you say just skip app config and make changes on site instead. Simple solution is to not app config and run default

This how boinc-client works and has nothing with to do which project how handle applications. It would be unknown at start.
Reset project or repair would only wipe master files and make client to download it again.

Removed app_config and waiting for some CMS stuff to clear out.
I don't recall why I made app config other than it was trying to run 8 cores and it would quit working correctly and just sit and do nothing until I aborted it. So I put in the app_config to limit it to 4 cores and to 1 running task. I guess now that is obsolete with the changes on the projects webpage.