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

Log hyperparameters in tensorboard #384

Merged
merged 3 commits into from
Jul 14, 2020
Merged

Conversation

jancio
Copy link

@jancio jancio commented Jul 13, 2020

Log both hyperparameters and command line options in tensorboard.

🛠️ PR Summary

Made with ❤️ by Ultralytics Actions

🌟 Summary

Enhanced TensorBoard logging with hyperparameter tracking in YOLOv5 training.

📊 Key Changes

  • Added recording of hyperparameters to TensorBoard during the training process.

🎯 Purpose & Impact

  • Purpose: To allow users to track and visualize the hyperparameters used during the model training in TensorBoard.
  • Impact: Provides better experiment tracking and facilitates the comparison of different training runs, which can lead to more informed decisions and improvements in model performance. 🚀

Log both hyperparameters and command line options in tensorboard.
@glenn-jocher
Copy link
Member

@jancio good idea!

img-size is not height and width though, it is train and test sizes. Can you fix this?

@jancio
Copy link
Author

jancio commented Jul 14, 2020

Oh, ok, thanks for pointing this out. I will fix that.

Janko Ondras and others added 2 commits July 14, 2020 08:48
This updates the PR to a one-liner to minimize additions. Perhaps we can include opt in the future but let's start with this for now.
@glenn-jocher glenn-jocher merged commit 1e94bcf into ultralytics:master Jul 14, 2020
@glenn-jocher
Copy link
Member

@jancio the hyp to tensorboard update is having some strange effects. Each run is showing up on tensorboard twice. For example exp3 and exp4 are single runs below, but they show up with this additional garbage string folder in them when the hyps are added. I think I'm going to comment this out for now until there's a fix. Do you know why this is happening and what we can do to resolve?

Screen Shot 2020-07-15 at 10 35 29 AM

@jancio
Copy link
Author

jancio commented Jul 29, 2020

I have tried couple of things but didn’t help. Do you think it is a tensorboard issue?

@glenn-jocher
Copy link
Member

glenn-jocher commented Jul 29, 2020

@jancio yeah I think it's just a tensorboard issue, you might want to raise an issue on the pytorch or tensorboard repos. In any case the hyps are saved in the run directory as hyp.yaml.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants