4 ms·
The fact that the prop controls could be split but the UI would not gray out the sliders on the screens that did not have control is a poor user interface desig
by userbinator 7y ago
The fact that the prop controls could be split but the UI would not gray out the sliders on the screens that did not have control is a poor user interface design choice. If the controls only appeared "active" on the screen they were transferred too this could have made things much more simple.
This reminds me of the Airbus control sticks, where the systemd averages the two inputs if e.g. one pilot pushes forward while the other pulls back. There is a warning but it can be easily ignored, as happened on https://en.wikipedia.org/wiki/Air_France_Flight_447 https://en.wikipedia.org/wiki/Air_France_Flight_447 .
Also, I suspect there may have been at least one person who raised the idea of disabling/graying out the controls if they're inactive, but it was not listened to or even actively opposed because "it's not in the spec" and the one who brought it up didn't have the power to do anything about it. I've worked in environments like that (thankfully not for long) enough to know that these big and highly bureaucratic projects will tend to have lots of "lack of common sense" problems, either because no one bothers to actually think about what they're trying to do, or the division of labour was so fine that no one could. Lots of process, lots of specification meetings, lots of cargo-culting dogma, but no real thought put into anything. The fact that such developer positions are treated as disposable and easily replaceable probably adds to the problem too.
- stallmanite 7y ago> This reminds me of the Airbus control sticks, where the systemd averages the two inputs Now I’m starting to understand the hostility towards systemd.
- arminiusreturns 7y agoAs someone who has been on both sides of the systemd debate, I heartily guffawed at this. Thanks. As for the topic at hand, at a 30k ft view, having seen the inside of DoD stuff from a ground troop level, and later from DC itself, I mostly blame the good-old-boy network from being too established and greedy. I figure it's always been this way and technology complicating things has just pulled the curtain back, but essentially they do DC/Virginia back-room dealing to get bids and then under-perform in the delivery but don't really care because DoD's budget is massive and they keep throwing money at them. This matters much less while we engage countries that can't engage back like Iraq and Afghanistan, but as we shift more towards the return of the tri-polar world and DoD has to start planning for more peer level agitation, these problems need to be fixed ASAP or people are going to die. There is a reason a handful of counties in Virginia had the highest growth of millionares in America post-9/11. I'm tired of contractors wasting money while the real military gets shite, and while maybe some of that is bias from my Marine Corps days (The Corps was notorious for "hand-me" down equipment and small budgets compared to Army, etc), I still say it's about time we financially body checked the good old boys and gave our boots on the ground better treatment. Hell, how about just not having boots on the ground in the first place in unconstitutional bullshit wars, but I digress.
- mannykannot 7y agoI have never understood why averaging the stick inputs makes any sense (who is controlling the aircraft in that case?) In this case, I see that the ship's left and right power controls were transferred from one station to another one at a time. Regardless of whether, in the system's byzantine command structure, there was a way to transfer them together, the fact that they could be transferred individually suggests that someone thought there was a scenario where it made sense to have two different people, possibly in widely separated places, handling the two sides of this function. perhaps someone could enighten me as to the scenarios in which that is useful?
- deleted 7y ago[deleted]
- jki275 7y agoThe general use case is Helm controlling the rudders on the left and Lee Helm controlling throttles on the right. They're two separate functions, and while they require coordination to run effectively they don't have to be the same person or the same station or even in the same room. That's actually the normal mode of operation (split responsibility between Lee Helm on the right and Helm on the left) on a CVN (which uses a very similar system, although with a larger console). It has the ability to control both functions from one side of the console, but that's not the normal mode of operation. If the bridge ceases to exist, then steering could be controlled from aft steering (directly above the rudders) and throttles from engineering central control (engineering owns the engines). That's a canonical thing, it's the way it's always been -- you have redundancy in those places for many obvious reasons for a warship.
- mannykannot 7y agoThanks for your informative reply, but if I am following what you are saying, the Lee Helm is normally controlling all the trottles, and responsibility for port and starboard throttles is not normally split between two people? - though I take your point that, in the case of damage, there might be no single console capable of controlling both the port and starboard power, so I can see why complete flexibility in the assignment of controls to consoles would be a requirement.