Remove pixel interpolation functions #751
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
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.
We do not use (most) of the interpolation functions. They were originally used for one specific type of visualization. The only function that was being used was
interpolated_add()in the fake data creation, but this can be replaced with a manual add.This PR removes a lot of unused code including:
RawImage.add()- Not used anywhereRawImage.interpolate()- Not used anywhere anymore.RawImage.get_interp_neighbors_and_weights()- Used only for interpolated_addRawImage.interpolated_add()- Used only in the fake data creation, where they can easily be replaced.manhattan_neighbors- Used only forRawImage's interpolate functions.