News for hackers. Stuff that matters.
Re:Air traffic failure caused by two locations 3600nm apart ... by snakeyjake on Monday November 18, 2024 @12:09PM (#42174445)
If 500 million literate and mentally well English speakers read that title, exactly and precisely 0 would think it implied nanometers.
Re:Air traffic failure caused by two locations 3600nm apart ... by jp57 on Monday November 18, 2024 @12:17PM (#42174538)
Sorry no. One interpretation, especially on this site, is that the problem was some kind of database bug, maybe where the same location was entered twice and a tiny location error ended up creating two locations.

I expect that out of any random sample 500 million literate and mentally healthy English speakers, more than 450 million of them are totally unaccustomed to thinking about nautical miles ever. Even people in science, or even who might have dealt with nanometers in school do not typically think about nautical miles unless they are sailors or airplane pilots.

Re:Air traffic failure caused by two locations 3600nm apart ... by snakeyjake on Monday November 18, 2024 @12:56PM (#42174969)
I never said anyone would assume that nm meant Nautical Miles.

I said that no normal, well adjusted, sensible, practical, literate, sane, person would assume that any distance anywhere in the world, under any context, for any reason, would be measured in nanometers.

I have used and broken some of the most sensitive measurement instruments ever built by man and even those output in microns.

Re:Air traffic failure caused by two locations 3600nm apart ... by s_tec on Monday November 18, 2024 @01:22PM (#42175291)
I assumed the post title meant nanometers. Why? Floating-point rounding bugs. A nanometer is about 9e-15 degrees of latitude, which is right about where a double-precision floating point number runs out of digits. So, if a piece of software uses exact `==` equality, it could easily have a bug where two positions 3600 nanometers apart are seen as being different, even though they should be treated as the same.
Re:Air traffic failure caused by two locations 3600nm apart ... by SilasX on Monday November 18, 2024 @03:09PM (#42176361)
Thank you. People can be very bad about judging which scenarios are truly implausible.

Here’s a previous thread where someone thought it was absurd that there could exist native English speakers who don’t regularly go shopping, and treated that supposed impossibility as a huge “checkmate”!

https://news.ycombinator.com/item?id=32625340

Re:Air traffic failure caused by two locations 3600nm apart ... by pests on Monday November 18, 2024 @02:53PM (#42176225)
I assumed nanometers.

I see it every day in chip/design/a few others. I was confused how I caused an issue with the points being so close.

I only realized NM means nautical miles only due to these comments.

Re:Air traffic failure caused by two locations 3600nm apart ... by contravariant on Monday November 18, 2024 @12:13PM (#42174493)
Well, I certainly read nanometers, but I have to admit I may not be mentally well.
Re:Air traffic failure caused by two locations 3600nm apart ... by remram on Monday November 18, 2024 @12:10PM (#42174468)
I assumed it probably wasn't nanometers but I have no idea what a nautical mile is.

Turns out 3600 NM = 6666 km

Re:Air traffic failure caused by two locations 3600nm apart ... by ortusdux on Monday November 18, 2024 @12:14PM (#42174508)
Well TIL I must be illiterate or mentally unwell.
Re:Air traffic failure caused by two locations 3600nm apart ... by moomin on Monday November 18, 2024 @12:28PM (#42174671)
The question isn't really how many would think it meant nanonmeters, it's how many would recognise it as nautical miles.
Re:Air traffic failure caused by two locations 3600nm apart ... by RandomThoughts3 on Monday November 18, 2024 @01:32PM (#42175403)
I used to work on military boats combat systems. I scanned the title, read it nanometers, thought it was weird, mentally corrected to nautical miles being familiar with the context and cursed the person who wrote the title for the incorrect capitalisation.

So, yes, people who have worked in a related field get it. Still annoying though.

Re:Air traffic failure caused by two locations 3600nm apart ... by briandear on Monday November 18, 2024 @01:12PM (#42175149)
In aviation? Literally everyone. Context clues should make it obvious.
Re:Air traffic failure caused by two locations 3600nm apart ... by ajford on Monday November 18, 2024 @01:46PM (#42175540)
And how many would assume that the incorrect unit abbreviation would mean something else? If I said Kbps and KBps, it's an entirely different unit of measure. NM and nm are VASTLY different, and unless you are already familiar with measurements in Aviation and know it's Nautical Miles, your first instinct is gonna be to read it as the unit it's supposed to be.

The article title is talking about location data and computers, I've seen many people forget floating point precision when comparing and getting bit by tiny differences at the 10^-9 or smaller. That seems just as obvious on the outset as non-unique location designations in what the average person would assume to be a dataset that's intentionally unique and unambiguous.

Re:Air traffic failure caused by two locations 3600nm apart ... by mulmen on Monday November 18, 2024 @02:32PM (#42176010)
The context is a bug. The bug could have been using nanometers when nautical miles were intended.
Re:Air traffic failure caused by two locations 3600nm apart ... by JadeNB on Monday November 18, 2024 @01:45PM (#42175528)
> In aviation? Literally everyone. Context clues should make it obvious.

But this is Hacker News, not Aviation News, and there are plenty of people, like me, who might find this interesting but aren't in aviation. I also thought it meant nanometers.

Re:Air traffic failure caused by two locations 3600nm apart ... by monktastic1 on Monday November 18, 2024 @12:31PM (#42174701)
It doesn't "imply" nanometers, it literally reads nanometers. The standard abbreviation for nautical miles is "NM."
Re:Air traffic failure caused by two locations 3600nm apart ... by sbelskie on Monday November 18, 2024 @12:34PM (#42174747)
Can’t claim to be “mentally well”, whatever that might mean, but I definitely read it as nanometers.
Re:Air traffic failure caused by two locations 3600nm apart ... by briandear on Monday November 18, 2024 @01:11PM (#42175125)
In aviation? You know how big an aircraft is right?
Re:Air traffic failure caused by two locations 3600nm apart ... by JadeNB on Monday November 18, 2024 @01:47PM (#42175547)
> In aviation? You know how big an aircraft is right?

Exactly, which makes the headline particularly intriguing—how could a 3600 nanometer difference matter? The standard resolution, which I pursued, is to read the article to find out, but it doesn't mention the distance at all.

Re:Air traffic failure caused by two locations 3600nm apart ... by ajford on Monday November 18, 2024 @01:40PM (#42175473)
I too first read it as nanometers. Perhaps it's just those with engineering/science backgrounds who have far more experience with nanometers than nautical miles?

I've never had cause to see the abbreviated form of nautical miles, but I know nanometers. Also, given purely the title I could see it being some kind of data collision due to precision errors between to locations that should be the same airport but perhaps two different sensors.