You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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:
'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
If the ADCP has an altimeter ping, consider using that distance instead (another dist_ variable). There's usually some disparity between them
Make sure you're taking the depth of the ADCP transducers below the vessel into account before plotting
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 tomhkit.river.d3d
This plot shows that the DOLfYN ADCP has an offset to the ADCP variable
dist_bt
read in by DOLfYNI expect DOLfYN river D3D should match WinRiver and MHKiT in this case.
The text was updated successfully, but these errors were encountered: