On Thu, 18 Dec 2003 20:53:21 GMT, "Kevin Brooks"
wrote:
"phil hunt" wrote in message
. ..
On Thu, 18 Dec 2003 05:26:01 GMT, Kevin Brooks
wrote:
I think there are two issues here. The first is when the sensor is
attached to the weapon, as it is in a sensor in a missile. Here,
there is no sensor/shooter cycle, unless you choose to have a human
involved in the decision to fire.
That is way beyond even our capabilities. You are talking autonomous
combat
systems.
Yes. The progrsamming for this isn't particularly hard, once you've
written software that can identify a vehicle (or other target) in a
picture. It's just a matter of aiming the missile towards the
target.
"The programming for this isn't particularly hard"? Gee, one wonders why
only one nation has to date fielded a system that even verges on that kind
of capability. And as to it being "just a matter of aiming the missile
towards the target..." uhhhh...yeeeah, if you consider "just" including
developing a navigational system that also supports its own survivability
(i.e., is able to negotiate a route to the target down in the weeds),
knowing where the target is in the first place and getting that data to the
firing point realtime, and provided that you target just happens to match up
with what is loaded in the missiles brain (Missile: "I am looking for a
tank...tank..tank..." as it flies across twenty light skinned trucks loaded
with dismounts). You are REALLY lowballing the estimate of how much R&D is
required to field such a semi-autonomous weapon. Ever wonder why you are
just now seeing such technology emerging in the US military (and hint--it
ain't because of our "bloated" defense industry)?
The first design of this sort that I read about was the WASP design
of the 1980's, where you would get a pod of 12 missiles with
millimetric gudience that would be launched to go after Russian tank
swarms. It was supposed to be low cost and hard to spoof.
I'm assuming that either A. low cost or B. hard to spoof or C.
worked at all, proved to be the stumbling block.
|