Hello all,
Just a quick question. Would anyone know where I might could find a tutorial on Nearest Neighbor with C++? I've searched extensively over the internet for the past month and a half and have been unable to find anything. I find plenty of programs out there written for it but I dont want to rip their stuff off. I want to understand it. If there is a book that would be helpful I would also like to know that as well.
By "nearest neighbor" do you mean a graph algorithm?
if you need help with graph algorithms, i preemptively suggest robert sedgewicks "algorithms in c++: volume 5"
.sect signature
Yes I am inquiring about a graph algorithm. Thank you for the suggestion ggs, I will definitley look into that book.
>>Yes I am inquiring about a graph algorithm.
I received a great many hits from a search on www.google.com. How many were relevant I am not sure, though most of them appeared to be what you are looking for including implementations in C++.
CheyenneWay:
Princeton:I find plenty of programs out there written for it but I dont want to rip their stuff off.
most of them appeared to be what you are looking for including implementations in C++.Just thought I'd point out the irony...
Just Google It. √
(\ /)
( . .)
c(")(") This is bunny. Copy and paste bunny into your signature to help him gain world domination.
>>I find plenty of programs out there written for it but I dont want to rip their stuff off.
I honestly missed that. Though reading code so that you might understand the algorithm better and develop your own implementation is hardly a "rip off", it is a valuable and enriching practice. Most algorithms are in the public domain as well, so it is only a rip off if you copy large portions of an implementation without permission and call it your own. Reading for comprehension is a good thing and I encourage it. Reading for plagiarism is not a good thing.
My answer remains the same despite not reading the question in its entirety.
exactly, what you should do is the followiing:Most algorithms are in the public domain as well, so it is only a rip off if you copy large portions of an implementation without permission and call it your own.
1) read several implementations and try to understand the differences and their effects on the systems integrity/efficiency/etc.
2) write your own implementation. If you followed step one appropriately, you should be able to go pretty far without using a reference every minute.
3) include in you documentation a little "thank you" section which includes the works you referenced to complete your work.
there used to be something here, but not anymore
