z-logo
Premium
Temporal characteristics of oxygenation‐sensitive MRI responses to visual activation in humans
Author(s) -
Fransson Peter,
Krüger Gunnar,
Merboldt KlausDietmar,
Frahm Jens
Publication year - 1998
Publication title -
magnetic resonance in medicine
Language(s) - English
Resource type - Journals
SCImago Journal Rank - 1.696
H-Index - 225
eISSN - 1522-2594
pISSN - 0740-3194
DOI - 10.1002/mrm.1910390608
Subject(s) - stimulus (psychology) , audiology , checkerboard , flip angle , nuclear magnetic resonance , darkness , neuroscience , psychology , chemistry , nuclear medicine , physics , magnetic resonance imaging , medicine , mathematics , optics , radiology , geometry , psychotherapist
Series of single‐shot blipped echo‐planar images with spin‐density weighting and T 2 * sensitivity (2.0 T, TR = 400 ms, TE = 54 ms, flip angle = 30°) were used to study the temporal response profiles to repetitive visual activation (5 Hz, reversing black and white checkerboard versus darkness) for protocols comprising multiple cycles of a 1.6‐s stimulus in conjunction with a 8.4‐s or 90‐s recovery phase and a 10‐s stimulus with a 20‐s or 90‐s recovery phase. Analysis of the real‐time data from all activated pixels resulted in a strong positive MRI response (mean values 3‐6%) as well as a marked poststimulus undershoot (mean values 1‐2%, duration 60‐90 s) for all paradigms. Repetitive protocols with insufficient recovery periods of 8.4 s or 20 s gave rise to a wraparound effect when analyzing time‐locked averages from multiple activation cycles. This problem may lead to an early signal decrease that originates from the ongoing undershoot of preceding activations folded back into the initial latency phase of a subsequent activation. When ensuring complete decoupling of responses to successive stimuli by using a 90‐s recovery period, the wraparound effect vanished and an initial dip was observed in one of seven subjects for a 10‐S/90‐S protocol.

This content is not available in your region!

Continue researching here.

Having issues? You can contact us here