Changes between Version 4 and Version 5 of JobTemplates

Timestamp:

Mar 26, 2014, 3:14:55 PM (11 years ago)

Author:

davea

Comment:

--

JobTemplates

@@ -47 +47 @@
 }}}
 Elements and tags must be on separate lines as shown.
-The components are:
 
- '''<file_info>''':: describes an [BoincFiles#Fileproperties input file].
-  '''<number>''':: use 0, 1, ...
-  '''<gzip/>''':: transfer the file in gzipped (compressed) format to reduce network usage.  '''You must stage the file with the --gzip option (see below)'''.  Only 7.0+ clients can handle compressed transfers; older clients will get the file in uncompressed form.
-  '''<sticky/>''':: if present, the file remains on the client after job is finished.
-  '''<no_delete/>''':: if present, the file is not deleted from the server after job is completed.  Use this if the file is used as input to more than one job.
-  '''<report_on_rpc/>''':: if present, report file in each scheduler request (for sticky files).
+Each '''<file_info>''' describes an [BoincFiles#Fileproperties input file]:
+
+ '''<number>''':: use 0, 1, ...
+ '''<gzip/>''':: transfer the file in gzipped (compressed) format to reduce network usage.
+   You must [JobStage stage the file with the --gzip option].
+   Only 7.0+ clients can handle compressed transfers;
+   older clients will download the file in uncompressed form.
+ '''<sticky/>''':: if present, the file remains on the client after job is finished.
+ '''<no_delete/>''':: if present, the file is not deleted from the server after job is completed.  Use this if the file is used as input to more than one job.
+ '''<report_on_rpc/>''':: if present, report file in each scheduler request (for sticky files).
    Include this for compatibility with old (pre-7.x) clients; 7.0+ clients report all sticky files.
-  '''<url>, <md5_cksum>, <nbytes>''':: Use these for files that are [JobStage staged] to
-   a server (or servers) other than your BOINC server.
-   Each '''<url>''' element specifies a directory (i.e. it should end with a /) to which the file name will
+
+The following are used for files that are [JobStage staged] to
+a server (or servers) other than your BOINC server:
+
+ '''<url>''':: specifies a directory (i.e. it should end with a /) to which the file name will
    be appended to give the URL.
-   You must provide the MD5 checksum and size of the file.
+   If the file is replicated, you can supply more than one.
+ '''<md5_cksum>''':: the file's MD5 checksum
+ '''<nbytes>''':: the file size.
+ '''<gzipped_nbytes>''': if '''<gzip/>''' is specified, the size of the gzip file.
 
- '''<file_ref>''':: describes [BoincFiles#Filereferences the way the file is referenced].
-  '''<file_number>''':: 0, 1, etc.
-  '''<open_name>''':: the logical name of the file
-  '''<copy_file>''':: if present, the file is copied into the job's slot directory
+The '''<file_ref>''' describes [BoincFiles#Filereferences the way the file is referenced]:
+ '''<file_number>''':: 0, 1, etc.
+ '''<open_name>''':: the [BoincFiles logical name] of the file
+ '''<copy_file>''':: if present, the file is copied into the job's slot directory
 
+The job parameters include:
  '''<command_line>''':: The command-line arguments to be passed to the main program.
   Note: if you're using the [WrapperApp BOINC wrapper],
@@ -123 +132 @@
 
  '''<file_ref>''':: describes how an output file will be referenced by the application.
- '''<open_name>''':: the "logical name" by which the application will reference the file.
+ '''<open_name>''':: the [BoincFiles logical name] by which the application will reference the file.
  '''<copy_file/>''':: if present, the file will be generated in the slot directory,
    and copied to the project directory after the job has finished.