Skip to content
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

0.9.0 rc16 tensorboard 2.3.0 can't find hparams data #3033

Closed
xiadingZ opened this issue Aug 18, 2020 · 3 comments · Fixed by #3132
Closed

0.9.0 rc16 tensorboard 2.3.0 can't find hparams data #3033

xiadingZ opened this issue Aug 18, 2020 · 3 comments · Fixed by #3132
Assignees
Labels
bug Something isn't working help wanted Open to be worked on priority: 0 High priority task

Comments

@xiadingZ
Copy link

tensorboard version: 2.3.0
pytorch-lightning version: 0.9.0 rc16

my code:

class Video_Base(pl.LightningModule):
    def __init__(self, hparams, *args, **kwargs):
        self.hparams = hparams

tensorbord 2.2.0 is ok, 2.3.0 can't show hparams, says no hparams data found

@xiadingZ xiadingZ added bug Something isn't working help wanted Open to be worked on labels Aug 18, 2020
@ananyahjha93 ananyahjha93 self-assigned this Aug 18, 2020
@ananyahjha93
Copy link
Contributor

@xiadingZ instead of setting self.hparams, can you try using self.save_hyperparameters() to save anything into self.hparams passed to the LightningModule?

@ananyahjha93 ananyahjha93 added the priority: 0 High priority task label Aug 18, 2020
@Borda
Copy link
Member

Borda commented Aug 18, 2020

lets freeze TB==2.2.0 for now and reopen this after 0.9 is out...

@ananyahjha93 ananyahjha93 removed their assignment Aug 18, 2020
@teddykoker teddykoker self-assigned this Aug 18, 2020
@teddykoker
Copy link
Contributor

Freezing TB, #3039, will reopen after 0.9

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working help wanted Open to be worked on priority: 0 High priority task
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants