Changes between Version 5 and Version 6 of WorkGeneration


Ignore:
Timestamp:
Apr 18, 2007, 4:39:00 PM (17 years ago)
Author:
davea
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • WorkGeneration

    v5 v6  
    44To submit a job:
    55
    6     * Write XML 'template files' that describe the job's input and outputs (typically the same template files will be used for many jobs).
     6    * Write XML 'template files' that describe the job's input and outputs (typically the same template files can be used for many jobs).
    77    * Create the job's input file(s), and put them in the right places in the [http://boinc.berkeley.edu/hier_dir.php download directory hierarchy].
    88    * Invoke a BOINC function or script that submits the job.
    … …  
    5858        [http://boinc.berkeley.edu/work.php Work unit attributes]
    5959
    60 Workunit database records include a field, 'xml_doc', that is an XML-format description of the workunit's input files. This is derived from the workunit template as follows:
    61 
    62     * Within a <file_info> element, <number>x</number> identifies the order of the file. It is replaced with elements giving the filename, download URL, MD5 checksum, and size.
    63     * Within a <file_ref> element, <file_number>x</file_number> is replaced with an element giving the filename.
    64 
    6560An output template file has the form
    6661{{{
    … …  
    7974</result>
    8075}}}
    81 Result database records include a field, 'xml_doc_in', that is an XML-format description of the result's output files. This is derived from the result template as follows:
    82 
    83     * <OUTFILE_n> is replaced with a string of the form 'wuname_resultnum_n' where wuname is the workunit name and resultnum is the ordinal number of the result (0, 1, ...).
    84     * <UPLOAD_URL/> is replaced with the upload URL.
    8576
    8677== Submitting a job manually ==
    8778
     79To move an input file to the download directory, use
    8880{{{
    8981dir_hier_path filename
    9082}}}
    91 It prints the full pathname and creates the directory if needed. Run this in the project's root directory. For example:
    92 {{{
    93 cp test_workunits/12ja04aa `bin/dir_hier_path 12ja04aa`
    94 }}}
    95 copies an input file from the test_workunits directory to the download directory hierarchy.
    96 
    97 The utility program is
    98 {{{
    99 create_work
    100     -appname name                       // application name
    101     -wu_name name                       // workunit name
    102     -wu_template filename               // WU template filename
    103         // relative to project root; usually in templates/
    104     -result_template filename           // result template filename
    105         // relative to project root; usually in templates/
    106     [ -batch n ]
    107     [ -priority n ]
    108 
    109     // The following may be passed in the WU template,
    110     // or as command-line arguments to create_work,
    111     // or not passed at all (defaults will be used)
    112 
    113     [ -command_line "-flags foo" ]
    114     [ -rsc_fpops_est x ]
    115     [ -rsc_fpops_bound x ]
    116     [ -rsc_memory_bound x ]
    117     [ -rsc_disk_bound x ]
    118     [ -delay_bound x ]
    119     [ -min_quorum x ]
    120     [ -target_nresults x ]
    121     [ -max_error_results x ]
    122     [ -max_total_results x ]
    123     [ -max_success_results x ]
    124     [ -additional_xml 'x' ]
    125 
    126     infile_1 ... infile_m           // input files
    127 }}}
     83This prints the full pathname and creates the directory if needed. Run this in the project's root directory. For example:
     84{{{
     85cp test_files/12ja04aa `bin/dir_hier_path 12ja04aa`
     86}}}
     87copies an input file from the test_files directory to the download directory hierarchy.
     88
     89To submit a job, run the program
     90{{{
     91create_work [ arguments] infile_1 ... infile_n
     92}}}
     93Mandatory argumens are:
     94    -appname name::
     95  application name
     96    -wu_name name::
     97        workunit name
     98    -wu_template filename::           
     99 WU template filename relative to project root; usually in templates/
     100    -result_template filename::
     101          result template filename, relative to project root; usually in templates/
     102Optional arguments are:
     103    -batch n::
     104    -priority n::
     105
     106The following may be passed in the WU template,
     107or as command-line arguments to create_work,
     108or not passed at all (defaults will be used)
     109
     110    -command_line "-flags foo"::
     111    -rsc_fpops_est x::
     112    -rsc_fpops_bound x::
     113    -rsc_memory_bound x::
     114    -rsc_disk_bound x::
     115    -delay_bound x::
     116    -min_quorum x::
     117    -target_nresults x::
     118    -max_error_results x::
     119    -max_total_results x::
     120    -max_success_results x::
     121    -additional_xml 'x'::
     122
    128123The program must be run in the project root directory. The workunit parameters are documented [http://boinc.berkeley.edu/work.php here]. The -additional_xml argument can be used to supply, for example, <credit>12.4</credit>.
    129124