-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
[wip] support save_hyperparameters after mutation #3622
Conversation
Hello @tbenst! Thanks for updating this PR.
Comment last updated at 2020-10-07 09:53:12 UTC |
This pull request is now in conflict... :( |
e477877
to
8ce4d2f
Compare
This pull request is now in conflict... :( |
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. If you need further help see our docs: https://pytorch-lightning.readthedocs.io/en/latest/CONTRIBUTING.html#pull-request or ask the assistance of a core contributor here or on Slack. Thank you for your contributions. |
@tbenst is it ready to review/finish it? |
@tbenst |
@tbenst there won't be any more releases in 1.1.x so I have changed your destination branch to feat 1.2 |
Dear @tbenst, Would you mind resolve the conflicts ? Best, |
@tbenst is this still WIP or ready to review? |
Sorry for my long delay. Finally back working on a project using pytorch lightning. I'm happy to update this PR. I've updated to latest version, but I'm having trouble getting the auto_lr_find to work at all:
error trace
Edit: realize it may not be clear that the original motivation for this PR is that |
Codecov Report
@@ Coverage Diff @@
## master #3622 +/- ##
========================================
+ Coverage 86% 92% +6%
========================================
Files 113 199 +86
Lines 8551 12957 +4406
========================================
+ Hits 7361 11963 +4602
+ Misses 1190 994 -196 |
Hi @tbenst! Thanks for looking into this PR again. I have not been able to reproduce any of those issues using our bug report model: https://github.com/PyTorchLightning/pytorch-lightning/blob/master/pl_examples/bug_report_model.py Please, give it a try and open separate issues for those if you can reproduce. It's easier for us to track it that way. |
What is the status of this PR? |
Closing this PR as it has become stale. We would agree to merge this if somebody wants to take over the authorship. Thank you for your time! |
What does this PR do?
Here's a WIP pull request that closes #3494 and closes #3522.
I had hoped this would be a simple one line fix, like
getattr(self, x) if hasattr(self,x) else init_args[x]
and it nearly was, but upon running tests I found that pytorch-lightning supports a diverse array ofhparams
, includingomega_conf
andNamespace
, which greatly complicates things.Please look at the two new tests,
test_hparams_inplace_mutation
andtest_hparams_after_mutation
for understanding the intent.This is my first pull request so greatly appreciate any help or feedback!!
Status
6 tests fail, including one that I wrote!
The test I wrote that fails is surprising to me and appears to be a case of Black Magic, as only the final assert fails.
Before submitting
PR review
@edenlightning @Borda