-
Notifications
You must be signed in to change notification settings - Fork 99
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
Adopted pytorch lightning DataModule instead of DataLoaders and Dataset #642
Adopted pytorch lightning DataModule instead of DataLoaders and Dataset #642
Conversation
Signed-off-by: samadpls <[email protected]>
Signed-off-by: samadpls <[email protected]>
Signed-off-by: samadpls <[email protected]>
…tion` Signed-off-by: samadpls <[email protected]>
Signed-off-by: samadpls <[email protected]>
Signed-off-by: samadpls <[email protected]>
Signed-off-by: samadpls <[email protected]>
Signed-off-by: samadpls <[email protected]>
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.
@samadpls thank you very much for this contribution! I think the PR is in great shape and that it's quite cool that you've been able to make a contribution to the backend so fast! I have left a few comments on line lengths along with some suggestions on how you can reduce them. Most of the complaints from CodeClimate is related to these lengthy lines of code, and I think it would be very quick for you to adjust them. Let me know if you have any questions!
Signed-off-by: samadpls <[email protected]>
Signed-off-by: samadpls <[email protected]>
@RasmusOrsoe, thank you for reviewing and giving your feedback. I have implemented the necessary adjustments to address the comment. 😋 |
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.
🥇
Adopted PyTorch Lightning DataModule instead of managing individual DataLoaders and Dataset.
This pull request addresses and resolves issue #579