Changes

Jump to navigation Jump to search
no edit summary
Line 4: Line 4:  
__TOC__
 
__TOC__
   −
== 6.1. Options for debugging ==
+
== Options for debugging ==
 
There are different ways to [[BrainStreamGlossary|debug]] your BCI application:
 
There are different ways to [[BrainStreamGlossary|debug]] your BCI application:
   Line 135: Line 135:     
===== How does !Brainstream deliver the data? =====
 
===== How does !Brainstream deliver the data? =====
Only when a [[BrainStreamGlossary|marker]] is associated with data (see xxx) and a timepoint t=DATA, it will get the data along with the [[BrainStreamGlossary|event]] structure, that is: <tt>event.data.raw</tt> (channels x data).
+
Only when a [[BrainStreamGlossary|marker]] is associated with data (see xxx) and a timepoint t=DATA, it will get the data along with the [[BrainStreamGlossary|event]] structure, that is: <tt>event.data.raw</tt> (channels x data).
    
===== Does BrainStream provide any standard data processing solutions? =====
 
===== Does BrainStream provide any standard data processing solutions? =====
The only supported data processing option available is [[BrainStreamGlossary|decimation]] of the data. In the block file it can be specified which decimation factor should apply to the data (topic: RunMode, key: SampleRateAfterDecimation). In fact it is specified what the sample rate should be after decimation. BrainStream verifies if the data acquisitions' sample rate allows for decimation of the data (decimation factor should be a power of 2).
+
The only supported data processing option available is [[BrainStreamGlossary|decimation]] of the data. In the block file it can be specified which decimation factor should apply to the data (topic: RunMode, key: SampleRateAfterDecimation). In fact it is specified what the sample rate should be after decimation. BrainStream verifies if the data acquisitions' sample rate allows for decimation of the data (decimation factor should be a power of 2).
    
=== Block files ===
 
=== Block files ===
Line 149: Line 149:     
===== Why is the connect_brainstream_client function not connecting? =====
 
===== Why is the connect_brainstream_client function not connecting? =====
A number of actions can be taken to solve this problem. First, check the addresses or ip-addresses used. If you are trying to connect a brainstream client, it must be identified in the blockfile under the [Clients] section. Make sure it is there, and if it is, make sure the dns-name or ip-address in the blockfile matches that of the computer you are running connect_brainstream_client on. Also make sure the dns-name or ip-address you are using in the connect_brainstream_client call matches that of the machine where brainstream is running on. Second, check if there is a firewall active on the machine that is running brainstream. If there is a firewall active, make sure that ports 5001 till 5020 are open, so the client can actually connect to brainstream. You could also try to only start connecting the brainstream client after Brainstream indicates that it is listening for incoming connections.
+
A number of actions can be taken to solve this problem. First, check the addresses or ip-addresses used. If you are trying to connect a brainstream client, it must be identified in the blockfile under the [Clients] section. Make sure it is there, and if it is, make sure the dns-name or ip-address in the blockfile matches that of the computer you are running connect_brainstream_client on. Also make sure the dns-name or ip-address you are using in the connect_brainstream_client call matches that of the machine where brainstream is running on. Second, check if there is a firewall active on the machine that is running brainstream. If there is a firewall active, make sure that ports 5001 till 5020 are open, so the client can actually connect to brainstream. You could also try to only start connecting the brainstream client after Brainstream indicates that it is listening for incoming connections.
    
=== Slicing ===
 
=== Slicing ===

Navigation menu