-
Notifications
You must be signed in to change notification settings - Fork 323
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reviewing GAN basics, VisionDataModule, MNISTDataModule, CIFAR10DataModule #843
Conversation
for more information, see https://pre-commit.ci
for more information, see https://pre-commit.ci
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi, all in all, it looks good, thank you! 🎉 However, I'd like to be sure that we are not raising any deprecation/user/any other warnings. For this, I just opened #844 which should then be used in tests (when it gets merged).
@@ -13,6 +13,7 @@ | |||
[ | |||
pytest.param(MNISTDataModule, id="mnist"), | |||
pytest.param(CIFAR10DataModule, id="cifar10"), | |||
pytest.param(STL10DataModule, id="stl10"), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd remove this test case, as it is very heavy dataset
…vision datamodule
…ting their test cases
Currently, all the modified classes and their test cases pass but with the exception that we filter |
Awesome work! Let's wait for #844 to see if the tests are passing on CI as well, but otherwise it looks good! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Let's wait for test and get this merged 👍 💪 🚀
@@ -30,6 +27,9 @@ def __init__( | |||
shuffle: bool = True, | |||
pin_memory: bool = True, | |||
drop_last: bool = False, | |||
train_transforms: Optional[Callable] = None, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shouldn't we include these transforms into the class docstring?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree we should add it. What will be an ideal way of doing this? Do I need to create another pull request for this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree with this as well, good catch @luca-medeiros!
@shivammehta007, yes, opening a new PR is the only option (not even I have push rights to master 😂). Since this PR is already merged, there really is no other option. Just write there it's a followup of #843
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@luca-medeiros Oh, absolutely! That's the whole point of our Slack channel. I think you're not in there yet, can you ping me on PL Slack (@Ota
) and I will add you there?
As discussed adding docstring in a separate PR #847. |
What does this PR do?
Part of #839
Before submitting
PR review
Anyone in the community is free to review the PR once the tests have passed.
If we didn't discuss your PR in Github issues there's a high chance it will not be merged.
Did you have fun?
Make sure you had fun coding 🙃