You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: development/realtime.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,7 +13,7 @@ This page is part of the documentation series of the FieldTrip buffer for realti
13
13
2. definition of the [buffer protocol](/development/realtime/buffer_protocol),
14
14
3. the [reference implementation](/development/realtime/reference_implementation), and
15
15
4. specific [implementations](/development/realtime/implementation) that interface with acquisition software, or software platforms.
16
-
5. the [getting started](/getting_started/realtime) documentation which takes you through the first steps of real-time data streaming and analysis in MATLAB
16
+
5. the [getting started](/getting_started/realtime/bci) documentation which takes you through the first steps of real-time data streaming and analysis in MATLAB
17
17
18
18
The page [scratchpad](/development/realtime/scratchpad) contains some loose ends that have no clear place.
Copy file name to clipboardExpand all lines: development/realtime/buffer.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,7 +13,7 @@ This page is part of the documentation series of the FieldTrip buffer for realti
13
13
2. definition of the [buffer protocol](/development/realtime/buffer_protocol),
14
14
3. the [reference implementation](/development/realtime/reference_implementation), and
15
15
4. specific [implementations](/development/realtime/implementation) that interface with acquisition software, or software platforms.
16
-
5. the [getting started](/getting_started/realtime) documentation which takes you through the first steps of real-time data streaming and analysis in MATLAB
16
+
5. the [getting started](/getting_started/realtime/bci) documentation which takes you through the first steps of real-time data streaming and analysis in MATLAB
17
17
18
18
This page documents the general concept behind the FieldTrip buffer.
Copy file name to clipboardExpand all lines: development/realtime/buffer_protocol.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,7 +11,7 @@ This page is part of the documentation series of the FieldTrip buffer for realti
11
11
2. definition of the [buffer protocol](/development/realtime/buffer_protocol),
12
12
3. the [reference implementation](/development/realtime/reference_implementation), and
13
13
4. specific [implementations](/development/realtime/implementation) that interface with acquisition software, or software platforms.
14
-
5. the [getting started](/getting_started/realtime) documentation which takes you through the first steps of real-time data streaming and analysis in MATLAB
14
+
5. the [getting started](/getting_started/realtime/bci) documentation which takes you through the first steps of real-time data streaming and analysis in MATLAB
15
15
16
16
This page provides a formal description of how the communication over the network is performed between the FieldTrip buffer server and clients.
Copy file name to clipboardExpand all lines: development/realtime/closing_the_loop.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ tags: [realtime]
7
7
8
8
To close the loop in your BCI application, you have to communicate the control signal from the application/computer that does the feature extraction and feature translation to the application that is controlled by the BCI system. The application that is controlled by the BCI signal can be anything from a generic stimulus presentation software (e.g., NeuroBS Presentation, ERTS, ANT EEvoke, ...) to a spelling device or to custom-built hardware device (e.g., robot arm).
9
9
10
-
Before you attempt to close the loop, please make sure that the data is streaming properly and that you are able to process it fast enough. Some examples are given in the [getting started](/getting_started/realtime) section.
10
+
Before you attempt to close the loop, please make sure that the data is streaming properly and that you are able to process it fast enough. Some examples are given in the [getting started](/getting_started/realtime/bci) section.
Copy file name to clipboardExpand all lines: development/realtime/implementation.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,7 +11,7 @@ This page is part of the documentation series of the FieldTrip buffer for realti
11
11
2. definition of the [buffer protocol](/development/realtime/buffer_protocol),
12
12
3. the [reference implementation](/development/realtime/reference_implementation), and
13
13
4. specific [implementations](/development/realtime/implementation) that interface with acquisition software, or software platforms.
14
-
5. the [getting started](/getting_started/realtime) documentation which takes you through the first steps of real-time data streaming and analysis in MATLAB
14
+
5. the [getting started](/getting_started/realtime/bci) documentation which takes you through the first steps of real-time data streaming and analysis in MATLAB
15
15
16
16
This page deals with specific implemenations of the FieldTrip buffer protocol. This includes interfacing with specific hardware (e.g., TMSi, Biosemi, CTF, Unicorn), software platforms (e.g., BCI2000, BrainStream) and links to the implementation in specific programming languages (e.g., MATLAB, Java, C/C++, Python).
17
17
@@ -31,7 +31,7 @@ This page deals with specific implemenations of the FieldTrip buffer protocol. T
@@ -48,11 +48,11 @@ This page deals with specific implemenations of the FieldTrip buffer protocol. T
48
48
## Additional useful tools
49
49
50
50
-[viewer](/development/realtime/viewer) is a graphical C++ application to visualize online signals from the FieldTrip buffer
51
-
-[serial_event](/development/realtime/serial_event) is a C application that turns incoming characters from a serial port into FieldTrip buffer events (used for translating TTL pulses in [realtime fMRI](/getting_started/realtime_fmri))
51
+
-[serial_event](/development/realtime/serial_event) is a C application that turns incoming characters from a serial port into FieldTrip buffer events (used for translating TTL pulses in [realtime fMRI](/getting_started/realtime/fmri))
52
52
-[buffer_java#MidiToBuffer](/development/realtime/buffer_java#MidiToBuffer) is a Java application that turns MIDI messages into FieldTrip buffer events
53
53
-[buffer_java#MarkerGUI](/development/realtime/buffer_java#MarkerGUI) is a graphical Java application that allows to write FieldTrip buffer events with a freely chosen _type_ and _value_ string.
54
54
-[Testing with sine waves and pre-recorded EEG data](/development/realtime/eeg)
55
-
-[Testing with pre-recorded fMRI data](/getting_started/realtime_fmri#testing_with_pre-recorded_fmri_data)
55
+
-[Testing with pre-recorded fMRI data](/getting_started/realtime/fmri#testing_with_pre-recorded_fmri_data)
Copy file name to clipboardExpand all lines: development/realtime/neuromag.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,7 @@ Volume 2011) in any work that uses it.
10
10
11
11
The rtMEG software relays signals from a 306-channel Neuromag/Elekta/Megin MEG device in real-time to a FieldTrip buffer. This buffer can then be read by any computer in the same network as the computer hosting the buffer. The data is still stored by the Acquisition computer (i.e. where you run the Acquisition software by Neuromag) as a FIF file, and it can be read by as many computers in the network as necessary. The rtMEG software has the capability of running the FieldTrip buffer by itself, or it can output the data to a separate computer hosting the buffer when necessary. The delay introduced by the software to the data being relayed has been measured to be smaller than 50ms, which is sufficient for most real-time studies.
12
12
13
-
For more information on how to read from a FieldTrip buffer, please check [here](/development/realtime) for a collection of technical documents or the [getting started section](/getting_started/realtime).
13
+
For more information on how to read from a FieldTrip buffer, please check [here](/development/realtime) for a collection of technical documents or the [getting started section](/getting_started/realtime/bci).
Copy file name to clipboardExpand all lines: development/realtime/reference_implementation.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,7 +11,7 @@ This page is part of the documentation series of the FieldTrip buffer for realti
11
11
2. definition of the [buffer protocol](/development/realtime/buffer_protocol),
12
12
3. the [reference implementation](/development/realtime/reference_implementation), and
13
13
4. specific [implementations](/development/realtime/implementation) that interface with acquisition software, or software platforms.
14
-
5. the [getting started](/getting_started/realtime) documentation which takes you through the first steps of real-time data streaming and analysis in MATLAB
14
+
5. the [getting started](/getting_started/realtime/bci) documentation which takes you through the first steps of real-time data streaming and analysis in MATLAB
15
15
16
16
This page deals with the cross-platform reference implementation in C.
Copy file name to clipboardExpand all lines: development/realtime/scratchpad.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ This page contains some loose ends and random pieces that don't fit elsewhere.
9
9
10
10
-[closing the loop](/development/realtime/closing_the_loop) lists some methods for interacting with, and controlling the external world (i.e. outside the analysis computer)
11
11
-[pipeline](/development/realtime/pipeline) contains example fMRI pipeline description
12
-
-[Siemens fMRI](/getting_started/realtime_fmri) also contains some fMRI details
12
+
-[Siemens fMRI](/getting_started/realtime/fmri) also contains some fMRI details
Copy file name to clipboardExpand all lines: development/realtime/serial_event.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ This page describes the tool **serial2event**, which is located in the directory
9
9
The user has the option to either only react on specific characters, and to write events with
10
10
a fixed _type_ and _value_, or to forward the received character as the _value_ of the event.
11
11
The _sample_ field of the event can be auto-incremented, and reset by sending the string "RESET"
12
-
to the UDP port (default = 1990) on which the tool listens. The latter feature is used in the DCCN's MRI lab to reset the sample counter when a new sequence is started on the scanner host (which is then picked up by the [fMRI gui_streamer](/getting_started/realtime_fmri) tool).
12
+
to the UDP port (default = 1990) on which the tool listens. The latter feature is used in the DCCN's MRI lab to reset the sample counter when a new sequence is started on the scanner host (which is then picked up by the [fMRI gui_streamer](/getting_started/realtime/fmri) tool).
13
13
14
14
The tool is started from the command line by typing
0 commit comments