Changes between Version 96 and Version 97 of WrapperApp

Timestamp:

Mar 22, 2016, 1:56:27 AM (9 years ago)

Author:

Christian Beer

Comment:

added documentation to features from PR#1508

WrapperApp

@@ -59 +59 @@
     </zip_output>
     ]
+    [
+    <rename_output>
+        <filename>foo</filename>
+    </rename_output> 
+    ]
 </job_desc>
 }}} 
@@ -72 +77 @@
  * $NTHREADS is replaced with the number of CPUs the client is allocating for this job.
  * $GPU_DEVICE_NUM is replaced with the device number of the GPU allocated to this job.
- * $PROJECT_DIR is replaced with the path of the project directory.
+ * $PROJECT_DIR is replaced with the absolute path of the project directory.
+ * $PWD is replaced with the absolute path of the current working directory.
+ * boinc_resolve(foo) is replaced with the return value of boinc_resolve_filename(foo) which eliminates the need to use the <copy_file/> attribute for foo.
  '''weight''':: the contribution of each task to the overall fraction done
   is proportional to its weight (floating-point, default 1).
@@ -124 +131 @@
     the wrapper will zip output files (specified by one or more regular expressions) into a zip file with the given name.
 
+The wrapper can optionally rename output files:
+ '''rename_output''':: for this to work, a result file with <open_name>foo.link</open_name> has to be specified in the result template.
+    After all tasks are completed, a file "foo" created by the application will be moved to become the result file, without using additional disk space or copy time.
+    Note: The link name to be specified in the result template is hardcoded right now but this may change in a future version.
+
 Notes:
  * One or more of the tasks may be [AppMultiThread multi-threaded] and/or [AppCoprocessor use GPUs].