-
Notifications
You must be signed in to change notification settings - Fork 2
Thoughts
blindenvy edited this page Jul 21, 2011
·
5 revisions
We should change the way we calculate range inside the move function. We don't need to calculate each range every time we move. Not sure exactly how to fix this but it should be changed to improve performance.
Are we applying the evaporation factor twice for every edge because of our data structure? This may be happening in our updatePheremonesPerEdge function. I will have to look at this again when I am less tired.
At some point we may want to add some other forms of tree construct depending on the file type or diameter. Just a thought for if our algorithm seems to be under-performing in future. Specifically we may want to implement an RTC algorithm for euclidean and estein instances.