Comments and Ratings

Hi Robert, thank you for this program, it is most helpful. I have a slight problem however, when I import a 16 bit dicom file the input image on the left appears with the jet colormap. I changed line 103 to gray but now I just get a black image. Do i need to edit dislayrange somehow?

Luca, see the help for GETFRAME. The optional arguments are what you need. :)

I'm just beginning to learn image segmentation for a Masters thesis. My thesis is on remote sensing and I was told that thresholding was the way to go on this thesis. Do you have any suggestions that could narrow my research in a more directed path?

Nathan and others, thanks for all the feedback. Some users have been tripped up by the requirement that the input must be an intensity image. RGB color is not supported. I will update the function to for this at the beginning and stop immediately with a more helpful error message.

didn't work for me - I got the same errors as listed above

Nice - you can also see values for all their cmaps at:
http://geography.uoregon.edu/datagraphics/color_scales.htm

Anders, interesting suggestion. Thanks!

As used with time series, not surprisingly a NaN enters the dataset. Therefore I suggest to use the replace this line of code by:

cv = nanstd(x(:))/nanmean(x(:))*100;

This will return a result even if NaN's are included into the dataset.

Make it more explanatory. so that it could be efficient for a beginner.

very useful

i wanted a code for segmentation of brain tumor from 2D MRI images.

getting the following error in R2007

??? Output argument "hout" (and maybe others) not assigned during call to "C:\Program Files\MATLAB\R2007a\toolbox\images\imuitools\imtool.m (imtool)".

Error in ==> imtool at 155
  close_all = nargin == 2 && ischar(varargin{1}) && ischar(varargin{2}) && ...

Error in ==> imview at 18
hh = imtool(varargin{:});

Error in ==> analyze_series8 at 53
imview close all

pls send me the mat lab coding & explanation for median background subtraction &
foreground graph cut method of an image

This is very good and fast. Slightly modified, it can be used from within code to provide reflection (that is, to identify which sub-functions are defined in the code itself)! The only glitch is that it gets deceived by functions defined as follows (I sometimes use this formatting style, to have all function names vertically aligned).

function output =...
   fun(input)

I very much like the idea of a colormap designed for color blind users. Are these maps viable for all the major color blind types? I.e., both for red-green and yellow-blue blindnesses? While I believe I know the answer, and I'm sure this is discussed in the references, a note to this effect would be useful to find in the help.

One point - Matlab uses a standard I/O paradigm. When you have a function that normally returns an argument, if no arguments are provided, it just dumps that variable to the variable ans. This is standard. However lbmap fails here. When you call lbmap with no outputs, it returns an error. So if all that you wish is to look at the resulting colormap without storing it in an array, lbmap fails. This is silly, and as I said, completely against the standard paradigm. For example:

>> lbmap(10,'redblue')
??? Error using ==> lbmap at 36
Not enough output arguments.

An alternative is to use the approach used by colormap itself. If no output is supplied, then it does not return an output at all, but merely applies the specified map to the current figure.

The code itself is quite good, simply using interp1 to expand a given map to the desired granularity.

The help is good. It includes a pair of examples. One of the variables is not defined though. While I can guess that a variable called n is the number of points in the resulting color map, an explicit comment to that effect would be helpful. Does it really cost that much more for one or two more lines?

I also like that references were listed in the code.

I found error checks, an H1 line, and nice readable code. Well done in many respects.

Best