InfoMessage
1) Message boards : CMS Application : CPU utilisation with CMS.
Message 52596
Posted 26 Oct 2025 by mmonnin
The age old question at LHC
2) Message boards : Xtrack/SixTrack : Xtrack (Xboinc)
Message 52566
Posted 23 Oct 2025 by mmonnin
Is Xtrack going to have steady work or be like SixTrack?
3) Questions and Answers : Windows : Docker installation guide for Boinc
Message 52565
Posted 23 Oct 2025 by mmonnin
Docker is not needed at LHC.

There are instructions at projects that actually require Docker
4) Questions and Answers : Wish list : Additional options for number of tasks to download
Message 52558
Posted 22 Oct 2025 by mmonnin
The only way to perform OPs request is to have separate BOINC clients on a PC each running one of the LHC apps.
5) Questions and Answers : Wish list : Additional options for number of tasks to download
Message 52551
Posted 20 Oct 2025 by mmonnin
I make a local config

https://github.com/BOINC/boinc/wiki/Client-configuration

<app_config>
<app>
<name>Atlas</name>
<max_concurrent>2</max_concurrent>
</app>
<app>
<name>CMS</name>
<max_concurrent>4</max_concurrent>
</app>
<app>
<name>XTrack</name>
<max_concurrent>12</max_concurrent>
</app
</app_config>


This does not change how many tasks are downloaded.
6) Message boards : Xtrack/SixTrack : Invalid tasks
Message 52544
Posted 18 Oct 2025 by mmonnin
https://lhcathome.cern.ch/lhcathome/forum_thread.php?id=6378&postid=52524
7) Message boards : Xtrack/SixTrack : Xtrack (Xboinc)
Message 52524
Posted 13 Oct 2025 by mmonnin
Bugged WU, might be interesting to find out what's wrong with it.


Just the switch from 0.41 to 0.5. Same issue as this post

https://lhcathome.cern.ch/lhcathome/forum_thread.php?id=6378&postid=52500
8) Message boards : ATLAS application : ATLAS tasks not honoring CPU limitations on some PCs
Message 52481
Posted 7 Oct 2025 by mmonnin
https://www.man7.org/linux/man-pages/man1/taskset.1.html

Limit cores/threads with taskset
9) Message boards : Xtrack/SixTrack : Xtrack (Xboinc)
Message 52467
Posted 5 Oct 2025 by mmonnin
Welcome to CreditNew

Wait until you run quorum = 2 tasks and your credit is 1/10th of what it should be because your wingman hasn't run benchmarks.
10) Message boards : Xtrack/SixTrack : Xtrack (Xboinc)
Message 52455
Posted 4 Oct 2025 by mmonnin
Some of the tasks progress the %, others jump from 0.10 % to completion. From the tasks I've been able to watch, its ones with flat in the name that jump to 100%. Due to the crazy high ETA, the client will not ask for more work as it's expecting the tasks to run basically forever. Tasks with round in the name only have 500 FLOPS vs 500k FLOPS with flat in the name so the % completion actually works even with similar run time.

camontan__tune_scan_start_of_collapse_flat_scan_195__ScanShort_2_1__Hm6gxUEpNDDl_0
11) Message boards : Xtrack/SixTrack : Xtrack (Xboinc)
Message 52449
Posted 4 Oct 2025 by mmonnin
Yay initial ETA of 149 days
12) Message boards : Xtrack/SixTrack : Xtrack (Xboinc)
Message 52445
Posted 3 Oct 2025 by mmonnin
While I also prefer a static credit per task, projects like E@H have much more consistent run time at any given time. On one of my PCs I see run times of 400s to 10,000 seconds.
13) Message boards : Xtrack/SixTrack : Xtrack (Xboinc)
Message 52388
Posted 29 Sep 2025 by mmonnin
Users seem to be quite interested in these xtrack tasks. Nice to crunch these are.

Computers : Registered in past 24 hours : 1457
https://lhcathome.cern.ch/lhcathome/server_status.php


Users always come out of the woodworks for non-VB tasks at LHC. Same thing for SixTrack when it had work.
14) Message boards : Xtrack/SixTrack : Xtrack (Xboinc)
Message 52369
Posted 28 Sep 2025 by mmonnin
Just like at LHC-dev, its the task setup that causes so many to download. Not the queue buffer or the benchmark. This is up to the project, not the user.
On top of the poor flops estimate, the tasks very in run time but there is no variation in the task setup.

This type of task runs for 30-35 min
camontan__tune_scan_end_of_levelling_scan_134__ScanShort_17_3__jR1XCEh0dIuY_0

While this type runs for 3.5-4 hours
camontan__tune_scan_start_of_collapse_round_scan_135__ScanShort_40_2__7pq3Q73qWe7d_0

Yet both have the same estimate in between at 53 min
15) Message boards : Xtrack/SixTrack : Xtrack (Xboinc)
Message 52363
Posted 27 Sep 2025 by mmonnin
At least in BOINCTssks it can only go 2 digits to the right of the decimal so 0.01 days is lowest it will accept. Attempting 0.001 will round off to 0.00
16) Message boards : Xtrack/SixTrack : Xtrack (Xboinc)
Message 52310
Posted 24 Sep 2025 by mmonnin
The app on LHC-dev has VERY low ETAs as in a couple min vs reality of possibly days. Possibility as in the tasks ran from 30 min to 4 days on the same PC. They also run to 100% quickly then sit there for days. Hopefully the low ETA and running to 100% is fixed as it doesn't play nice with how the client operates.

As some have seen, be wary of admins dumping work so no one gets credit for completed work.
17) Message boards : CMS Application : CMS@Home -- jobs update
Message 51363
Posted 7 Jan 2025 by mmonnin
https://lhcathome.cern.ch/lhcathome/result.php?resultid=418694926

Run time 46 min 22 sec
CPU time 33 min 47 sec

Ya don't want logs? Posting task links is not useful for history as task data is purged. I've often come to BOINC forums and been unable to verify if I am having the same issue as described as only a link was posted. It also doesn't help when searching either. For this PC, I was able to fix the vbox issue on this PC yesterday by searching LHC forums with the error. This was only possible because someone posted their log.
18) Message boards : CMS Application : CMS@Home -- jobs update
Message 51361
Posted 7 Jan 2025 by mmonnin
All the tasks I've gotten on Linux PCs have been single threaded even with it set to be 4 threads in LHC preferences. The lone task I've completed in Win10 was mt. Both say Setting CPU Count for VM. (4)

Dev site seems to be missing but services must be up as I can download a task.
19) Message boards : CMS Application : Why all CMS virtualbox task were all failed... host was damaged?
Message 51327
Posted 25 Dec 2024 by mmonnin
https://lhcathome.cern.ch/lhcathome/forum_thread.php?id=6265&postid=51310#51310

There is no point running CMS atm as no work s being sent to the VM Task.
20) Message boards : CMS Application : Short CMS-Tasks ok?
Message 51252
Posted 6 Dec 2024 by mmonnin
The server hardware is being swapped around. Major reconfigurations are taking place. In other words - the machines the volunteers connect to are taken off line sporadically during this.
There is no work is available while the entire LHC@home crew are all busy doing this There's just no need to cater for generating the BOINC volunteers work while the system is mostly off line.
The work units that 'pop out' are just empty data transport vehicles with no actual LHC@home data for crunching in them. The data transport system is functioning but there are no "passengers", or in this case data in them.

There are gaps but often there is work available from the LHC@home project during this maintenance. I still have a very long Theory job running from last week. Last week saw ATLAS jobs available too. Sometimes you get all three at the same time. CMS, ATLAS & Theory!

These empty tasks are, some think, a bit of a waste of time. Stop them if you want.
I stopped pulling CMS work units a few days ago.
To do this:
Click on the "Project" item in the menu bar at the top of any LHC@home web page.
In the drop down list select "Preferences".
Click "Edit preferences".
Un-check the "CMS Simulation".
Un-check "If no work for selected applications is available, accept work from other applications?" (Leave everything else alone!)
Click "Update preferences".
--------
So it's just a matter of time before we see a completion of the maintenance upgrades.
It's a big old system y'all. Patience needed by all.


Bro, you're replying to the LHC overall #3, #11 and #18 users with nearly 1b credit. They know how to edit BOINC preferences.
Next 20


©2026 CERN