Changes between Version 7 and Version 8 of RemoteJob

Timestamp:

Oct 11, 2010, 4:44:07 AM (14 years ago)

Author:

tonig

Comment:

--

RemoteJob

@@ -48 +48 @@
 == Annotating the WU template files ==
 
-Workunit template files should be marked as RBoinc-enabled at the top.
-This marks the template as RBoinc-enabled
-and thus ''scientist-visible'' as an application.
+First, workunit template files should be marked as RBoinc-enabled at the top.
 This is achieved prepending the following tag
 to the relevant workunit template:
@@ -60 +58 @@
 }}}
 
+The above line marks the template as RBoinc-enabled
+and thus ''scientist-visible'' as an application.
 The ''application'' attribute will be the user-visible name of the application
 (which may or may not coincide with BOINC application names).
 The scientist will identify this template
-through the {{{-app }}} command line switch.
+through the {{{-app }}} command line switch on the {{{boinc_submit}}} operation.
 
 
@@ -78 +78 @@
                 parameter_description="Binary velocities"
                 [ optional="true" ]
+                [ immutable="true" ]
+                [ encode="true" ]
                 />
     </file_ref>
@@ -100 +102 @@
 If not, it will be replaced by a (server-supplied) default file.
 
+Likewise, the optional ''immutable'' flag specifies
+that the given file will be replaced by a server-supplied default file,
+and the submitter has no chance to override it.
+
+Finally, if ''encode'' is true, the file is subject to 
+a (server-defined) encoding before being sent. The server will
+store both the original and the encoded version (suffixed with ''_enc'').
 
 
@@ -121 +130 @@
     <url><UPLOAD_URL/></url>
     <gzip_when_done/>
-    <rboinc aliases=".vel" [ chain="3" ]/>
+    <rboinc aliases=".vel" 
+          [ chain="3" ]  />
 </file_info>
 }}}
@@ -129 +139 @@
 that output file should be used as a third input file
 for the next step in the chain.
-The ''aliases'' attribute (currently unimplemented)
-allows automatic renaming upon retrieval. 
+
+The ''aliases'' attribute contains a space-separated list of 
+extensions which are considered when deciding whether a file has been
+already downloaded.  Upon retrieval, files have BOINC-assigned outfile 
+names ending by '_1', '_2', and so on. Upon retrieval, it is
+possible to fix these extension by mass-renaming the retrieved files,
+e.g. ''*_1'' to ''*_1.vel''. If an alias is specified as above,
+files ending with ''_1'' will be considered already
+downloaded if a file  named ''*_1.vel'' is present in the 
+retrieve directory.
 
 For details on the chaining mechanism, please see the paper T. Giorgino, M. J. Harvey and G. De Fabritiis, ''Distributed computing as a virtual supercomputer: Tools to run and manage large-scale BOINC simulations'', Comp. Phys. Commun. 181, 1402 (2010).  [[http://boinc.berkeley.edu/rboinc.pdf pdf]]