-
Notifications
You must be signed in to change notification settings - Fork 21
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
Unfolding stops at 0 #178
Comments
isn't this a pyart issue? for reference the desiasing is done either with: if you are talking about the manual unfold, such a case can not be corrected with that simple of an algorithm, I recommend using the pyart methods before. |
I'm not really sure how we can solve this, since as you said the zero line is what is being used to separate what need dealing and what does not. We could allow the user to change this threshold value, but I'm not sure about that. We could also add a component to do a linear transformation in a selected region + gatefilter, that would probably be much more difficult to work with, but gives you full control. Let me know what you think and we may add as a to do, and it will hopefully be addressed at some time. Also if you want to do it your self I would be glad to give directions. |
by the way @pfhein I'm planning to be presenting ARTView in the AMS's 38th Conference, on august. If you have any thoughts I would be glad to hear, send me an e-mail. |
I have seen a case where the unfolding/deliasing stops at zero velocity. The velocity is large enough that is wraps around and goes past the 0m/s mark. but the unfolding does not catch it.
The text was updated successfully, but these errors were encountered: