My understanding of an MRI is that it takes a cross-section image of your body and pieces it back together digitally. So it’s not exactly taking an instant snapshot, but instead is compositing several images taken over a duration of time.
Now, if your heart is pumping during the scan (which I’m hoping it does), then wouldn’t the size of the heart vary between each image?
Do they do something to account for this in the software, or do they physically do something during the scan?
In: 35
I’ve worked on this a little. It’s usually a combination of gating and superresolution.
**Superresolution** — MRI scanners get faster at lower resolutions. You can do a very low res or small volume scan in less than 100 milliseconds, which is fast enough to freeze most heart movement.
You can’t see much in these very low res images, so instead you take 100s of them, with slight movement of the scanner each time, and then reconstruct a high-res image from all the low res images. The image reconstruction techniques in modern video games work a little like this.
**Gating** — you attach a heart monitor and note the exact point in the heart cycle of each tiny scan you make. When you want to reconstruct the final movie, you put all the tiny scans into maybe 32 buckets, with one bucket for each 50ms period of the cycle, and then do the superresolution reconstruction on just the scans in that bucket. Put the 32 final images together and bingo, you have a movie you can loop.
People have experimented with extra techniques, like estimating motion vectors to remove movement and increase sharpness, but I don’t know much about that. No doubt you could use ML to help as well.
tldr: the movies you see are composites of many, many heart cycles recorded over a long period of time.
Latest Answers