News for hackers. Stuff that matters.
Re:Air traffic failure caused by two locations 3600nm apart ... by jp57 on Monday November 18, 2024 @11:48AM (#42174194)
FYI: nm = nautical miles, not nanometers.
Re:Air traffic failure caused by two locations 3600nm apart ... by dietr1ch on Monday November 18, 2024 @12:10PM (#42174463)
Thanks, from the title I was confused on why there was such a high resolution on positions.
Re:Air traffic failure caused by two locations 3600nm apart ... by barbazoo on Monday November 18, 2024 @11:54AM (#42174260)
Given the context, I'd say NM actually https://en.wikipedia.org/wiki/Nautical_mile
Re:Air traffic failure caused by two locations 3600nm apart ... by jp57 on Monday November 18, 2024 @11:55AM (#42174279)
I was clarifying the post title, which uses "nm".
Re:Air traffic failure caused by two locations 3600nm apart ... by pvitz on Monday November 18, 2024 @02:05PM (#42175744)
Yes, it looks like they should have written "NM" instead of "nm".
Re:Air traffic failure caused by two locations 3600nm apart ... by andkenneth on Monday November 18, 2024 @03:47PM (#42176819)
No one is using nanometers in aviation navigation. Quite a few aviation systems are case insensitive or all caps only so you can't always make a distinction.

In fact, if you say "miles", you mean nautical miles. You have to use "sm" to mean statute miles if you're using that unit, which is often used for measuring visibility.

Re:Air traffic failure caused by two locations 3600nm apart ... by ianferrel on Monday November 18, 2024 @04:31PM (#42177292)
Sure but I could imagine some kind of software failure caused by trying to divide by a distance that rounded two zero because the same location was listed in two databases that were almost but not exactly the same location. In fact I did when I first read the headline, then realized that it was probably nautical miles.

That would be roughly consistent with the title and not a totally absurd thing to happen in the world.

Re:Air traffic failure caused by two locations 3600nm apart ... by scarlehoff on Monday November 18, 2024 @10:02PM (#42179719)
This is exactly what I thought q when I first read the title.
Re:Air traffic failure caused by two locations 3600nm apart ... by anigbrowl on Monday November 18, 2024 @05:02PM (#42177604)
Indeed, but you can easily imagine a software glitch over what looks like a single location but which the computer sees as two separate ones.
Re:Air traffic failure caused by two locations 3600nm apart ... by jp57 on Monday November 18, 2024 @06:41PM (#42178493)
Indeed, having locations internally represented in software with a resolution of nanometers is as ridiculous as having your calendar's internal times represented as milliseconds since some arbitrary moment more than fifty years ago!
Re:Air traffic failure caused by two locations 3600nm apart ... by rob74 on Tuesday November 19, 2024 @03:01AM (#42180982)
Yes. And, to quote the Wikipedia article: "Symbol: M, NM, or nmi". Not nm (as used in the title, but the article also uses it).
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.

Re:Air traffic failure caused by two locations 3600nm apart ... by ikiris on Monday November 18, 2024 @01:06PM (#42175073)
Nanometers would be a very short flight.
Re:Air traffic failure caused by two locations 3600nm apart ... by cheschire on Monday November 18, 2024 @04:50PM (#42177488)
I could imagine conflict arising when switching between single and double precision causing inequality like this.
Re:Air traffic failure caused by two locations 3600nm apart ... by noqc on Monday November 18, 2024 @01:12PM (#42175148)
man, this ruins everything.
Re:Air traffic failure caused by two locations 3600nm apart ... by andyjohnson0 on Monday November 18, 2024 @02:00PM (#42175695)
Even though I knew this was about aviation, I still read nm as nanometres. Now I'm wondering what this says about how my brain works.
Re:Air traffic failure caused by two locations 3600nm apart ... by lostlogin on Monday November 18, 2024 @02:18PM (#42175862)
It says ‘metric’. Good.
Re:Air traffic failure caused by two locations 3600nm apart ... by tialaramex on Monday November 18, 2024 @04:28PM (#42177260)
Indeed. There are plenty of things in aviation where they care so much about compatibility that something survives decades after it should reasonably be obsolete and replaced.

Inches of mercury, magnetic bearings (the magnetic poles move! but they put up with that) and gallons of fuel, all just accepted.

Got a safety-of-life emergency on an ocean liner, oil tanker or whatever? Everywhere in the entire world mandates GMDSS which includes Digital Selective Calling, the boring but complicated problems with radio communication are solved by a machine, you just need to know who you want to talk to (for Mayday calls it's everyone) and what you want to tell them (where you are, that you need urgent assistance and maybe the nature of the emergency)

On an big plane? Well good luck, they only have analogue radio and it's your problem to cope with the extensive troubles as a result.

I'm actually impressed that COSPAS/SARSAT wasn't obliged to keep the analogue plane transmitters working, despite obsoleting (and no longer providing rescue for) analogue boat or personal transmitters. But on that, at least, they were able to say no, if you don't want to spend a few grand on the upgrade for your million dollar plane we don't plan to spend billions of dollars to maintain the satellites just so you can keep your worse system limping along.

Re:Air traffic failure caused by two locations 3600nm apart ... by mnw21cam on Tuesday November 19, 2024 @05:02AM (#42181745)
Air pressure is reported in hectopascals and fuel quantity in kilograms (or tons). It's only in America where this isn't the case. We're still using feet for altitude in most places though (it's mainly Russia that uses metres).
Re:Air traffic failure caused by two locations 3600nm apart ... by p_l on Tuesday November 19, 2024 @05:30PM (#42188793)
Feet are "optionally accepted" due to USA being China of aviation and flooding the market with feet-marked hardware
Re:Air traffic failure caused by two locations 3600nm apart ... by rounce on Tuesday November 19, 2024 @05:24AM (#42181896)
> Inches of mercury, magnetic bearings (the magnetic poles move! but they put up with that) and gallons of fuel, all just accepted.

Here in Europe we use hectopascals for pressure, as does pretty much everywhere else. It’s important to have a magnetic bearing in case your glass dies and you’re reliant on a paper map and compass, if you didn’t plan with magnetic bearings you’d be screwed if this happened in an area of high magnetic variation.

Re:Air traffic failure caused by two locations 3600nm apart ... by jp57 on Monday November 18, 2024 @06:23PM (#42178308)
Though one could argue that the (original) definition of a meter and the definition of a nautical mile are equally arbitrary and yet similarly based.

Originally 1 meter was one ten-millionth of the distance over the surface of the earth from the equator to the pole.

One nautical mile is the length one arc-minute of latitude along a meridian. (About 1.85km).

Re:Air traffic failure caused by two locations 3600nm apart ... by lmm on Monday November 18, 2024 @09:03PM (#42179442)
They were. The difference is one is part of a standard system of units with sensible relations between different units in the system, and the other isn't; the specifics aren't what's important, the relations are.
Re:Air traffic failure caused by two locations 3600nm apart ... by eru on Monday November 18, 2024 @09:51PM (#42179662)
Yes, the nautical mile is actually les arbitrary than the 'normal' mile.

> Originally 1 meter was one ten-millionth of the distance over the surface of the earth from the equator to the pole.

Even more originally, they wanted to use the length of a pendulum that takes one second to swing. But they discovered that this varies from place to place. So they came up with the newer definition based on the size of the earth. And just like with all the subsequent redefinitions (like the one based on the speed of light etc), the new length of the metre matches the old length of the metre:

> [The] length of the string will be approximately 993.6 millimetres, i.e. less than a centimetre short of one metre everywhere on Earth. This is because the value of g, expressed in m/s^2, is very close to π^2.

The definitions matching is by design, not an accident.

See https://en.wikipedia.org/wiki/History_of_the_metre and https://en.wikipedia.org/wiki/Seconds_pendulum

If you want something less arbitrary, you can pick 'Natural Units': https://en.wikipedia.org/wiki/Natural_units

Re:Air traffic failure caused by two locations 3600nm apart ... by water-data-dude on Friday November 22, 2024 @05:11PM (#42217777)
1 foot is allllllllmost the distance light travels in a nanosecond. If we’d just adjusted the length a tiny bit it would be an excellent unit of measurement
Re:Air traffic failure caused by two locations 3600nm apart ... by jug on Monday November 18, 2024 @05:05PM (#42177635)
Yeah, I went into the article thinking this because I expected someone had created waypoints right on top of each other and in the process also somehow generating the same code for them.
Re:Air traffic failure caused by two locations 3600nm apart ... by skykooler on Monday November 18, 2024 @06:33PM (#42178424)
"Hacker News failure caused by two units 12 orders of magnitude apart sharing 2-letter code"
Re:Air traffic failure caused by two locations 3600nm apart ... by Nevermark on Monday November 18, 2024 @07:08PM (#42178709)
We better get this sorted out before open source manned Mars missions.

That all programming languages, down to statically typed assembly, don’t support something as simple to validate as unit consistency says something strange about how the science of replacing unreliable manual processes with automated systems is really bad at the practice of replacing its own risky manual processes with automated systems.

If numeric types just required a given unit, without even supporting automated conversions, it would make incorrectly unit-ed/scaled literals vastly less likely.

Re:Air traffic failure caused by two locations 3600nm apart ... by astrange on Monday November 18, 2024 @07:23PM (#42178834)
Some languages do; F# and Ada have units.

I agree no sexy languages have it, and almost all languages have terrible support or anti-support for correctness in numerical programming. It's very strange.

(By anti-support I mean things that waste your time and make it harder. For instance, a lot of languages think "static typing" means they need to prevent you from doing `int a,b; short c = a * b;` even if this is totally well-defined.)

Re:Air traffic failure caused by two locations 3600nm apart ... by KerrAvon on Monday November 18, 2024 @07:43PM (#42178978)
`short c = a * b` can be both well-defined and a serious bug if (a * b) is greater than `sizeof(short)`. Whether it _is_ a bug depends on what you're doing.

Swift has units as part of the standard library. In the sense that matters here, Rust and C++ could also have units. It requires a level of expressiveness in the type system that most modern languages do have, if you put it to use.

Re:Air traffic failure caused by two locations 3600nm apart ... by astrange on Monday November 18, 2024 @07:47PM (#42179005)
It can be a serious bug if it overflows and you didn't intend it to happen or you expected overflow behavior to do something different. But that's also true of `int c = a*b`, and yet that's not a compiler error.

int/short should be thought of as storage size optimizations for memory. They're very bad ways to specify the correct range of values for a variable.

(Ada has explicitly ranged integers though!)

Re:Air traffic failure caused by two locations 3600nm apart ... by rkagerer on Tuesday November 19, 2024 @01:52PM (#42186852)
Whenever it's vague, I include the units as part of the parameter name (eg. delay_ms). Not perfect, but for practical purposes it helps. It's simple and I'm not sure why there aren't more people/libraries doing this.
Re:Air traffic failure caused by two locations 3600nm apart ... by eru on Monday November 18, 2024 @09:53PM (#42179674)
> That all programming languages, down to statically typed assembly, don’t support something as simple to validate as unit consistency [...]

Many programming languages are flexible and strong enough support this. We just don't do it by default, and you'd need libraries.

Btw, units by themselves are useful, but not enough. Eg angular momentum and energy have the same units of Newton * metre, but adding them up is not recommended.

Re:Air traffic failure caused by two locations 3600nm apart ... by jjk166 on Tuesday November 19, 2024 @03:22PM (#42187689)
> Eg angular momentum and energy have the same units of Newton * metre, but adding them up is not recommended.

The unit of angular momentum is kg.m^2.s^-1, you're thinking of torque. Although even then we distinguish the Newton meter (Nm) from the Joule (J) even if they have the same dimensionality.

Re:Air traffic failure caused by two locations 3600nm apart ... by eru on Tuesday November 19, 2024 @08:18PM (#42189887)
Thanks, yes, I meant torque.

Well, 1 J = 1 Nm, the differentiation you mention only helps humans a bit, but would be really hard to make work for a computer.

Re:Air traffic failure caused by two locations 3600nm apart ... by jjk166 on Wednesday November 20, 2024 @12:26PM (#42196207)
I don't think it would be too difficult for a computer to handle. We already deal with situations like float(1) = int(1), it doesn't seem any harder to handle torque(1) = energy(1).
Re:Air traffic failure caused by two locations 3600nm apart ... by eru on Wednesday November 20, 2024 @08:43PM (#42200190)
The problem is that you want torque not being equal to energy.

Specifically you have:

torque = force * distance

energy = force * distance

The only difference being that in the former the farce is perpendicular to the distance, and in the latter it's in line with the distance.

A vector based system could distinguish the two, but you don't always want to deal with vectors in your computations. (And I'm fairly sure there are problems where even using vectors ain't enough to avoid this problem.)

Re:Air traffic failure caused by two locations 3600nm apart ... by krick on Tuesday November 19, 2024 @07:01AM (#42182506)
I wouldn't have guessed until I read the comments. My assumption was somebody just mistyped km and somehow nobody cared to fix it.
Re:Air traffic failure caused by two locations 3600nm apart ... by QuercusMax on Monday November 18, 2024 @03:54PM (#42176898)
Ah! I thought this was a case where the locations were just BARELY different from each other, not that they're very far apart.
Re:Air traffic failure caused by two locations 3600nm apart ... by fabrixxm on Monday November 18, 2024 @04:18PM (#42177165)
It took me a while, tbh..
Re:Air traffic failure caused by two locations 3600nm apart ... by cduzz on Monday November 18, 2024 @05:20PM (#42177735)
I was wondering; it seemed like if the to airports were 36000 angstroms apart (3600 nanometers), it'd be reasonable to give them the same airport code since they'd be pretty much on top of each other.

I've also seen "DANGER!! 12000000 μVolts!!!" on tiny little model railroad signs.

Re:Air traffic failure caused by two locations 3600nm apart ... by atonse on Monday November 18, 2024 @05:27PM (#42177785)
That's so adorable (for model railroads)
Re:Air traffic failure caused by two locations 3600nm apart ... by joemi on Monday November 18, 2024 @07:14PM (#42178751)
It's quite amusing that they used the incorrect, lowercase abbreviation for "nautical mile" which means something else ("nanometer") in an article about a major issue caused by two things sharing the same abbreviation.
Re:Air traffic failure caused by two locations 3600nm apart ... by SergeAx on Saturday November 23, 2024 @07:12AM (#42220519)
I learned navigation around 2005, and we used "nm" then. I honestly don't remember the moment when this abbreviation was granted to nanometer.
Re:Air traffic failure caused by two locations 3600nm apart ... by ainiriand on Tuesday November 19, 2024 @12:48AM (#42180393)
Exactly the first thing that came to my mind when I saw that abbreviation.
Re:Air traffic failure caused by two locations 3600nm apart ... by hughdbrown on Tuesday November 19, 2024 @01:02AM (#42180446)
Wow, I read this article because I could not understand how two labeled points on an air path could be 3600 nanometers apart. Never occurred to me that someone would use 'nm' to mean nautical miles.
Re:Air traffic failure caused by two locations 3600nm apart ... by animal531 on Tuesday November 19, 2024 @04:19AM (#42181435)
And for those like myself wondering how much 3600nm is, it is of course 0.0036mm
Re:Air traffic failure caused by two locations 3600nm apart ... by larsnystrom on Tuesday November 19, 2024 @08:54AM (#42183432)
Ah, yes, like when people put in extraordinary amounts of effort to avoid sending a millibit (mb) of data over the wire.
Re:Air traffic failure caused by two locations 3600nm apart ... by endoblast on Tuesday November 19, 2024 @10:25AM (#42184452)
We all need to stop using abbreviations, in my opinion.

EDIT: I mean the point of abbreviations is to facilitate communication. However with the world wide web connecting multiple countries, languages and fields of endeavour there are simply too many (for example) three letter acronyms in use. There are too many sources of ambiguity and confusion. Better to embrace long-form writing.