Changes between Version 1 and Version 2 of CompoundApps

Timestamp:

Apr 25, 2007, 8:55:35 AM (17 years ago)

Author:

Nicolas

Comment:

Required manual changes to automatic conversion.

CompoundApps

@@ -3 +3 @@
 
 == Compound applications ==
-  A '''compound application''' consists of a '''main program''' and one or more '''worker programs'''. The main program executes the worker programs in sequence, and maintains a 'main state file' that records which worker programs have completed. The main program assigns to each worker program a subrange of the overall 'fraction done' range of 0..1. For example, if there are two worker programs with equal runtime, the first would have range 0 to 0.5 and the second would have range 0.5 to 1.   The BOINC API provides a number of functions, and in developing a compound application you must decide whether these functions are to be performed by the main or worker program. The functions are represented by flags in the BOINC_OPTIONS structure. Each flag must be set in either the main or worker programs, but not both.
+A '''compound application''' consists of a '''main program''' and one or more '''worker programs'''. The main program executes the worker programs in sequence, and maintains a 'main state file' that records which worker programs have completed. The main program assigns to each worker program a subrange of the overall 'fraction done' range of 0..1. For example, if there are two worker programs with equal runtime, the first would have range 0 to 0.5 and the second would have range 0.5 to 1.   The BOINC API provides a number of functions, and in developing a compound application you must decide whether these functions are to be performed by the main or worker program. The functions are represented by flags in the BOINC_OPTIONS structure. Each flag must be set in either the main or worker programs, but not both.
 
 
@@ -38 +38 @@
         If set, the CPU of all threads (not just the worker thread)     will be counted.     For apps that do computation in more than one thread.
 
-
 Typical main program logic is:
-
 
 {{{
@@ -64 +62 @@
 boinc_finish()
 }}}
- where x and y are the appropriate fraction done range limits.  Typical worker program logic is:
 
+where x and y are the appropriate fraction done range limits.  Typical worker program logic is:
 
 {{{
@@ -79 +77 @@
 ...
 boinc_finish();        // this writes final CPU time to app_init.xml file
+}}}
 
-}}}
-  If the graphics is handled in a program that runs concurrently with the worker programs, it must also call boinc_init_options(), typically with all options false, then boinc_init_graphics(), and eventually boinc_finish().
+If the graphics is handled in a program that runs concurrently with the worker programs, it must also call boinc_init_options(), typically with all options false, then boinc_init_graphics(), and eventually boinc_finish().
 
 If the main program is responsible for reporting application status to the core client, it should periodically call
-
 
 {{{