Re: efficient way to process data

References	(4 earlier) <CACwCsY74dTc9vJ=j06Fq9rqXe_wmSHpYQ-qaC284CcgjEnrQ9Q@mail.gmail.com> <CAPTjJmrv7aG09p8H_v6tyJRQHo37o=_2ZX0sL96L_ZaDsddJNw@mail.gmail.com> <CACwCsY62pqvKVrs11+yv5Ox9QBSv4McQDZ3-0aGnaUezfm2Ywg@mail.gmail.com> <CAPTjJmp3MW2a1SE-zqZY5ZJSeZ3wnt+NnjKTuWYY1Coi5dLt5g@mail.gmail.com> <CACwCsY7eS2Ls7YWDSJET-b-Xt+hZnpsiCiPPDam3QnxXUHdQ4w@mail.gmail.com>
Date	2014-01-15 03:37 +1100
Subject	Re: efficient way to process data
From	Chris Angelico <rosuav@gmail.com>
Newsgroups	comp.lang.python
Message-ID	<mailman.5465.1389717471.18130.python-list@python.org> (permalink)

Show all headers | View raw

On Wed, Jan 15, 2014 at 3:23 AM, Larry Martell <larry.martell@gmail.com> wrote:
>> As far as I'm concerned, you won geek cred the moment you said
>> "electron microscope", and "semiconductor wafers as they are being
>> manufactured" is just gravy.
>
> Thanks! You made my day. I showed this to my wife and she asked "Is that good?"

Heh! Geek language can be a bit weird at times. Of course, it's not a
dream job if things like this get tantalizingly dangled in front of
you and then taken away as you're given something less fun and more
urgent to do...

>> Do you actually mean here that the two points need to be within 1
>> micron, or that data gets combined if it's nearby in *either*
>> coordinate?
>
> Either coordinate.

Okay, so the code I put together earlier in the thread is correct.

ChrisA

Back to comp.lang.python | Previous | Next | Find similar | Unroll thread

Thread

Re: efficient way to process data Chris Angelico <rosuav@gmail.com> - 2014-01-15 03:37 +1100

csiph-web