-
Notifications
You must be signed in to change notification settings - Fork 76
New issue
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
Parse AZFP pressure data when available #1181
Comments
After parsing the pressure data, the data array needs to be written into the EchoData object. I think there are two steps here:
|
PR #1189 addressed item 1 above: parsing and storing pressure data, plus tests. For item 2, we'll need to decide what conversion formula / algorithm / library to use to convert from pressure to depth. |
For reference, here's the functionality used by the AZFP Matlab toolbox to calculate density (The links below are to a private repo):
|
Hmm, the |
@praneethratna Ok, I now have a recommendation for implementing the conversion from pressure to depth. Let's use the UNESCO 1983 formulation (pages 25-27). This site lists the equations nicely and includes a calculator. We'll make the standard seawater assumption used in that site: salinity of 35 PSU and temperature of 0 C. That makes the Let's implement this as a new function
In the function, The function returns a depth numpy array. PS. I'm including here other references I consulted. No need to look at them. I just want to be able to find them after I close those tabs in my browser 😉.
|
AZFP deployments can contain a pressure sensor. However, the echopype AZFP parser currently does not look for and read pressure data, as it does for temperature. Add this.
When read, it should be used to populate
Platform.vertical_offset
while also settingPlatform.water_level
to 0. See https://echopype.readthedocs.io/en/stable/data-proc-additional.html#vertical-coordinate-z-axis-variablesWe'll need to obtain a sample data file that includes pressure data.
The text was updated successfully, but these errors were encountered: