-
@lgarzio we are posting much of our email exchange here so it's much easier to track and resolve. I'm making small edits for clarity.
**(2021-6-18, from @lgarzio)**
I’ve been working with a smal…
-
Currently we use `frequency` as a dimension in the echopype-generated dataset (in place of having data from different frequency channels saved into different `Beam_groupX`s defined in the SONAR-netCDF…
-
This issue stems from PR #672, separating out improvements and harmonization of time variable attributes from the actual renaming of time dimensions and variables (in `Environment`, `Platform` and `Pl…
-
This issue is split from #407 since the symptom is similar but the underlying cause is different.
Tagging @oftfrfbf, @lsetiawan @emiliom so that we can continue the discussion here. 😃
This issu…
-
*(Updated 2022-3-30)*. Add a `beam` dimension to `Beam_groupX` groups. We've decided to always include the `beam` dimension, instead of relying on an implicit length-1 dimension.
- [x] Currently fo…
-
With the addition of the `beam` dimension to a large number of variables in the `Beam_groupX` groups for compliance with the convention, now the outputs of `compute_Sv/TS` would also have a `beam` dim…
-
We should implement this:
source: https://aslenv.com/AZFP-data.html
The axes are depth, time of day, and dates -- just one more dimension than the flat echogram.
Let's also see how to relate …
-
Currently echopype's output contain coordinates in units range from sensor. For further analysis, researchers may want to be working with coordinates in watercolumn depth for scientific visualizations…
-
Scanning through some miscellaneous EK60 files I have been finding issues when redundant frequencies are packaged in the raw data.
Example code:
```python
import echopype as ep
raw_file_s3path…
-
**What happened**:
`ep.calibrate.compute_Sv(echodata)` completed with the expected Sv xarray dataset. However, trying to calculate MVBS with ep.preprocess.compute_MVBS, I get a `ValueError: Di…