Prev: Memory bug in Tcl 8.6
Next: WS::Client::DoCall receiving an "HTTP/1.1 100 Continue" response
From: Christian Gollwitzer on 27 Jan 2010 05:06
Roger O schrieb:
> [...] Our higher
> level library for all this is available in Tcl via SWIG. And that is
> the level at which we process images.
>
> The Tk part is mainly a viewer that will be used when setting up the
> cameras. However, one of the 'images' is really a high precision (0.25
> mm vertical resolution) elevation profile where each 16-bit pixel
> value is the elevation. The image rows are 1536 pixels wide and occur
> at 500 or 1000 Hz. For sanity reasons, a number of rows are grouped
> into the images under discussion here. When setting up the camera, we
> need to magnify some of the elevation ranges to see that they are
> being detected as expected. I think my best solution will be to use a
> Tk slider set to select the elevation ranges from a 16-bit range of
> values, and then recalculate an 8-bit image from the original 16-bit
> data in the C code, updating the viewed image with Tk_PhotoPutBlock().


Yes, that is exactly our approach also. You can have a look at the
program, if you are interested in the user interface:

http://www.staff.uni-bayreuth.de/~btp916/software.html

(you need one of the starpacks and the example image. Use the OPen..
button to load the image). The mouse bindings are as follows:

left bttn: drag a rectangle in the image. The contrast is adjusted to
the range in the image
right btt: Output coordinates and height in the console
on the "contrast" pane, there are sliders.

The image processing stuff is done in C with a high level interface to
tcl, exactly like the one you described:)

Regards,

Christian
First  |  Prev  | 
Pages: 1 2
Prev: Memory bug in Tcl 8.6
Next: WS::Client::DoCall receiving an "HTTP/1.1 100 Continue" response