Closed AthinaLange closed 4 years ago
Turns out the issue was that we had left our coordinate system in GPS coordinates. The grid had to be flipped 180deg to work. Thanks to Brittany Bruder for figuring it out.
Here's the explanation from her: Kappa is a measure of enlarging the analysis as you go offshore, cBathy assumes the shoreline is on the left and offshore is on the right, which west coast beaches have the opposite. params.offshoreRadCCWFromx is a guess of the wave direction. Without rotating the system, a value of 0 indicates the waves are coming from the right. So on an unrotated west coast beach--the waves are coming from the land.
Hi all, I'm using the CIRN Introduction to Quantitative Coastal Imaging Toolbox to rectify images extracted from a 17min drone flight and now I'm trying to run them through cBathy.
I use their G2_pixelInstruments to get the pixInst variable on a grid (in world GPS coordinates) that does include all of the beach and some of the road with our stability/ground control points and extends out past the surfzone (see image).
To organize the pixInst variable into a cBathy input format, I use:
There are some points along the boundary that occasionally have values due to the FOV moving slightly from the drone, that are set to 0. There are some values 'inside' the wavefield that are also zero that I've set to the mean value at that point.
I noticed in the demo cBathy, that the grid is only defined at the non-zero values, which I've also tried with no more success than the other ones.
I've been using the demo argus02a.m file for the settings file, only changing: params.xyMinMax = []; .
cBathy is able to run with no errors (a few Jacobian ill-conditioned warnings), however the output bathy.fDependent.k is almost completely filled with NaN's, and then fCombined is NaN's as well.
I've put our pixInst, data, t, xyz and the resulting bathy file in this dropbox link (https://www.dropbox.com/s/5ult5nms9ipf7aa/input_data.mat?dl=0)
Any help would be greatly appreciated. Thanks!