Skip to content
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.

Sign up for GitHub

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

Jump to bottom

ODIM sweep_number is off by one #80

Closed
kmuehlbauer opened this issue Feb 8, 2023 · 0 comments · Fixed by #81
Closed

ODIM sweep_number is off by one #80

kmuehlbauer opened this issue Feb 8, 2023 · 0 comments · Fixed by #81

Comments

@kmuehlbauer
Copy link
Collaborator

  • xradar version: 0.0.11
  • Python version: 3.11
  • Operating System: Linux

Description

xradar tries to align to standard, so sweep_number starts from 0 (sweep_0). As ODIM_H5 is 1-based (starting with /dataset1), sweep_number is currently wrongly decoded. The odim-backend based data starts therefore with sweep_1 instead of sweep_0.

This does not give problems, because the iteration process over the groups are the same. Nevertheless this should be corrected.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

FIX: ODIM_H5 backend inconsistencies kmuehlbauer/xradar
1 participant
@kmuehlbauer