Changes between Version 2 and Version 3 of JobSubmission

Timestamp:

Sep 22, 2009, 8:56:44 AM (15 years ago)

Author:

davea

Comment:

--

JobSubmission

@@ -9 +9 @@
 
 Once this is done, BOINC takes over: it creates one or more instances of the job,
-distributes them to client hosts, collects the output files,
-finds a canonical instance, assimilates the canonical instance, and deletes files.
+distributes them to client hosts, collects the output files.
+It [ValidateIntro validates] and
+[AssimilateIntro processes] the results,
+and deletes the input and output files.
 
 Typically, steps 2) and 3) are done by a [WorkGeneration work generator] program
@@ -50 +52 @@
 The components are:
 
- <file_info>, <file_ref>::
+ '''<file_info>''':: describes an [BoincFiles#Fileproperties input file].
+ '''<open_name>''':: the physical name of the file.
+ '''<sticky/>''':: if present, the file remains on the client after job is finished.
+ '''<nodelete/>''':: if present, the file is not deleted from the server after job is completed.
+ '''<report_on_rpc/>''':: if present, report file in each scheduler request (sticky files)
 
-        Each pair describes an [BoincFiles#Fileproperties input file] and [BoincFiles#Filereferences the way it's referenced].
+ '''<file_ref>''':: describes [BoincFiles#Filereferences the way the file is referenced].
+ '''<open_name>''':: the logical name of the file
+ '''<copy_file>''':: if present, the file is copied into the job's slot directory
 
- <command_line>::
+ '''<command_line>'''::
 
         The command-line arguments to be passed to the main program.
 
- <credit>::
+ '''<credit>'''::
 
         The amount of credit to be granted for successful completion of this workunit. Use this only if you know in advance how many FLOPs it will take. Your [ValidationSimple validator] must use get_credit_from_wu() as its compute_granted_credit() function.
 
- Other elements::
+ '''<rsc_fpops_est>''' etc.::
         [JobIn Work unit attributes]
 
@@ -85 +93 @@
 
 Elements and tags must be on separate lines as shown.
-Each <file_info>, <file_ref> pair describes an output file.
+'''<file_info>''': describes an output file.
+ <file_ref> pair describes an output file.
 The elements include:
  '''<name>''' and '''<file_name>''':: the physical file name.  Typically use <OUTFILE_0>, <OUTFILE_1> etc.; this will be replaced with a generated name based on the job name.
@@ -181 +190 @@
 Other job parameters may be passed either in the DB_WORKUNIT structure or in the input template file (the latter has priority).
 On a successful return, wu.id contains the database ID of the workunit.
+