Best Programming Language for Medical Image Processing [closed]

Answer 1

ITK is the bee's knees of medical image processing, and that's in C++. so i guess i'd recommend C++ w/ ITK.

Answer 2

Personally, I'm a c++ and python guy, and I would probably go with c++, because this sounds like a relatively intensive project, and I do most of my best high level design in C++ (great for building fast, flexible code base), while I tend to use python for things like django, where there is less application logic, but being able to tune the function, look and feel quickly is very important. However, my choice doesn't mean it should be your choice. Here's a few things to consider:

Foremost 1) Familiarity. If you are coding production code, you want to go with something you know, and works well for you, or you'll be struggling with the language and be missing deadlines. And even when you complete the project, you are bound to have a lot of messy code for things you were learning. I'm all for learning new languages, but make it on something you can afford to screw up on.

2) Third party libraries; which ones do you want besides the one you mentioned? If they don't have wrappers, you'll be rolling your own. What you want to write your GUI in would be an example.

3) Deployment: I assume this will be an assumed windows executable. C# and C++ both do this easily, but you'll have to be familiar with py2exe if you are planning on deploying a python program without a python interpreter

Answer 3

If you can get away with python — in other words, if you know it will run fine in python, I would definitely chose it over C#/C++.

I'm sure whatever 3D library you use is built in C or C++ anyway, so interfacing with it with a high level language like python shouldn't cause a slowdown.

Answer 4

Most professional medical imaging companies use the Accusoft Pegasus PICTools libraries. They provide the fastest, and most standard compression and decompression for all DICOM lossy and lossless formats such as JPEG 2000, Lossless JPEG, JPEG-LS, and others.

IF speed is required, nothing will compare.

If you're deploying on Windows, ImageGear .NET or ImageGear Pro will give you easy-to-use environments with full support for DICOM dcm files.

You can also use ImagXpress for Windows development.

Answer 5

I agree with Todd Gardner that familiarity is probably the biggest factor determining the success of a programming language choice. So if you are much more familiar with one of those three languages than the other two (or whatever your other options are), I would recommend picking that one.

However, if you are equally unfamiliar with all of them, then I would second cloudhead's recommendation of Python. I believe it is the easiest of the three to learn and become productive in.

Answer 6

Python is getting popular for 3d visualization - several labs use it for brain imagery, for example. So it is definitely usable for that kind of problems. Library-wise, I guess you are aware than things like vtk and co can be used from python.

http://neuroimaging.scipy.org/site/doc/manual/html/faq/why.html

Of course, doing it in C++, in theory, will result in faster programs, everything else being equal (same algorithms, programmers proficient in the language, etc...) and given 'infinite time'. But python is certainly more productive than C++: in a given amount of time, you will get more things done in python than in C++, unless you are a much better programmer in C++ than in python. Also, if there is a need to interact with scientific people who are not programmers, python will be more readable than C++. C++ produced by researchers/scientific people tend to be really horrible in my experience (even worse than Fortran :) ).

The biggest problem I can foresee is if python is not fast/memory efficient enough, so that it involves a lot of constraints from an architectural point of view. I don't think it will be the case for imagery (python, as most high level languages, has scalability problems when you need ten of thousand of objects with a lot of interactions - that's one of the few areas where using C++ for a project started from scratch still makes sense IMHO nowadays).

Disclaimer: I should mention that I am involved quite a lot in the scientific python community, and that I am not an image processing specialist.