3 | | Input files may be "local" (resident on the project server) or "non-local". |
4 | | For local files, BOINC fills in the download URL, the file size, and the MD5. |
5 | | For non-local files, you must supply these yourself in the input template. |
6 | | You can supply multiple URLs if the file is on multiple data servers. |
| 3 | Before using an input file you must "stage" it, |
| 4 | i.e. put it where it is accessible via HTTP from volunteer computers. |
| 5 | The default way to do this is to store it on your BOINC server, |
| 6 | in your project's '''download''' directory hierarchy. |
| 7 | To do this, run |
| 8 | {{{ |
| 9 | bin/stage_file [--gzip] [--copy] file_path |
| 10 | }}} |
| 11 | --gzip:: send the file in compressed form to 7.0+ clients. Note: you must also include the '''<gzip/>''' attribute for this file in the job's [JobTemplates input template]. |
| 12 | --copy:: copy the file from its current location to the BOINC download directory. The default is to move it. |
8 | | == Staging local input files == |
9 | | Before submitting a job, you must '''stage''' its local input files using |
10 | | {{{ |
11 | | bin/stage_file [--gzip] [--copy] file |
12 | | }}} |
13 | | --gzip:: send the file in compressed form to 7.0+ clients. Note: you must also include the '''<gzip/>''' attribute for this file in the job's input template (see above). |
14 | | --copy:: copy the file from its current location to the BOINC download directory. The default is to move it. |
| 14 | '''stage_file''' also |
| 15 | * checks whether a file of that name already exists in the download hierarchy. |
| 16 | If so, it verifies that the file has the same contents. |
| 17 | * computes and saves the file's MD5 hash. |
| 18 | This eliminates the need to do this each time a job submission refers to the file. |