Difference between revisions of "Setup EEG amplifier plugins in MNE Scan"
(→Available amplifier plugins in MNE Scan) |
|||
| Line 9: | Line 9: | ||
== Structure of an acquisition plugin == | == Structure of an acquisition plugin == | ||
| − | The following flow sheet describes the structure of the | + | The acquisition plugins of MNE Scan have similiar structure and therefore can be explained on the basis of the gUSBamp EEG driver example. The following flow sheet describes the structure of the acquisition plugin. |
[[File:Structure_gUSBampAcquisition.png|center|900px|thumb| Flow sheet of the gUSBamp acquisition plugin]] | [[File:Structure_gUSBampAcquisition.png|center|900px|thumb| Flow sheet of the gUSBamp acquisition plugin]] | ||
| + | |||
| + | On the left side the border of MNE Scan can be seen, whereas on the right side the border to the actual device, in this case the gUSBamp amplifier, is depicted. In between, according to their hierarchical order, the three main classes are depicted as the interface between program and device: | ||
| + | |||
| + | # '''gUSBamp''': regulates the communication between MNE Scan and the driver and acts as the main-class. | ||
| + | # '''gUSBampproducer''': controls the data acquisition and manages the interface between driver and gUSBamp | ||
| + | # '''gUSBampdriver''': actual driver which provides data acquisition and controls the communication between the project and the device | ||
| + | |||
| + | However, gUSBampdriver is the actual class, communicating and exchanging data with the device. The gUSBamp and gUSBampproducer classes can be seen as a way, how to integrate the gUSBampdriver class properly into the project. | ||
| + | |||
| + | When establishing a new plugin to the plugin-box like shown in the [[gUSBAmp]] example, all three classes are initialized. | ||
Revision as of 04:01, 11 November 2016
Available amplifier plugins in MNE Scan
Following driver setup tutorials are offered for MNE Scan:
EEGoSports, TMSI Refa, gUSBAmp and BrainAmp
Structure of an acquisition plugin
The acquisition plugins of MNE Scan have similiar structure and therefore can be explained on the basis of the gUSBamp EEG driver example. The following flow sheet describes the structure of the acquisition plugin.
On the left side the border of MNE Scan can be seen, whereas on the right side the border to the actual device, in this case the gUSBamp amplifier, is depicted. In between, according to their hierarchical order, the three main classes are depicted as the interface between program and device:
- gUSBamp: regulates the communication between MNE Scan and the driver and acts as the main-class.
- gUSBampproducer: controls the data acquisition and manages the interface between driver and gUSBamp
- gUSBampdriver: actual driver which provides data acquisition and controls the communication between the project and the device
However, gUSBampdriver is the actual class, communicating and exchanging data with the device. The gUSBamp and gUSBampproducer classes can be seen as a way, how to integrate the gUSBampdriver class properly into the project.
When establishing a new plugin to the plugin-box like shown in the gUSBAmp example, all three classes are initialized.
