Comments and Ratings

see http://www.mathworks.com/matlabcentral/fileexchange/25929-general-dilation-code for comment

could be solved more efficiently by calling bsxfun...

A = magic(4);
An = bsxfun(@rdivide,A,sum(A,2));

When you and others experienced this problem with finding dlmwrite, than this should encourage you to take even more care to give a good documentation for your function.

A good documentation should provide an H1-line (the very first line in the help block of your function)
http://www.mathworks.com/access/helpdesk/help/techdoc/index.html?/access/helpdesk/help/techdoc/matlab_prog/f7-41453.html&http://www.google.ch/search?q=h1+line+mathworks&ie=utf-8&oe=utf-8&aq=t&rls=org.mozilla:de:official&client=firefox-a

, a good description and syntax of the function. Moreover, providing an example of the function usage is always a good help for others.

dlmwrite might be difficult to find, yet, once found, it still provides a more powerful tool than this function due to its flexibility. Still, it lacks some features such as adding header lines/column names or supporting cell arrays. I'd like to see, that you should built upon these shortcomings and include such functionalities (in case you have the time to do so).
  

"Please don't send me emails with questions because i don't have time to reply. Try to find the answer online. This function is very simple and don't need questions to be asked. "

You have no time to write emails?? Well, than you should take the time to write a proper help for this function. True, the function is simple and some people might find it useful and use it. Still, be a friendly software developer that does not force the user to look through the source code (no matter how short it is).

When this script is "better", why not update the existing LDA file? Have you never heard of the update function?

This file needs major revision. As it stands right now, it is useless. It is a script and not a function

clc
clear all
close all
clear memory

It reads an image that is not supplied with this function.

And again: Why do you repeatedly clear the variable memory that does not exist. Or does the command clear memory make sense? Correct me if I am wrong. As it stands right now, the script is only useful to you. Since there is no help, it does not even have educational purpose.

Shortest_route returns an error when called. May be you forgot to submit the Shortest_route.fig file. But, please, before you resubmit, please add a more informative help to your m-file. As it stands now, I only know from the text above, that a adjacency matrix is required.

>> Shortest_route
??? Error using ==> load
Unable to read file Shortest_route.fig: No such file or directory.

Error in ==> hgload at 43
fileVars = load(filename,'-mat');

Error in ==> openfig at 72
    [fig, savedvisible] = hgload(filename, struct('Visible','off'));

Error in ==> gui_mainfcn>local_openfig at 286
    gui_hFigure = openfig(name, singleton, visible);

Error in ==> gui_mainfcn at 159
        gui_hFigure = local_openfig(gui_State.gui_Name, gui_SingletonOpt, gui_Visible);

Error in ==> Shortest_route at 19
    gui_mainfcn(gui_State, varargin{:});

Shabab, I am somewhat surprised and disappointed. I gave an honest and careful review on your file ( http://www.mathworks.com/matlabcentral/fileexchange/22233 ) but you despise my efforts because you expected a higher rating. Well, if so, then everyone should get a perfect rating and everyone is happy, although at the cost of a decreasing quality of the FEX. I used to rely on ratings on files in order to not always have to judge myself programming correctness, efficiency etc. Well, it will turn out that I only trust FEX long-time residents like John D'Errico, Jos, us, ... who hopefully keep contributing. But that's bad for newcomers, so also for you, who deserve a chance.

I agree with Duane,
I wouldn't like to search a pdf first before being able to use a function. You?

Hi Shabab,

same happened to me once. The immediate submission of a rating by just clicking one of the stars is really annoying.

Still, I looked at your files and there are some things I want to address.

First, there are no H1-lines. This first line in your function help block is supported by the function lookfor.

Second, what is the function demireledge good for except that it passes the variables to demirel , clears the variable memory (what do you want to do with the command clear memory?), if there is any, and clears your command window.

Third, I look at the function demirel. The function syntax in the help text does not say anything of a third input variable T, which, however, is required to run the function. demirel applies edge detection to binary images, but allows for rgb images, too, by simply converting them to grayscale with the function rgb2gray and then to binary with im2bw. You should refer to this mechanism in your help text.

When you create the Kernel, you apply the variable T. What, if the user supplies a thickness of 0.1? Check the validity of this input argument.

After filtering the bw image with a cross shaped kernel, you set elements in the result Q to zero, if they are less than 1. You accomplish this by
Q([find(Q<1)])=0;
Since logical indexing is allowed, it would be totally sufficient and more effective to write
Q(Q<1) = 0;
But, do you expect any values to be below 1? Given the Kernel and the bw image, this will not occur.

Instead of line 24-27, I'd just write
h = Q>0 & ~im1;
and return h as a logical matrix.

At the end, you apply edge detection to a logical matrix. You calculate edges with specified thickness around objects previously simply identified by thresholding a gray scale image.

What is new about it to give it the name demirel edge detection detection?

No, a capacitor indipendent to time is still a capacitor with time. Imagine two capacitors walking side by side. Even without time the second walks faster than the first because their relation is point in the half. If three capacitor, this gets complicated. Because then point of half becomes point of half by half. Yours assumption is wrong. Think of relativity ... capacitor 1 divided by 2 and 3. Realize all of them are equal but with different speeds they become different. Negative velocities will remain as long as you retain your position relative to capacitor 1 2 or 3. You think you know capacitors, but you know only one. You have to beware, because all are different, some dangerous some friendly. Finding a formular of it requires classification in good or bad. But I'm sure, you find the answer. But beware, some female capacitors can be very attractive, and their boyfriend capacitors don't like see you after them.

Sometime he'll give a submission and nobody will download...