coastal-imaging-research-network / pixel-toolbox

Routines to create pixel lists for stack collections

PIXel-Toolbox

Routines to create pixel lists for stack collections. See the pixelToolboxManual.pdf for more info.

This version of the PIXel-Toolbox is not complete. It has the ability to create pixel lists and the standard structures for pixel collections so that it can be used with the UAV-Toolbox. It needs modification for the pixel retrieval backend.

pixel-toolbox's Issues

Convert pixelToolboxManual.pdf to Markdown

If we convert the manual to markdown document it can be hosted on the github via the README.md, which is a more native document for github and wouldn't require users to browse and open the document.

First time kick-start...

Hi All,
I'm new to the PIXel-Toolbox and unclear as to how to use it. Judging by the manual, it looks like the toolbox will be pretty useful.

I have been collecting video timestacks using hotm. Hotm extracts video at all of the pixels specified in my pixel list - which includes all of my pixel instruments in a single list. I.e. all of the instruments are contained in a single stack .ras file.

Given that I'm starting with a .ras file, where do I begin?
Is there a tool to tease out the instruments from the .ras file?

Thanks for the nudge,
Shawn

PIXMakeVBAR.m hard coded to create vbars with .10 m resolution

In line 13 of PIXMakeVBAR.m, an input argument is hard coded to be .1 which results in vbars that are sampled at 10 cm resolution. Is there a particular reason 0.1 is chosen? Is it ok to make this a variable chosen by the user? I'm interested to find out if sampling vbars at a resolution greater than the rectified image results in any changes in processing results, like when using the Video Currents Toolbox.

I went ahead and made a new branch (development) that includes an edited version of PIXMakeVBAR.m where 0.1 is replaced with dy. This new input argument is also added in line 1 of the function along with an if statement that defaults dy to .1 if no input argument is provided. The user can now define a dy in their pixel instruments file when running through the UAV toolbox, or default to .1 cm vbar resolution.

3d survey lines to PIXCreateInstrument

Dear John,

How do we assign a 3d line (x,y,z) from meat-space into pixel coordinates? I don't see the appropriate flag in the pixelToolboxManual.pdf for lines that have z values (i.e. 'PIXFixedZ')

e.g.
tid = PIXCreateInstrument( 'randomLine', 'line', PIXFixedZ+PIXUniqueOnly );
PIXAddLine( tid, 250, 39.5, 250, -150, 1.1, .1, 'x250line' );