can some say me how matlab can be used by a biomedical engineer. IN BREIF

I am a biomedical student and want to know how MATLAB can be used by a biomedical engg.

[Stephen23]

This booklist might be of interest:

http://www.mathworks.com/support/books/index_by_categorytitle.html?category=15

Answer 1

[Star Strider]

As an internal medicine physician (M.D.) and biomedical engineer (M.S.), I have used MATLAB since 1994 to model physiological and other control systems (Control Systems Toolbox), experiment design and statistical analysis of experimental data, linear and nonlinear parameter estimation and system identification (Statistics Toolbox, Optimization Toolbox, Global Optimization Toolbox, System Identification Toolbox), signal processing of EEGs, EKGs, and other signals (Signal Processing Toolbox, Wavelet Toolbox), and some image processing (Image Processing Toolbox), although I intend to do more medical image processing now that I need to learn it. I’ve also used the Neural Network Toolbox from time to time to do nonlinear classification, and I’ve experimented with the Fuzzy Logic Toolbox with physiologic control systems as well, since physiologic control systems are in fact ‘fuzzy’.

So you need MATLAB for just about everything in Biomedical Engineering. You could probably get along without it, but only if you really restricted what you want to do to your own software that you would have to write to emulate what MATLAB already does.

[pilla john venkata sai nagendra]

is it required to learn matlab programming for the image , signal processing and related stuff

[Image Analyst]

It helps. It's not required though - there are other languages or programs (e.g. ImageJ, OpenCV, Image Pro Plus, etc.) that can be used.

[Star Strider]

Yes. In order to use the toolboxes correctly (including writing the correct calls to their functions) you need to know at least the basics of MATLAB programming, as well as being able to understand matrix operations and cell arrays.

Please read the Getting Started documentation first, and experiment with the example code. Two of the more important sections in the documentation (at least in my opinion), are Cell Arrays and Array vs. Matrix Operations.

I particularly like the R2015a documentation for the fft function. With respect to signal processing, my filter design procedure is here: How to design a lowpass filter for ocean wave data in Matlab? That may help you get started with it.

Be sure to check out the File Exchange for user-contributed functions that may help you with tasks that MATLAB and the Toolboxes do not already cover.

I hope others reading this will add their suggestions as well. Since you mentioned signal processing and image processing, I added those to the subject tags, so others will see them and know those are your particular interests. You can add tags as well.

[Walter Roberson]

The pre-built applications are limited. In practice you will end up learning some MATLAB programming.

There are some commercial or non-profit image packages such as SPM (which is mostly for MRI.) On occasion I assisted people who were using SPM; to use it you might not need to be a MATLAB programmer yourself, but you had better have a MATLAB programmer on staff or available because the software is not nearly as resilient as one might hope.

[Steven Lord]

Doctor Strider,

I know this is slightly off-topic but I'm a bit curious about why you called out the release R2015a documentation for FFT. Did you call that out because you prefer that version of the documentation to the R2015b version of the doc, because you're using R2015a and so that's the version of the documentation to which you refer most frequently, or for some other reason?

[Star Strider]

Nothing is really ‘off topic’ on Answers! I’m using R2015b, and I already bought R2016. I like it because the code between the first two plot figures is easier to interpret and use in ‘real world’ applications, particularly the way the frequency vector is coded for the plot (using linspace). It’s then easy to create an index vector from it for the transformed data (as 1:length(f)). I use it as a basis of my answers here, and also refer people specifically to that code as ‘the code between the first two plot figures’. The later documentation is (to my reading) less obvious. Mayhap I’m just used to the format of the previous versions, since I’ve been using them as long as I have.