1,658
edits
Changes
Jump to navigation
Jump to search
Line 2:
Line 2: − + Line 10:
Line 10: − + + − + Line 31:
Line 32: − + Line 44:
Line 45: − + − + Line 61:
Line 62: + − + − + Line 76:
Line 78: − + − + − + Line 91:
Line 93: − + − + − +
BrainStreamExampleSpellerPart1 (view source)
Revision as of 16:05, 26 September 2018
, 16:05, 26 September 2018→Evaluation of the speller
= Part 1 =
= Part 1 =
[[BrainStreamExampleSpellerIntro <-|Go back to the introduction]] - [[BrainStreamExampleSpellerPart2|Continue with Part 2 ->]]
[[BrainStreamExampleSpellerIntro|<- Go back to the introduction]] - [[BrainStreamExampleSpellerPart2|Continue with Part 2 ->]]
This example can be found in the folder <tt>brainstream/examples/blocks/visual_speller1</tt>.
This example can be found in the folder <tt>brainstream/examples/blocks/visual_speller1</tt>.
Below, the experiment is shown in the [[BrainStreamBrainStreamEditor|BrainStream editor]].
Below, the experiment is shown in the [[BrainStreamBrainStreamEditor|BrainStream editor]].
[[File:DocsSectionsExampleSpellerPart1.BS_editor.png|838px|471x]]
[[File:DocsSectionsExampleSpellerPart1_BS_editor.png|838px|471x]]
''Figure 1: Visual speller in the BrainStream Editor''
''Figure 1: Visual speller in the BrainStream Editor''
As explained in the [[BrainStreamExampleSpellerIntro#SecExperiment|introduction]] to this example, the experiment consists of three parts: train, classify and test. In the Block files section of the BrainStream editor, you can see that a [[BrainStreamBuildingExperiments#SecBlock|block file]] has been created for each part of the experiment. In addition, there are two common block files which define settings that are applied to all blocks. In the Tables section, you can see that there is an [[BrainStreamBuildingExperiments#SecExpDef|experiment definition table]] for each of the blocks, and one common table that is used in all blocks.
As explained in the [[BrainStreamExampleSpellerIntro#SecExperiment|introduction]] to this example, the experiment consists of three parts: train, classify and test. In the Block files section of the BrainStream editor, you can see that a [[BrainStreamBuildingExperiments#SecBlock|block file]] has been created for each part of the experiment. In addition, there are two common block files which define settings that are applied to all blocks. In the Tables section, you can see that there is an [[BrainStreamBuildingExperiments#SecExpDef|experiment definition table]] for each of the blocks, and one common table that is used in all blocks.
== Train block flowchart ==
== Train block flowchart ==
Below, a flowchart of the Train block is shown:
Below, a flowchart of the Train block is shown:
[[File:DocsSectionsExampleSpellerPart1.flowchart.png|656px|261x]]
[[File:DocsSectionsExampleSpellerPart1_Flowchart.png|656px|261x]]
''Figure 1: Flowchart''
''Figure 1: Flowchart''
A [[BrainStreamPlugIns|imported] table (StimDisplay in speller_common) is used to define all actions related to stimulus presentation. You can see the reference to this imported table in the 9th row of the main Actions table: '@speller_common.edt StimDisplay'. The imported table is shown below:
A [[BrainStreamPlugIns|imported] table (StimDisplay in speller_common) is used to define all actions related to stimulus presentation. You can see the reference to this imported table in the 9th row of the main Actions table: '@speller_common.edt StimDisplay'. The imported table is shown below:
[[File:DocsSectionsExampleSpellerPart1.speller_common_actions_2.png|832px|167x]]
[[File:DocsSectionsExampleSpellerPart1_Speller_common_actions_2.png|832px|167x]]
''Figure 2: StimDisplay imported table.''
''Figure 2: StimDisplay imported table.''
| stimSequence || several repetitions of highlighting all rows (1-3) and columns (4-6) || 231546 132654 312645 ...
| stimSequence || several repetitions of highlighting all rows (1-3) and columns (4-6) || 231546 132654 312645 ...
|-
|-
| stimDict || <p>dictionary: translates stimulus numbers to grids with ones for <br />highlighted elements and zeros for non highlighted elements</p> || [[File:DocsSectionsExampleSpellerPart1_stimDict.png|225px|61x]]
| stimDict || <p>dictionary: translates stimulus numbers to grids with ones for <br />highlighted elements and zeros for non highlighted elements</p> || [[File:DocsSectionsExampleSpellerPart1_StimDict.png|225px|61x]]
|-
|-
| stimCode || current stimulus number || 3
| stimCode || current stimulus number || 3
|-
|-
| curStim || <p>current stimulus grid (ones for highlighted elements and <br />zeros for non highlighted elements)</p> || [[File:DocsSectionsExampleSpellerPart1_curStim.png|78px|66x]]
| curStim || <p>current stimulus grid (ones for highlighted elements and <br />zeros for non highlighted elements)</p> || [[File:DocsSectionsExampleSpellerPart1_CurStim.png|78px|66x]]
|}
|}
When the sequence is initialized, the epoch counter is increased by 1 and the speller grid is shown. Immediately afterwards, the highlightGrid function is executed. This function determines the number of the current stimulus (stimCode) and the corresponding grid (curStim), displays the correct image on the screen and inserts the marker highlightOn. After 0.05 seconds, the non-highlighted grid is shown. Another 0.05 seconds later, a decision is made whether to show another stimulus or end the sequence.
When the sequence is initialized, the epoch counter is increased by 1 and the speller grid is shown. Immediately afterwards, the highlightGrid function is executed. This function determines the number of the current stimulus (stimCode) and the corresponding grid (curStim), displays the correct image on the screen and inserts the marker highlightOn. After 0.05 seconds, the non-highlighted grid is shown. Another 0.05 seconds later, a decision is made whether to show another stimulus or end the sequence.
== Data selection ==
== Data selection ==
As explained in the introduction, the visual speller is based on the brain response to the flashing rows and columns. Therefore, we need to collect a certain amount of data after each flash. The highlightGrid function (see the [[#StimPres|Stimulus presentation section]]), inserts a marker highlightOn each time a row or column of the grid is highlighted. As we need accurate synchronization with the data, this marker is inserted [[BrainStreamMarkerHandling#HardwareMarker|via the hardware]]. Data selection is specified for the highlightOn marker in the speller_common import-table. This is the import-tables' [[BrainStreamBuildingExperiments#SecDataSel|DataSelection table]:
As explained in the introduction, the visual speller is based on the brain response to the flashing rows and columns. Therefore, we need to collect a certain amount of data after each flash. The highlightGrid function (see the [[#StimPres|Stimulus presentation section]]), inserts a marker highlightOn each time a row or column of the grid is highlighted. As we need accurate synchronization with the data, this marker is inserted [[BrainStreamMarkerHandling#HardwareMarker|via the hardware]]. Data selection is specified for the highlightOn marker in the speller_common import-table. This is the import-tables' [[BrainStreamBuildingExperiments#SecDataSel|DataSelection table]]:
[[File:DocsSectionsExampleSpellerPart1.speller_common_data.png|456px|53x]]
[[File:DocsSectionsExampleSpellerPart1_Speller_common_data.png|456px|53x]]
''Figure 4: DataSelection table''
''Figure 4: DataSelection table''
Each time a row or column of the grid was highlighted, the highlightOn marker was inserted. Thus, in the log file we can look up what the time between two successive highlightOn markers was. These are the first three highlightOn markers:
Each time a row or column of the grid was highlighted, the highlightOn marker was inserted. Thus, in the log file we can look up what the time between two successive highlightOn markers was. These are the first three highlightOn markers:
<pre>18Nov11|14:39:43.559 INFO > '''***''' ( highlightOn) '''*************************************************************'''
<pre>18Nov11|14:39:43.559 INFO > ***** ( highlightOn) *************************************************************
18Nov11|14:39:43.559 INFO > 17.10 (eeg:#2972.00) 17.10 17.29 act: getvar (t=EVENT) highlightOn
18Nov11|14:39:43.559 INFO > 17.10 (eeg:#2972.00) 17.10 17.29 act: getvar (t=EVENT) highlightOn
.
.
.
.
18Nov11|14:39:43.682 INFO > '''***''' ( highlightOn) '''*************************************************************'''
18Nov11|14:39:43.682 INFO > ***** ( highlightOn) *************************************************************
18Nov11|14:39:43.683 INFO > 17.23 (eeg:#3007.00) 17.23 17.42 act: getvar (t=EVENT) highlightOn
18Nov11|14:39:43.683 INFO > 17.23 (eeg:#3007.00) 17.23 17.42 act: getvar (t=EVENT) highlightOn
.
.
.
.
18Nov11|14:39:43.897 INFO > '''***''' ( highlightOn) '''*************************************************************'''
18Nov11|14:39:43.897 INFO > ***** ( highlightOn) *************************************************************
18Nov11|14:39:43.897 INFO > 17.36 (eeg:#3039.00) 17.36 17.63 act: getvar (t=EVENT) highlightOn
18Nov11|14:39:43.897 INFO > 17.36 (eeg:#3039.00) 17.36 17.63 act: getvar (t=EVENT) highlightOn
</pre>
</pre>
These are the last three highlightOn markers:
These are the last three highlightOn markers:
<pre>18Nov11|14:40:25.825 INFO > '''***''' ( highlightOn) '''*************************************************************'''
<pre>18Nov11|14:40:25.825 INFO > ***** ( highlightOn) *************************************************************
18Nov11|14:40:25.825 INFO > 58.80 (eeg:#13647.00) 58.80 59.56 act: getvar (t=EVENT) highlightOn
18Nov11|14:40:25.825 INFO > 58.80 (eeg:#13647.00) 58.80 59.56 act: getvar (t=EVENT) highlightOn
.
.
.
.
18Nov11|14:40:25.835 INFO > '''***''' ( highlightOn) '''*************************************************************'''
18Nov11|14:40:25.835 INFO > ***** ( highlightOn) *************************************************************
18Nov11|14:40:25.835 INFO > 58.96 (eeg:#13688.00) 58.96 59.57 act: getvar (t=EVENT) highlightOn
18Nov11|14:40:25.835 INFO > 58.96 (eeg:#13688.00) 58.96 59.57 act: getvar (t=EVENT) highlightOn
.
.
.
.
18Nov11|14:40:25.844 INFO > '''***''' ( highlightOn) '''*************************************************************'''
18Nov11|14:40:25.844 INFO > ***** ( highlightOn) *************************************************************
18Nov11|14:40:25.845 INFO > 59.12 (eeg:#13730.00) 59.12 59.58 act: getvar (t=EVENT) highlightOn </pre>
18Nov11|14:40:25.845 INFO > 59.12 (eeg:#13730.00) 59.12 59.58 act: getvar (t=EVENT) highlightOn </pre>