Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Tensorboard.dev upload to specified experiment ID
See original GitHub issueCurrently, there is no way to upload new data to an existing experiment once the tensorboard client has been interrupted. However, this use case comes up very often (e.g. running a bunch of hyperparameter search experiments, then another bunch, or implementing a new model a few days later and wanting to compare). The only solution is to delete the older experiment and start a new experiment, assuming that the data exist on the same machine. This brings us to the second benefit: in case one is performing experiments on different machines, it is a lot more convenient to upload all to the same URL/experiment ID, than to aggregate the data (or mount the remote drives) on a single machine and then upload them to an experiment.
The proposed functionality would be evoked like this:
tensorboard dev update --experiment_id EXPERIMENT_ID --logdir logs
Issue Analytics
- State:
- Created 3 years ago
- Reactions:26
- Comments:11
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Thank you for your feature request @gzerveas, this is a request we have heard from several users, and something we will prioritize.
Tested a flow on this today, looks like it may be possible. Need to work around a few side effects.