Rooba
/
boinc
mirror of https://github.com/BOINC/boinc.git
1
0
Fork 0
Code Issues 1 Packages Projects Releases Wiki Activity

*** empty log message *** 

svn path=/trunk/boinc/; revision=4654
This commit is contained in:
David Anderson 2004-11-25 07:58:14 +00:00
parent da3bffef60
commit f3fb76d593
2 changed files with 30 additions and 29 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

49
doc/app.php
View File

@ -3,9 +3,9 @@ require_once("docutil.php");
page_head("Applications and versions");
echo "
<p>
An <b>application</b> represents a particular distributed computation;
it consists of a program (perhaps with versions for different platforms)
and a set of workunits and results.
An <b>application</b> represents a collection of related computation.
It consists of a program (perhaps with versions for different platforms)
and a set of <a href=work.php>workunits</a> and <a href=result.php>results</a>.
A project can operate many applications.
Applications are maintained in the <b>application</b> table in the BOINC DB,
and can be created using the <a href=tool_xadd.php>xadd</a> utility.
@ -16,15 +16,16 @@ An application program may go through a sequence of
A particular version, compiled for a particular platform, is
called an <b>application version</b>.
An application version can consist of multiple files: for example, a
controller script, pre- and post-processing programs, and a primary executable.
controller script, pre- and post-processing programs, and a primary program.
<p>
Each application version has an integer <b>version number</b>.
Projects can assign version numbers however they like; for example,
version 304 might represent major version 3 and minor version 4.
This number is of the form 100*major + minor;
for example, 304 represents major version 3 and minor version 4.
An application version will only run on a core client
having the same major version.
Version numbers should be used consistently across platforms;
Windows version 304 should be computationally identical to
Mac version 304.
Windows version 304 should be computationally identical to Mac version 304.
<p>
Each application has a <b>minimum version</b>.
@ -37,22 +38,22 @@ Application versions are maintained in the <b>app_version</b> table
in the BOINC DB.
Each entry includes an XML document describing the
files that make up the application version:
<pre>
&lt;file_info&gt; ...
&lt;/file_info&gt;
[ ...
]
&lt;app_version&gt;
&lt;app_name&gt;foobar&lt;/app_name&gt;
&lt;version_num&gt;4&lt;/version_num&gt;
&lt;file_ref&gt;
&lt;file_name&gt;program_1&lt;/file_name&gt;
&lt;main_program/&gt;
&lt;/file_ref&gt;
&lt;file_ref&gt;
&lt;file_name&gt;library_12&lt;/file_name&gt;
&lt;/file_ref&gt;
&lt;/app_version&gt;
<pre>".htmlspecialchars("
<file_info>
...
</file_info>
[ ... ]
<app_version>
<app_name>foobar</app_name>
<version_num>4</version_num>
<file_ref>
<file_name>program_1</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>library_12</file_name>
</file_ref>
</app_version>")."
</pre>
Application versions can be created using
<a href=tool_update_versions.php>update_versions</a>.

10
doc/work.php
View File

@ -4,7 +4,7 @@ page_head("Workunits");
echo "
<p>
A <b>workunit</b> describes a computation to be performed.
The basic workunit attributes include:
Its attributes include:
";
list_start();
@ -14,10 +14,10 @@ list_item(
);
list_item(
"application",
"Which application performs the computation.
A workunit is associated with an application, not with a particular
version or range of versions.
If the format of your input data changes in
"Which <a href=app.php>application</a> will perform the computation.
A workunit is associated with an application,
not with a particular version or range of versions.
If the input data format changes in
a way that is incompatible with older versions,
you must create a new application.
This can often be avoided by using XML data format. "