-
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
Generalize assignment of beam coordinate var attributes #480
Conversation
…fp. Add range_bin long_name
for more information, see https://pre-commit.ci
Codecov Report
@@ Coverage Diff @@
## dev #480 +/- ##
==========================================
- Coverage 76.66% 72.27% -4.40%
==========================================
Files 38 16 -22
Lines 3339 2287 -1052
==========================================
- Hits 2560 1653 -907
+ Misses 779 634 -145
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
Thanks @emiliom, this looks great! One thing I thought of when going through this is that On an unrelated note, I noticed that |
Continuing the unrelated note, I think I noticed that DEFAULT_CHUNK_SIZE is actually declared in two different modules, the same way, But yeah, that's for another issue |
Let's revisit that thought for sure, once we're creating the convention-compliance architecture for 0.6.0 |
Thanks for the review. I'll self merge now |
Unified where the attributes for the core beam coordinate variables (
frequency
,ping_time
,range_bin
) are set. I've created a newDEFAULT_BEAM_COORD_ATTRS
dict inset_groups_base.py
that declares these common attributes and their values, then import that variable in the various set_groups_x.py modules. This PR implements that change for ek60, ek80, azfp.This abstraction/centralization will reduce the potential for variability across sensors and make it a tiny, tiny bit easier to roll out support for new sensors in a consistent fashion.Also added a
long_name
attribute torange_bin
, partly addressing #373