Contents
- Introduction
- FAQ
Contents
- What is an Independent Component (IC) and how do I know what each one means?
- How do I use MELODIC to filter out unwanted components from my functional data?
- How does MELODIC calculate the number of Independent Components (ICs)?
- How do I transform the MELODIC results from a low-resolution standard space to a higher-resolution one?
What is an Independent Component (IC) and how do I know what each one means?
Independent Component Analysis (ICA) attempts to split the 4D functional data into a set of spatial maps, each with an associated time course. This is a way of breaking up the original data set in a way which does not require the experimental paradigm to be specified and hopefully separates out signals of interest from other signals or artefacts. It is particularly useful when examining data where the timecourse of the response is uncertain. Ideally the result of running ICA will be a set of Independent Components (ICs), some of which are clearly related to activation while some are related to other physiological processes (e.g. respiration, resting-state signals, etc) or to imaging artefacts (e.g. motion, ghosting, slice dropout, noise, etc). Examples of a wide range of artefacts can be found in the FIX papers. There is no automatic way of determining which ICs are artefacts and which are not (since the process is model-free) and some knowledge of the experiment (and standard artefacts) is usually required to interpret the results.
Technically, ICA performs a linear decomposition of the original data, such that when all the Independent Components (ICs) are added together (each one being a 4D signal formed by the outer product of the spatial map and timecourse) they equal the original data. This is a similar concept to PCA but enforces independence between the components spatially while PCA enforces orthogonality both spatially and temporally. Note that in ICA for FMRI no relationship between the timecourses is imposed - they can be very similar. In addition, MELODIC uses a dimensionality estimation technique which separates out much of the noise before performing the ICA, thus reducing the number of purely noise-driven ICs in the output.
How do I use MELODIC to filter out unwanted components from my functional data?
To filter out unwanted components from the original data using MELODIC you will need (i) the name of the original data, (ii) the mixing matrix that defines the decomposition and (iii) a list of component numbers to remove. This is described more fully in an FSL Course Example. In brief, the required command is:
melodic -i inputdata -v -o outputname.ica --mix=inputdata.ica/melodic_mix -f "a,b,c,d,e,f,..."
where inputdata has previously been run through MELODIC, creating the output directory inputdata.ica and a,b,c etc. are the component numbers of the unwanted components found in this ouptut.
Note: You need those doublequotes so that the entire list of numbers is passed to melodic as the argument of the -f option!
How does MELODIC calculate the number of Independent Components (ICs)?
The number of components is calculated using Bayesian dimensionality estimation techniques, as detailed in the FMRIB technical report TR02CB1. Refer to this report for full details on this and other aspects of the probabilistic ICA method used in MELODIC. This dimensionality estimation is used by default in both the command line and GUI versions. It can be turned off and the number of components specified manually, although this is not recommended for FMRI data.
How do I transform the MELODIC results from a low-resolution standard space to a higher-resolution one?
Transforming an image between different resolution versions of standard space (e.g. 3mm to 2mm) should be done with flirt:
flirt -in image3mm -ref $FSLDIR/data/standard/MNI152_T1_2mm -applyxfm -usesqform -out image2mm
Note that in this case the flirt command line must be used (not applywarp) since the -usesqform flag aligns the images based on standard space coordinates, and not using a prior transformation matrix or warp. The input image can be at any resolution as long as it is in standard space (as created by MELODIC) and the reference image can be at a higher resolution (e.g. 1mm) if desired.
CategoryFAQ CategoryMELODIC