This is a BOINC server for LHC@home development. Please note that some of the applications on LHC@home requre Virtual Box to be installed. Please visit the LHC@home information site for more information. If you have any problems or questions please visit the Message Boards, Questions and Answers and FAQ.
Development project "face lift"
The development project has been upgraded to use the latest BOINC upstream code. Thus, it now has a new look based on Bootstrap in accordance with other projects like SETI@home.
Your feedback and suggestions are, as always, appreciated.
11 Oct 2017, 8:16:29 UTC · Discuss
Over the next week, some of the servers will be migrated in order to upgrade from SL6 to CC7. This will hopefully be transparent but if there are issues, this may be the reason.
6 Oct 2017, 8:30:12 UTC · Discuss
The server will be upgraded today to use the latest version of the Web interface. We anticipate that things may break so expect some instability over the next few days. What we discover by doing this will hopefully make the upgrade of the production server smoother.
3 Oct 2017, 7:45:01 UTC · Discuss
Reminder -- 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:25:22 UTC · Discuss
A new feature has been implemented to shutdown multicore VMs at the end of their life when the idle time > busy time. This means that if we are wasting more time with empty cores than we would loose by kill the remaining jobs, those jobs are killed. This should avoid the situation where a looping Theory job keeps the VM alive while wasting idle cores. If this works the following message should be seen in the task output.
Multicore Shutdown: Idle > Busy ( 1439s > 1382s )