-
Notifications
You must be signed in to change notification settings - Fork 281
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
Tensorboard Logging #37
Comments
I agree and am currently thinking about other ways of logging (also because tb logs are very memory inefficient). Do you have any suggestions? If you want I could also point you to where the logs are performed and you could write a PR |
Mh - I'm not sure whether ditching tensorboard in general makes sense 🤔 I think with pytorch and tensorflow using it, that makes it kind of a standard? I found where the logging is done and I will look into it. Do you know why logging would be memory-inefficient? Running the tensorboard-server surely is, but on the logging-side of it, shouldn't the logs just be written to the file regularly? I'll have a look but for now I'll be installing |
In my opinion, it would be better if seperate logging is made for each model. Something like,
Different I think we can have another But as the number of models gets large, it will be soon very crowded. But you can filter some of the models. |
@maxmarketit Yes! Separate writers for separate models / training processes would be a good idea. I'm just not sure where to create and where to pass the writer in this pipeline... |
@shukon I might not understand the situation here but I do not see any problem I think we can set the root directory and every model trained can saved to subdirectory with appropriate name which convealing main architecture 'resnet-100-20-30' or 'shapedmlpnet-diamond-...-...' and as the optimization goes, it could change to resnet-100-20-30-i01' '-i02' '-i03' etc |
Currently
tensorboard_logger
is used. I don't think it's actively supported anymore, they point to pytorch's own tensorboard-module on their Github.Why bother?
tensorboard_logger
uses a singleton-default-logger and I cannot reset the path to write the tensorboard-eventfiles. That would be helpful though, to distinguish between different configurations when refitting configurations from the incumbent-trajectory :)The text was updated successfully, but these errors were encountered: