Fix data point skipping on hodo #188
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This seems to be a subtle off-by-one index error when drawing each colored 3-km segment of the hodo. The first data point after a segment cutoff is skipped when connecting u,v points. If z = [..., 2900, 3100, 3300, ...], then the u,v point at 3100 m AGL is skipped, since it's the first index after the 3-km segment cutoff. Only becomes noticeable with vertically sparse data.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This seems to be a subtle off-by-one index error when drawing each colored 3-km segment of the hodo. The first data point after a segment cutoff is skipped when connecting u,v points. If z = [..., 2900, 3100, 3300, ...], then the u,v point at 3100 m AGL is skipped, since it's the first index after the 3-km segment cutoff. Only becomes noticeable with vertically sparse data.