Draft
Conversation
Contributor
Author
|
@alex404 I created this pull request also because it shows an alternative way to implement the input transforms, maybe worth discussing whether this would be better (as opposed to the current way of 'hijacking' the input normalization) Otherwise I think it's a nice feature for future experiments but not urgent atm, so for now it will 'just exist' |
5a60a34 to
e263062
Compare
This file contains hidden or 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.
Adds the possibility to 'warp' the input and by that get a 'foveated' vision.
It does so by sampling at full resolution in the center and then skipping more and more rows/lines to the outside, depending on
and the output size after warping defined through
Open TODOs: