Changes between Version 11 and Version 12 of JobIn

Timestamp:

Sep 15, 2009, 9:04:38 PM (15 years ago)

Author:

davea

Comment:

--

JobIn

@@ -18 +18 @@
         A text string, unique across all workunits in the project.  You can guarantee uniqueness by embedding the PID of the creating process, a sequence number, and a Unix timestamp in the name.
  '''application'''::
-        Which [CompoundApps application] 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 either a) release new versions for all supported platforms, or b) create a new application. Such incompatibilities can often be avoided by using XML data format.
+        Which [AppVersion application] 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 either a) release new versions for all supported platforms, or b) create a new application. Such incompatibilities can often be avoided by using XML data format.
  '''input files'''::
         A list of the input files: their names, and the names by which the application refers to them. Typically these file are downloaded from a data server. However, if the `<generate_locally/>` element is present, the file is generated on the client (typically by an earlier instance of the same application). Applications should use file locking to prevent two jobs from generating the file at the same time.
@@ -50 +50 @@
         If the number of client error results exceeds this, the work unit is declared to have an error; no further results are issued, and the assimilator is triggered. This safeguards against workunits that cause the application to crash.
  '''max_total_results'''::
-        If the total number of results for this workunit exceeds this, the workunit is declared to be in error. This safeguards against workunits that are never reported (e.g. because they crash the core client).
+        If the total number of results for this workunit would exceed this, the workunit is declared to be in error. This safeguards against workunits that are never reported (e.g. because they crash the core client).
  '''max_success_results'''::
         If the number of success results for this workunit exceeds this, and a consensus has not been reached, the workunit is declared to be in error. This safeguards against workunits that produce nondeterministic results.