DOLfYN Teledyne River depth

[browniea]

The "river depth" output from WinRiver appears to have an offset or different reference that can be validated with the bathymetry data.
I was looking in the user guide here for "river depth" WinRiver II user guide There are a few different refences the river depth can be using. DOLfYN might not be using the right one.

WinRiver River Depth comparted to mhkit.river.d3d

This plot shows that the MHKiT river d3d module matches the output from WinRiver

mhkit.dolfyn River Depth comparted to mhkit.river.d3d

This plot shows that the DOLfYN ADCP has an offset to the ADCP variable dist_bt read in by DOLfYN

I expect DOLfYN river D3D should match WinRiver and MHKiT in this case.

[jmcvey3]

Hey @browniea, thanks for bringing this up.
Any raw variables that dolfyn reads are what is directly stored in the raw file. A couple things to check:

1. 'dist_bt' should be a 4x vector with one time-series per beam - if the boat is pitching and rolling you'll probably want to use the minimum distance rather than the average
2. If the ADCP has an altimeter ping, consider using that distance instead (another dist_ variable). There's usually some disparity between them
3. Make sure you're taking the depth of the ADCP transducers below the vessel into account before plotting

[ssolson]

Close #375

[jmcvey3]

PR #378 should officially solve this bug, which I didn't originally see, involving the changing depth cell sizes that the RiverPro/StreamPro firmware creates. I've removed RDI's "bin1_dist_m" and replaced it the dolfyn agnostic "range_offset", so the user knows how far the range coordinate is offset based on the ADCP's submerged depth.