6 | | * Write XML 'template files' that describe the job's input and outputs (typically the same template files can be used for many jobs). |
7 | | * Create the job's input file(s), and put them in the right places (as determined by the file names) in the [DirHierarchy download directory hierarchy]. |
8 | | * Invoke a BOINC function or script that submits the job. |
9 | | |
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. |
| 6 | 1. Write XML 'template files' that describe the job's input and outputs (typically the same template files can be used for many jobs). |
| 7 | 1. Create the job's input file(s), and put them in the right place (as determined by the file name) in the [DirHierarchy download directory hierarchy]. |
| 8 | 1. Invoke a BOINC function or script that submits the job. |
| 9 | |
| 10 | Once this is done, BOINC takes over: it creates one or more instances of the job, |
| 11 | distributes them to client hosts, collects the output files, |
| 12 | finds a canonical instance, assimilates the canonical instance, and deletes files. |
| 13 | |
| 14 | Typically, steps 2) and 3) are done by a '''work generator''' program |
| 15 | that creates lots of jobs. |