Changes between Version 19 and Version 20 of WorkGeneration
- Timestamp:
- Oct 10, 2007, 8:20:00 AM (17 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
WorkGeneration
v19 v20 10 10 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. 11 11 12 == Input and output template files == 12 == Input and output template files == #templates 13 13 14 14 An input template file has the form … … 88 88 You can safely remove a workunit template file after creating your last WU with it. However, you can't delete a result template file until any WU that refers to it is completed (i.e. no more replicas will be created). 89 89 90 == Submitting a job manually == 90 == Submitting a job manually == #creatework-tool 91 91 92 92 To move an input file to the download directory, use … … 135 135 This can be used to supply, for example, <credit>12.4</credit>. 136 136 137 == Submitting jobs from a C++ program == 137 == Submitting jobs from a C++ program == #cpp-workgen 138 138 139 139 BOINC's library provides the functions: … … 163 163 Other job parameters may be passed either in the DB_WORKUNIT structure or in the input template file (the latter has priority). 164 164 165 === Making one workunit === 165 === Making one workunit === #cpp-one 166 166 167 167 Here's a program that submits one job (error-checking is omitted for clarity): … … 217 217 The program must be run in the project directory. 218 218 219 === Making lots of workunits === 219 === Making lots of workunits === #cpp-lots 220 220 221 221 If you're making lots of workunits (e.g. to do the various parts of a parallel computation) you'll want the workunits to differ either in their input files, their command-line arguments, or both. … … 266 266 Again, you only need one input template file and one output template file. 267 267 268 == Example work generators == 268 == Example work generators == #examples 269 269 270 270 Two work generator programs are supplied with BOINC. 271 271 272 === Sample work generator === 272 === Sample work generator === #examples-sample 273 273 Many projects have an essentially infinite supply of work. 274 274 This can be handled by a 'flow-controlled work generator' … … 280 280 You can easily modify this program to suit your application. 281 281 282 === make_work === 282 === make_work === #examples-makework 283 283 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 284 284 {{{
