-
Notifications
You must be signed in to change notification settings - Fork 77
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
Drop beam dimension #1056
Drop beam dimension #1056
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@emiliom : I checked the changes and they look fine. I think it makes more sense to review this once all changes for different sonar_models are in, since there are some redundant code in set_groups_base.py
that needs changing too (I just found out).
Also, a quick note that please make sure for EK80 backscatter data and some parameters the beam
dimension is removed too. There are also other parameters Thanks!
Related to this, I just did #1057 to capture the other half of what #978 exposed but not specifically called out. The artificial expansion (repetition of the same value) along the |
Yeah, for now I just wanted to make these changes visible to you.
Yup, absolutely. That was the original scope of #978. I'm realizing now that we haven't either changed that scope there or created a new issue to specify that we're removing the I'll edit the PR description above to mention EK80. Initially, I was focusing on the cases (EK60 and AZFP) where the |
|
…st output in export_engine
Codecov Report
@@ Coverage Diff @@
## dev #1056 +/- ##
===========================================
- Coverage 78.12% 60.47% -17.65%
===========================================
Files 67 46 -21
Lines 6253 5204 -1049
===========================================
- Hits 4885 3147 -1738
- Misses 1368 2057 +689
Flags with carried forward coverage won't be shown. Click here to find out more.
... and 48 files with indirect coverage changes 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
…d only with complex samples
…ve elimination of beam dim from EK80
|
…st output in export_engine
Note: It's quite possible that in calibration modules there are some checks for the presence of the echopype/echopype/calibrate/calibrate_ek.py Lines 579 to 584 in c5afb65
|
for more information, see https://pre-commit.ci
I've caught the cases in calibration code where the There are few more cases where the
|
I've added the remaining changes. Will merge this now to move forward to #1057. |
Great, thanks!! |
* Remove beam dimension previously added during EK60 conversion * Handle case in EK calibration where beam dimension is not present * Remove beam dimension previously added during AZFP conversion * Remove handling of beam dimension in AZFP calibration * Update convert and echodata tests to account for elimination of beam dim from EK60 and AZFP * Forgot to undo in previous commit the temporary removal of netcdf4 test output in export_engine * Remove forced addition of beam dim in EK80 when not required. Now used only with complex samples * Remove forced handling of beam dim in EK80 calibration when beam is not present * Update convert, echodata and calibration tests to account for selective elimination of beam dim from EK80 * Forgot to undo in previous commit the temporary removal of netcdf4 test output in export_engine * fix test_nan_range_entries * fix test mock ata * remove added if-else * remove beam dim handling in calibrate/cal_params.py * revise comment re one place where the beam dim should be dropped explicitly * remove outdated comments re which var has beam dim * remove redundant check for if beam dim exists * remove beam dim from test_cal_params.py::beam_AZFP * remove beam dim check cal_params.py::_get_interp_da under the alternative case --------- Co-authored-by: Wu-Jung Lee <[email protected]> Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
I'll leave this PR as a draft. For now, it's meant only for discussion, especially for @leewujung to see the minimal changes I made that fully remove the "unnecessary" use of the
beam
dimension for EK60 and AZFP data.only, for now; I'll add AZFP later, where we're also dropping theFor EK80, the removal will not be complete, as thebeam
dimension completely.beam
dimension will remain for a few variables.Addresses #978
As this will be a breaking change, our intent is to release it with version 0.8.0.