Tutorial 25: Difference

[TUTORIAL UNDER DEVELOPMENT: NOT READY FOR PUBLIC USE]

Authors: Francois Tadel, Elizabeth Bock, Dimitrios Pantazis, Richard Leahy, Sylvain Baillet

In this auditory oddball experiment, we would like to test for the significant differences between the brain response to the deviant beeps and the standard beeps, time sample by time sample. Until now we have been computing measures of the brain activity in time or time-frequency domain. We were able to see clear effects or slight tendencies, but these observations were always dependent on an arbitrary amplitude threshold and the configuration of the colormap. With appropriate statistical tests, we can go beyond these empirical observations and assess what are the significant effects in a more formal way.

We are typically interested in comparing different groups of samples. We want to know what is significantly different in the brain responses between two experimental conditions or two groups of subjects. So we will be essentially computing differences, then testing if these differences are significantly different from zero.

This tutorial focuses only on the first part of this problem. Computing a difference between condition A and condition B sounds trivial, but it requires some reflexion when it comes to interpreting the sign of the subtraction of two signals oscillating around zero. We can compute the difference between two conditions in many different ways, we will try to give clear directions of the use cases of each option. The statistical significance will be discussed in the next tutorial.

Sign of the signals

First we need to define on which signals we want to compute the difference: sensor recordings, constrained sources (one signal per grid point) or unconstrained sources (three signals per grid point). For the first two we can compare directly the signals oscillating around zero or their absolute value, for unconstrained sources we have the addional option to compare the norm of the three orientations.

Using the rectified signals (absolute value) give us the an idea of the amount activity in one particular brain region, but alter the frequency information and therefore cannot be used for time-frequency or connectivity analysis. Additionally, the rectified signals are not appropriate to detect effects between different experimental conditions, as illustrated in the next section.

In general, you should not apply an absolute value explicitely to your recordings. The only application cases for rectified signals are the display of the cortical maps (and it is done on the fly) and the comparison of magnitudes between conditions (and then it is done within the process).

diff_signals.gif

Computing a difference

diff_sign_table.gif

Using sensor recordings or constrained sources:

Using unconstrained sources (three orientations per grid point):

Sources: Normalized or not

Processing current density maps or normalized source maps do not change these facts, as long as you did not rectify the signals during the computation of the Z-score.

You should be using the Z-score(minnorm) instead of Z-score(abs(minnorm))

Normalize the source maps if you are intending to compare different subjects, it will be help bringing the source maps in the same range of values.

Difference deviant-standard

Before running complicated statistical tests that will take hours of computation, you can start by checking what the difference of the average responses looks like. If in this difference you observe obvious effects that are clearly not what you are expecting, it's not worth moving forward with finer analysis: either the data is not clean enough or your initial hypothesis is wrong.

We are going to use the Process2 tab, at the bottom of the Brainstorm figure. It works exactly like the Process1 tab but with two lists of input files, referred to as FilesA (left) and FilesB (right).

Difference of means

Another process can compute the average and the difference at the same time. We are going to compute the difference of all the trials from both runs at the sensor level. This is usually not recommended because the subject might have moved between the runs. Averaging the recordings across runs is not accurate but can give a good first approximation, in order to make sure we are on the right tracks.








Feedback: Comments, bug reports, suggestions, questions
Email address (if you expect an answer):


Tutorials/Difference (last edited 2015-11-04 14:15:30 by FrancoisTadel)