Changes between Version 9 and Version 10 of AssimilateIntro

Timestamp:

Apr 15, 2010, 9:50:24 AM (15 years ago)

Author:

davea

Comment:

--

AssimilateIntro

@@ -43 +43 @@
 Assimilators have the following command-line options:
 
- -app name :: the application name
+ --app name :: the application name
 
- [ -mod N R ] :: process only jobs with mod(ID, N) == R.  This lets you run multiple assimilators in parallel to increase throughput.
+ [ --mod N R ] :: process only jobs with mod(ID, N) == R.  This lets you run multiple assimilators in parallel to increase throughput.
 
  [ -d N ] :: set verbosity level (1 = least, 3 = most)
 
- [ -dont_update_db ] :: don't mark jobs as assimilated (for testing)
+ [ --dont_update_db ] :: don't mark jobs as assimilated (for testing)
  
 == The sample assimilator ==
@@ -56 +56 @@
 It does the following:
 
- * For successful workunits, it writes the canonical instance's output files to the directory '''PROJECT/sample_results/'''.  If there is only one output file it is named WU_NAME.  If there are more than one they are named WU_NAME_0, WU_NAME_1, etc.  If there are no output files, an empty file WU_NAME_no_output_files is created.
- * If the workunit failed (to many errors, etc.) it appends a line to '''sample_results/errors''' containing the workunit name and the error code.
+ * For successful workunits, it writes the canonical instance's output files to the directory '''PROJECT/sample_results/'''.
+  If there is only one output file it is named WU_NAME.
+  If there are more than one they are named WU_NAME_0, WU_NAME_1, etc.
+  If there are no output files, an empty file WU_NAME_no_output_files is created.
+ * If the workunit failed (e.g., too many errors) it appends a line to '''sample_results/errors''' containing the workunit name and the error code.
 
 The sample assimilator can be used as a placeholder while you