Page History: LSL Event Marker Element
Compare Page Revisions
Page Revision: 2018/08/02 23:28
Summary
|
LSL Event Marker
|
Info |
Category: |
Communication |
|
AddIn: |
Signal Processing |
Creator: |
OkazoLab |
|
Scope: |
Parent event |
Owns Snippets: |
None |
|
Usage: |
Snippets |
Properties
Name | Description | Constraints | Type | On runtime change |
---|
LSL Settings |
Stream Type | Defines a type of the LSL stream. Arbitrary type names can be defined, but some software may require the 'Markers' type, in order to process event markers correctly | | String | |
Stream Name | Defines which LSL stream will be connected at runtime. You must have the LSL stream running, when you change this property for the first time. Note that the channel configuration of the element is updated each time as you change this property | | String | |
Marker Type | Define a sample type of the event marker. | | Int32 | |
Working Mode | Define a working mode for the element. | | Int32 | |
Runtime Control |
Marker Value | Defines a value that will be sent as event marker, The value type must match or be convertible to the chosen marker type | | String | |
Send Marker Now | Runtime action that instantly sends an event marker with the current marker value. You have to invoke this action in snippets by 'SendMarkerNow=true;', if the element works in the manual mode. | | Boolean | |
Control |
Is Enabled | If set to false the element is completely omitted when the experiment is run | | Boolean | |
Title | Title of the element | | String | |
|
LSL Event Marker Element allows sending 'event' markers to external applications via a single-channel LSL stream.
Description
...
Snapshots
Snapshot 1
| Snapshot 2 |
Practical Use
...
Technique 1
- Step 1
- Step 2
...
=== Technique 2 === - Step 1
- Step 2
...
// Check the trial outcome. Result and RT just other user variables
// insert code snippet here..
...
== Notes ==
... - Insert Notes here..
- Insert Notes here..