Final Analysis

STEP 5) Final Analysis

Data analysis finishes when either all the frames have been analyzed or when the findNewBeta.m is no longer able to find the first reference point (usually because the operator turned the UAV to head for home but left the video running). At that point the final image products are made by the function makeFinalImages.m and data are organized to save in the cx directory. All important inputs are stored in a metadata file using standard Argus naming conventions. Note that since the geometries (betas) are saved, new pixel tool analysis can be done subsequently using much less CPU time, if new instruments are desired. This is done by changing the content of the instrument file then rerunning the sampleAerielleVideoDemo.m.

Time stack data are then saved in cx, again using standard Argus names including the instrument name selected by the user, for example vBar150. These can be plotted in standard ways, for example, imagesc(stack.xyzAll(:,1), stack.dn, stack.data). Figure 4 shows an example runup time stack, figure 5 shows a vBar time stack.

Figure 4. Example runup time stack for y = 600 for the demo run.

Figure 5. Example vBar stack for x = 175 for the demo run. Currents obviously flow north (down left) on the north side of the pier and to the south (down right) on the south of the pier.

Image products are saved as png’s in cx using standard naming conventions and in matlab format using the routine printAndSaveImageProducts.m. Matlab versions are saved in files with the image type ‘imageProducts.mat’. These can be loaded and shown using, for example for Figure 6, Imagesc(finalImages.x, finalImages.y, finalImages.timex)

Figure 6. Rectified time exposure for the 10/01/15 demo data run.