Changes between Version 36 and Version 37 of WrapperApp


Ignore:
Timestamp:
Oct 21, 2010, 3:01:09 PM (14 years ago)
Author:
davea
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • WrapperApp

    v36 v37  
    4949  (specified in the [WorkGeneration#templates input template]);
    5050   these are passed to each worker program after those specified in the job file.
    51  '''weight''':: the contribution of each task to the overall fraction done is proportional to its weight (floating-point, default 1).
    52   For example, if your job has tasks A and B, and A uses 100 times more CPU time than B, set A.weight=100 and B.weight=1.
    53  '''checkpoint_filename''':: the name of the checkpoint file used by the app, if any.
    54   When this is modified, the wrapper assumes that a checkpoint has been completed and notifies the core client.
    55  '''fraction_done_filename''':: the name of a file to which the app will periodically write
    56   its fraction done (0 to 1).
     51 '''weight''':: the contribution of each task to the overall fraction done
     52  is proportional to its weight (floating-point, default 1).
     53  For example, if your job has tasks A and B,
     54  and A uses 100 times more CPU time than B, set A.weight=100 and B.weight=1.
     55 '''checkpoint_filename''':: the name of the checkpoint file used by the app,
     56  if any.
     57  When this is modified, the wrapper assumes that a checkpoint
     58  has been completed and notifies the core client.
     59 '''fraction_done_filename''':: the name of a file to which the app will
     60  periodically write its fraction done (0 to 1).
    5761  This is used by the wrapper to report overall fraction done.
    5862
     
    9094== Example ==
    9195
    92 Here's an example that shows how to use the legacy application mechanism.
    93 We assume that you have already [MakeProject created a project] with root directory PROJECT/.
    94 
    95  * Compile the program 'worker' from [ExampleApps boinc/samples], producing (say) 'worker_5.10_windows_intelx86.exe'. This is the legacy app. It reads from stdin and writes to stdout; it also opens and reads a file 'in', and opens and writes a file 'out'. It takes one command-line argument: the number of CPU seconds to use.
    96  * Compile the program 'wrapper' from [ExampleApps boinc/samples], producing (say) 'wrapper_5.10_windows_intelx86.exe'.
    97  * [AppVersion Create an application] named 'worker' and a corresponding directory 'PROJECT/apps/worker'. In this directory, create a directory 'wrapper_5.10_windows_intelx86.exe'. Put the files 'wrapper_5.10_windows_intelx86.exe', and 'worker_5.10_windows_intelx86.exe' there.  Rename the latter file to 'worker=worker_5.10_windows_intelx86.exe' (this gives it the logical name 'worker').
    98  * In the same directory, create a file 'job.xml=job_1.12.xml' (1.12 is a version number) containing
     96Here's an example that shows how to use the wrapper.
     97We assume that you have already [MakeProject created a project]
     98with root directory PROJECT/,
     99and that you have an executable program for a particular target platform
     100(say "worker_windows_intelx6_0.exe" for Win32)
     101
     102 * Download the wrapper for the target platform (see links above) to your server.
     103 * [AppVersion Create an application] named 'worker' and a corresponding directory
     104  'PROJECT/apps/worker'. In this directory,
     105  create a directory 'wrapper_windows_intelx86_22420.exe'.
     106  Put the files 'wrapper_windows_intelx86_22420.exe',
     107  and 'worker_windows_intelx86_0.exe' there.
     108   Rename the latter file to 'worker=worker_windows_intelx86_0.exe'
     109   (this gives it the logical name 'worker').
     110 * In the same directory, create a file 'job.xml=job_1.12.xml'
     111  (1.12 is a version number) containing
    99112{{{
    100113<job_desc>
     
    202215
    203216
     217