Work Unit/Result Name
From Unofficial BOINC Wiki
Contents |
[edit] General
This is the "Name" of the Work Unit. The Work Unit has, in fact, two items that will uniquely identify it. One is the human readable "Name" and the other is the Work Unit ID. The Work Unit ID is a number which is used by the database to track the Work Unit (for database freaks, the Primary Key value). This second, usually hidden value, is the one that is a positive integer that is used in the links connecting pages like the "Result" Page to the "Work Unit" Page.
The one we are concerned about here is a descriptive name that uses a Project specific scheme to create uniquely named object of work. For example, the SETI@Home Project identifies the tape from which this Work Unit has been extracted, along with a bunch of other information about the source of the Work Unit.
Other BOINC Powered Projects will be doing the same type of thing, but in the context of their Project. There is one constant across all Projects the last number in the Work Unit Name is the Result Identifier. For the most part this is a lot of "who cares?" other than we know that the Work Unit has a unique identifier.
The way that the Work Units are identified should be described on that Project's Web Site (if you really care that much). The identification data may be a simple, but long identifier, or may have within its seemingly random collection of numbers, letters, and punctuation encoded information that can be decoded if you send in enough box-tops and get the Genuine Captain Paul Marvell's Magic Secret Decoder Ring (the ring itself is free, but the shipping and handling is a low, low $56.95 U.S.; don't wait, rush down to the post office while supplies last …).
A Result Name is simply a modification of the Work Unit Name by adding an identifier. This identification number, as a suffix to the Work Unit Name, provides a means of establishing a unique Result identifier. So, when the Work Unit is split into Results to be sent out to the Participant's Computers, a Result Identifier is appended to the Work Unit Name. The format of this identifier is "_#". An underscore ("_") separates the Result Identifier from the Work Unit Name. The "#" is replaced with the sequence number beginning with zero (0) and continuing upwards in increasing value.
This value may, if the Project requires, be more than a single digit in length.
[edit] Example: BURP
In the BURP Project, for example, the Work Unit Name breaks down as follows:
| Name Part | Description |
|---|---|
| 137in0.zip | The session number. |
| ses0000000137 | The session number again. |
| frm0000000282 | The frame number. |
| prt00003 | The part number. |
| wu | This is a Work Unit. |
- Note:
- When the Work Unit is split into Results and sent out to Hosts for processing a Result Identifier is appended to the Work Unit Name. The format is "_#". The underscore ("_") separates the Result Identifier from the Work Unit Name. The "#" is replaced with the sequence number beginning with zero (0).
[edit] Example: LHC@Home
In the LHC@Home Project, for example, the Work Unit Name breaks down as follows:
| Name Part | Description |
|---|---|
| wjun4B | A workspace directory name |
| v6s4hhpac_mqx | The study name where: |
| v6s4 | LHC Version 6 Subversion 4 |
| hhpac_mqx | Just a name for the particular physics case |
| 9 | The current seed number (typically between 1 and 60) representing a set of magnet errors |
| 64.2914_59.3077 | The tunes x and y (the current topic of investigation) |
| 6_8 | The initial amplitude range of the tracked particles |
| 6 | The order of the the number of turns 1000000 |
| 10 | The initial angle in phase space (between 0 and 90 degrees) |
| 1_sixvf_boinc12302 | Identification string for the BOINC System |
- Note:
- When the Work Unit is split into Results and sent out to Hosts for processing a Result Identifier is appended to the Work Unit Name. The format is "_#". The underscore ("_") separates the Result Identifier from the Work Unit Name. The "#" is replaced with the sequence number beginning with zero (0).
[edit] Example: Rosetta@Home
In the Rosetta@Home Project, for example, the Work Unit Name breaks down as follows:
| Name Part | Description |
|---|---|
| 1btn | The first four characters represent the pdbid of the protein being tested.
Where the pdbid is the uniquie identifier given to each structure in the Protein Data Bank. A pdbid is represented by a 4 character alphanumeric identifier, assigned upon its deposition. For example, 4hhb and 9ins are identification codes for PDB entries for hemoglobin and insulin, respectively. Many of the PDB Web site pages, including the PDB home page, allow you to enter a PDB ID and retrieve information for the corresponding structure. |
| abrelax | Signifies that the Work Unit is going to be doing low resolution ab "initio prediction" followed by high resolution full-atom relax. |
| 32948 | The Work Unit specific identifier. |
- Note:
- The names are fairly arbitrary and will change with different experiments.
- Note:
- When the Work Unit is split into Results and sent out to Hosts for processing a Result Identifier is appended to the Work Unit Name. The format is "_#". The underscore ("_") separates the Result Identifier from the Work Unit Name. The "#" is replaced with the sequence number beginning with zero (0).
[edit] Example: SETI@Home
In the SETI@Home Project, for example, the Work Unit Name breaks down as follows:
| Name Part | Description | ||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 08au03ab | This indicates the date the data was recorded and the tape number where this Work Unit was recorded. In this case the signal was recorded on the 8th of August 2003 and it was recorded on tape "ab" which is the second tape of the day.
This breaks down as:
| ||||||||||||||||||||||||
| 28481 | This is the "process ID" (or process number) of the "Splitter" program that is running on the server that is writing out the file. This allows them to trace back if there is a failure with a particular batch of Work Units. | ||||||||||||||||||||||||
| 2178 | The tape's current record number. This identifies the location along the length of the data tape which is where this Work Unit's data was recorded. I'm not sure what the record size is in this case, but basically how far along into the tape we are - probably the same as the "block" number on the tape. | ||||||||||||||||||||||||
| 117304 | The byte offset from the start of the record number where the Work Unit's data actually starts (in any case, it is another datum about Work Unit's position on the tape). | ||||||||||||||||||||||||
| 159 | Spectrum Identification Value:
|
- Note:
- When the Work Unit is split into Results and sent out to Hosts for processing a Result Identifier is appended to the Work Unit Name. The format is "_#". The underscore ("_") separates the Result Identifier from the Work Unit Name. The "#" is replaced with the sequence number beginning with zero (0).
RSS Feeds
