LHC@home

Unknown Application ATLAS, known Application CMS and SIXTRACK?
in app_config:
<app_config>
<app>
<name>ATLAS</name>
<max_concurrent>4</max_concurrent>
</app>
<app_version>
<app_name>ATLAS</app_name>
<avg_ncpus>2</avg_ncpus>
<plan_class>vbox64_mt_mcore_atlas</plan_class>
<cmdline>--memory_size_mb 6250</cmdline>
</app_version>
</app_config>

Unknown Application ATLAS, known Application CMS and SIXTRACK?

Do you still get this message after you got at least 1 ATLAS-task?

Have CMS and Atlas in prefs active, but only CMS is running.
https://lhcathome.cern.ch/lhcathome/results.php?hostid=10631979
2021-10-21 15:40:28 (4408): Detected: vboxwrapper 26202
2021-10-21 15:40:28 (4408): Detected: BOINC client v7.16.20

Deselect CMS and get only 1 ATLAS and that message will disappear, I suppose.

CMS deselected, no ATLAS tasks.
Had nothing changed, only Boinc from 7.16.11 to 7.16.20 (new Version on Boinc-Homepage) upgraded.
Because of app_config.xml, is this from Cern Server a default parameter missing?
Will testing a deattach and new attach of lhc@home tomorrow.

I updated all mine and I didn't see any changes, this is mine

<app_config>

<app>
<name>ATLAS</name>
<max_concurrent>42</max_concurrent>
</app>
<app_version> 
<app_name>ATLAS</app_name> 
<plan_class>vbox64_mt_mcore_atlas</plan_class> 
<avg_ncpus>1.0</avg_ncpus> 
<cmdline>--memory_size_mb 10200</cmdline> 
</app_version>
</app_config>

I would check if "Run native if available?" is deselected for the venue that computer is connected to.

Why do you need app_config for ATLAS if you can just change the preferences in your user profile?
I dumped app_config long ago after I saw this:

Max # jobs 1
Max # CPUs 4

That's my configuration and it works just fine. I grind 1 ATLAS tasks at a time on 4 cores and I can run other projects as well on the other cores. No memory issues, no bog downs or errors and no error messages about unknown project names.

This is my project setup for LHC

Run only the selected applications

SixTrack: no
sixtracktest: no
CMS Simulation: yes
Theory Simulation: yes
ATLAS Simulation: yes
ATLAS (long simulation): no

This is the message after reading configuration:
22.10.2021 18:07:11 | LHC@home | Your app_config.xml file refers to an unknown application 'ATLAS'. Known applications: 'CMS', 'sixtrack'

Have nothing changed and got with 7.16.11 Atlas and not this message.
native is active for CentOS8-VM. (using work instead of school or home).

This is the message after reading configuration:
22.10.2021 18:07:11 | LHC@home | Your app_config.xml file refers to an unknown application 'ATLAS'. Known applications: 'CMS', 'sixtrack'

Have nothing changed and got with 7.16.11 Atlas and not this message.
native is active for CentOS8-VM. (using work instead of school or home).

Remove app_config or rename it with something like.old extension, change your preferences in your user profile. I am finding app_config is not working very well with the new BOINC. I have removed it from all my projects and just used project settings to control things.

Uncheck everything but ATLAS.
Set your cpu's to 2 or 4 (I was told long long ago that ATLAS likes even numbers of cores)
Set your tasks to 1 (it will download one task and process it and upload it and start a new one) or if you have enough memory you can download and run more. I just do one since ATLAS is not my sole project.

For me the 4 cores 1 task at a time works very well and I get no errors.
I'm thinking this current BOINC hates app_config.

You'll get this time of message when referencing an app name in an app_config file until you've gotten a task for the named app. The message does no harm. Ignore it.

Have app_name deleted. This are the new messages:
23.10.2021 04:08:59 | LHC@home | Your app_config.xml file refers to an unknown application ''. Known applications: 'CMS', 'sixtrack'
23.10.2021 04:08:59 | LHC@home | Your app_config.xml file refers to an unknown application ''. Known applications: 'CMS', 'sixtrack'

<app_config>
<max_concurrent>1</max_concurrent>
</app>
<app_version>
<avg_ncpus>2</avg_ncpus>
<plan_class>vbox64_mt_mcore_atlas</plan_class>
<cmdline>--memory_size_mb 6250</cmdline>
</app_version>
</app_config>

Have app_name deleted. This are the new messages:
23.10.2021 04:08:59 | LHC@home | Your app_config.xml file refers to an unknown application ''. Known applications: 'CMS', 'sixtrack'
23.10.2021 04:08:59 | LHC@home | Your app_config.xml file refers to an unknown application ''. Known applications: 'CMS', 'sixtrack'

<app_config>
<max_concurrent>1</max_concurrent>
</app>
<app_version>
<avg_ncpus>2</avg_ncpus>
<plan_class>vbox64_mt_mcore_atlas</plan_class>
<cmdline>--memory_size_mb 6250</cmdline>
</app_version>
</app_config>

All the above needs to go...no app_config.xml,,rename it app_config.old if you want to keep the text.

No need to set memory size, ATLAS uses a specific amount and only that amount per task.
The amount of cores used can be set in your user profile in this section:

Preferences for this project LHC@home preferences
Within that section you will find at the bottom of the page this:

Max # jobs
Max # CPUs

My personal setting is 1 job and 4 cpu's. You can try 1 job and 2 cpu's since that is what you had in app_config.

You can change this by clicking on the edit settings text at the bottom of the page.


Your app config is doing exactly what the web based preferences are doing.

Thanks greg_be,
BUT, my way is WITH app_config, sorry.
You are right. It's the easy way to do it so.
When you have a mixture of Projects with W10pro and CentOS8-VM and only three options of prefs (home, school, work), or
have to reduce Projects to run more than one in a VM or Windows, an app_config is the only way.
Yes, as computezrmle wrote, to deselect native will be run.
In this app_config is a fault, because get only CMS and no Atlas for W10pro.

@maeax: What are your settings in project preferences for Max # jobs and Max # CPUs for the venue conncted to that Host.?
Is 'native' not ticked and all applications off except ATLAS?
Btw: Is the host-id 10631979?

Maximale Anzahl Aufgaben 5
Maximale Anzahl CPUs 1
Startet nur die ausgewählte Anwendung/en SixTrack: nein
sixtracktest: nein
CMS Simulation: ja
Theory Simulation: nein
ATLAS Simulation: ja
ATLAS (long simulation): nein

native is enabled, because of CentOS8-VM.
https://lhcathome.cern.ch/lhcathome/results.php?hostid=10631979
Edit: if native is enabled, and it is not a VM, but Win10pro
Tasks for Atlas should be possible.
When CMS is disabled, no new tasks in Win10pro.

Maximale Anzahl CPUs 1

I think there's still the server-side bug, that you get only twice the tasks for the number of CPU's set. (bug), but not relevant for not getting ATLAS.

native is enabled, because of CentOS8-VM.

For Windows you have to disable 'native' (sorry), so you should use different venues for Windows and Linux, if you want to run native ATLAS on Linux.

As CP already wrote:
"Run native if available?" MUST be disabled to get ATLAS tasks for a Windows computer (at least temporarily :-) ).

As mmonnin already wrote:
"The message does no harm...", hence it's save to ignore it.


The discussion about an app_config.xml does not solve the issue here as the decision whether to send ATLAS or not is made at the server and the server does not even know whether an app_config.xml is in use or not.


"...only three options of prefs (home, school, work)..."
There's a 4th venue that can be used: the default venue.

"...only three options of prefs (home, school, work)..."
There's a 4th venue that can be used: the default venue.

Ok, you all have beat me with news... thank you.
Yes default is also a option, but not well, when using the other three.
Must be more careful to use the three options well....

Edit: Default... Zero is not Null ;-)

"...only three options of prefs (home, school, work)..."
There's a 4th venue that can be used: the default venue.

Ok, you all have beat me with news... thank you.
Yes default is also a option, but not well, when using the other three.
Must be more careful to use the three options well....

Edit: Default... Zero is not Null ;-)

Good luck! I leave you in the hands of the experts.
Happy Error Free Crunching.