Changes between Version 35 and Version 36 of WorkGeneration


Ignore:
Timestamp:
04/30/14 12:06:48 (4 years ago)
Author:
davea
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • WorkGeneration

    v35 v36  
    8888Note that you only need one workunit template file and one result template file.
    8989
    90 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:
     90Now suppose you want to run a program against a single input file,
     91but with ten command lines, '-flag 0', '-flag 1', ..., '-flag 9'.
     92You might modify the above program with the following code:
    9193{{{
    9294    char command_line[256];
     
    123125You can easily modify this program to suit your application.
    124126
    125 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].
     127In order to scan a directory for input files and create jobs therefrom,
     128the default sample work generator can be adapted with a patch provided [http://boinc.berkeley.edu/trac/ticket/1202 here].
    126129
    127130=== make_work === #examples-makework
    128 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
     131During the testing phase of a project,
     132you may want to copy a given workunit as needed to maintain a constant supply of work.
     133The daemon program
    129134{{{
    130 make_work -wu_name name [-wu_name name2 ... ] -cushion N
     135make_work --wu_name name [--wu_name name2 ... ] --cushion N
    131136}}}
    132 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.
     137does this;
     138it creates copies of the given workunits (cyclically) as needed to maintain a supply of at least N unsent results.
     139Other command-line arguments:
     140 '''--max_wus N''':: exit after creating N workunits
     141 '''--one_pass''':: check if workunits are needed, if so create them, and exit.
    133142
    134 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.
     143Note: if you run the file_deleter and/or db_purge,
     144the master workunit or its input files may be deleted (which will cause make_work to fail).
     145To avoid this, give the master workunit a name that contains 'nodelete' as a substring.
     146This causes the file_deleter and db_purge to skip over it.
    135147
    136 It may be convenient to have a script that recreates the master workunit. For example:
     148It may be convenient to have a script that recreates the master workunit.
     149For example:
    137150{{{
    138151cp test_workunits/12ja04aa `bin/dir_hier_path 12ja04aa`