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.
Fix the Gaussian Blur as detailed in #1051. This is just a quick fix example, feel free to reject this PR and write your own clean implementation, although I would love to help if I can.
In particular, this is probably a classical problem, but I am not sure how to handle cleanly the old parameters of GaussianBlur filter as scale or kernel_size that we don't need anymore with this fix : either one can delete these two parameters, but it does not ensure compatibility with older version of Lightly (if a user happened to use the Gaussian Blur function, this will lead to an issue), or one can leave these two unused parameters as is with default values, resulting in a not very clean implementation having useless parameters (current state of the PR).
One important question would be about using the Gaussian Blur either from PIL or from TorchVision.