Photo-finish

From ElphelWiki
(Redirected from Linescan)
Jump to: navigation, search

Elphel Network Cameras Manual

Using the cameras | Camera software | Camera hardware | Diagnostic and repair | Development documentation | Information | Glossary | About Elphel, Inc

Photo-finish | Zeroconf for Elphel cameras | Elphel cameras and Zoneminder | USB host interface | Motorized lens control | Outdoor enclosure

What is line scan?

Line-scan is an image acquisition method that continuously samples (sensor) lines into a composite image. A Flatbed or hand held scanner is essentially also kind of a line-scanner. For some historic reasons (I guess due to the various application and realms they derived from) there are many terms:

Basically they all describe the same principle, a principle that is rather old and was already used in traditional analogue photography (for instance rotating panorama cameras), where you have a slit as an aperture, exposing the film as it moves by. In the digital realm one would cut out slices of existing image footage or – as in case of dedicated line-scan cameras – it is really just a one line sensor (to be correct: that’s true for monochrome cameras, color line-scan cameras normally have either 3 lines – in case of CCD sensor: one for each color – or 2, if the sensor is CMOS using Bayer pattern).

Applications of these line-scan method include industrial surface scanning, photo-finish, rotating panorama cameras, aerial imaginary, the arts (an interesting overview of art and research related slit-scan approaches can be found here) and certainly many more.


Line scan with Elphel

This image is downsized from 2592x8000 and rotated by 90° CCW
Another sample
Camera series Photo finish support
333 +
353 +
393 +

Since 2005 and the older 333 model, Elphel cameras have a “photo-finish” mode. With its 3Mpix Aptina CMOS sensor Elphel 333 was able so sample around 3072 lines per second. The photo-finsh mode was revived for the current Elphel 353 model with firmware release 8.0.8.7 by end of April 2010. The current 5Mpix Aptina CMOS sensor (width: 2536px) is a bit slower and allows a sample rate of approx. 2300 lines per second – or a line rate of 2.3 kHz (as it seems to be measured in dedicated line-scan cameras).

Elphel 353 software is fully ported to the new Elphel 393 generation of camera systems and works for JP4 format.

In the photo finish mode the camera then samples just lines and delivers composite images as video frames via RTSP network stream or directly to a hard-disc.

Due to the Bayer pattern of the sensor the minimal sample height is 2 lines.

Instructions for 393

  • A link for quick access to parameters that might be required:

http://192.168.0.9/parsedit.php?sensor_port=0&WB_EN&AUTOEXP_ON&EXPOS&COMPRESSOR_RUN&TRIG&TRIG_PERIOD&PF_HEIGHT&WOI_HEIGHT&WOI_TOP&WOI_LEFT&WOI_WIDTH

  • Before changing any image parameters affecting this mode it's better to stop the compressor and restart it only after everything is set. If image freezes it's better to reboot and start over.

More info on changing parameters.

  • If sensor is in a free run mode, the line-pairs are sampled as fast as (exposure) settings allow with a maximum rate of ~2300 line-pairs per second and a maximum width of the composite frame of 16384px, defined by WOI_HEIGHT. The sensor location that is used as source for these lines is defined by WOI_TOP, WOI_LEFT and WOI_WIDTH.
  • For variable control of the line sampling speed you can either:
    • Change exposure settings.
    • Slow down that process by defining a virtual size with VIRT_KEEP and VIRT_HEIGHT (which still samples as fast as it can for given virtual size and exposure settings)
    • Use the camera’s internal trigger mode with TRIG=4 and TRIG_PERIOD settings to generate a regular trigger impulse. (but due to camera’s internal delays in that mode the line rate is a bit smaller).
  • The instructions are the same as for 353, the key difference is switching sensor to free run (or reasonable fps) and JP4 format modes.

393's factory default setting is 10 fps from internal trigger while 353's factory default is free run mode.

Examples

Note: Parameters in a single line can be changed at the same time

  • Example 1: 2592x1936, not changing any frame dimensions, sensor is in a free run mode
    • COMPRESSOR_RUN=0, WB_EN=0, AUTOEXP_ON=0, EXPOS=400, TRIG=0, COLOR=5
    • PF_HEIGHT=2
    • COMPRESSOR_RUN=2
  • Example 2: 2592x3872, not changing any frame dimensions, sensor is in a free run mode
    • COMPRESSOR_RUN=0, WB_EN=0, AUTOEXP_ON=0, EXPOS=400, TRIG=0, COLOR=5
    • PF_HEIGHT=2
    • WOI_HEIGHT=3872
    • COMPRESSOR_RUN=2
  • Example 3: 2592x1936, not changing any frame dimensions, sensor is triggered from internal counter at 2000 fps
    • COMPRESSOR_RUN=0, WB_EN=0, AUTOEXP_ON=0, EXPOS=400, TRIG=0, COLOR=5
    • PF_HEIGHT=2
    • TRIG_PERIOD=50000 (units are in 1/100MHz)
    • TRIG=4
    • COMPRESSOR_RUN=2


Tips and notes

  • Works in JP4 (COLOR=5) and MONO(COLOR=1) formats
  • How to process JP4
  • To seamlessly join 2 consecutive JP4 photo finish frames - their pixels has to be joined before demosaicing. Otherwise demosaicing algorithm will create a seam.
  • FPS can be controlled by exposure for sensor in a freerun mode or external or internal trigger for sensor in a snapshot mode (TRIG=4)
Example: at 2000 fps and PH_HEIGHT=2, The 2592x16384 composite frame consists of 8192 2592x2 stacked frames and covers 4.096 seconds

Instructions for 353

  • A link for quick access to parameters that might be required:

http://192.168.0.9/parsedit.php?WB_EN&AUTOEXP_ON&EXPOS&COMPRESSOR_RUN&TRIG&TRIG_PERIOD&PF_HEIGHT&WOI_HEIGHT&WOI_TOP&WOI_LEFT&WOI_WIDTH

  • Before changing any image related parameters in this mode it's better to stop the compressor and restart it after everything is set. If image freezes it's better to reboot and start over.

For more details about changing parameters, see Accessing camera parameters.

Examples

Note: Parameters in a single line can be changed at the same time

  • Example 1: 2592x1936, not changing any frame dimensions, sensor is in a free run mode
    • COMPRESSOR_RUN=0, WB_EN=0, AUTOEXP_ON=0, EXPOS=400, TRIG=0, COLOR=1
    • PF_HEIGHT=2
    • COMPRESSOR_RUN=2

Tips and notes

  • Works in JPEG format
  • 2 consecutive JPEG photo finish frames can be "seamlessly" joined without any special processing. Demosaicing related artifacts are taken care of in fpga.
  • FPS can be controlled by setting exposure. Setting fps for line scan by programming internal trigger period was not implemented for 353.

Important notes

  • A common pitfall in trying out photo-finish mode is that one needs to take care of appropriate exposure setting before going into photo-finish mode. If you just start that mode in low light conditions you will end up waiting for frames endlessly – and get the impression the camera does not work anymore. For example:

 Switching to photo finish from 2592x1936 and 50ms exposure to 2592x2 and 2592x1936 composite image will result in waiting for that composite image for 50 seconds (1936/2*50ms).

Example images

Free Software and Open Hardware. Elphel, Inc., 2005-2017

Retrieved from "https://wiki.elphel.com/index.php?title=Photo-finish&oldid=15850"