We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Right now our parser handles data from EC150 ADCP fine, but we still need to determine how to store the data properly and enable calibrating the data.
Should we store the data 1) as a separate Beam_group3, or 2) along with existing Beam_group1 or Beam_group2?
Beam_group3
Beam_group1
Beam_group2
On the calibration side, we need to make sure all the parameters are stored properly, and arguments to compute_Sv are compatible.
compute_Sv
Right now we are skipping all datagrams generated by EC150 (#1357) just so that we can just handle data from other channels sitting in the same file.
The text was updated successfully, but these errors were encountered:
@jmjech @spacetimeengineer this is relevant to #995 - could use your inputs also.
Sorry, something went wrong.
No branches or pull requests
Right now our parser handles data from EC150 ADCP fine, but we still need to determine how to store the data properly and enable calibrating the data.
Should we store the data 1) as a separate
Beam_group3, or 2) along with existingBeam_group1orBeam_group2?On the calibration side, we need to make sure all the parameters are stored properly, and arguments to
compute_Svare compatible.Right now we are skipping all datagrams generated by EC150 (#1357) just so that we can just handle data from other channels sitting in the same file.
The text was updated successfully, but these errors were encountered: