log in


This a research project that uses Internet-connected computers to advance Particle and Accelerator Physics. Participate by downloading and running a free program on your computer. By default, you can run the classic LHC@home application Sixtrack, for simulations of accelerator physics, and help researchers at CERN to improve the LHC.

Other LHC@home simulations that utilizes virtualization to run applications for Theory and experiment simulations for ATLAS, CMS and LHCb are also available. In order to run these, you need to install VirtualBox and enable the additional applications in your LHC@home project preferences.

Please visit the LHC@home web site for more documentation, data and instructions. If you have any problem, question or doubt please visit the Message Boards, Questions and Answers and FAQ sections of the project.

Join LHC@home

  • Read our rules and policies
  • This project uses BOINC. If you're already running BOINC, select Add Project. If not, download BOINC.
  • When prompted, select LHC@home from the list of projects, or enter the URL:
  • If you're running a command-line version of BOINC, create an account first.
  • If you have any problems, get help here.

User of the day

User profile Profile killik
I'm system admin. I like to listen good music. Member of Czech National Team.


Phaseout of legacy site: lhcathomeclassic.cern.ch/sixtrack
LHC@home has been consolidated and uses SSL for communication as mentioned in this thread last year.

Some BOINC clients are still connecting to the old lhcathomeclassic.cern.ch/sixtrack address, that will be phased out soon.

If this is the case for you, please re-attach the project to the current LHC@home URL presented in the BOINC manager. (http://lhcathome.cern.ch will redirect your BOINC client to https://lhcathome.cern.ch/lhcathome )

For those who are still running an old BOINC 6 client, please upgrade to BOINC 7.2 or later. (The current BOINC client releases are 7.6.33 or 7.8.)

Many thanks for your contributions to LHC@home!
29 Sep 2017, 13:50:32 UTC · Comment

CMS jobs unavailable Weds 27th September
An upgrade to the CMS@Home workflow management system (WMAgent) is planned for tomorrow (Wed Sep 27th). This needs the current batch of jobs to be stopped so that the queue is empty. I plan to do this about 0700-0800 UTC on Wednesday.
To avoid "error while computing" task failures and the resulting back-off of your daily quotas, we suggest you set all your CMS machines to No New Tasks at least 12 hours beforehand to allow current tasks to time out in the normal way. You can stop BOINC once all your tasks are finished, if you wish.
Exactly how long the intervention will take is unclear, and there will be a delay of up to an hour to get a new batch of jobs queued afterwards. I will post here when jobs are available again, hopefully before the end of the day European time.
26 Sep 2017, 12:23:21 UTC · Comment

Possible systems failures
We seem to be in the early stages of a system failure for several sub-projects. The proxy server has flatlined and my running jobs monitor is dipping alarmingly. Please check if you are getting tasks flagged as computing failures, and set No New Tasks if so.
[Edit] On closer inspection, it may just be the CMS app. [/Edit]
Obviously I'll apologise if this is a false alarm, but it's the wrong time of day to expect a prompt response from the CERN admins.
18 Sep 2017, 22:00:28 UTC · Comment

New SixTrack exes
Dear all,

After testing them as the sixtracktest app, we have just pushed out executables to the sixtrack app. For the moment, we have exes only targeted for the main OSs, i.e. Windows, Linux, and the brand new one for MacOS. We are still finalising the definition of the plan classes with the sixtracktest app for targeting Android, freeBSD, and Arm CPUs - e.g. see

Thanks a lot for your contribution and ... happy crunching!
Alessio, for the sixtrack team
5 Sep 2017, 16:40:44 UTC · Comment

Deadline change for ATLAS jobs
Due to the tight deadline of the ATLAS tasks, we change to deadline of ATLAS jobs from 2 weeks to 1 week. The ATLAS job takes about 3-4 CPU hours to finish on a moderate CPU (2.5GFLOPS). 16 Aug 2017, 8:42:03 UTC · Comment

... more

News is available as an RSS feed   RSS