mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Peter T. Breuer" <ptb@it.uc3m.es>
To: "linux kernel" <linux-kernel@vger.kernel.org>
Subject: Re: Non-GPL modules
Date: Thu, 18 Oct 2001 17:40:08 +0200 (MET DST)	[thread overview]
Message-ID: <200110181540.f9IFe8S24810@oboe.it.uc3m.es> (raw)
In-Reply-To: <Pine.LNX.3.95.1011018110604.802A-100000@chaos.analogic.com> from "Richard B. Johnson" at "Oct 18, 2001 11:21:38 am"

"A month of sundays ago Richard B. Johnson wrote:"
> On Thu, 18 Oct 2001, Peter T. Breuer wrote:
> 
> > "Richard B. Johnson wrote:"
> > > We have a data interface that feeds high-speed data from 4,000 +
> > > X-Ray detectors directly to memory at RAM/Bus memory speeds. There
> > > is no way in hell that we are going to let the world know how this
> > 
> > Oh my gosh. You aren't working on a project for CERN too, are you?
> 
> No. Amongst many other things, we make the "Exact" baggage scanners
> market by L3 division of Lockheed-Martin. All airplane baggage

Well, in that case, you may find that there _IS_ prior art. The
triggers for the LHC at CERN are PCI boards running to linux (or
solaris) machines.  I seem to be involved in projects to take the data
off at about 13GB/s (as far as I recall the back of envelope).  The
first ring is about 1000 machines in the current design, I believe.

> will eventually be scanned (at baggage-conveyor speeds) at all
> airports serving commercial airliners. The scanning detects
> various devices and chemical compounds. It uses X-Rays of different
> frequencies (hardness) to actually detect chemical compounds
> at their elementary atomic levels.

The CERN stuff gets about 6000 particle traces per collision. Each
particle marks several detectors in a sandwich, and the raw data (lots
of bytes per sandwich layer) is taken off and the trajectories and
timings for each trace are computed. Essentially "digital Xray
detection". I forget what the collision rate is at the target. High
enough that the events aliase.

> For instance, most X-Ray systems only detect density. The X-Ray
> density of a jar of peanut butter is similar to the density of
> the explosive C4. Without chemical discrimination, anybody with
> a jar of peanut butter in their luggage is suspect. However,

I suspect them anyway. I've never seen anything in peanut butter.

> by using dual-energy, we can zero in on nitrogen, while allowing

?? You mean the nitrogen in the explosive?

> the same-density substances containing other atoms.

[to go through]

> We do this in an incredibly fast hardware/software environment
> so that baggage runs through the machines at normal conveyor
> speeds, not slowing down the loading/boarding process.

I've news for you .. the passengers were already slowed down by the
visual Xray inspection as they came in, and as there are on average one
piece of hold baggage  per passenger, the bottleneck is at passenger
entry to the airport!

> This is NOT the scanner used to X-Ray carry-on luggage. That
> uses a much less robust and cheaper process because there
> are attendants present that can ask that suspect carry-on
> luggage be opened for inspection. 

But it seems to be the bottleneck. I imagine most airports have about 4
carry-on scanners, and each passenger takes 60s to go through, so you
cannot have an overall _average_ flow of more than about 4 pieces of
_hold_ baggage per minute to deal with.

Granted, the peaks might be higher, as they are bottlenecked by the
checkin desks. There may be about 100 of those, and each passenger
probably takes 3mins at them, so the flow can peak at about 33 hold
bags per minute (at 1pc/passenger). But there must be long intervals
of low activity because of the average flow calculation.

> Presently, we are using DEC/Alpha machines for the hardware/software
> interface. Our next generation will use PC/AT/Linux machines for
> the same function (at twice the performance).

I see.

Peter

  reply	other threads:[~2001-10-18 15:40 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-18 13:15 Richard B. Johnson
2001-10-18 13:38 ` Adrian Bunk
2001-10-18 13:58   ` Richard B. Johnson
2001-10-18 14:11     ` Ben Collins
2001-10-18 14:46       ` Richard B. Johnson
2001-10-18 14:53         ` Peter T. Breuer
2001-10-18 15:21           ` Richard B. Johnson
2001-10-18 15:40             ` Peter T. Breuer [this message]
2001-10-18 16:40               ` Jan Niehusmann
2001-10-18 17:02         ` Martin Dalecki
2001-10-18 17:16           ` Ben Collins
2001-10-18 17:15             ` Martin Dalecki
2001-10-18 18:06               ` Mark Hahn
2001-10-18 14:06   ` Ben Collins
2001-10-18 14:04 ` M. R. Brown
2001-10-18 14:31   ` Jesper Juhl
2001-10-18 14:37 ` Martin Donnelly
2001-10-18 14:50   ` Arjan van de Ven
2001-10-18 15:48   ` M. R. Brown
2001-10-20 22:08   ` Alan Cox

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200110181540.f9IFe8S24810@oboe.it.uc3m.es \
    --to=ptb@it.uc3m.es \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®