Emphasise the optical flow is calculated at input resolution. #5350
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.
Category:
Documentation
Description:
I personally have made a mistake in using this operator by misinterpreting the output vector quantities as the resolution of the output image. A common pattern pytorch to automate dealing with flow vectors is to autmatically scale the flow magnitude and resolution at the same time in the following code.
By emphasising the output of this operator is always at the resolution of the input, but the resolution of the output may differ, I hope to prevent others from making this same mistake.
Context
Original datapipe code...
...was fixed with (since default output_grid=4)
Additional information:
Affected modules and functionalities:
Key points relevant for the review:
Tests:
Checklist
Documentation
DALI team only
Requirements
REQ IDs: N/A
JIRA TASK: N/A