Even outside Buell, which was a bit of a neither-fish-nor-foul anomaly, they've had the odd innovative model here and there--the V-Rod comes to mind. And I've seen some interesting things in their ABS systems and some other components. But I think the most successful models have been very conservative about their drivetrain as it's part of their signature sound/feel.
My hope is that Polaris' recent critical success with the Indian Scout (which I bought over HD--far better bang for buck than a Sportster) gives the segment a kick in the ass.
Buell had some great innovative designs too, but you could tell that was all Erik and not the motor company. I wasn't surprised when the split happened.
What I found did not convince me that it would fare better than an off-the-shelf (somewhat) non-interpretable statistical supervised learning algorithm.
It can be a nice way of bootstrapping the rule writing process, or to go the other way : to discover and analyze new expert knowledge by looking at the rules.
But performance-wise, I would go the machine learning way anytime.
Also, Inverse Reinforcement Learning seems to be very promising : one guesses the reward function by observing the expert acting.
For example, a very specific condition can either mean that this particular condition is useful, or that simply the training data happened to have those particular instances of a more general condition - and a human expert can usually easily decide which rules need to be extended for proper generalization beyond your training data, but the automated generation helps identify factors that the expert could recognize, but wouldn't think of if doing it themselves from scratch.
The plus side is that it allows you to make systems that can be tweaked using trial and error to handle cases that would require very complex logic otherwise. The down side is that alot of the time the systems aren't provable the way other types of logic are, and they can be a pain to debug.
It is very hard to ask for management to trust a system they know nothing about, where they have literally no control over final behaviour, even if in the end it will perform better overall. In a rule-based system, instead, it is always possible to make adjustments and blame mistakes very efficiently to specific causes.
I guess this is the main reason why "true" AI is currently being used mostly in information fields, rather than on physical machines and engineering. No-one would know how to deal with the outcome of a fuzzy learned algorithm making the wrong decision. This is also a reason why autonomous cars are very interesting to me, even though I bet they are still full of ad-hoc rules in order to have a layer of "manageability" over the overall system.
Air combat is also one of those areas which does notionally have narrowly computable victory parameters - given hardware of capabilities X, there is a model we don't know which should generally predict the outcome.
If it ends up like thousands upon thousands of if statements then you got it wrong (or so I think).
Getting it right IMO means realizing that rules are not necessarily source code but often data to be iterated over, filtered etc.
This is a form of metaprogramming that can be practiced even in Java ;-)
When an expert system beats some human in a complex real-life problem the comments are about how it is narrow, boring, not sufficiently tested and ultimately doesn't matter.
When a neural network (with the help of MCTS and an entire data-center full of servers) beats some human in a board game the comments here hype it through the roof and jump to conclusions about the coming dawn AGI.
I think it's because only recently has AI been in the news again and it's been the news thanks to machine learning and neural networks in particular (and more specifically, deep learning). The last time there was a big todo about AI was in the '90s and most people writing here were probably not old enough to figure out what the hell was up back then.
Er, I'm not dating myself here. I know about those things out of happy accident (maybe a story for another time). Most people who graduated from CS in the last five or six years will not have heard anything about expert systems and GOFAI, except that it failed etc, if that.
Then along comes Google and promises it can make your phone talk to you. People are intrigued.
But of course, those who don't know their history are doomed to repeat it.
The fighter jet AI technique is hard-coded to a very specific problem domain, and could only be reproduced in a different problem domain by doing it from scratch.
The technique used by AlphaGo is at least closer to the idea that we can eventually build generically trainable machines that can learn to do a variety of tasks, without having to code them from scratch every time.
So are machine learning models, ultimately. Although the algorithms that build the models have more general application, once you train a model on a certain set of data, that model can only ever be used in the domain circumscribed by the data. They're one-trick ponies, yes?
>> we can eventually build generically trainable machines that can learn to do a variety of tasks, without having to code them from scratch every time.
We would however have to train them from scratch every time, for each separate task, and each time we'd need terabytes of data and megawatts of power.
AlphaGo has several handcoded training features, uses Monte-Carlo tree search, and was primed by a huge human-made dataset. It's not like it can be throws at other problems without heave re-engineering.
Human pilots are limited in maneuvering by the amount of force their body can take. Computer pilots are limited by the amount of force the airframe can take. The later allows much more aggressive and radical maneuvers.
That means, compared to playing Go, the robot pilot can be comparatively much worse than the human and still win decisively by taking advantage of high g maneuvers.
In simulation, the algorithms demonstrated for doing this do quite well with, being able to complete the mission with a success rate of 97.5%, so long as one has 6 search robots and 3 gun robots.
This did not work so well in real life, partially because real robots are difficult to do with. It is still disturbing though because of the high success rate, not to mention the immediate applicability to robot SWAT teams. As a civilian, I'd be much more concerned with a SWAT AI than a fighter jet AI.
However, robot swat teams are still a ways off.
[0]http://singularityhub.com/2010/03/19/teams-of-military-robot... [1]https://en.wikipedia.org/wiki/Multi_Autonomous_Ground-roboti... [2]http://www.frc.ri.cmu.edu/~ssingh/Sanjiv_Singh/PUBS_CONF_fil...
Maybe one day war will be less about killing people, and more of a battle between countries' best engineers.
Maybe I'm just optimistic, but I think robot wars would be a hell of a lot better than real wars.
When two robots fight each other, it's not because the other robot is the target, it's because it's an obstacle between them and the human targets that will actually affect the war.
That is of course assuming that the most efficient strategy to achieve a surrender doesn't actually end up being a bypass of enemy AI and direct targeting of human populations. This would only be possible if there's a huge mismatch between offensive and defensive capability. But then you end up with a MAD situation similar to what we have with nukes.
That said, I expect that the flip-side is that this tech would ultimately make a guerilla war by a local population against an occupying force very very ugly for the guerillas.
So it boils down not to robots killing robots, but robots killing humans, while other robots try to stop them.
(That said I'm less optimistic I guess.)
Well, why should it? No one is inventing HAL-like AI anytime soon, or ever. If this system does a better job of killing the enemy than human pilots then its quite the breakthrough. Projecting air power is one of the ways countries keep aggressors away and this would be quite an advantage for variety of reasons. Not the least of which means you can now design AI driven fighters that have zero design compromises to keep human pilots alive.
I imagine fighter engagement consists of a fairly limited set of problems to solve. Think of this as just a souped up autopilot/autoland system, except with guns and missiles. We're not asking the AI to write the next Romeo and Juliet here.
>because the paper is very light on details
Defense contractors aren't known for sharing details. I imagine this is a competitive advantage and they want to keep their cards close to their chest. There may even be national security issues here.
Because what is trumpeted as a breakthrough may in fact be so narrow in scope that it may not even be possible to use it in a flight combat video game without a lot of work, let alone any real life environment.
It is absolutely, very closely tied to the mathematical model of aerial combat that they devised and can not easily be made to accommodate new insights, or new challenges.
What? They were quite literally running the AI in a simulator -- ie, a very expensive video game. The only thing that might not scale is the computational power necessary to execute.
Learning approaches which depend on mass-simulation are great when your problem only ever exists in a "virtual" context, but what happens when you want to take your trained neural network out into the real world? Clearly it's going to have to adapt to the differences between the real world and the virtual world - but how would you do that? You can't run millions of dogfights in the real world to adjust its training.
?
For small scale problem where most of the variables are well understood, this kind of approaches work beautifully. Big problem are better tackled by a more generic approach (maybe with some ad-hoc adaptations, such as mixed approach between expert systems and statistical algorithms, feature engineering, etc.) because these approaches will be more resilient to an exposure to the real world, and the manpower invested in them is useful in more than one problem domain.
To address your last point, there is an extensive body of work on data-scarce environments. I've even seen a talk about applying reinforcement learning to endangered species preservation, where you only get a single digit number of interaction with the system !
But the decision tree is much more tractable, thus the longer it's kept on this format, the more future-proof is the work.
This makes (clever) use of hundreds, if not thousands, man hours of painstakingly entering expert rules if the form IF <some input value is above or below some threshold> THEN <put some output value in the so and so range>.
The mathematical model of Fuzzy Trees is nice, but this is completely ad-hoc to the specific modelization of the problem, and will fail to generalize to any other problem space.
This kind of techniques has some nice properties (its "reasonings" are understandable and thus kind of debuggable and kind of provable, it smoothes some logic rules that would otherwise naively lead to non smooth control, etc.) but despite the advances presented here that seem to make the computation of the model tractable, I don't see how it could make the actual definition of model anywhere near tractable.
Also, I dislike having to wade though multiple pages of advertising before I can find the (very light) scientific content.
-- Edit: I realize I am very negative here. I do not mean to disparage the work done by the authors. It's just that the way it is presented make it sound way more impressive than it is. It's still interesting and novative work.