Changes between Version 7 and Version 8 of WorkGeneration

Timestamp:

Apr 18, 2007, 4:57:59 PM (17 years ago)

Author:

davea

Comment:

--

WorkGeneration

@@ -9 +9 @@
 
 Once this is done, BOINC takes over: it creates one or more instances of the job, distributes them to client hosts, collects the output files, finds a canonical instance, assimilates the canonical instance, and deletes files.
-
-During the testing phase of a project, you can use the [http://boinc.berkeley.edu/busy_work.php make_work daemon] to replicate a given workunit as needed to maintain a constant supply of work. This is useful while testing and debugging the application.
 
 == Input and output template files ==
@@ -218 +216 @@
             wu,
             wu_template,
-            "templates/results_template.xml",
-            "templates/results_template.xml",
+            "templates/output_template.xml",
+            "templates/output_template.xml",
             infiles,
             1,
@@ -237 +235 @@
             wu,
             wu_template,
-            "templates/results_template.xml",
-            "templates/results_template.xml",
+            "templates/output_template.xml",
+            "templates/output_template.xml",
             infiles,
             1,
@@ -246 +244 @@
     }
 }}}
-Again, you only need one input template file and one output template file. 
+Again, you only need one input template file and one output template file.
+
+== Sample work generators ==
+
+Two example work generators are supplied with BOINC.
+
+=== make_work ===
+During the testing phase of a project, you can use the [http://boinc.berkeley.edu/busy_work.php make_work daemon] to replicate a given workunit as needed to maintain a constant supply of work. 
+
+=== Sample work generator ===
+Many projects have an essentially infinite supply of work.
+This can be handled by a 'flow-controlled work generator'
+that tries to maintain a constant number of unsent jobs
+(typically a few hundred or thousand).
+It does this by periodically querying the BOINC database
+to find the number of unsent jobs.
+An example of this is sched/sample_work_generator.C.
+You can easily modify this program to suit your appliation.