Export Connectivity Results - Revision history

Olga at 07:40, 26 May 2023

2023-05-26T07:40:47Z

Mateusz at 14:42, 5 May 2021

2021-05-05T14:42:31Z

Mateusz at 14:41, 5 May 2021

2021-05-05T14:41:48Z

Robert at 07:41, 5 May 2021

2021-05-05T07:41:17Z

Robert at 11:07, 2 February 2021

2021-02-02T11:07:54Z

Robert at 20:35, 12 October 2020

2020-10-12T20:35:01Z

Robert at 13:36, 27 June 2018

2018-06-27T13:36:36Z

Robert: Created page with "{{BESAInfobox |title = Module information |module = BESA Connectivity |version = 1.0 or higher (BC) }} BESA Connectivity provides export of connectivity results via the menu..."

2018-06-27T13:31:43Z

Created page with "{{BESAInfobox |title = Module information |module = BESA Connectivity |version = 1.0 or higher (BC) }} BESA Connectivity provides export of connectivity results via the menu..."

New page

{{BESAInfobox
|title = Module information
|module = BESA Connectivity
|version = 1.0 or higher (BC)
}}

BESA Connectivity provides export of connectivity results via the menu entry ''Export'' → ''Export Results'' → ''Export Connectivity Data''. This option will export the entire connectivity matrix (for all latencies and frequencies) of the currently selected connectivity method, time-frequency decomposition method and condition.

[[File:BESA Connectivity Selected Connectivity and Time-Frequency Methods.png]]

The connectivity matrix is written in a simple ASCII file that can be opened and edited with a text editor (e.g.: Notepad, Notepad++). The extension .conn will be added.
The first line of the connectivity results file format is a comma-separated list of information on the expoted data. It contains the following key - value pairs:

{| class="wikitable"
! style="text-align: center; font-weight:bold;" | Key
! style="text-align: center; font-weight:bold;" | Value
! style="text-align: center; font-weight:bold;" | Description
|-
| VersionNumber
| 1.0
| File format version
|-
| DataType
| Coherence / Granger Causality, etc.
| Connectivity method
|-
| DecompositionType
| Complex Demodulation / Wavelet Transform
| Time-frequency method
|-
| ConditionName
| Stimulus condition
| Name of condition
|-
| NumberTrials
| 12
| Number of trials
|-
| NumberTimeSamples
| 120
| Number of latencies
|-
| TimeStartInMS
| -400.0000
| Start latency in [ms]
|-
| IntervalInMS
| 50.0000
| Latency spacing in [ms]
|-
| NumberFrequencies
| 31
| Number of frequencies
|-
| FreqStartInHz
| 2.000
| Start frequency in [Hz]
|-
| FreqIntervalInHz
| 1.000
| Frequency spacing in [Hz]
|-
| NumberChannels
| 64
| Number of channels/sources
|}

The second line defines the channel/source labels. Please note that the list is comma-separated, therefore the list of labels must not contain spaces!

'''Example header'''

<source lang="dos">
VersionNumber=1.0 DataType=Coherence DecompositionType=Complex Demodulation ConditionName=Condition 1 NumberTrials=10 NumberTimeSamples=33 TimeStartInMS=-400.0000 IntervalInMS=50.0000 NumberFrequencies=31 FreqStartInHz=2.0000 FreqIntervalInHz=1.0000 NumberChannels=3
ACsR_RC0 ACsL_RC0 PrM_RC0
</source >

After the file header, the connectivity data is exported column-wise as indicated in the following image:

[[File:BESA_Connectivity_Data_Blocks.png]]

The columns of each data block indicate the latencies, starting with the earliest latency up to the latest latency. Therefore, there should be as many columns in each data block as specified in the header by the value of the ''NumberTimeSamples'' key. The rows of each data block indicate the frequencies, starting with the lowest frequency up to the maximum frequency. Therefore, there should be as many rows in each data block as specified in the header by the value of the ''NumberFrequencies'' key.

[[Category:Connectivity]]

← Older revision		Revision as of 11:07, 2 February 2021
Line 81:		Line 81:
	The columns of each data block indicate the latencies, starting with the earliest latency (first column) up to the latest latency (last column). There should be as many columns in each data block as specified in the header by the value of the ''NumberTimeSamples'' key. The rows of each data block indicate the frequencies, starting with the lowest frequency (first row) up to the maximum frequency (last row). There should be as many rows in each data block as specified in the header by the value of the ''NumberFrequencies'' key.		The columns of each data block indicate the latencies, starting with the earliest latency (first column) up to the latest latency (last column). There should be as many columns in each data block as specified in the header by the value of the ''NumberTimeSamples'' key. The rows of each data block indicate the frequencies, starting with the lowest frequency (first row) up to the maximum frequency (last row). There should be as many rows in each data block as specified in the header by the value of the ''NumberFrequencies'' key.

−	[[Category:Connectivity]]	+	[[Category:Connectivity]] [[Category:Data Import/Export]]

@@ Line 79: / Line 79: @@
 [[File:BESA_Connectivity_Data_Blocks.png]]
-The columns of each data block indicate the latencies, starting with the earliest latency (first column) up to the latest latency (last column). Therefore, there should be as many columns in each data block as specified in the header by the value of the ''NumberTimeSamples'' key. The rows of each data block indicate the frequencies, starting with the lowest frequency (first row) up to the maximum frequency (last row). Therefore, there should be as many rows in each data block as specified in the header by the value of the ''NumberFrequencies'' key.
+The columns of each data block indicate the latencies, starting with the earliest latency (first column) up to the latest latency (last column). There should be as many columns in each data block as specified in the header by the value of the ''NumberTimeSamples'' key. The rows of each data block indicate the frequencies, starting with the lowest frequency (first row) up to the maximum frequency (last row). There should be as many rows in each data block as specified in the header by the value of the ''NumberFrequencies'' key.
 [[Category:Connectivity]]

@@ Line 26: / Line 26: @@
 |-
 | DecompositionType
-| Complex Demodulation / Wavelet Transform
+| Complex Demodulation / Wavelet Transform / Multitapering
 | Time-frequency method
 |-
@@ Line 59: / Line 59: @@
 | FreqIntervalInHz
 | 1.000
-| Frequency spacing in [Hz]
+| Frequency spacing in [Hz] (only relevant for complex demodulation)
 |-
 | NumberChannels
@@ Line 69: / Line 73: @@
 '''Example header'''
 <source lang="dos">
 VersionNumber=1.0 DataType=Coherence DecompositionType=Complex Demodulation ConditionName=Condition 1 NumberTrials=10 NumberTimeSamples=33 TimeStartInMS=-400.0000 IntervalInMS=50.0000 NumberFrequencies=31 FreqStartInHz=2.0000 FreqIntervalInHz=1.0000 NumberChannels=3
 ACsR_RC0 ACsL_RC0 PrM_RC0
 </source >

@@ Line 9: / Line 9: @@
 [[File:BESA Connectivity Selected Connectivity and Time-Frequency Methods.png]]
-The connectivity matrix is written in a simple ASCII file that can be opened and edited with a text editor (e.g.: Notepad, Notepad++). The extension .conn will be added.
+The connectivity matrix is written in a simple ASCII file that can be opened and edited with a text editor (e.g.: Notepad). The extension .conn will be added.
 The first line of the connectivity results file format is a comma-separated list of information on the expoted data. It contains the following key - value pairs:

@@ Line 2: / Line 2: @@
 |title = Module information
 |module = BESA Connectivity
-|version = 1.0 or higher
+|version = BESA Connectivity 1.0 or higher
 }}