Closed gtauzin closed 4 years ago
Might be worth rebasing or pulling from upstream master to get the latest changes involving the use of check_collection
here.
@gtauzin accidentally "approved" this PR, I meant to just comment/request changes.
@gtauzin accidentally "approved" this PR, I meant to just comment/request changes.
Too late xD
@ulupo I see no check_collection
being used in the images
submodule so far. Do you want me to enable it?
@gtauzin you're right: check_collection
is not really used and it might take some work to use it throughout images
, with the exception perhaps of ImageToPointCloud
. What do you think?
@gtauzin you're right:
check_collection
is not really used and it might take some work to use it throughoutimages
, with the exception perhaps ofImageToPointCloud
. What do you think?
I would argue that if images are passed as lists, we need to make sure that they have the same number of dimensions and possibly the same number of pixels per dimensiosn for most of the transformers. Here I guess it's better no to allow check_collection
(at least for now).
I have one thing to add after Umberto's comments: a test case with floats would be useful, so that we're sure it works :)
@wreise That's very true. Would you mind helping me with it?
@wreise That's very true. Would you mind helping me with it?
Done. Please let me know if that doesn't look good
@wreise LGTM, thanks :)
@ulupo Ready to be merged :)
Types of changes
Description Extends images.Padder and images.Inverter to greyscale images.
Screenshots (if appropriate)
Any other comments?
Checklist
flake8
to check my Python changes.pytest
to check this on Python tests.