Changes between Version 38 and Version 39 of WrapperApp

Timestamp:

Feb 19, 2011, 11:27:52 PM (14 years ago)

Author:

carlgt1

Comment:

--

WrapperApp

@@ -35 +35 @@
         [ <checkpoint_filename>filename</checkpoint_filename> ]
         [ <fraction_done_filename>filename</fraction_done_filename> ]
-        [ <exec_dir>directory to start the application (relative or use $PROJECT_DIR macro)</exec_dir> ]
-        [ <setenv>environment variable in the form of LD_LIBRARY_PATH=$PROJECT_DIR:$LD_LIBRARY_PATH (i.e. VARNAME=VAR_VALUE)</setenv> ]
-        [ <setenv>you can have more than one setenv entry as needed by your application</setenv> ]
+        [ <exec_dir>dirname</exec_dir> ]
+        [ <setenv>VARNAME=VAR_VALUE</setenv> ]
         [ <fraction_done_filename>filename</fraction_done_filename> ]
     </task>
@@ -43 +42 @@
 </job_desc>
 }}} 
-
+ 
 The job file describes a sequence of tasks.
 The descriptor for each task includes:
@@ -64 +63 @@
   periodically write its fraction done (0 to 1).
   This is used by the wrapper to report overall fraction done.
+""exec_dir"":: The directory to start the application (relative to slot, or use $PROJECT_DIR macro)
+""setenv"":: Environmental variable needed for the applications run-time environment - you can have more than one <setenv> entry, use the VARNAME=VAR_VALUE form, e.g. LD_LIBRARY_PATH=$PROJECT_DIR:$LD_LIBRARY_PATH
+
 
 The job file can specify multiple tasks.
@@ -77 +79 @@
  * Worker programs must exit with zero status; nonzero values are interpreted as errors by the wrapper.
  * If you run '''wrapper''' in standalone mode (while debugging), you must provide input files with the proper logical, not physical, names.
+ * job.xml may be different for different platforms (i.e. app_versions) due to diretory requirements (exec_dir) and environment variables (setenv)
 
 == Physical file management ==