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.
Previously, dtypes were not propagated correctly in composed transforms, resulting in errors when different dtypes were mixed. Even specifying a dtype in the constructor does not fix this. Neither does specifying the dtype for each composition function invocation (e.g. as a
kwarg
inrotate_axis_angle
).With the change, I also had to modify the default dtype of
RotateAxisAngle
, which wastorch.float64
; it is nowtorch.float32
like for all other transforms. This was required because the fix in propagation broke some tests due to dtype mismatches.This change in default dtype in turn broke two tests due to precision changes (calculations that were previously done in
torch.float64
were now done intorch.float32
), so I changed the precision tolerances to be less strict. I chose the lowest power of ten that passed the tests here.