29833
Comment:
|
29291
|
Deletions are marked like this. | Additions are marked like this. |
Line 43: | Line 43: |
* Note that in general, you should not compute the time-frequency decomposition of the average, but rather TF decompositions of the single trials and average the power of the TF maps you obtain. This is illustrated further on this page. | |
Line 82: | Line 83: |
* '''Hide edge effects''': When this option is selected, the time-frequency coefficients that could not be properly estimated because of a lack of time samples are hidden. It allows you to see only the information that is really reliable. In this example, you can see that it masks a large portion of the window: 600ms is not enough to perform a correct time-frequency decomposition. Try to work on larger time windows when using these tools.<<BR>><<BR>> {{attachment:example_hide.gif||height="181",width="498"}} | * '''Hide edge effects''': When this option is selected, the time-frequency coefficients that could not be properly estimated because of a lack of time samples are hidden. It allows you to see only the information that is really reliable. In this example, you can see that it masks a large portion of the window: 600ms is not enough to perform a correct time-frequency decomposition. Try to work on much larger time windows when using these tools.<<BR>><<BR>> {{attachment:example_hide.gif||height="181",width="498"}} |
Line 152: | Line 153: |
* '''Power spectrum''': For the given time, show the power of all the sensors across the frequencies. * '''Time series''': For the given frequency, show the power of all the sensors in time.<<BR>><<BR>>{{attachment:tf_spectrum.gif}} == Scouts time series == * The previous section introduces an interesting tool to display the TF for a single source, but it is hard to extract meaningful information that can be analyzed statistically or compared between subjects this way. A better option is to define cortical regions of interest (scouts, see [[Tutorials/TutScouts|tutorial #8]]), and compute the TF for the average time series of these scouts. * Define the scouts:<<BR>> * Double click for the source file in the Left condition. * Make sure that your LeftSS and RightSS scouts are still available in your cortex surface.If not, go back to tutorial 8, and recreate them <<BR>><<BR>> {{attachment:createScouts.gif}} * Compute the TF decomposition for these scouts: * Drag and drop the Left source file (''MN: MEG(Constr)'') into ''Process1''. * Select the "Process sources" button. * Click on Run. Select "Frequency > Time-frequency (Morlet wavelets)". * As some scouts are available for the input, you will see this new box:<<BR>><<BR>> {{attachment:selectScouts.gif}} * Select "Use scouts time series", and select both scouts in list. * Click on Edit. This time, most of the options are available again. We are going to compute the full TF matrix at once for the two scouts, so we can compute the power right away, together with time and/or frequency bands. * Leave all the options to the default (linear time, linear frequencies, scout function: After), then click on Ok, then Run. * A new file appears in the tree, as a child of the sources file: "Scouts,Power,1:1:60Hz". * To compute the TF of each scout, the operations performed by the program are the following: * Get time series for each source in the scout * If the scout function is applied __before__ the TF: * Apply the "scout function", that combines the different sources to get only one time series for each scout. * Compute the power of the TF for each scout. * If the scout function is applied __after__ the TF: * Compute the power of the TF for each source * Apply the "scout function", that combines the different sources TF to get one TF only for each scout. * The selection of the "scout function" is done in the "Scout" tab. * '''Output''': * '''Save individual TF maps''': This option stops the computation here, and saves in the database one time-frequency file for each input file. * Be very careful using this option because if you have hundreds of trials, it will fill your hard drive very quickly. * One full TF file in this case contains [nSensors x nTime x nFreq] = 3.397.500 values = 25 Mb. * You can however limit the amount of data produced by using time and/or frequency bands. For 15 time bands and 6 frequency bands, the size of each file drops to: 110 Kb. * '''Save average TF maps''': This option is available only when there are more than one input files (number of files you dropped in the Processes tab). * Instead of saving the TF for each file separately, it automatically computes the average of the power of all the TF. * This is a good choice if you do not plan to use independently all the TF files, because it saves a lot of time and disk space. * Right-click on this file and try all the visualization menus available (including "Time series" and "Power spectrum").<<BR>><<BR>> {{attachment:scoutsTfFile.gif}} |
* '''Power spectrum''': For the current time, shows the power of all the sensors across the frequencies. * '''Time series''': For the current frequency, shows the power of all the sensors in time.<<BR>><<BR>> {{attachment:tf_spectrum.gif||height="179",width="587"}} == Scouts / Single trials == Similar calculations can be done at the level of the sources, either on the full cortex surface or on the a limited number of regions of interests. We will start with the latter as it is usually an easier approach.<<BR>>We will use this section to illustrate the online averaging of the trials TF decomposition as well. * Drag and drop all the '''deviant trials''' from '''both runs''', select ['''Process sources''']. * Run process "'''Frequency > Time-frequency (Morlet wavelets)'''". <<BR>>Select the option "Use scouts" and '''select all the scouts''' defined in the previous tutorial. <<BR>><<BR>> {{attachment:scouts_process.gif||height="347",width="448"}} * In the advanced options, select "Scout function: '''After'''" and "Output: '''Save average'''". <<BR>>Run the process (it may take a while).<<BR>><<BR>> {{attachment:scouts_options.gif||height="637",width="380"}} * The scout function was introduced in the previous tutorial. It is the method we use to group the time series for the 40*3=120 unconstrained dipoles we have in each scout into one unique signal per orientation (three signals in the unconstrained case). When computing the TF of one scout, we have the choice between applying this function before or after the time-frequency decomposition itself. * '''Before''': Extract the 120 source signals, apply the scout function to get three signals (one per orientation), run the TF decomposition of the three signals, and finally sum the power of the three TF maps. This is faster but may lose some frequency resolution (especially for constrained sources). * '''After''': Extract the 120 source signals, run the TF decomposition of the 120 signals, apply the scout function on the power of the TF maps for each orientation separately, and finaly sum the three orientations. You should always prefer this option if the computation times are not insane. * '''Save individual TF maps''': This option stops the computation here and saves in the database one time-frequency file for each input file (40 files), with one TF map for each scout. * '''Save average TF maps''': Instead of saving the TF for each file separately, it automatically computes the average of the power of all the TF. This is a good choice if you do not plan to use independently all the TF files, because it saves a lot of time and disk space. * Rename the new file to add a tag "Deviant" in it. Then right-click > '''Time-freq: All scouts'''. <<BR>><<BR>> {{attachment:scouts_file.gif}} |
Line 192: | Line 172: |
* Double-click on the new file to display the time-frequency decomposition of the first sensor. <<BR>><<BR>> {{attachment:example_display.gif||height="216",width="623"}} | * * Double-click on the new file to display the time-frequency decomposition of the first sensor. <<BR>><<BR>> {{attachment:example_display.gif}} |
Line 205: | Line 186: |
Creates files that are very large. Easier with frequency bands. |
Tutorial 24: Time-frequency
Authors: Francois Tadel, Dimitrios Pantazis, Sylvain Baillet
This tutorial introduces how to compute time-frequency decompositions of MEG/EEG recordings and cortical currents using complex Morlet wavelets and Hilbert transforms.
Contents
- Introduction
- Morlet wavelets
- Edge effects
- Simple example
- Process options
- Display: One channel
- Display: Mouse and keyboard shortcuts
- Display: All channels
- Display: Sensor topography
- Display: Power spectrum and time series
- Scouts / Single trials
- Normalized time-frequency maps
- Cortical sources
- Hilbert transform
- Time and frequency bands
- On the hard drive
- Additional discussions on the forum
Introduction
Some of the MEG/EEG signal properties are difficult to access in time domain (graphs time/amplitude). A lot of the information of interest is carried by oscillations at certain frequencies, but the amplitude of these oscillations is sometimes a lot lower than the amplitude of the slower components of the signal, making them difficult to observe.
The averaging in time domain may also lead to a cancellation of these oscillations when they are not strictly locked in phase across trials. Averaging trials in time-frequency domain allows to extract the power of the oscillation regardless of the phase shifts. For a better understanding of this topic, we recommend the lecture of the following article: Bertrand O, Tallon-Baudry C (2000), Oscillatory gamma activity in humans: a possible role for object representation
In Brainstorm we offer two approaches for computing time-frquency decompositions (TF): the first one is based on the convolution of the signal with series of complex Morlet wavelets, the second filters the signal in different frequency bands and extract the envelope of the filtered signals using the Hilbert transform.
Morlet wavelets
Complex Morlet wavelets are very popular in EEG/MEG data analysis for time-frequency decomposition. They have the shape of a sinusoid, weighted by a Gaussian kernel, and they can therefore capture local oscillatory components in the time series. An example of this wavelet is shown below, where the blue and red curves represent the real and imaginary part, respectively.
Contrary to the standard short-time Fourier transform, wavelets have variable resolution in time and frequency. When designing the wavelet, we basically decide a trade off between temporal and spectral resolution.
To design the wavelet, we first need to choose a central frequency, ie the frequency where we will define the mother wavelet. All other wavelets will be scaled and shifted versions of the mother wavelet. Unless interested in designing the wavelet at a particular frequency band, the default 1Hz should be fine.
Then, the desirable time resolution for the central frequency should be defined. For example, we may wish to have a temporal resolution of 3 seconds at frequency 1 Hz (default parameters). These two parameters, uniquely define the temporal and spectral resolution of the wavelet for all other frequencies, as shown in the plots below.
Resolution is given in units of Full Width Half Maximum of the Gaussian kernel, both in time and frequency. The relevant plots are given below.
Edge effects
Users should pay attention to edge effects when applying wavelet analysis. Wavelet coefficients are computed by convolving the wavelet kernel with the time series. Similarly to any convolution of signals, there is zero padding at the edges of the time series and therefore the wavelet coefficients are weaker at the beginning and end of the time series.
From the figure above, which designs the Morlet wavelet, we can see that the default wavelet (central frequency 1Hz, FWHM=3sec) has temporal resolution 0.25sec at 5Hz and 0.1sec at 10Hz. In such case, the edge effects are roughly half these times: 125ms in 5Hz and 50ms in 10Hz. Examples of such edge effects are given in the figures below.
Simple example
Let's start with a simple example to explore the options of the time-frequency decomposition process.
In Process1, select the average recordings for the deviant condition for Run#01.
Select process: Frequency > Time-frequency (Morlet wavelets).
Enter "MEG" for the sensor types, do not select the "Spectral flattening" option.
Click on the button [Edit] to see all the process options.
Time definition: Same as input, Frequency definition: Log 1:40:150, Compute measure: Power.
- Note that in general, you should not compute the time-frequency decomposition of the average, but rather TF decompositions of the single trials and average the power of the TF maps you obtain. This is illustrated further on this page.
Process options
Comment: String that will be displayed in the database explorer to represent the output file.
Time definition
Same as input file: The output file has the same time definition as the input file.
In this example, it means: 361 samples between -100ms and 500ms.Group in time bands: This option adds a step of computation. First it computes the TF decomposition for all the input file, then averages the power by time band. To define a time band:
Enter your own time bands in the text area, one line per time band, with following format: "name / time definition / function"
- Click on the "Generate" button to automatically create a list of time bands with the same length. You will be asked the maximal length of each time band.
The function is the measure we take to combine the values for all the individual frequencies into one for the frequency band. Possible values are: mean, max, std, median.
Frequency definition: Frequencies for which the power will be estimated at each time instant
Linear: You can specify the frequencies with the Matlab syntax start:step:stop.
The default is "1:1:60", which produces 60 values [1, 2, 3, 4, ..., 59, 60].Group in frequency bands: As for the time definition, this option leads to a two-step process. First it computes the TF decomposition for several values in the frequency band, then it averages the power of TF coefficients per frequency band. To define a frequency band:
One line per frequency band, with the format "name / frequency definition / function"
The frequency definition is a Matlab expression evaluated with an eval() call. If the frequency definition contains only two values, Brainstorm adds two extra values in the middle so that the final averaged value is a bit more robust. Example of valid expressions:
"2,4": Evaluates to [2,4], and then expands to the frequency vector [2, 2.66, 3.33, 4]
"2:0.5:4": evalues to [2 2.5 3 3.5 4]
"2, 2.5, 3, 3.5, 4": Evaluates to [2 2.5 3 3.5 4]The function is the measure we take to combine the values for all the individual frequencies into one for the frequency band. Possible values are: mean, max, std, median.
Morlet wavelet options
Central frequency: Frequency where the mother wavelet is designed. All other wavelets will be shifted and scaled versions of the mother wavelet
Time resolution (FWHM): Temporal resolution of the wavelet at the central frequency (in units of Full Width Half Maximum). Click [Display] to see the resolution of the wavelet for other frequencies.
Compute the following measure:
- The convolution of the signal with complex Morlet wavelets returns the complex coefficients for each frequency/time/sensor. Typically, what we display is the power of the coefficients (square of the amplitude: abs(TF).^2). You can choose if you want to apply this transformation or not.
Power: Computes the "power" transformation immediately after the TF decomposition. This discards the phase information, but produces files that are twice smaller and a lot easier to process.
None: Save the TF coefficients as they are computed. This can be useful if you plan to use these decompositions for other purposes that require the phase.
- Some combinations of options may disable this choice. If you select frequency bands, the program will have to compute the power before averaging the values, therefore "none" is not an option.
Display: One channel
Right on the new time-frequency file > One channel (same as double-clicking on the file).
This menu displays the time-frequency decomposition of the first sensor. The Brainstorm window shows two new elements: the tab "Display" and the "current frequency" slider.
Current frequency: Slider that shows the current frequency selected in all the figures.
Just like the time, the frequency selection is centralized and managed by one control only for all the figures. As a consequence, it is impossible to display TF files with different frequency definitions at the same time. This can be perceived as an annoying limitation, but it allows all the simultaneous displays to be consistent at anytime and makes the interface more intuitive to manipulate, with lower risks of mistakes in the interpretation of the different figures.List of sensors: This drop-down list shows the current entry displayed in the selected figure. In this case, it is by default the MEG sensor "MLC11". Try to change it, it will update the display of the figure, showing the frequency power for another sensor.
Hide edge effects: When this option is selected, the time-frequency coefficients that could not be properly estimated because of a lack of time samples are hidden. It allows you to see only the information that is really reliable. In this example, you can see that it masks a large portion of the window: 600ms is not enough to perform a correct time-frequency decomposition. Try to work on much larger time windows when using these tools.
Smooth display: Re-interpolates the time-frequency maps on a finer grid to produce nicer plots.
Measure: Type of measure that is currently represented in the selected figure. The entries that are enabled depend on the type of data that is saved in the file. In this case, we saved directly the power of the wavelet coefficients in the file, we discarded the angle/phase information, so the "phase" option is disabled. The other options are: Magnitude = sqrt(power), Log = 10*log10(power)
Colormap: As explained in the previous tutorials, you can change the colormap by clicking+moving on the colorbar on the right of the figure. Double-click on the colorbar to restore the defaults.
Display: Mouse and keyboard shortcuts
Mouse shortcuts
Left-click: Selection of current time and frequency.
Left-click + move: Select a time/frequency range. The legends of the X/Y axis show the selection.
Mouse wheel: Zoom in time, centered on the current time cursor.
Control + mouse wheel: Zoom in frequencies, centered on the current frequency cursor.
Right-click + move, or Control + left-click + move: Move in the zoomed image.
Double-click: Restore initial view.
Keyboard shortcuts:
Left/right arrows: Change the current time.
Page-up/page-down: Change the current time, 10 time samples at a time.
Up/down arrows: Change the the sensor displayed in this figure.
Control + up/down arrows: Change the current frequency.
Enter: View the original time series for this sensor.
Control + R: View the original MEG recordings.
Control + T: View the time-frequency 2D topography.
Control + I: Save as image.
Control + D: Dock figure in the Matlab environment.
Figure popup menu
Set selection manually: Does the same thing as drawing a time/freq selection square on a figure, but by typing the values for time and frequency manually.
Export to database: Save the selection for the displayed sensor in a new file in the database.
Export to file: Same as "Export to database", but the saved file is not registered in the database.
Export to Matlab: Same as "Export to database", but the output structure is sent to a variable in the Matlab base workspace instead of being saved to a file.
Display: All channels
Three menus display the time-frequency of all the sensors with different spatial organizations.
All channels: All the maps are displayed one after the other, in the order they are saved in the file.
2D Layout (maps): Shows each TF map where the sensor is located on a flattened 2D map.
2D Layout (no overlap): Similar to the the previous display, but the positions of the images are reorganized so that they do not overlap.
Useful shortcuts for these figures:
Click: clicking on any small TF image opens a new figure to display only the selected sensor.
Shift + click: Same, but opens the original recordings time series of the sensor instead of the TF.
Mouse wheel: Zoom in/out.
Right click + move: Move in a zoomed figure.
Display: Sensor topography
The menus below show the distribution of TF power over the sensors, for one one time point and one frequency bin, very similarly to what was introduced in tutorial Visual exploration.
2D Sensor cap / 2D Disc / 3D Sensor cap: 90ms, 8Hz
2D Layout: 8Hz (black), 35Hz (white)
Useful shortcuts for these figures:
Left/right arrows: Change the current time.
Up/down arrows: Change the current frequency.
Control + E: Display the sensors markers/names.
Shift + click on a sensor: Displays the time-frequency decomposition for that specific sensors.
Right click + move: Select a group of sensors.
Shift + scroll: Change the gain of the time series (2D Layout).
Control + scroll: Change the length of the window displayed around the current time (2D Layout).
Display: Power spectrum and time series
These two menus generate similar figures:
Power spectrum: For the current time, shows the power of all the sensors across the frequencies.
Time series: For the current frequency, shows the power of all the sensors in time.
Scouts / Single trials
Similar calculations can be done at the level of the sources, either on the full cortex surface or on the a limited number of regions of interests. We will start with the latter as it is usually an easier approach.
We will use this section to illustrate the online averaging of the trials TF decomposition as well.
Drag and drop all the deviant trials from both runs, select [Process sources].
Run process "Frequency > Time-frequency (Morlet wavelets)".
Select the option "Use scouts" and select all the scouts defined in the previous tutorial.
In the advanced options, select "Scout function: After" and "Output: Save average".
Run the process (it may take a while).
- The scout function was introduced in the previous tutorial. It is the method we use to group the time series for the 40*3=120 unconstrained dipoles we have in each scout into one unique signal per orientation (three signals in the unconstrained case). When computing the TF of one scout, we have the choice between applying this function before or after the time-frequency decomposition itself.
Before: Extract the 120 source signals, apply the scout function to get three signals (one per orientation), run the TF decomposition of the three signals, and finally sum the power of the three TF maps. This is faster but may lose some frequency resolution (especially for constrained sources).
After: Extract the 120 source signals, run the TF decomposition of the 120 signals, apply the scout function on the power of the TF maps for each orientation separately, and finaly sum the three orientations. You should always prefer this option if the computation times are not insane.
Save individual TF maps: This option stops the computation here and saves in the database one time-frequency file for each input file (40 files), with one TF map for each scout.
Save average TF maps: Instead of saving the TF for each file separately, it automatically computes the average of the power of all the TF. This is a good choice if you do not plan to use independently all the TF files, because it saves a lot of time and disk space.
Rename the new file to add a tag "Deviant" in it. Then right-click > Time-freq: All scouts.
Normalized time-frequency maps
Double-click on the new file to display the time-frequency decomposition of the first sensor.
Time-frequency files, once computed, can be processed with Process1 and Process2, exactly as recordings or sources file, as introduced in ?Tutorial #9.
- Only the TF of sensors, clusters and scouts can be processed this way.
- The TF of full source files, as explained above, are saved in the database in an incomplete form, that requires a few more on-the-fly computation steps. The processing engine requires an access to the full TF matrix, which is usually too big to be handled in Matlab for these TF/sources files.
- If you need to average or do some group-analysis on time-frequency data at the source level, the problem has to be simplified a few steps before: for instance by doing your analysis only on a few scouts instead of the full cortex.
Drag and drop one of the TF files in Process1, select the "Time-frequency" button, click on Run.
- One of the process that is commonly applied on the time-frequency maps is the Z-score, to normalize the values in each frequency band with respect to a baseline. This way, all the frequency bands can be compared directly in terms of amplitude. If we look directly at the power of the Morlet coefficients, the values we observe are always lower in the high frequencies than in the low frequencies. The Z-score fixes this and helps getting figures that are easier to read.
Select the process "Standardize > Compute Z-score (static)". Leave the baseline to the default value (the pre-stimulus interval). Click on run.
- Red values are positive, representing an increase in power with respect with the baseline, blue values are negative, representing a decrease.
The time-frequency map may appear all white or all blue depending on the way the colormap is configured. To edit the colormap, right-click on the figure > Colormap.
Cortical sources
Creates files that are very large. Easier with frequency bands.
- How to display the TF decompositions for the source time series?
- It is possible to estimate the TF for each source of the brain, but it would be unrealistic to save this information to a file. The size of the TF matrix would be [nVertices x nTimes x nFrequencies] = [15010 x 375 x 60] complex-double = 5.2 Gb!
- We need then to simplify this problem. Two methods: compute the TF only for a few scouts (next section), or use the linear property of the TF decomposition.
As both the source reconstruction process (ImagingKernel * recordings) and the TF are linear operators, it is possible to exchange them:
TF(Inverse(Recordings)) = Inverse(TF(Recordings))
=> Power(TF(Inverse(Recordings))) = Power(Inverse(TF(Recordings)))So the solution is to estimate the TF of the recordings, and then multiply it on the fly by the ImagingKernel only for the required sources and/or frequency and/or time instant. This is done in a completely transparent way from the user point a view.
- Start the computation of the TF for a source file:
Drag and drop the source file computed for the Left / ERF file in Process1.
- Select the "Process sources" button.
- Click on Run. Select "Time-frequency (Morlet wavelets)". Do NOT check the box "Use scouts time series".
- Click on Edit. There is a new option available, that offers between saving only the kernel and the TF of sensors, or the full TF matrix. Select the optimized solution.
Note that this solution is not compatible with any of the operations that requires to compute explicitly the power of all the TF decomposition: time bands and frequency bands.
Click on Ok, then Run. A new file appears in the database explorer, as a child of the source file. Right-click on it, try all the visualization menus.
If you understood well how to use the visualization of both the sources and the time-frequency maps, the manipulation of these figures should be rather intuitive. Change several times the current time and the current frequency in different ways. Change current time and frequency so that you can observe the main response in the somatosensory cortex (eg. t = 46.40ms, f = 45Hz).
Shift + click on the cortex surface: This is a useful shortcut that you should remember. It displays the TF decomposition of the selected source.
Right-click on the brain: This selects the closest vertex and displays the popup menu at the same time. The first three menus are relative to the source that was just clicked.
Hilbert transform
Time and frequency bands
Frequency bands
Drag and drop the averaged file Left / ERF in the Process tab, click on Run, select the process "Frequency > Time-frequency (Morlet wavelets)". Click on "Edit" to get the options.
- Just change the frequency definition: select "Group in frequency bands", leave the default frequency bands, and click on Ok. Click on Run.
Right-click on the file you've just computed "Power,FreqBands" > "One channel".
- You can notice that now the frequency selection is discreet, both in the figure and in the frequency slider, it is not possible to select a frequency in between. At each time and for each sensor, there are now just 6 values, one per frequency band.
- Now if you try to open at the same time the first TF that you have computed "Power,1:1:60Hz", you would get an error message: This frequency definition is not compatible for display with the linear [1...60] scale.
- Display the other possible views (All sensors, 2D Sensor Cap, 2D Layout), and change the current time and the current frequency in different ways (sliders, keyboard, clicks on figures). Play with the open figures until you are completely comfortable with these representations.
Time bands
Compute TF again for file Left / ERF, but this time select the option "Group in time bands" (with "linear" frequency definition). To generate a list of regular time intervals, click on "Generate" and enter "30" ms as the duration of each time band.
- You get 11 time bands: t-2 and t-1 before 0ms, and t1 to t9 after 0ms. Click on Ok to start the computation.
Right-click on this new file "Power,1:1:60Hz" > Time-frequency maps.
- Observe that the behavior is not the same as with the frequency bands: it is still possible to select a specific time in a time band (using the slider or clicking on the figure). This is because the time definition in the interface is still based on the ERF averaged file time definition, which is "continuous". Only 11 values in time are computed, and when requesting values a specific time point, the interface gets the values associated with the time band that time point belongs to.
- As a consequence, it is possible to open at the same time the first TF file that you have computed: "Power,1:1:60Hz". You would not get an error message like with the frequencies mismatching.
- Display also other types of figures (All sensors, 2D topographies), change current time and frequency several times in several ways (sliders, keyboard, clicks on figures).
Time bands and frequency bands
On the hard drive
Right click one of the TF files, and select the menu File > View file contents, to have a look to what is the actual contents of these structures.
TF: [nSensors x nTime x nFrequency] matrix containing all the values of the time-frequency decomposition (complex wavelet coefficients, or power of amplitudes)
- nSensors: Number of sensors for which the TF has been estimated
- nTime:
If there are time bands defined, nTime = size(TimeBands,1) = number of time bands
- If there are no time bands (linear time sampling): nTime = length(Time)
- nFrequency:
- If there are frequency bands defined, nFrequency = size(Freqs,1) = number of frequency bands
- If there are no frequency bands (linear frequency sampling): nFrequency = length(Freqs)
Comment: String displayed in the database explorer to represent the file.
DataType: Explains from what kind of data this file was computed. Possible values are: 'data', 'results', 'scout, 'matrix'...
Time: Time vector used to estimate this file.
TimeBands: Description of the time bands. Cell array {nTimeBands x 3}, where each line represents a time band {'band_name', 'time definition', 'function'}
Freqs:
- If frequency bands: Cell array {nFreqBands x 3}, where each line represents a frequency band {'band_name', 'frequency definition', 'function'}
- In linear frequency sampling: vector containing all the frequencies
RowNames: Cell array of strings that describes each row of the TF matrix. In this specific case, it would be the list of all the MEG sensor names. But it could also be a list of names of scouts or clusters.
Measure: Contains the name of the function that was applied right after the computation of the wavelet coefficients. So it represents the type of data contained in the TF matrix. Possible values:
- 'none': No measure applied, TF contains the complex wavelet coefficients.
- 'power': TF contains the power for each frequency, ie. the square of the amplitude: abs(coefficients).^2
- 'magnitude': abs(coefficients)
- 'log': 10 * log10( abs(coefficients).^2)
- 'phase': angle(coefficients)
Method: String that identifies the process that generated the file; possible values: {'morlet', 'fft', 'psd', 'hilbert', 'corr', 'cohere', 'granger', 'plv'}
DataFile: Initial file from which this file was computed. In the database explorer, the TF file will be shown as a child of this DataFile file.
nAvg: Number of trials that were averaged to obtain this file (copied from the recordings file at computation)
Options: Options that were selected in the time-frequency options window.
History: List of operations performed on this file (better visualized with popup menu File > View file history)
Document file tags
Additional discussions on the forum
Time and frequency resolution: http://neuroimage.usc.edu/forums/showthread.php?1848