Changes between Version 19 and Version 20 of WrapperApp

Timestamp:

Jul 23, 2007, 10:47:01 AM (17 years ago)

Author:

Nicolas

Comment:

--

WrapperApp

@@ -31 +31 @@
 the descriptor specifies the logical names of the files
 to which these are to be connected.
-The descriptor may also specify command-line argments to be passed to the worker program.
+The descriptor may also specify command-line arguments to be passed to the worker program.
 '''wrapper''' itself may be passed command-line arguments (specified in the workunit template);
 these are passed to each of the worker programs after those specified in the job file.
@@ -38 +38 @@
 This is useful for two purposes:
 
- * To handle jobs that involve multiple steps (e.g., preprocessing and postprocessing).
+ * To handle jobs that involve multiple steps (e.g., pre-processing and post-processing).
  * To break a long job up into smaller pieces. This provides a form of checkpointing: ''wrapper'' does checkpointing at the task level, so that lost CPU time is limited even if the legacy applications themselves are not restartable.
 
@@ -44 +44 @@
 
  * The job file can be part of the workunit (e.g. if its command line elements differ between workunits) or the application version (if it's the same between workunits).
- * Files opened directly by a worker program must have the <copy_file/> tag. This requires version 5.5 or higher of the BOINC core client (you can specify this limit at either the [AppVersion application] or [ProjectOptions project] level.
+ * Files opened directly by a worker program must have the <copy_file/> tag. This requires version 5.5 or higher of the BOINC core client (you can specify this limit at either the [AppVersion application] or [ProjectOptions#Clientcontrol project] level.
  * If you run wrapper in standalone mode (while debugging), you must provide input files with the proper logical, not physical, names.