-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
Fix LightningDataModule
hparams parsing
#12806
Fix LightningDataModule
hparams parsing
#12806
Conversation
@awaelchli I have tried this, without touching the |
This looks great! Would you mind extending the test |
@awaelchli sure |
Hi @tanmoyio! Thanks for working on this! Here's the TODO list in this PR!
Let us know if you need help! |
b8c09d8
to
e9d5205
Compare
for more information, see https://pre-commit.ci
@akihironitta I have added the unit tests, let me know if I need to modify anything, then I modify the changelog when everything is ready to go. |
@tanmoyio Would you mind having a look at the test failures? Also, could you update the changelog? |
@akihironitta sorry, I should have done that earlier, will take a look into that. |
we should not consider |
Thanks @rohitgr7 will modify it that way |
LightningDataModule
hparams parsing
Co-authored-by: Akihiro Nitta <[email protected]> Co-authored-by: Jirka <[email protected]> Co-authored-by: Rohit Gupta <[email protected]>
Co-authored-by: Akihiro Nitta <[email protected]> Co-authored-by: Jirka <[email protected]> Co-authored-by: Rohit Gupta <[email protected]>
Co-authored-by: Akihiro Nitta <[email protected]> Co-authored-by: Jirka <[email protected]> Co-authored-by: Rohit Gupta <[email protected]>
What does this PR do?
Updates DataModule hparams for
tuner.scale_batch_size()
Fixes #12768
The actual fix was that we need to correctly parse datamodule hparams too. check the review for a better understanding.
Does your PR introduce any breaking changes? If yes, please list them.
No
Before submitting
PR review
Anyone in the community is welcome to review the PR.
Before you start reviewing, make sure you have read the review guidelines. In short, see the following bullet-list:
Did you have fun?
Make sure you had fun coding 🙃