BCI2000 Wiki - Recent changes [en]

User Tutorial:BCI2000 Tour

2013-06-18T17:02:12Z

Programming Reference:Building Qt for BCI2000

2013-06-17T16:57:26Z

‎Build and copy mingw libraries and auxiliary files:

Contributions:StatisticsFilter

2013-06-14T20:08:57Z

‎Weight function:

Programming Reference:Building Qt for BCI2000

2013-06-14T18:36:42Z

‎Build and copy MSVC libraries and auxiliary files:

@@ Line 70: / Line 70: @@
 ==Stimulus Presentation==
 In addition to the cursor feedback paradigm, BCI2000 comes with a multi-purpose [[User Reference:StimulusPresentationTask|Stimulus Presentation]] module.
-This module has many of the features of dedicated programs like [http://www.neurobs.com/presentation Presentation] or [http://www.pstnet.com/products/e-prime/ e-Prime]. In BCI research, the BCI2000 StimulusPresentation module is often used for  [[User Tutorial:Obtaining Mu Rhythm Parameters in an Initial Session|an initial Mu rhythm session]]. Still, it has very good [[User Reference:Timing|timing precision]], and thus makes its use suitable for a wide range of psychophysiological experiments such as the ERP experiments described  [[User Tutorial:Introduction to the P300 Response|here]]. In addition, it can be used in conjunction with the P3SignalProcessing module (which can average and classify ERPs) to provide real-time feedback to evoked potentials.
+This module is able to deliver visual and auditory stimuli in user-defined or pseudo-random sequences, and may respond to input from external devices. Thus, in many situations, it omits the need for dedicated programs like [http://www.neurobs.com/presentation Presentation] or [http://www.pstnet.com/products/e-prime/ e-Prime]. In BCI research, the BCI2000 StimulusPresentation module is often used for  [[User Tutorial:Obtaining Mu Rhythm Parameters in an Initial Session|an initial Mu rhythm session]]. Still, it has very good [[User Reference:Timing|timing precision]], and thus makes its use suitable for a wide range of psychophysiological experiments such as the ERP experiments described  [[User Tutorial:Introduction to the P300 Response|here]]. In addition, it can be used in conjunction with the P3SignalProcessing module (which can average and classify ERPs) to provide real-time feedback to evoked potentials.
 To try the stimulus presentation module, start BCI2000 using the <tt>batch/StimulusPresentation_SignalGenerator.bat</tt> batch file.

@@ Line 76: / Line 76: @@
   -no-style-cde
 The full command line is:
-  configure -platform win32-g++ -static -no-sql-sqlite -no-qt3support -fast -qt-zlib-qt-libpng -qt-libmng -no-libtiff -no-libjpeg -no-phonon -no-webkit -no-scripttools -no-style-plastique -no-style-motif -no-style-cde
+  configure -platform win32-g++ -static -no-sql-sqlite -no-qt3support -fast -qt-zlib -qt-libpng -qt-libmng -no-libtiff -no-libjpeg -no-phonon -no-webkit -no-scripttools -no-style-plastique -no-style-motif -no-style-cde
 *When prompted for the type of license, choose "Open Source", and answer "yes" when asked whether you accept the terms of the license.
 *If you have previously done a full build, open a console window, and run <tt>mingw32-make</tt> in the following directories:
@@ Line 123: / Line 123: @@
 *Likewise, copy the <tt>QtCore</tt>, <tt>QtGui</tt>, <tt>QtOpenGL</tt> include directories to <tt>qt-x.y.z/include</tt>, omitting the respective <tt>private</tt> directories.
-==Remove debugging information from MSVC libraries==
+==Hide debugging information in MSVC libraries==
 *Despite current MSVC compilers store debugging information in .pdb files, .lib files still contain traditional debugging information. In addition, .lib debugging information refers to .pdb files, and the MSVC linker will issue a large number of warnings if it cannot find those .pdb files.
-*Basically, we can use the GNU objcopy tool in order to strip debugging information from MSVC .lib files. Due to nonstandard behavior of MSVC, it is necessary to do some fixup before and after running objdump on an MSVC-generated .lib file.
+*Basically, we might use GNU binutils, which are able to handle COFF binaries, in order to strip debugging information from those libraries. However, it seems that MSVC compilers store information in such a way that it is not possible to remove arbitrary sections without breaking the files. Thus, we keep all sections but change names of debugging sections such that the MSVC linker will not be able to identify them as such. While this has the disadvantage of retaining large file sizes, it still provides the benefit of fast linking, and suppression of linker warnings.
-*In cygwin, go to <tt>build/buildutils</tt>, and run
+*To hide debugging information, open a cygwin shell, and cd to the qt lib directory that contains MSVC libraries. There, execute
- g++ fixup_msvc_lib.cpp -o fixup_msvc_lib
+  /full/path/to/build/buildutils/strip_msvc_lib.sh *
- g++ coff_set_debug.cpp -o coff_set_debug
-*Then, go to the qt lib directory that contains the MSVC libraries to be stripped, and execute
-  /path/to/build/buildutils/strip_msvc_lib.sh *
-*To strip 64-bit libraries, you will need to have the cygwin-64-bit-toolchain installed, and to add -64 as a first argument to the script:
- /path/to/build/buildutils/strip_msvc_lib.sh -64 *
 ==Upload Qt to the BCI2000 server==

@@ Line 12: / Line 12: @@
 *Tested under: 4151
 *Known to compile under: 4164
 ==Functional Description==
@@ Line 67: / Line 121: @@
 =====obs.CentralMoment(n)=====
 The n-th central moment for each dimension of observer "obs".
-=====obs.Quantile(0>=p>=1)=====
+=====obs.Quantile(p)=====
-The value corresponding to the the given relative frequency in each dimension of observer "obs".
+The value corresponding to the the given relative frequency p in each dimension of observer "obs". p is restricted by <math>0\leq p \leq 1</math>.
 =====obs.QQuantiles(n)=====
 For each dimension of observer "obs", a vector of values corresponding to the n-th q-quantile. This vector has n+1 entries, with the minimum in the first entry, and the maximum in the last entry.

@@ Line 8: / Line 8: @@
 *Open the file <tt>qt/mkspecs/win32-msvc2008/qmake.conf</tt> in a text editor. <!--Add <tt>-Fd$(DESTDIR)$(QMAKE_TARGET).pdb</tt> as a compiler option to  <tt>QMAKE_CFLAGS_DEBUG</tt>.--> In <tt>QMAKE_CFLAGS_RELEASE</tt> and <tt>QMAKE_CFLAGS_DEBUG</tt>, replace the <tt>-MD</tt> and <tt>-MDd</tt> with <tt>-MT</tt> and  <tt>-MTd</tt>, respectively.
 <!--*To optimize for size rather than speed, replace the <tt>-O2</tt> option in <tt>QMAKE_CFLAGS_RELEASE</tt> with <tt>-O1</tt>.-->
 *Open the VS2008 console window from the start menu, and from the Qt installation's <tt>qt</tt> directory, run <tt>configure</tt> with the following options:
   -platform win32-msvc2008