Extend RandomShortestSize
to support Video specific flavour of the augmentation
#6770
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.
Our
RandomShortestSize
implementation on the references is developed with Object Detection in mind. Videos require a slight variation (see reference implementation for detection vs video).This PR extends the transform in a BC-way so that it can support both. In particular, we make the
max_size
optional and this allows us to reparameterize the transform for videos as such:Though the names of
min_size
andmax_size
are confusing (better names would have beenshortside_min_size_range
andlongside_max_size
), their semantics align with the arguments thatF.resize()
has forsize
and andmax_size
. On the latter the default value ofmax_size
(which again applies to the longest edge) isNone
, so this transform uses the same semantics and default values as in other places of the API.