Changes between Initial Version and Version 1 of BasicApi

Timestamp:

Apr 19, 2007, 9:55:57 PM (17 years ago)

Author:

KSMarksPsych

Comment:

--

BasicApi

@@ +1 @@
+= The BOINC application programming interface (API) =
+        
+
+The BOINC API is a set of C++ functions. Most of the functions have a C interface, so that they can be used from programs written in C and other languages. Unless otherwise specified, the functions return an integer error code; zero indicates success.
+
+BOINC applications may generate graphics, allowing them to provide a screensaver. This API is described [GraphicsApi here].
+
+BOINC applications may consist of several programs that are executed in sequence; these are called compound applications. This API is described [http://boinc.berkeley.edu/compound_app.php here].
+
+== Initialization and termination ==
+
+Applications should [http://boinc.berkeley.edu/diagnostics.php initialize diagnostics] before any other BOINC calls.
+
+Initialization for graphical and compound applications are described elsewhere (see links above). Other applications must call
+
+{{{
+int boinc_init();
+}}}
+
+before calling other BOINC functions or doing I/O.
+
+When the application has completed it must call
+
+{{{
+int boinc_finish(int status);
+}}}
+
+`status` is nonzero if an error was encountered. This call does not return.
+
+== Is your application running under the control of the BOINC client? ==
+
+BOINC applications can be run in "standalone" mode for testing, or under the control of the BOINC client. You might want your application to behave differently in the two cases. For example you might want to output debugging information if the application is running standalone. To determine if the application is running in standalone mode or under the control of the BOINC client, call
+
+{{{
+int boinc_is_standalone(void);
+}}}
+
+This returns non-zero (True) if the application is running standalone, and zero (False) if the application is running under the control of the BOINC client.
+
+== Resolving file names ==
+
+Applications that use named input or output files must call
+
+{{{
+int boinc_resolve_filename(char *logical_name, char *physical_name, int len);
+}}}
+
+or
+
+{{{
+int boinc_resolve_filename_s(char *logical_name, std::string& physical_name);
+}}}
+
+to convert logical file names to physical names. For example, instead of
+
+{{{
+f = fopen("my_file", "r");
+}}}
+
+the application might use
+
+{{{
+string resolved_name;
+retval = boinc_resolve_filename("my_file", resolved_name);
+if (retval) fail("can't resolve filename");
+f = fopen(resolved_name.c_str(), "r");
+}}}
+
+`boinc_resolve_filename()` doesn't need to be used for temporary files.
+
+== I/O wrappers ==
+
+Applications should replace fopen() calls with
+
+{{{
+boinc_fopen(char* path, char* mode);
+}}}
+
+This deals with platform-specific problems. On Windows, where security and indexing programs can briefly lock files, boinc_fopen() does several retries at 1-second intervals. On Unix, where signals can cause fopen() to fail with EINTR, boinc_fopen checks for this and does a few retries; it also sets the 'close-on-exec' flag.
+
+== Checkpointing ==
+
+Computations that use a significant amount of time per work unit may want to periodically write the current state of the computation to disk. This is known as '''checkpointing'''. The state file must include everything required to start the computation again at the same place it was checkpointed. On startup, the application reads the state file to determine where to begin computation. If the BOINC client quits or exits, the computation can be restarted from the most recent checkpoint.
+
+Frequency of checkpointing is a user preference (e.g. laptop users might want to checkpoint infrequently). An application must call
+
+{{{
+int boinc_time_to_checkpoint();
+}}}
+
+whenever it reaches a point where it is able to checkpoint. If this returns nonzero (True) then the application should checkpoint immediately (i.e., write the state file and flush all output files), then call
+
+{{{
+void boinc_checkpoint_completed();
+}}}
+
+`boinc_time_to_checkpoint()` is fast, so it can be called frequently (hundreds or thousands of times a second).
+
+== Critical sections ==
+
+{{{
+void boinc_begin_critical_section();
+void boinc_end_critical_section();
+}}}
+
+Call these around code segments during which you don't want to be suspended or killed by the core client. NOTE: this is done automatically while checkpointing.
+
+== Atomic file update ==
+
+To facilitate atomic checkpoint, an application can write to output and state files using the MFILE class.
+
+{{{
+class MFILE {
+public:
+    int open(char* path, char* mode);
+    int _putchar(char);
+    int puts(char*);
+    int printf(char* format, ...);
+    size_t write(const void* buf, size_t size, size_t nitems);
+    int close();
+    int flush();
+};
+}}}
+
+MFILE buffers data in memory and writes to disk only on `flush()` or `close()`. This lets you write output files and state files more or less atomically.
+
+== Credit reporting ==
+
+By default, the claimed credit of a result is based on the product of its total CPU time and the benchmark values obtained by the core client. This can produce results that are too low if the application uses processor-specific optimizations not present in the core client, is compiled with different compiler settings, or uses a GPU or other non-CPU computing resource. To handle such cases, the following functions can be used.
+
+{{{
+void boinc_ops_per_cpu_second(double floating_point_ops, double integer_ops);
+}}}
+
+This reports the results of an application-specific benchmark, expressed as number of floating-point and integer operations per CPU second.
+
+{{{
+void boinc_ops_cumulative(double floating_point_ops, double integer_ops);
+}}}
+
+This reports the total number of floating-point and integer operations since the start of the result. It must be called just before boinc_finish(), and optionally at intermediate points.
+
+== Communicating with the core client ==
+
+The core client GUI displays the percent done of workunits in progress. To keep this display current, an application should periodically call
+
+{{{
+boinc_fraction_done(double fraction_done);
+}}}
+
+The `fraction_done` argument is an estimate of the workunit fraction complete (0 to 1). This function is fast and can be called frequently. The sequence of arguments in successive calls should be non-decreasing. An application should never 'reset' and start over if an error occurs; it should exit with an error code.
+
+{{{
+double boinc_get_fraction_done();
+}}}
+
+returns the last value set, or -1 if none has been set (this would typically be called from graphics code).
+
+The following functions get information from the core client; this information may be useful for graphics.
+
+{{{
+int boinc_get_init_data_p(APP_INIT_DATA*);
+int boinc_get_init_data(APP_INIT_DATA&);
+
+struct APP_INIT_DATA {
+    int major_version;
+    int minor_version;
+    int release;
+    int app_version;
+    char app_name[256];
+    char symstore[256];
+    char acct_mgr_url[256];
+    char* project_preferences;
+    int userid;
+    int teamid;
+    int hostid;
+    char user_name[256];
+    char team_name[256];
+    char project_dir[256];
+    char boinc_dir[256];
+    char wu_name[256];
+    char authenticator[256];
+    int slot;
+    double user_total_credit;
+    double user_expavg_credit;
+    double host_total_credit;
+    double host_expavg_credit;
+    double resource_share_fraction;
+    HOST_INFO host_info;
+    PROXY_INFO proxy_info;  // in case app wants to use network
+    GLOBAL_PREFS global_prefs;
+
+    // info about the WU
+    double rsc_fpops_est;
+    double rsc_fpops_bound;
+    double rsc_memory_bound;
+    double rsc_disk_bound;
+
+    // the following are used for compound apps,
+    // where each stage of the computation is a fixed
+    // fraction of the total.
+    double fraction_done_start;
+    double fraction_done_end;
+};
+}}}
+
+to get the following information:
+
+||'''core version'''||The version number of the core client||
+||'''app_name'''||The application name (from the server's DB||
+||'''project_preferences'''||An XML string containing the user's project-specific preferences.||
+||'''user_name'''||The user's 'screen name' on this project.||
+||'''team_name'''||The user's team name, if any.||
+||'''project_dir'''||Absolute path of project directory||
+||'''boinc_dir'''||Absolute path of BOINC root directory||
+||'''wu_name'''||Name of workunit being processed||
+||'''authenticator'''||User's authenticator for this project||
+||'''slot'''||The number of the app's 'slot' (0, 1, ...)||
+||'''user_total_credit'''||User's total work for this project.||
+||'''user_expavg_credit'''||User's recent average work per day.||
+||'''team_total_credit'''||Team's total work for this project.||
+||'''team_expavg_credit'''||Team's recent average work per day.||
+||'''host_info'''||A structure describing the host hardware and OS||
+
+An application may call
+
+{{{
+int boinc_wu_cpu_time(double &cpu_time);
+}}}
+
+to get its total CPU time (from the beginning of the work unit, not just since the last restart). This excludes CPU time used to render graphics.
+
+== Requesting network connection ==
+
+If it appears that there is no physical network connection (e.g. gethostbyname() fails for a valid name) then
+
+    * Call `boinc_need_network()`. This will alert the user that a network connection is needed.
+    * Periodically call boinc_network_poll() until it returns zero.
+    * Do whatever communication is needed.
+    * When done, call `boinc_network_done()`. This enables that hangup of a modem connection, if needed. 
+
+{{{
+void boinc_need_network();
+int boinc_network_poll();
+void boinc_network_done();
+}}}
+
+Note: this should be enclosed in `boinc_not_using_cpu() ... boinc_using_cpu()`.