-
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
Hparams are not automatically saved to WandB logger in 1.0.2 #4179
Comments
If you aren't doing anything fancy w/ your args, its usually easier to explicitly type them. That's my quick answer, but it doesn't solve your problem. I've never used Wandb, but I'm giving it a go right now 😄 . will let ya know |
well we are saving the initial arguments, so you should be calling EDIT: the reccomended flow is: class MyModule(pl.LightningModule):
def __init__(self, arg1, arg2):
super().__init__()
self.save_hyperparameters()
... |
Yeah your issue is solved if you just switch to using class YourModel(pl.LightningModule):
def __init__(self, **kwargs):
super().__init__()
self.save_hyperparameters()
# ... This made it work fine for me. seeing the correct hparams on WandB |
Feel free to reopen if needed :] |
I also recommend writing the args explicitly. code just reads better that way (imo). |
🐛 Bug
When I update to 1.0.2, when I assign
self.hparams = args
in Lightning module, the hparams are not logged in WandB anymore. This bug is not present in 1.0.0 however. Snippets of my code.The text was updated successfully, but these errors were encountered: