comp.lang.ada
 help / color / mirror / Atom feed
From: "counterpoint: jim carleton" <coleridge@usenet-performance-arto.rg>
Subject: Re: Boeing Begins Flight Testing F-22 Block 3S Avionics
Date: 2000/04/26
Date: 2000-04-26T00:00:00+00:00	[thread overview]
Message-ID: <8e8c15$ai3$2@ljutefisk.databasix.com> (raw)
In-Reply-To: 8e7vio$28f$10@blackhelicopter.databasix.com

This, from Axel:

>David Castrodale <anagrama@home.com> proves the law of fives:
>
>>
>>
>>Ken Garlington wrote:
>>> 
>>> "Tarver Engineering" <jtarver@tminet.com> wrote in message
>>> news:39074a04_3@news4.newsfeeds.com...
>>> >
>>> 
>>> > > Ah, now I see what's been confusing you!
>>> >
>>> > I am not in the least confused Ken and in fact it is yourself that has had
>>> > to make major modifications to your original statements to maintain any
>>> kind
>>> > of credibility.
>>> 
>>> a) Cite "major modifications"? (I know, it's a waste of bandwidth to ask for
>>> justification from a tarver generator -- sort of like asking a fart why it
>>> smells -- but I always feel obliged to make the point...)
>>> 
>>> b) If you're not confused, then I assume the strange claim that there's a
>>> sudden 5+ month slip in the F-22 schedule was just a tarver. I'll give you a
>>> double-tarver if you make it a 10+ month slip based on some random words in
>>> this post.
>>> 
>>> > > The designation "4004" refers to an _airframe_. Block 3S refers to a
>>> > > _software configuration_.  Although not all software configurations are
>>> > > compatible with all airframes, there is not a one-to-one correspondence.
>>> >
>>> > So in fact the software suite fails the first test of Ada
>>> transportability.
>>> 
>>> Actually, no. Aircraft 4001-4003 do not have a CIP (Common Integrated
>>> Processor) installed, nor do they have all of the sensors that are installed
>>> in the later aircraft. Ada's good, but no software language can compensate
>>> for missing hardware. In other words, if you select the "print" function in
>>> your favorite software package, and you have no printer, only a crazy person
>>> (Q.E.D.) would complain about the software.
>>> 
>>> > Why thank you Mr. Garlington for helping those of us at ram understand
>>> > Software,
>>> 
>>> You're quite Welcome. I know that some people have difficulty using the
>>> Internet (e.g., being unable to locate references on the Wall Street Journal
>>> website), but there's certainly no reason to be embarrassed about it. Glad
>>> to clear up any confusion about the distinction between 4001 (scheduled to
>>> be delivered in May) and Block 3.0 software (scheduled to be delivered at
>>> the end of October).
>>> 
>>> > > You may find it helpful to read the Delaney reference previously
>>> provided:
>>> >
>>> > <snip of irrelevent information>
>>> >
>>> > > * "Block 3S, is currently in testing at the AIL and initiates the sensor
>>> > > fusion and sensor tasking key to the F-22 performance."
>>> > >
>>> > > * "Block 3.0 software... will provide the full sensor fusion and weapons
>>> > > integration for the F-22."
>>> >
>>> > John
>>> >
>>> > <snip of notice of intent to fail to deliver at minimums>
>>> <snip of notice of intent to fail to deliver at minimums over the bridge>
>>> 
>>> (Cross-posted to alt.non.sequitur and comp.lang.ada, since both seem to now
>>> be relevant.)
>>
>>you have no idea what you've just gotten yourself into
>
>I'm just a truck-drivin' man.

we here at comp.lang.ada are a little weird, if you know what i mean




  reply	other threads:[~2000-04-26  0:00 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <gMAN4.2366$X55.297215@news.flash.net>
     [not found] ` <390721ce_4@news4.newsfeeds.com>
     [not found]   ` <1JHN4.122$wb7.9308@news.flash.net>
     [not found]     ` <39074a04_3@news4.newsfeeds.com>
2000-04-26  0:00       ` Boeing Begins Flight Testing F-22 Block 3S Avionics Ken Garlington
2000-04-26  0:00         ` Ken Garlington
2000-04-28  0:00           ` Kent Kinal
2000-04-27  0:00             ` Tarver Engineering
2000-04-28  0:00             ` Ken Garlington
2000-04-28  0:00               ` Kent Kinal
2000-04-26  0:00         ` David Castrodale
2000-04-26  0:00           ` Axel
2000-04-26  0:00             ` counterpoint: jim carleton [this message]
2000-04-27  0:00               ` David Kim
2000-04-27  0:00                 ` counterpoint: jim carleton
2000-04-27  0:00                   ` Axel
2000-04-27  0:00                     ` hoKEy wOLf
2000-04-28  0:00                       ` Beekeeper
2000-04-29  0:00                         ` Axel
2000-04-29  0:00                           ` hoKEy wOLf
2000-04-29  0:00                             ` Axel
2000-04-27  0:00                 ` hoKEy wOLf
     [not found]                   ` <9K4O4.919$wb7.88787@news.flash.net>
2000-04-27  0:00                     ` hoKEy wOLf
2000-04-27  0:00                       ` counterpoint: jim carleton
2000-04-28  0:00                         ` hoKEy wOLf
2000-04-28  0:00                           ` Keith Thompson
2000-04-28  0:00                       ` Beekeeper
2000-04-28  0:00                         ` David Castrodale
2000-04-29  0:00                           ` Axel
2000-04-29  0:00                             ` David Castrodale
2000-04-29  0:00                               ` Axel
2000-04-30  0:00                                 ` jim carleton (new! improved!)
2000-04-28  0:00                   ` Beekeeper
2000-04-29  0:00                     ` Axel
2000-04-28  0:00               ` Beekeeper
2000-04-29  0:00                 ` Axel
2000-04-26  0:00           ` Tarver Engineering
2000-04-26  0:00             ` Stanley R. Allen
2000-04-27  0:00         ` Marin D. Condic
2000-04-27  0:00           ` Tarver Engineering
2000-04-28  0:00             ` David Castrodale
2000-04-28  0:00             ` Ken Garlington
2000-04-27  0:00         ` Tarver Engineering
2000-04-28  0:00           ` Ken Garlington
2000-04-27  0:00             ` Tarver Engineering
replies disabled

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox