RALPH@home

Join RALPH@home

  UW Seal
 
[ Home ] [ Join ] [ About ] [ Participants ] [ Community ] [ Statistics ]
  [ login/out ]

Getting Started

READ THIS FIRST BEFORE DECIDING TO JOIN

This is an alpha test project with the goal to improve the Rosetta@home production project. We will be testing application updates, new work units, and other improvements on this project before applying them to Rosetta@home. Please consider the following before deciding to join:

  • Since this project is a testing environment, applications and work units may be unstable at times.
  • Credits and other competitive statistics do not mean anything in this test project. Credits may be lost due to instabilities and may be reset at any time for testing.
  • There will not be a continual flow of work units. Work units will be issued only when necessary for testing.
  • We urge participants to not abort work units to help with testing.
  • Please set the resource share low for this project compared to other production projects in your RALPH@home preferences.


It's easy to participate in RALPH@home
  1. Read the following pages first:

  2. Download, install, and run the BOINC software used by RALPH@home.

    Go to the download page, download the BOINC software for your type of computer, install it, and run it.

    You will be asked to enter the project URL:

    http://ralph.bakerlab.org/

    and to set up your account.

That's it!

Returning participants

If you are already running RALPH@home, you can

How it works

When you run BOINC on your PC, it works as follows (see below):

  1. Your PC gets a list of instructions from the project's scheduling server. The instructions depend on your PC: for example, the server won't give it work that requires more RAM than you have. The instructions may include many separate pieces of work. Projects can support several applications, and the server may send you work from any of them.
  2. Your PC downloads executable and input files from the project's data server. If the project releases new versions of its applications, the executable files are downloaded automatically to your PC.
  3. Your PC runs the application programs, producing output files.
  4. Your PC uploads the output files to the data server.
  5. Your PC reports the completed results to the scheduling server, and gets instructions for more work. This cycle is repeated indefinitely.
BOINC does this all automatically; you don't have to do anything.

Credit

The project's server keeps track of how much work each participant has contributed; this is called credit. The following system is used to ensure that credit is granted fairly:
  • Each work unit is sent to at least two computers.
  • When a computer reports a result, it claims a certain amount of credit, based on how much CPU time was used.
  • When at least two results have been returned, the server compares them. If the results agree, then users are granted the smaller of the claimed credits.


There may be a delay of several days between when your computer reports a result and when it is granted credit for the result. Your User page shows you how much credit is 'pending' (claimed but not granted).

More information

More detailed information about participating in BOINC projects is here.

Home | Join | About | Participants | Community | Statistics

Copyright © 2017 University of Washington

Last Modified: 21 Nov 2008 3:41:12 UTC
Back to top ^