log in

vLHCathome-dev

If you would like to join this project you will need to get an invitation code first.
In order to get an invitation code, please check out this post.

This is a project that utilizes the CERN-developed CernVM virtual machine and the BOINC virtualization layer to harness volunteer cloud computing power for full-fledged LHC event physics simulation on volunteer computers.
This is just a BOINC server. Please visit the LHC@home information for more information. If you have any problems or questions please visit the Message Boards, Questions and Answers and FAQ.

Join vLHCathome-dev

  • Read our rules and policies
  • Create an account on this page, for this you will need an invitation code. In order to get an invitation code, please check out this post.
  • This project uses BOINC. If you're already running BOINC, select Add Project. If not, download BOINC.
  • When prompted, enter
    http://lhcathomedev.cern.ch/vLHCathome-dev/
  • 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 Steve Hawker*
I've been crunching since 2012 and the more I do, the more I like it. I try to crunch every project I can find. I don't have a server farm or a...

News

Infrastructure Update
The authentication server used to get the proxy has been changed. New tasks from now on will use the new server. This change should be transparent but in case everything breaks in the next few hours, this will be why. 24 May 2016, 13:31:00 UTC · Comment


CERN Bulletin
This article was published in the CERN Bulletin yesterday.

http://cds.cern.ch/journal/CERNBulletin/2016/20/News%20Articles/2151943?ln=en
18 May 2016, 11:20:48 UTC · Comment


Project Configuration Update 2
Some project configuration parameters have been changed to help avoid hosts being swamped with tasks and to back off problem hosts.

<daily_result_quota> 2 </daily_result_quota>

<max_wus_in_progress> 1 </max_wus_in_progress>

<max_wus_to_send> 1 </max_wus_to_send>

<min_sendwork_interval> 60 </min_sendwork_interval>


Note that the values are multiplied by the number of cores and we estimate tasks lasting for at least 12 hours.

Ref: https://boinc.berkeley.edu/trac/wiki/ProjectOptions

Please post if this causes any problems for anyone. 3 May 2016, 19:22:10 UTC · Comment

Error Codes
At the beginning of next week work will start on providing consistent error codes and behaviour for all applications. Three error codes will be used:


  • EXIT_INIT_FAILURE (When an error is detected on contextualizing the VM or setting up the job environment)
  • EXIT_NO_JOBS (When the job queues are empty)
  • EXIT_JOB_FAILURE (When an error is detected that caused all jobs to fail or all jobs have failed)


Any of these errors should cause the BOINC client to back-off. If you see any errors and one of these codes is not used, please let us know.

EDIT: To get this into the upstream release the codes have changed to:


  • EXIT_NO_SUB_TASKS
  • EXIT_TASK_FAILURE

30 Apr 2016, 17:51:59 UTC · Comment


Refactoring
The bootstrapping code used to prepare the environment for the jobs in the VM has been re-factored so that common tasks for the five applications are abstracted to common functions. It has been tested in a VM but there may be issues relating to the diversity of our environment and error conditions. 22 Apr 2016, 14:44:49 UTC · Comment


... more

News is available as an RSS feed   RSS