Changes between Version 22 and Version 23 of JobSubmission


Ignore:
Timestamp:
Oct 22, 2012, 2:43:52 PM (12 years ago)
Author:
davea
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • JobSubmission

    v22 v23  
    44To submit a job you must
    55
    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).
     6 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).
    77 1. "Stage" the job's input file(s) (see below).
    88 1. Invoke a BOINC function or script that submits the job.
     
    2525    <file_info>
    2626        <number>0</number>
     27        [ <gzip/> ]
    2728        [ <sticky/> ]
    2829        [ <no_delete/> ]
     
    6061 '''<file_info>''':: describes an [BoincFiles#Fileproperties input file].
    6162  '''<number>''':: use 0, 1, ...
     63  '''<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.
    6264  '''<sticky/>''':: if present, the file remains on the client after job is finished.
    6365  '''<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.
    64   '''<report_on_rpc/>''':: if present, report file in each scheduler request (sticky files)
     66  '''<report_on_rpc/>''':: if present, report file in each scheduler request (for sticky files)
    6567  '''<url>, <md5_cksum>, <nbytes>''':: used only for "non-local" input files (see below)
    6668
     
    170172
    171173=== Staging local input files ===
    172 Before submitting a job, you must put its local input files
    173 into the proper place in the [ServerDirs download directory hierarchy].
    174 BOINC provides both a command-line tool and a function for this.
    175 The command-line tool is:
    176 {{{
    177 dir_hier_path filename
    178 }}}
    179 which prints the full pathname and creates the directory if needed
    180 (run this in the project's root directory). For example:
     174Before submitting a job, you must '''stage''' its local input files using
     175{{{
     176bin/stage_file [--gzip] [--copy] file
     177}}}
     178 --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).
     179 --copy:: copy the file from its current location to the BOINC download directory.  The default is to move it.
     180
     181Note: '''stage_file''' was added to the BOINC trunk on 16 Oct 2012.
     182If your server code is older than that, use
    181183{{{
    182184cp test_files/12ja04aa `bin/dir_hier_path 12ja04aa`
    183 }}}
    184 copies an input file from the test_files directory to the download directory hierarchy.
    185 
    186 The function (a member function of the {{{SCHED_CONFIG}}} class) is
    187 {{{
    188 // convert filename to path in download hierarchy
    189 //
    190 SCHED_CONFIG::download_path(
    191     const char* filename,    // name of input file
    192     char* path               // path in download hierarchy where it should go
    193 );
    194185}}}
    195186