Fix the Lambda transform #261
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.
In the current implementation of
Lambdabbox and keypoint transforms are added to the_targetsdict using 'bbox' and 'keypoint' (in singular forms) keys respectively. However, DualTransform uses keys 'bboxes' and 'keypoints' (in plural forms) to find the appropriate transform methods. And because of that Lambda will always use default implementations ofapply_to_bboxandapply_to_keypointmethods from NoOp.Here is a possible fix for this problem, but I am not sure, maybe there is a better way. @BloodAxe what do you think?