A result describes an instance of a computation, either unstarted,
in progress, or completed.
The attributes of a result include:
- name
-
The name of the result (unique across all results in the project).
- workunit name
-
- output files
-
A list of the names of the output files,
and the names by which the application refers to them.
- state
-
Values include:
- Inactive (not ready to dispatch)
- Unsent (ready to dispatch, but not dispatched)
- In progress (dispatched, not done)
- Done successfully
- Timed out
- Done with error
- host
-
The host that executed the computation.
- CPU time
-
The CPU time that was used.
- exit status
-
The following attributes are defined after the result is completed:
- An XML document giving the sizes and checksums of its output
files (filled in after the result is completed).
- The stderr output of the result.
- The host that was sent the result.
- The times when the result was received.
Results are normally created using the
create_work utility.
The XML document listing the output files has the form:
<file_info>...</file_info>
[ ... ]
<result>
<name>foobar</name>
<wu_name>blah</wu_name>
<exit_status>blah</exit_status>
<file_ref>...</file_ref>
[ ... ]
</result>
The components are:
- The <name> element is the result name.
- The <wu_name> element is the workunit name.
- Each <file_ref> element is an association to an
output file, described by a corresponding <file_info> element.
The XML document describing the sizes and checksums of the output
files is just a list of <file_info> elements, with the
nbytes and md5_cksum fields present.
The project back end
must parse this field to find the locations and checksums of output files.
";
page_tail();
?>