Click here to Skip to main content
14,599,112 members
Rate this:
Please Sign up or sign in to vote.
See more:
i have a program which is used for dijkstra algorithm..its working correctly but there is a problem in this application.
it can find the shortest path.
Node Count : 6 (0,1,2,3,4,5)

my program can find shortest path between from 0 to 5 but it cant find between 4 to 5, 2,5 or 1,4...etc..
is there anyone to help for tht?

for (i = 1; i < sayac; ++i)
             EKM[i] = ebas;
             ead = 0; 
         for (i = 0; i < sayac; ++i)
             for (j = 0; j < sayac; ++j)
                 if (elealindi[j] == 0)
                     if (graph[ead, j] != -1) 
                         if (EKM[j] > graph[ead, j] + EKM[ead])
                             EKM[j] = graph[ead, j] + EKM[ead];
                             System.String.Concat(ROTA[j], ROTA[ead]);
                             ptr = ROTA[j];
                             while (ptr == null)

                             ptr = Convert.ToChar('A' + ead);
                             Label2.Text = Label2.Text + "  " + ROTA[j];
             ek = ebas;
             for (j = 1; j < sayac; ++j)
                 if (elealindi[j] == 0)
                     if (EKM[j] < ek)
                         ek = EKM[j];
                         ead = j;

             elealindi[ead] = 1;

What I have tried:

Finding the shortest path from one node to another node..
Updated 11-Jul-16 12:22pm
Rate this:
Please Sign up or sign in to vote.

Solution 1

Compiling does not mean your code is right! :laugh:
Think of the development process as writing an email: compiling successfully means that you wrote the email in the right language - English, rather than German for example - not that the email contained the message you wanted to send.

So now you enter the second stage of development (in reality it's the fourth or fifth, but you'll come to the earlier stages later): Testing and Debugging.

Start by looking at what it does do, and how that differs from what you wanted. This is important, because it give you information as to why it's doing it. For example, if a program is intended to let the user enter a number and it doubles it and prints the answer, then if the input / output was like this:
Input   Expected output    Actual output
  1            2                 1
  2            4                 4
  3            6                 9
  4            8                16
Then it's fairly obvious that the problem is with the bit which doubles it - it's not adding itself to itself, or multiplying it by 2, it's multiplying it by itself and returning the square of the input.
So with that, you can look at the code and it's obvious that it's somewhere here:
private int Double(int value)
   return value * value;

Once you have an idea what might be going wrong, start using the debugger to find out why. Put a breakpoint on your line:
for (i = 0; i < sayac; ++i)

and run your app. Think about what each line in the code should do before you execute it, and compare that to what it actually did when you use the "Step over" button to execute each line in turn. Did it do what you expect? If so, move on to the next line.
If not, why not? How does it differ?

This is a skill, and it's one which is well worth developing as it helps you in the real world as well as in development. And like all skills, it only improves by use!

Yes, I could probably tell you what "the problem" is - but it's not difficult to do this yourself, and you will learn something really worthwhile at the same time!
BillWoodruff 12-Jul-16 6:22am
"Think of the development process as writing an email"

That is memorable :) ... and left me wondering what per-cent of my code is spam.
OriginalGriff 12-Jul-16 6:36am
In your case, none!
In some of our members case's 100% ...
Me? I'm about 10% spam due to banging on about AOMEI Backuper :laugh:
Rate this:
Please Sign up or sign in to vote.

Solution 2

its working correctly but there is a problem in this application.
Problem mean that the app don't work correctly.

Your code snipset us not usable, it use things we don't know and I don't see how you tell start and end points toy want.

My only possible advice is debugger.

The debugger allow you to follow the execution line by line, inspect variables and you will see that there is a point where it stop doing what you expect.
Debugger - Wikipedia, the free encyclopedia[^]
Mastering Debugging in Visual Studio 2010 - A Beginner's Guide[^]

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

CodeProject, 503-250 Ferrand Drive Toronto Ontario, M3C 3G8 Canada +1 416-849-8900 x 100