Skip to content

AppVersion

Vitalii Koshura edited this page Jul 15, 2024 · 6 revisions

Applications and app versions

In BOINC terminology, an application is not a single program; it's a set of programs (for different platforms and processor types) that compute the same thing. These individual programs are called app versions.

Jobs are submitted to applications, not app versions. BOINC decides what app version to use when sending a job to a host.

Applications

Applications have the following required properties:

  • Name: A short name (used to name directories, so don't use special characters like /).
  • User friendly name: the name shown to volunteers.

Optional properties:

A project can have many applications. Applications can be created using the xadd utility, based on a description in the project.xml file. Applications can be created or edited using the Manage Applications page of the administrative web interface.

App versions

An app version can consist of multiple files: for example, a controller script, pre- and post-processing programs, and a primary program.

An application version has the following required properties:

  • Version number: an integer. Assign these in increasing order; for a given application and platform, BOINC will use only the app version with the greatest version number.

and the following optional properties:

  • Beta: whether jobs should be sent only to beta-test users.
  • Min and max client version: don't send jobs to clients outside this range. Specified as an integer, encoded as 10000major + 100minor + release.

Application versions are created using update_versions. Descriptions of application versions are stored in the app_version table in the BOINC DB. Application versions can be edited using the Manage Application Versions page of the administrative web interface.

Clone this wiki locally