Re:ML Basics: K Nearest Neighbors in Ruby
by aub3bhat on Thursday September 14, 2017 @04:03PM
(#15251990)
Umm that's a beautiful theoretical result no doubt. But in practice the choice of the "space" that determines the neighborhood, matters more than anything else on the top of that space. Also as another commenter pointed out the result is applicable when infinite labeled samples are present, which is almost never.
IMHO the reason Machine Learning is NOT Stats or Information theory because these beautiful fundamental result were found to be futile in practice.
Re:ML Basics: K Nearest Neighbors in Ruby
by taeric on Thursday September 14, 2017 @12:13PM
(#15249432)
This feels like a more significant result than it appears to get. I'm guessing the problem then comes down solely to defining a distance metric that you can easily/quickly evaluate? Or is this merely the upper bound and many folks do markedly better nowdays?
Re:ML Basics: K Nearest Neighbors in Ruby
by highd on Thursday September 14, 2017 @12:26PM
(#15249552)
The result is in the large sample limit, which is pretty much never the case for high dimensional datasets like the ones most popular for ML these days (images, audio, text). It doesn't mean what the parent thinks it means.
Re:ML Basics: K Nearest Neighbors in Ruby
by apathy on Thursday September 14, 2017 @11:07PM
(#15254277)
You are proposing that a reduced dimensional projection of a large dataset cannot approach this limit?
I.e. expose the underlying low rank of nearly any huge sparse data matrix with an SVD or NMF. Enable fast recovery with a shitty (CS-wise) hash function. Recover most of the information about an observation's neighbors in a fraction of the time taken by many other approaches.
What's popular for ML benchmarking these days is not necessarily the same as what's needed for a specific application. It's a useful proof to keep in mind before prematurely optimizing with overly complicated approaches.
Re:ML Basics: K Nearest Neighbors in Ruby
by highd on Friday September 15, 2017 @12:13AM
(#15254580)
You are of course free to try simple dimensionality reduction and nearest neighbors, and if that works on your problem that's fantastic. To the research community, though, problems where approaches like that work were considered "solved" decades ago. And of course, in industry, if there's a chance of that working it's tried. But no one's building self driving cars with PCA and LSH.
When Cover & Hart proved that the error for k-NN classification is no worse than twice the Bayes (optimal) error, "machine learning" as a phrase had not yet been observed in the wild.
http://ieeexplore.ieee.org/document/1053964/
EE, CS, stats -- these are your fundamentals...