LHC@home

Two of my machines, which have run multiple ATLAS WU's previously, are getting a single WU and then the error sequence:

10/25/2017 11:18:03 PM | LHC@home | Requesting new tasks for CPU
10/25/2017 11:18:07 PM | LHC@home | Scheduler request completed: got 0 new tasks
10/25/2017 11:18:07 PM | LHC@home | No tasks sent
10/25/2017 11:07:48 PM | LHC@home | No tasks are available for ATLAS Simulation

Server shows over 2000 unsent tasks.
All server feeds green lit.

Preferences set to
unlimited WU
Project cores 1

relevant app_config:

<project_max_concurrent>32</project_max_concurrent>

<app>
<name>ATLAS</name>
<max_concurrent>6</max_concurrent>
<fraction_done_exact/>
</app>

<app_version>
<app_name>ATLAS</app_name>
<plan_class>vbox64_mt_mcore_atlas</plan_class>
<avg_ncpus>1.000000</avg_ncpus>
<cmdline>--nthreads 1.000000</cmdline>
<cmdline>--memory_size_mb 3400</cmdline>
</app_version>

On the one machine the single ATLAS WU is the only CPU work BOINC is undertaking and there is 20+ free GB RAM and 90GB free on the partition.
Set to 0.5 days work +1.5 days additional. Use 90% RAM.

The other machine ran 3x single core ATLAS at a time a few days back and just ran 32x Theory WU at a time.

Is this task limiting like YAFU does when it limits to maximum 2 WU's per computer or is there some issue?

Preferences set to
unlimited WU
Project cores 1

try using a specific number (not unlimited)

Preferences set to
unlimited WU
Project cores 1

try using a specific number (not unlimited)

That actually worked although it left me with the inability to d/l enough tasks to support all cores on the machine. Although there is the other issue that LHC won't send Theory sims to fill out the remaining cores once several ATLAS are in the queue. Gave up on ATLAS for a while until I can find time to double install BOINC.

...Gave up on ATLAS for a while until I can find time to double install BOINC.

You needn't double install BOINC. One simply BOINC-Install has the option to run more than one Instance, you only have to set up several Startup-Parameters and one additional Data-Directory for each Instance.

If you are a german speeking guy, you can find a "HowTo" here: https://www.rechenkraft.net/forum/viewtopic.php?f=92&t=16614

---

Supporting BOINC, a great concept !

...Gave up on ATLAS for a while until I can find time to double install BOINC.

You needn't double install BOINC. One simply BOINC-Install has the option to run more than one Instance, you only have to set up several Startup-Parameters and one additional Data-Directory for each Instance.

If you are a german speeking guy, you can find a "HowTo" here: https://www.rechenkraft.net/forum/viewtopic.php?f=92&t=16614

I've tried that option and it's not as flexible and a double install with separate WUprops tracking and separate cc_config.xml files. Each installation is on the drive with its data and can be moved to another computer and is isolated from drive failure. Single install is less portable.

I would run 32 core ATLAS tasks if that were an option.

Only remember a few German words from my grandmother.

For the ones who aren't good in foreign languages , there is a good site for translation , this is deepl.com.
It is not as efficient as a human traductor , but more than usual and automatic translators like google traduction.
It uses a neural networks to determine the surrounding of a text ,globally, before providing a translation.
The number of tongues it is able to translate is still going to increase.
To follow...

I've tried that option and it's not as flexible and a double install with separate WUprops tracking and separate cc_config.xml files. Each installation is on the drive with its data and can be moved to another computer and is isolated from drive failure. Single install is less portable.

Nope, you are not right.

You are able to put each instance of BOINC whereever you want and it is as flexibel as a second / third install. Each Instance has its own queue with own WUs and own projects

---

Supporting BOINC, a great concept !

I've tried that option and it's not as flexible and a double install with separate WUprops tracking and separate cc_config.xml files. Each installation is on the drive with its data and can be moved to another computer and is isolated from drive failure. Single install is less portable.

Nope, you are not right.

You are able to put each instance of BOINC whereever you want and it is as flexibel as a second / third install. Each Instance has its own queue with own WUs and own projects

You are saying a single install of BOINC can handle multiple queues and project lists? How, and what is the advantage when not using remote administration?
Three BOINC icons on the task bar takes you straight to each of the three installs and opens up it's management interface. There's no messing around with switches on startup icon. I can get a triple BOINC install setup in the amount if time it takes to copy the BOINC folder and is much easier than setting up a single new install and then messing around with configurations.

Setup speed and ease of maintenance are crucial.

Your solution is not portable.
The BOINC App needs to be in the same folder as the Data folder.
(D:\BOINC\APP and D:\BOINC\DATA) so that the entire install can be ported to another partition and each data folder can be moved with its app independently to a different computer.
That would be D:\BOINC\APP and D:\BOINC\BUNKER\1

You don't need to reinstall BOINC.
You just need to copy D:\BOINC to a new computer with it's projects and app_config.xml intact and allow a new crossID to be created once the new computer requests work.

You are saying a single install of BOINC can handle multiple queues and project lists?

YES

How, and what is the advantage when not using remote administration?

You give each BOINC-Instance an own Data-Directory and own Management-Ports

Three BOINC icons on the task bar takes you straight to each of the three installs and opens up it's management interface.

What do you with 100 instances or more ?

Your solution is not portable.

shure it is

The BOINC App needs to be in the same folder as the Data folder.

NO

My BOINC-APPs are at c:\ProgrammFiles\....
My DATA-Directorys are at x:\...

---

Supporting BOINC, a great concept !

The BOINC App needs to be in the same folder as the Data folder.

NO

That is the definition of portable apps.
Application and data forks within the same main folder.

My BOINC-APPs are at c:\ProgrammFiles\....
My DATA-Directorys are at x:\...

Not a portable install.
The C:\programmFiles\ folder is on the OS partition (unless you create a hard directory link to another partition) and will be lost when the OS is wiped for reinstall or it won't be transferred when you take the USB external/thumb drive or swappable partition, with data folders, and move it to another computer.


https://en.wikipedia.org/wiki/Portable_application