-
Notifications
You must be signed in to change notification settings - Fork 17
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
iPoints are difficult to decode #159
Comments
Agree this is a hassle @bart1. The points array has been introduced at some point by Jurriaan Spaaks from eScience center as a simplification, originally everything was read from the sweeps directly. Instead of working on the points array which I wouldn't mind deprecating at some point, you could also consider working on In bioRad the flags and classifications of each gate would then be read as an additional |
I agree with you I was now working on a quick hack to get things working for initial exploration. I seem to have it figured out now. Long term #129 is indeed the solution, i just dont have the familiarity to solve this in vol2bird yet. (just in this exercise figured out the min and max ranges are indeed ranges (atleast in 0.3.20) and not distances as I kind of default assumed). |
I'm currently parsing the iPoints array. In case there are multiple scans with same elevation angle this is some what challenging. This is partially due to the ordering by height bin. A simple fix would be to add the
scan id
andrange gate id
as an additional column.The text was updated successfully, but these errors were encountered: