z-logo
Premium
Simultaneous MRI tagging and through‐plane velocity quantification: A three‐dimensional myocardial motion tracking algorithm
Author(s) -
Kuijer Joost P.A.,
Marcus Tim,
Götte Marco J.W.,
van Rossum Albert C.,
Heethaar Robert M.
Publication year - 1999
Publication title -
journal of magnetic resonance imaging
Language(s) - English
Resource type - Journals
SCImago Journal Rank - 1.563
H-Index - 160
eISSN - 1522-2586
pISSN - 1053-1807
DOI - 10.1002/(sici)1522-2586(199903)9:3<409::aid-jmri8>3.0.co;2-d
Subject(s) - displacement (psychology) , tracking (education) , plane (geometry) , magnetic resonance imaging , motion (physics) , physics , match moving , algorithm , artificial intelligence , mathematics , computer science , geometry , medicine , radiology , psychology , pedagogy , psychotherapist
A tracking algorithm was developed for calculation of three‐dimensional point‐specific myocardial motion. The algorithm was designed for images acquired with simultaneous magnetic resonance imaging (MRI) grid tagging and through‐plane velocity quantification. The tagging grid provided the in‐plane motion while the velocity quantification measured the through‐plane motion. In four healthy volunteers, the in vivo performance was evaluated by comparing the systolic through‐plane displacement with the displacement of tagging‐grid intersections in long‐axis images. The correlation coefficient was 0.93 ( P < 0.001, N = 183). A t ‐test for paired samples revealed a small underestimation of the through‐plane displacement by 0.04 ± 0.09 cm (mean ± SD, P < 0.001) on an average displacement of 0.77 ± 0.23 cm toward the apex. The authors conclude that three‐dimensional point‐specific motion tracking based on simultaneous tagging and velocity quantification is competitive with other methods such as tagging in mutually orthogonal image planes or quantification of three orthogonal velocity components. J. Magn. Reson. Imaging 1999;9:409–419. © 1999 Wiley‐Liss, Inc.

This content is not available in your region!

Continue researching here.

Having issues? You can contact us here