SignalPlant: an open signal processing software platform

SignalPlant is designed to work with several data formats; a generally known subset is shown in table 1. Hierarchical Data Format (HDF5) (The HDF Group 1997) was chosen as the preferred format to store data from SignalPlant. It is also possible to load Matlab files, though Matlab^® must be installed on the target computer for this functionality. The widely-used European Data Format (EDF) (Kemp and Olivan 2015) is also supported. EDF supports the use of different sampling frequencies for single channels which is not allowed by SignalPlant. When such a situation occurs, all channels are up-sampled to the highest sampling frequency.

For publishing purposes, the lossless PNG (Randers-Pehrson and Boutell 1999) format is used for exporting displayed signals. A useful feature is export screen to vector graphic formats such as 'Scalable Vector Graphics' (SVG) (W3C World Wide Web Consortium 2011) and Adobe^® 'Encapsulated PostScript' (EPS) (Adobe 1992).

An important feature is the fact that third parties can extend input/output (I/O) capabilities to any other format. Samples on the project website contain a plugin source code for *.csv I/O operations.

When a record is loaded into SignalPlant, each signal is held in one instance of special object (graph panel—GP) responsible for displaying. When data is modified (e.g. using some filter), the new layer of the signal is added to the parent GP, meaning the ability of non-destructive editing. Any number of such layers can be added, limited only by the available memory. The user can choose which layer of each signal is to be displayed. This feature allows the user to (for example) apply several different filters to the source signal and quickly see the differences. An editable list of signal layers holds information about these layers, such as creation time and creation plugin name (e.g. FIR LP) and settings (e.g. cut-off frequency and order).

Another part of the data structure is a list of marks (i.e. labels). These may be used, for example, for triggering in EEG, as QRS annotation marks in ECG, or as artifact labels. They may be created manually by the user or may be produced automatically by plugins. These marks have several properties (such as 'Info', 'Group', 'Validity', etc) and may have both left and right borders defined. This allows marks to be used for interval selection (e.g. artifact selection in EEG). Marks can be both imported and exported as a text file (with the *.sel extension). This means, for example, that QRS marks detected by SignalPlant can be transferred to another piece of software.

A major requirement for SignalPlant was a fast inspection of large recordings. Therefore, an agile navigation in data is important. SignalPlant allows several navigation methods using mouse in display area (figure 1(A)), mouse in navigation bar (figure 1(C)) or keyboard (all navigation options are described in SignalPlant manual). Here, we were partially inspired by navigation control used in music recording/production software such as Tracktion (Loud Technologies 2007) and Cubase (Steinberg Media Technologies 2016), where the user may navigate in the data using only a mouse (mouse movements or mouse wheel plus the Shift and Control keys). This approach tends to be more user-friendly than the approach used in EEGLAB, RASCHLab, SigViewer or Physionet LightWave (Goldberger et al 2000), where the user has to click through the menu(s) or repetitively use GUI buttons or sliders to zoom in on a specific detail and back out again. On the other hand, an agile mouse or touch oriented control requires an effective display engine.

In SignalPlant (using the default display plugin), each channel (i.e. signal) is drawn independently of the others and runs its own asynchronous thread (figure 2). When a zoom/pan operation or data update calls for a display refresh, each thread is activated and its priority reconsidered (visible channels on the screen have the highest priority). Next, the minimum and maximum values in the corresponding signal interval are found for each displayed sample on the screen. For long records, precomputed minimum and maximum values are used. Once the arrays of minimal and maximal values (at the physical length of the graph in pixels on the screen) are found, graph redrawing is launched and the asynchronous thread is set back to idle status. Graph redrawing is performed on the main GUI thread, though this consists (mostly) of the quick drawing of minimal and maximal value lines and the filling of the inner area. The channel closest to the mouse or touch pointer is favored over the others and is processed first with the highest priority. This provides the feeling of live navigation in the data.

Zoom In Zoom Out Reset image size

SignalPlant is extendable by plugins which can be written by third parties. Plugins can be used to increase post-processing functionality (to implement new detection methods, filters, etc), as well as to adapt I/O capabilities to new file formats. Furthermore, plugins can also be used to replace a default display engine without any changes to the application core. They must be compiled in the form of a dynamic-linked library (DLL).

Plugins usually run in a separate window (figure 3) and allow a real-time preview. The ability to save presets is essential for productive work, especially when plugins offer a large number of settings. Presets are available (if this is allowed by the developer of the plugin) from the plugin window main menu (figure 3—left). They are stored in XML form and can, therefore, be easily transferred between users.

Zoom In Zoom Out Reset image size

SignalPlant allows one to do specific tasks with a subset of loaded data (e.g. filtering of specific channels only). We equipped SignalPlant with several ways to select specific channels or marks.

When the user needs to select channels to display or to link them to a plugin, this can be performed with common drag & drop operation. It is, however, useful in some cases (such as EEG records with 100–200 channels) to select channels by an expression that can be written in the text field at the top of the channel list (figure 1(B)) or inside the form for channel selection.

Marks querying is useful when the user needs to work with specific marks only. As marks may have multiple properties defined, they can be used for querying as in figure 3 with the MultiSketch plugin, where only QRS complexes of a specific morphology group were used for image generation. The expression for marks querying is set in the specific window (figure 4) showing the location of the resultant marks (figure 4(B)) based on the current expression (figure 4(A)). Another example of marks querying is shown in supplement S7 (stacks.iop.org/PM/37/N38/mmedia).

Zoom In Zoom Out Reset image size

SignalPlant allows the use of simple scripts for the automation of repetitive tasks or for batch processing of multiple records. Using scripts, it is possible to launch a sequence of commands defined by plugins.

• Operating system: 64-bit Windows^® 7 or newer with .NET framework 4.5 or newer
• Multi-core CPU
• Enough memory (due to parallelism and non-destructive processing capabilities)
• Mouse or touch screen preferred

The software is available free at https://signalplant.codeplex.com along with sample ECG files and documentation. SignalPlant is available under an MIT license. Because one of SignalPlant's features is plugin extendability, the source code of a sample I/O plugin (for *.csv import and export) and Visual Studio template (for plugin with GUI) are also available for download.

The current software version (1.2.1.20) does not use any installator. The archive from the project website should be unpacked and is prepared for execution. Simple and quick registration is required when the software is executed for the first time.

The standard plugin set offers 30 plugins with GUI (for filtering, analysis, detection, maintenance, etc) and 12 plugins for file-format extensions. A list of current plugins is available in S1 of the supplementary data (stacks.iop.org/PM/37/N38/mmedia).

SignalPlant functionality can be extended by new plugins, written in C# and compiled into DLL. Each DLL may contain multiple plugins as is the case with the standard plugin set. New plugins are loaded during SignalPlant initialization and they can be executed from the 'Plugins' folder. The project website contains source codes for several plugins.

SignalPlant is accompanied by a help file describing the deployment process and program elements, as well as the basic plugin set. Short tutorial movies are also available from the project website at https://signalplant.codeplex.com.

Although SignalPlant was developed primarily for work with biological signals, and first and foremost for EEG and ECG processing, other signal types may also be processed. This applies, for example, to the time-frequency analysis of sound recordings (S3 of the supplementary data (stacks.iop.org/PM/37/N38/mmedia)) or statistical analysis of cryogenic experiments (S6 of the supplementary data (stacks.iop.org/PM/37/N38/mmedia)). The availability of a specific I/O plugin may prove a limitation. In the case of biological signals, the BIOSIG project (Vidaurre et al 2011) may be used for data conversion to, for example, the EDF format. Otherwise, the *.CSV format may be used, though this is not recommended due to its text-based nature leading to excessive data consumption with large files. Another limitation is the need for a fixed sampling frequency for all signals in a record, as well as all signals being of the same length.

The number of channels and layers in SignalPlant is limited only by the available memory (technically, the maximal numbers of channels as well as maximal number of layers in each channel is 2146 435 071 (Microsoft 2016b)). Because SignalPlant is a 64-bit application, it can allocate a maximum of 8 GB–4 TB of memory depending on the OS version (Microsoft 2016a). SignalPlant uses 32-bit floating point datatype to store signal values and, therefore, each signal layer is limited to hold 2146 435 071 (Microsoft 2016b) samples. SignalPlant loads all data into the memory, which is one of the conditions for fast display refresh. Data miniatures are precomputed, consuming additional memory. Therefore, our approach consumes a slightly larger amount of memory than the real size of the data (in case of HDF5 files). As an example, a record with 30 channels and 32-bit quantization, 25 kHz sampling rate, 40 min long is saved in a non-compressed HDF5 file of a size of 7.14 GB. After loading and the precomputing of miniatures, the memory consumed by SignalPlant is 7.7 GB of RAM. If the user merely investigates this record, no other memory will be allocated, though if the user decides to filter all signals, a larger amount of memory will be allocated during multi-thread filtering (the exact amount is dependent on available system resources and is driven by the .NET framework). When the filtering process ends and .NET framework clears unused memory blocks allocated during processing, the amount of memory consumed by SignalPlant is 15.37 GB. This number reflects the fact that each channel now contains an additional layer with a filtered signal.

In case of loading EDF files, users should expect that the amount of requested memory will be higher than the file size. It is caused by use of a 32-bit floating point datatype (while EDF is usually 16-bit), request of constant sampling frequency over all channels (while signals in EDF may differ in sampling) and some amount of memory needed for data miniature. As an example, a Physionet (Goldberger et al 2000) MIMIC II (Saeed et al 2011) record 's32701-3247-02-13-00-43' downloaded as a 2.11 GB EDF file will consume 4.56 GB of RAM (4.33 GB for data and 240 MB for data miniatures and SignalPlant data structure). However, when the amount of available memory is an issue, the user can select which signals and which data area will be loaded from the EDF record into SignalPlant.