from the won't-you-be-my-neighbor? dept.
The nearest neighbor problem asks where a new point fits in to an existing data set. A few researchers set out to prove that there was no universal way to solve it. Instead, they found such a way.
If you were opening a coffee shop, there's a question you'd want answered: Where's the next closest cafe? This information would help you understand your competition.
This scenario is an example of a type of problem widely studied in computer science called "nearest neighbor" search. It asks, given a data set and a new data point, which point in your existing data is closest to your new point? It's a question that comes up in many everyday situations in areas such as genomics research, image searches and Spotify recommendations.
And unlike the coffee shop example, nearest neighbor questions are often very hard to answer. Over the past few decades, top minds in computer science have applied themselves to finding a better way to solve the problem. In particular, they've tried to address complications that arise because different data sets can use very different definitions of what it means for two points to be "close" to one another.
Now, a team of computer scientists has come up with a radically new way of solving nearest neighbor problems. In a pair of papers, five computer scientists have elaborated the first general-purpose method of solving nearest neighbor questions for complex data.
(Score: 5, Informative) by c0lo on Wednesday August 15 2018, @01:12PM (1 child)
Data-Dependent Hashing via Nonlinear Spectral Gaps [ilyaraz.org]
Hölder Homeomorphisms and Approximate Nearest Neighbors [ilyaraz.org]
(Score: 1) by khallow on Sunday August 19 2018, @01:35AM
(Score: 1, Interesting) by Anonymous Coward on Wednesday August 15 2018, @02:12PM (5 children)
and if not, why not
(Score: 2) by takyon on Wednesday August 15 2018, @02:18PM (3 children)
Why solve when you can buy?
[SIG] 10/28/2017: Soylent Upgrade v14 [soylentnews.org]
(Score: 0) by Anonymous Coward on Wednesday August 15 2018, @06:06PM (2 children)
Why buy when you can steal?
(Score: 0) by Anonymous Coward on Wednesday August 15 2018, @07:03PM (1 child)
Why steal when you can control?
(Score: 2) by fyngyrz on Wednesday August 15 2018, @10:56PM
Why control when you can simply disenfranchise?
(Score: 4, Informative) by Non Sequor on Wednesday August 15 2018, @02:40PM
Well, the graph theory version of the problem actually has intractable cases, so-called expander graphs that are both highly connected (you have to remove a lot of vertices or edges to split the graph in two pieces) and with low average degree (most vertices aren’t connected to many others).
Write your congressman. Tell him he sucks.
(Score: 5, Funny) by Kalas on Wednesday August 15 2018, @02:41PM (4 children)
When I find I'm having too much trouble sorting data sets I just send it all to /dev/null.
It may not make the boss too happy but it damn sure relieves my stress, at least until the next job hunt begins. :P
(Score: 4, Funny) by shrewdsheep on Wednesday August 15 2018, @03:35PM (1 child)
I suggest you pipe to /dev/random next time. For starters, you safe the world from global warming by providing free random numbers (they are not sorted, you said) to others. If they data is from HR or marketing, they can even be used for cryptographic purposes (undistinguishable from pure white noise). Finally, your boss will promote you for having gotten rid of his incriminating emails while simultaneously having created marketable property.
(Score: 0) by Anonymous Coward on Wednesday August 15 2018, @05:36PM
Shouldn't you wipe incriminating emails with a cloth instead?
(Score: 3, Funny) by requerdanos on Wednesday August 15 2018, @05:01PM
If /dev/null is fast I will use it... You turn it on and it scales right up.
(Score: 4, Funny) by jasassin on Wednesday August 15 2018, @10:32PM
That technique really speeds up backups also!
firstname.lastname@example.org GPG Key ID: 0x663EB663D1E7F223
(Score: 4, Funny) by bob_super on Wednesday August 15 2018, @05:25PM
Remember, folks: You need to optimize finding the nearest neighbor, so you know where to build your wall. Everyone else, you can handle with tariffs and insults.
(Score: 2) by wonkey_monkey on Wednesday August 15 2018, @06:37PM (1 child)
What about simply testing every point in turn and seeing which one is closest?
It didn't say anything about it being efficient...
systemd is Roko's Basilisk
(Score: 3, Informative) by fyngyrz on Wednesday August 15 2018, @11:09PM
As TFS indicated, data sets can differ significantly on what "near" is.
For instance, geographically near doesn't mean near by road. The other side of Ft. Peck Lake here is only a couple miles away from where I am right now... but requires almost 200 miles of driving over some of the worst roads you can imagine if you don't have a boat. You need a 4WD, a great suspension, lots of power, and should bring shovels, traction pads, and emergency food.
On the plus side, you might find a T. Rex fossil, or a Triceratops, or a duckbill, something of equal interest, while digging your 4WD out. Again. :) Not that you're allowed to pick up the big 'saur remains, but there are large geodes (I have brought back a couple of 300 lb-plus ones), and invertebrate fossils are fair game (and some of those can be huge as well.) Which makes (most) boats impractical; large rocks in a boat are a very bad idea where large waves are not uncommon. Way too easy to get "that sinking feeling."
The way I (as a user of such data in my applications) have approached this is to first triage by a radius using lat/long blocked data, then do a second level pass by road using road path data. It can still be quite a tricky process, especially when various means of access are considered, and the interim paths chosen have to comply with the various means of transport chosen.
Quite aside from the classical search problem, it's not an easy hill to climb. So to speak.