Description of files included in OpenViBE

  • NB: updated for OpenViBE 1.1.0 (08.oct.2015)

This article contains a short description of all of the files contained in the distribution of the OpenViBE software. For the purpose of this article we will assume that ROOT is the folder where you have installed/unpacked the software.

Windows Installer

Folder structure

Contains all of the binary files necessary to run and use the OpenViBE platform.

This folder contains all dependencies necessary for OpenViBE, their binary and header files.

Files you will need to include to use some of the functions provided by OpenViBE are stored here.

Supporting files are stored here. This folder contains several subfolders worth mentioning.

Positions of electrodes using standard 10–20 system are available here. These are used by some visualisations.

Files, such as textures, 3D models and Gtk UI files are stored in this folder. Each application has its own subfolder.

Scenarios provided by OpenViBE are available here. Demos of BCI implementations as well as tutorials on how to use boxes are provided here. There is also a folder containing some sample signals.

All logs and some configuration files created by OpenViBE applications are stored under this folder. Example: “C:\Users\Joe\AppData\Roaming\openvibe\log” for the log dir on Win7.

Executable files

In the main folder you will find several executable files.

Launches the Acquisition Server.

Launches the OpenViBE designer.

This is a small script used to create IDs for new boxes.

This program generates the previews of the boxes and takes screenshots of them to be used in the documentation. If you develop a new box and you would like to create openvibe-like documentation then you need to run this script before running Doxygen.

A developer tool for creating c++ code skeletons for easier development of new boxes.

A simple game using the SSVEP paradigm. This program is called automatically by the scenarios.

Training application for the SSVEP paradigm, called by the training scenario.

Example implementation of an application using the motor imagery paradigm.

The “Lift the spaceship” demonstrator. Uses scenarios relying on the beta rebound paradigm.

An application made for testing VRPN connections. This application can send a number of button related events to VRPN clients (such as the VRPN Client box).

Source code distribution

The source code distribution contains the source code as well as the necessary scripts to build and run the OpenViBE software, along with some developer utilities.

Files that you would normally find in the installed version of the software can be found in the ROOT/dist folder after a successful compilation.

Folder structure

The source distribution has several differences compared to the binary one.

This folder contains all CMake configuration files.

applications, common, documentation, kernel, modules, openvibe, plugins, toolkit, …
Source code of OpenViBE’s core components.

Parts of OpenViBE contributed by the community.

This folder contains scripts necessary for building OpenViBE. Their functions are described in the following section.

Script files

Most of the files are available with both linux- and win32- prefixes. Files with the same name do the same thing. We will first discuss these files

This scripts builds the OpenViBE platform according to the current settings. Prior to running the script the dependencies have to be installed.

Cleans the build environment. Deletes all of the compiled binary files and the helper files created during the process.

Installs the necessary dependencies needed to run OpenViBE.

Some scripts are only available on one platform.

This file sets up the compilation toolchain and environment variables. Not needed on Linux.

Creates a Visual Studio project which can be opened afterwards in VS. This is done to make developing on Windows easier using an IDE.

Launch Visual Studio IDE with the OpenVIBE solution. You must run win32-generate-vc-proj first.

This entry was posted in Miscellaneous manual pages. Bookmark the permalink.