Re: Image Processing with Geode GX2: Win CE or XPe?
From: Alexis (Alexis_at_discussions.microsoft.com)
Date: 02/27/05
- Next message: Alexander Grigoriev: "Re: NTFS block allocation policy (Windows XP)"
- Previous message: Kerwin Cabrera: "Font Component"
- In reply to: Slobodan Brcin \(eMVP\): "Re: Image Processing with Geode GX2: Win CE or XPe?"
- Messages sorted by: [ date ] [ thread ]
Date: Sun, 27 Feb 2005 07:03:03 -0800
Hello Slobodan and Dave,
I even care about my work on sunday (maybe I will be hired at the end of my
training =) )
We never intended to do all the processing quoted above at the same time and
in one pass. It's either pattern matching either OCR either...
We'll sell the hardware, with maybe an image processing library bundled, and
our customers will implement the processing they'd like for their particular
needs.
Since the Linux version works well with our hardware for this kind of
processing (2D barcode, pattern matching...) we would like to stick with our
hardware.
Thus we need to supply and effcient system for capture and IO and have
enough remaining ressources for our customers custom applications.
We are currently in a validation process to determine which stuff will be
achievable with the smart cam and which ones won't be.
I'm testing with the XPe evaluation kit, I'll have a better understanding of
what could be done with our hardware once I get my first XPe image.
Thank you very much for your support,
Alexis
"Slobodan Brcin (eMVP)" wrote:
> Alexis,
>
> Few facts if you use color picture: If you use 2 bytes per pixel (which is minimum) then you will have following memory bandwidth
> requirements: (that is if you capture hardware and its drivers are pure perfection)
>
> 1280x960x2x60 > 140.65 MB/s for bringing RAW video over PCI-?
> PCI-33 could yield <125MB/s but this is theory. You should be extremely happy with ~100 MB/s and that is if you card is the only one
> on PCI bus.
> So first thing that you need is PCI-66+.
>
> Memory BW:
> Just for picture capture to memory you lost 140+ MB of bandwidth.
> For processing you need to read this picture and apply some algorithm. Provided that all happen inside the processor cache you lost
> minimum of 140+MB of bandwidth as well.
>
> >Common image processing tasks in machine vision:
> -Pattern, Geometric, Shape matching.
> -Edge Analysis.
> -Color Analysis.
> -Barcode recognition, OCR.
> -Measurement, and so on.
>
> Please let me know of algorithm that can do all this in one read pass, I am really interested.
>
> To make at least some of the things possible with high resolutions you will probably have to cut your initial requirements if you
> plan to stick with Geode platform.
> BTW if you need every bit of performance then you should integrate all image handling and processing in to the driver/preferably in
> symbiosis with capture custom driver.
>
> I had to write similar thing for our hardware although I had HTT 2.4 GHz processors, with three separate PCI buses. And a lot of
> memory for storing captured pictures in case that processor(s) can't keep up at certain moments.
> I'm talking here about capture of (3x2x4) cameras in 702x288x2x25 resolution.
>
> Regards,
> Slobodan
- Next message: Alexander Grigoriev: "Re: NTFS block allocation policy (Windows XP)"
- Previous message: Kerwin Cabrera: "Font Component"
- In reply to: Slobodan Brcin \(eMVP\): "Re: Image Processing with Geode GX2: Win CE or XPe?"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
|
