Education, tips and tricks to help you conduct better fMRI experiments.
Sure, you can try to fix it during data processing, but you're usually better off fixing the acquisition!
Sure, you can try to fix it during data processing, but you're usually better off fixing the acquisition!
Friday, December 30, 2011
Common persistent EPI artifacts: Gibbs artifact, or ringing
Don't ask me why there's no apostrophe, it looks possessive to me. Perhaps it's (the) Gibbs artifact rather than Gibbs (his) artifact. Most people simply refer to the effect as ringing anyway, so let's move on. This post concerns a phenomenon that, like aliasing last time, isn't unique to EPI but is a feature of all MRIs that are obtained via Fourier transformation.
In short, ringing is a consequence of using a period of analog-to-digital conversion in order to apply a (discrete) FT to the signals and produce a digital image. Or, to put it another way, we are using a digital approximation to an analog process and thus we can never properly attain the infinite resolution that's required to fully represent every single feature of a real (analog) object. Ringing is an artifact that results from this imperfect approximation.
We had already encountered one consequence of digitization in the Nyquist criterion in PFUFA Part Six. However, for our practical purposes, ringing isn't a direct consequence of digitization like the Nyquist criterion, but instead results from the duration of the digitization (or ADC) period relative to the persistence of the signals being measured. In principle, a signal decaying exponentially decays forever, which is rather a long time to wait for the next acquisition in a time series, so we instead enable the ADC for a window of time that coincides with the bulk - say 99% - of the signal, then we turn it off. This square window imposed over the exponentially decaying signal causes some degree of truncation, and it's this truncation that leads to ringing. (See Note 1.)
An example of ringing in EPI of a phantom
Let's start with an unambiguous example of ringing by looking at the artifact in a homogeneous, regular phantom. Below is a 64x64 matrix EPI acquired from a spherical gel-filled phantom. You're looking for the wave-like patterns set up inside and outside the edges of the main signal region:
In the left image, which is contrasted to highlight ringing artifacts within the signal region itself, the primary ringing artifact appears as a series of concentric circles, each with progressively smaller diameter and lower intensity as you move in from the edge of the phantom. One section of the bright bands is indicated with a red arrow, but you should be able to trace these circles all the way around the image. Also visible is a strong interference pattern (blue arrows) that arises between the aforementioned ringing artifact and the overlapping N/2 ghosts. This is because the ghosts maintain the contrast properties of the main image; they are, after all, simply weak (misplaced) clones of the main image.
Tuesday, December 27, 2011
Another brief explanation of decoding
Here's another short video produced by UC's media people in which Jack Gallant explains in broad terms how his group's recent decoding experiment was conducted:
A good place to go next for more details is the Gallant Lab website. Read the FAQ on that page to gain a basic understanding of what the experiment was, and what it wasn't. Then go read the paper, it's written very accessibly!
A good place to go next for more details is the Gallant Lab website. Read the FAQ on that page to gain a basic understanding of what the experiment was, and what it wasn't. Then go read the paper, it's written very accessibly!
Wednesday, December 14, 2011
Common persistent EPI artifacts: Aliasing, or wraparound
In Part Eleven of the series Physics for understanding fMRI artifacts (hereafter referred to as PFUFA) you saw how setting parameters in k-space determined the image field-of-view (FOV) and resolution. In that introduction I kept everything simple, and the Fourier transform from the k-space domain to the image domain worked perfectly. For instance, in one of the examples the k-space step size was doubled in one dimension, thereby neatly chopping the corresponding image domain in half with no apparent problems. At the time, perhaps you wondered where the cropped portions of sky and grass had gone from around the remaining, untouched Hawker Hurricane aeroplane. Or perhaps you didn't.
In any event, you can assume from the fact that this is a post dedicated to something called 'aliasing' that in real world MRI things aren't quite as neat and tidy. Changing the k-space step size - thereby changing the FOV - has consequences depending on the extent of the object being imaged relative to the extent of the image FOV. It's possible to set the FOV too small for the object. Alternatively, it's possible to have the FOV set to an appropriate span but position it incorrectly. (The position of the FOV relative to signal-generating regions of the sample is a settable parameter on the scanner.) Overall, what matters is where signals reside relative to the edges of the FOV.
Now, on a modern MRI scanner with fancy electronics, aliasing is a problem in one dimension only: the phase encoding dimension. (Yeah, the one with all the distortion and the N/2 ghosts. Sucks to be that dimension!) The frequency encoding dimension manages to escape the aliasing phenomenon by virtue of inline analog and digital filtering, processes that don't have a direct counterpart in the phase encoding dimension. Instead, signal that falls outside the readout dimension FOV, either because the FOV is too small or because the FOV is displaced relative to the object, is eliminated. It's therefore important to know what happens where and when as far as both image dimensions are concerned. One dimension gets chopped, the other gets aliased.
I will first cover the signal filtering in the frequency encoding dimension and then deal with aliasing in the phase encoding dimension. Finally, I'll give one example of what can happen when the FOV is set inappropriately for both dimensions simultaneously. At the end of the process you should be able to differentiate the effects with ease. (See Note 1.)
Effects in the frequency encoding dimension
Below are two sets of EPIs of the same object - a spherical phantom - that differ only in the position of the readout FOV relative to the phantom. In the top image the readout FOV is centered on the phantom, whereas in the bottom image the FOV is displaced to the left, causing the left portions of the phantom signal in each slice to be neatly, almost surgically, removed:
![]() |
| Readout FOV centered relative to the phantom. |
![]() |
| Readout FOV displaced to the left of the phantom, resulting in attenuation of the signal from the left edge of each slice. |
Monday, November 28, 2011
Twitter. Damn.
@practiCalfMRI
I thought I could resist, I really did. (I've been off Facebook* for more than two years!) But when Neuroskeptic took the plunge in June I started thinking that maybe I should suck it up, too. I mean, Neuroskeptic blogs ten times more frequently than I do and he still has time to tweet.
Not sure exactly how it will go. I'm going to treat it as an experiment. I can guarantee that there won't be daily tweets let alone hourly ones. I'm not going to bring anyone's cellular network to its knees. But I do come across little things related to fMRI that aren't worth a full blog post. A micro-blog ought to fit the bill, eh? We'll see...
* Okay, so technically I am still on fb. I maintain an account so that I can post comments to websites, merge with other online media, etc. Turns out it's really, really hard not to have fb unless you don't mind registering separately for every online newspaper and music service yet invented. But I never actually look at my fb page, so I apologize if you have a "friend" request suspended somewhere in cyberspace.
Sunday, November 27, 2011
Understanding fMRI artifacts: "Good" coronal and sagittal data
Front, back, side to side
Now that you have an appreciation of "good" axial EPI time series data we should be able to zip through a review of "good" coronal and sagittal EPIs. This isn't the post to get deep into the reasons why you might want to acquire these prescriptions instead of axial or axial-oblique slices, but here's a short list (and some music) for you to be going on with:
Pros
There are, naturally, drawbacks to coronal and sagittal slices, just as there are for axial slices. I'll mention some of these in more detail below, as we consider the individual artifacts, but here's another brief list:
Cons
Okay then, that's the introduction over with. Let's now put aside the justification for using one prescription over another and look at what constitutes "good" data in the case of coronal and sagittal slices. The features should be immediately recognizable from what you saw in the axial data of the last post.
Pros
- coronal slices tend to exhibit less dropout of frontal and temporal lobes compared to axial slices.
- coronal slices might permit a smaller field-of-view and higher spatial resolution without signal aliasing than achievable with other prescriptions, assuming your gradient performance and other pulse sequence parameters can be driven sufficiently hard.
- sagittal slices may also show some improved signal in frontal and temporal lobes compared to axial slices, but the real benefit is the unique coverage afforded. You could acquire a single hemisphere, for instance; could be useful in a handful of situations. Alternatively, if you are interested in the whole brain, including cerebellum and perhaps even brain stem, these structures are naturally included in sagittal slices.
- sagittal slices tend to make the most common type of head motion - chin to chest rotations - an in-plane phenomenon which might lead to improved motion correction in post-processing.
There are, naturally, drawbacks to coronal and sagittal slices, just as there are for axial slices. I'll mention some of these in more detail below, as we consider the individual artifacts, but here's another brief list:
Cons
- safety limits on gradient switching (to avoid peripheral nerve stimulation) tend to force the phase encoding direction to be left-right for coronal slices, rendering the EPIs strongly asymmetric. While the absolute level of distortion may actually be very similar to that present in axial slices, the disruption of left-right symmetry can be a shock to your aesthetic sensibility.
- bizarre distortion is also a "feature" of sagittal slices where, as you'll soon see, the distortion can make the frontal lobes look like a duck's bill! But, as before, the absolute level of distortion may not be significantly different to that in axial slices; it's really the unnatural appearance that shocks us. (We ought to be just as outraged at the symmetric distortions in axial slices!)
- perhaps the biggest limitation to both coronal and sagittal prescriptions is the number of slices required to cover the entire brain in the given TR. Slicing along the longest axis of the brain, as done for coronal slices, is clearly the least efficient way to do it. The efficiency of sagittal slices falls somewhere between coronal and axial. And, of course, anything that leads to more (fixed width) slices means that TR might have to get longer. It all depends on your application.
Okay then, that's the introduction over with. Let's now put aside the justification for using one prescription over another and look at what constitutes "good" data in the case of coronal and sagittal slices. The features should be immediately recognizable from what you saw in the axial data of the last post.
Wednesday, November 16, 2011
Understanding fMRI artifacts: "Good" axial data
Good EPI data has a number of dynamic features that are perfectly normal once a few basic properties of the sample - a person's head - are considered. The task is to differentiate these normal features from abnormal (or abnormally high) artifacts and signal changes. We'll look at axial slices first because these are the most common slice prescription for fMRI. (Axial oblique slices will exhibit much the same features as the axial data considered here.)
The data we will consider in this post were acquired with a single shot, gradient echo EPI sequence on a Siemens Trio/TIM scanner, using the 12-channel head RF coil and a pulse sequence functionally equivalent to the product sequence, ep2d_bold. (See Note 1.) Parameters were typical for whole cortex coverage (the lower portion of the cerebellum tends to get cut off): 34 slices, 3 mm slice thickness, 10% slice gap, TR=2000 ms, TE=28 ms, flip angle = 90 deg, 64x64 matrix over a 22.4 cm field-of-view yielding 3.5 mm resolution in-plane, full k-space with phase encoding oriented anterior-posterior. (See Note 2 for advanced parameters.) The entire time series was 150 volumes in duration but in the movies and statistical images that follow I've considered only the first fifty volumes. (See Note 3 if you want to download the entire raw data and/or the movies and jpeg images.)
Let's start by simply looping through the volumes with the contrast set to reveal anatomy. Play this through a couple of times to familiarize yourself with it, then read on (click the 'YouTube' icon on the video to launch an expanded version in a separate tab/window):
Other than movement of the eyes and some large blood vessels in the inferior slices, at this resolution it's difficult to determine with certainty which regions are fluctuating and which are stationary. So let's zoom in on some of the central slices and replay the cine loop:
Now we can see that there's quite a bit of brain pulsation going on. Indeed, nothing appears stationary now! However, the edges of the brain don't appear to be moving very much so we can be reasonably confident that the pulsation is due to normal physiology and not a fidgety subject.
Tuesday, November 15, 2011
Understanding fMRI artifacts
Introducing the series
The workhorse sequence for fMRI in most labs is single-shot gradient echo echo planar imaging (EPI). As we saw in the final post of the last series, EPI is selected for fMRI because of its imaging speed (and BOLD contrast), not for its ability to produce accurate, detailed facsimiles of brain anatomy. Our need for speed means we are forced to live with several inherent artifacts associated with the sequence.
However, in addition to the "characteristic three" EPI artifacts of ghosting, distortion and dropout, when we're doing fMRI we are more concerned with changes over time than with the artifact level of an individual image. So, in this series we need to assess the sources of changes between images, even if the images themselves appear to be perfectly acceptable (albeit subject to the "characteristic three").
What's the data supposed to look like?
It would be rather difficult for you to determine when something has gone wrong during your fMRI experiment if you didn't have a solid appreciation of what the images ought to look like when things are going well. Accordingly, I'll begin this series with a review of what EPIs are supposed to look like in a time series. We'll look at typical levels of the undesirable features and assess those parts of an image that vary due to normal physiology. This is what we should expect to see, having taken all reasonable precautions with the subject set up and assuming that the entire suite of hardware (scanner and peripherals) is behaving properly.
Good axial data will be the focus of the first post in the series. (Axial oblique images will exhibit qualitatively similar features to the axial slices I'll show.) In the second post I'll show examples of good sagittal and coronal data. Artifacts may appear quite differently and with dissimilar severity merely by changing the slice prescription, so it's important to keep in mind the anisotropic nature of many EPI defects. Motion sensitivity is also different, of course. Motion that was through-plane for an axial prescription is in-plane for sagittal images, for example.
Ooh, that's bad. Is it...?
With a review of good data under our belts it will be time to look at the appearance of EPI when things go tango uniform. I will group artifacts according to their temporal behavior - either persistent or intermittent - and their origins - either from hardware, from the subject, or from operator error. You should then be able to understand and differentiate the various artifacts and be able to properly diagnose (and fix) them when it counts the most: during the data acquisition. Waiting until the subject has left the building before finding a scanner glitch is a bit like doing a blood test on a corpse. Sure, you might be able to determine that it was the swine flu that finished him off, either way he's dead. Our aim will be to do our “blood tests” while there is still a chance of administering medicine and perhaps achieving a recovery.
Subscribe to:
Posts (Atom)



