Does anybody here know anything about MRI software?

Community General Discussion
1

Particularly

  • what companies create/own/license (ect.) the software
  • what platform/languages they run on
  • what kind of hardware/firmware is required
2

If by MRI you mean magnetic resonance imaging, then the software would not run on an Arduino.

3

Does anybody here know anything about MRI software?

Probably very expensive.

4

this is all I could find.

5

Well, JEMRIS is open source, so have at it!

All you need is an MRI machine and a patient.

6

Philips Medical in the Netherlands.
Probably using C/C++ as it is one of the fastest languages.
image format, DICOM is the standard

+1 for the summary of zoomkat

7

ringringlingling:
Jemris - Wikipedia

this is all I could find.

But why are you asking this on an Arduino forum?

I know there are a lot of smart people here, but Arduino has about as much to do with MRI as politicians have to do with facts. :roll_eyes:

8

I know there are a lot of smart people here, but Arduino has about as much to do with MRI as politicians have to do with facts

Mini MRI for people with small brains? :wink:

9

Well - not the same as an MRI - but there is a "desktop CT scanner" that uses an Arduino:

http://www.tricorderproject.org/blog/towards-an-inexpensive-open-source-desktop-ct-scanner/

10

I've done first and second generation x-ray CAT back-projection software.
The trig and arithmetic isn't difficult, but there's an awful lot of it.
I was doing 256 detector views, generating a 500ish pixel diameter image, taking 30 to 240 seconds on a 68000 with a Mercury coprocessor (mostly a 100ns cycle 16x16 MAC with sequencer and a small amount of memory).
Very, very slow on an AVR, I imagine.

11

Groove:
The trig and arithmetic isn't difficult, but there's an awful lot of it.
... taking 30 to 240 seconds on a 68000 with a Mercury coprocessor (mostly a 100ns cycle 16x16 MAC with sequencer and a small amount of memory).

I wonder how well a Teensy3.1 would handle the computation - if it would fit in 256kB flash and 64kB ram. It has a 96MHz Cortex M4 with DSP instructions, including single-cycle 16x16 MAC.

Pete

12

You'd have to be able to move out large lumps of RAM to somewhere else very quickly, or that would become your bottleneck.
64k isn't a very big segment of image.
The Mercury used DMA into and out of the 68k's memory.