Changes between Version 22 and Version 23 of JobSubmission

Timestamp:

Oct 22, 2012, 2:43:52 PM (11 years ago)

Author:

davea

Comment:

--

JobSubmission

@@ -4 +4 @@
 To submit a job you must
 
- 1. Write XML 'template files' that describe the job's input and outputs (typically the same template files can be used for many jobs).
+ 1. Write XML 'template files' that describe the job's input and output files (typically the same template files can be used for many jobs).
  1. "Stage" the job's input file(s) (see below).
  1. Invoke a BOINC function or script that submits the job.
@@ -25 +25 @@
     <file_info>
         <number>0</number>
+        [ <gzip/> ]
         [ <sticky/> ]
         [ <no_delete/> ]
@@ -60 +61 @@
  '''<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 (sticky files)
+  '''<report_on_rpc/>''':: if present, report file in each scheduler request (for sticky files)
   '''<url>, <md5_cksum>, <nbytes>''':: used only for "non-local" input files (see below)
 
@@ -170 +172 @@
 
 === Staging local input files ===
-Before submitting a job, you must put its local input files
-into the proper place in the [ServerDirs download directory hierarchy].
-BOINC provides both a command-line tool and a function for this.
-The command-line tool is:
-{{{
-dir_hier_path filename
-}}}
-which prints the full pathname and creates the directory if needed
-(run this in the project's root directory). For example:
+Before submitting a job, you must '''stage''' its local input files using
+{{{
+bin/stage_file [--gzip] [--copy] file
+}}}
+ --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).
+ --copy:: copy the file from its current location to the BOINC download directory.  The default is to move it.
+
+Note: '''stage_file''' was added to the BOINC trunk on 16 Oct 2012.
+If your server code is older than that, use
 {{{
 cp test_files/12ja04aa `bin/dir_hier_path 12ja04aa`
-}}}
-copies an input file from the test_files directory to the download directory hierarchy.
-
-The function (a member function of the {{{SCHED_CONFIG}}} class) is
-{{{
-// convert filename to path in download hierarchy
-//
-SCHED_CONFIG::download_path(
-    const char* filename,    // name of input file
-    char* path               // path in download hierarchy where it should go
-);
 }}}