Changes between Version 35 and Version 36 of WorkGeneration

Timestamp:

Apr 30, 2014, 12:06:48 PM (11 years ago)

Author:

davea

Comment:

--

WorkGeneration

@@ -88 +88 @@
 Note that you only need one workunit template file and one result template file.
 
-Now suppose you want to run a program against a single input file, but with ten command lines, '-flag 0', '-flag 1', ..., '-flag 9'. You might modify the above program with the following code:
+Now suppose you want to run a program against a single input file,
+but with ten command lines, '-flag 0', '-flag 1', ..., '-flag 9'.
+You might modify the above program with the following code:
 {{{
     char command_line[256];
@@ -123 +125 @@
 You can easily modify this program to suit your application.
 
-In order to scan a directory for input files and create jobs therefrom, the default sample work generator can be adapted with a patch provided [http://boinc.berkeley.edu/trac/ticket/1202 here].
+In order to scan a directory for input files and create jobs therefrom,
+the default sample work generator can be adapted with a patch provided [http://boinc.berkeley.edu/trac/ticket/1202 here].
 
 === make_work === #examples-makework
-During the testing phase of a project, you may want to replicate a given workunit as needed to maintain a constant supply of work. The daemon program
+During the testing phase of a project,
+you may want to copy a given workunit as needed to maintain a constant supply of work.
+The daemon program
 {{{
-make_work -wu_name name [-wu_name name2 ... ] -cushion N
+make_work --wu_name name [--wu_name name2 ... ] --cushion N
 }}}
-creates copies of the given workunits (cyclically) as needed to maintain a supply of at least N unsent results. This is useful for testing purposes.
+does this;
+it creates copies of the given workunits (cyclically) as needed to maintain a supply of at least N unsent results.
+Other command-line arguments:
+ '''--max_wus N''':: exit after creating N workunits
+ '''--one_pass''':: check if workunits are needed, if so create them, and exit.
 
-Note: if you run the file_deleter and/or db_purge, the master workunit or its input files may be deleted (which will cause make_work to fail). To avoid this, give the master workunit a name that contains 'nodelete' as a substring. This causes the file_deleter and db_purge to skip over it.
+Note: if you run the file_deleter and/or db_purge,
+the master workunit or its input files may be deleted (which will cause make_work to fail).
+To avoid this, give the master workunit a name that contains 'nodelete' as a substring.
+This causes the file_deleter and db_purge to skip over it.
 
-It may be convenient to have a script that recreates the master workunit. For example:
+It may be convenient to have a script that recreates the master workunit.
+For example:
 {{{
 cp test_workunits/12ja04aa `bin/dir_hier_path 12ja04aa`