Agreed. The software situation seems to be getting more confusing by the month. AAOS builds have suddenly jumped from 3.x to 4.x and the release notes say "various fixes". Um, like what? Was there a major update to something or not?
I'm still on a AAOS 2.x release from 2023 and will not upgrade at this point.
Volvo tries to assign profiles (and Google logins) to each key so the idea is that the car is set up for you when you enter. They don't fully have it right (profiles only swap when the car is unlocked), so it's kind of pointless at the moment.
You are assuming military pilots will pay attention enough to unilaterally notice and stay clear without making mistakes. In the Dulles disaster at least, this clearly didn't happen.
With transponders on, both aircraft (via TCAS) and the air traffic controllers are able to pay attention and avoid the situation, so much better chance of catching.
This does seem insane from a civilian perspective, but I'm curious to know the military side of it. Is this totally normal and not something they worry about, or is this as crazy as it seems for everyone involved?
From what I have seen, I believe that both types of aircrafts are controlled by the same ATC. Otherwise, the two ATCs will have to coordinate among themselves to create non intersecting vectors for each aircraft - which sounds needlessly tedious. But the military does have its own ATCs in many areas. They usually separate the airspace into 'civilian corridors' and 'military corridors', each under the control of the respective ATCs. In conflict zones though, the military operates entirely under their own control. The concept of ATC becomes a bit blurred here. The aircrafts are vectored either by ship-based controllers or more frequently by AEW&CS aircrafts. This is what I assume was happening with the tanker in the story. They were near Venezuela and the Curacao ATC had no information about the tanker.
Even if the military aircraft could read the ADS-B from the commercial plane, they were flying with their night vision goggles on. It's very unlikely that they would have seen all the instruments and could very well have missed the display. And since the two aircrafts were flying approximately at right angles to each other, the warning may have been degraded. (I'm not very sure about this point though. Needs confirmation.)
I'm not working on anything at all. I'm stuck in SAFe planning meetings for the next week. I fucking hate the whole thing but they pay me to sit there and watch others play with their Miro boards, so Merry Christmas you filthy animals.
I've worked on bootloaders for multiple ARM SoCs and each one has their own charms, their own quirks, and their own hair-pulling features. I wouldn't touch Broadcom parts with a ten-foot pole but, thankfully, they don't want to work with me either so we're cool.
TI and NXP are probably the better choices. 3358/Beagle still looks for a IBM PC/MSDOS-era Master Boot Record at the start of flash when strapped the normal way, which is charming. Most allow for UART bootstrapping when nothing else is available, which is a lifesaver. I do wish more parts picked up the USB-UF2 bootloading method that Pico has created. THAT is awesome.
I worked McD in the 80s and the Coke syrup was in gallon jugs at ambient temp, then dumped into a large stainless steel holding tank at pressure. This was before bag-in-box. I've never heard of the cold temperature thing before.
My belief is that they just consume so much of it so fast that there's no time for the syrup to alter.
In that case your memory (or perhaps just attention to detail when watching) is better than mine, and I withdraw my previous belief! Thanks for the correction
They're just spooky names for simple concepts - and the article defines them on first use. If abstract algebra were a requirement, they'd skip these definitions.
Paraphrasing 'Group' from the article to see if I've understood it:
A set of elements G, and some operation ⊕, where
(g1 ⊕ g2) is also in G. // "Type-safety"
Some g0 exists such that (gn ⊕ g0) == (g0 ⊕ gn) == gn // "Zero"
For every g, there's some inverse gi such that (g ⊕ gi) == (gi ⊕ g) == g0 // "Cancelling-out"
a ⊕ (b ⊕ c) == (a ⊕ b) ⊕ c // "Associative"
If (a ⊕ b) == (b ⊕ a) then the group is also "abelian/commutative"
Is the aspirin symbol you're using as + figure, a special kind of +, or just a different looking +? What does the circle around the + mean?
I'm mentioning this, as other people in this thread are discussing "explaining symbols you use", and you're using a non-standard symbol for +. I can easily imagine a circle around + making + a different operation, and wonder if it is so?
Aspirin I've bought in the past has a + on it, and its trademark is a + within a circle. That's why I've latched on what a "common person" might view the symbol as:
⊕ is a standard symbol for this kind of math. The symbol itself is ancient because it's so simple, so I don't see what Bayer's aspirin logo has to do with it.
It acts as a normal +, mostly. When you're dealing with modulo math, the "normal" plus becomes a bit weird as there are rules attached to a number expressed as "(a + b) mod c", so mathematicians often use symbols like ⊕ to mean something like "+, but different". The second link you posted does the same, it acts sort of like normal addition, conceptually, except it's not done on actual numbers but groups.
In definitions like these, you may as well use a peace symbol or a picture of a frog; "some operation ⊕" means "there is some operation we write down like this, and it does this and that".
Another place you may find ⊕ is when it's used to represent XOR in some cases; (a + b) mod 2 is a bitwise XOR when operating on single bits (again, it means "normal addition except with weird rules", namely the mod 2 that makes you throw out anything larger than the last bit).
You can see a group and similar structures as sets of rules an object needs to follow to be considered a group or whatever. Conceptually, a group is anything that behaves like a group. It could be a dog! So, the operator can be anything you want as long as the indicated properties hold. It's like a generic API that lets you use whatever concrete type you want as long as it conforms to certain rules.
edit: What I mean is that, as a consequence, the symbol used is not really important.
I'm still on a AAOS 2.x release from 2023 and will not upgrade at this point.
reply