Tensorboard dev
See original GitHub issueOne of the use cases we want to show for the CML site is producing a tensorboard link in the report. For example:
View your TensorBoard live at: https://tensorboard.dev/experiment/E31QaKfWTQaQuEUR6H03UA/
I’m running into some trouble using the tensorboard dev
command inside my GH runner. This is my workflow (project repo is here):
name: train-my-model
on: [push]
jobs:
run:
runs-on: [ubuntu-latest]
container: docker://dvcorg/cml-py3:latest
steps:
- uses: actions/checkout@v2
- name: dvc_cml_run
env:
repo_token: ${{ secrets.GITHUB_TOKEN }}
run: |
pip3 install -r requirements.txt
python train.py
tensorboard dev upload --logdir logs
I’ve confirmed the commands work on my local machine. On the runner, I’m getting this error message:
Traceback (most recent call last):
File "/usr/local/bin/tensorboard", line 8, in <module>
sys.exit(run_main())
File "/usr/local/lib/python3.6/dist-packages/tensorboard/main.py", line 75, in run_main
app.run(tensorboard.main, flags_parser=tensorboard.configure)
File "/usr/local/lib/python3.6/dist-packages/absl/app.py", line 299, in run
_run_main(main, args)
File "/usr/local/lib/python3.6/dist-packages/absl/app.py", line 250, in _run_main
sys.exit(main(argv))
File "/usr/local/lib/python3.6/dist-packages/tensorboard/program.py", line 289, in main
return runner(self.flags) or 0
File "/usr/local/lib/python3.6/dist-packages/tensorboard/uploader/uploader_main.py", line 633, in run
return _run(flags)
File "/usr/local/lib/python3.6/dist-packages/tensorboard/uploader/uploader_main.py", line 120, in _run
_prompt_for_user_ack(intent)
File "/usr/local/lib/python3.6/dist-packages/tensorboard/uploader/uploader_main.py", line 76, in _prompt_for_user_ack
response = six.moves.input("Continue? (yes/NO) ")
EOFError: EOF when reading a line
Continue? (yes/NO)
##[error]Process completed with exit code 1.
I tried passing in a “yes” with
echo "yes" | tensorboard dev upload --logdir logs
but got the same error. Does this make any sense given the setup of the runner?
Issue Analytics
- State:
- Created 3 years ago
- Comments:10 (10 by maintainers)
Top Results From Across the Web
TensorBoard.dev - Upload and Share ML Experiments for Free
TensorBoard is TensorFlow's visualization toolkit, enabling you to track metrics like loss and accuracy, visualize the model graph, view histograms of weights, ...
Read more >Introducing TensorBoard.dev: a new way to share your ML ...
It enables tracking experiment metrics, visualizing models, profiling ML programs, visualizing hyperparameter tuning experiments, and much more.
Read more >Tensorboard dev upload bug · Issue #3751 - GitHub
Unable to upload my experiment on tensorboard.dev. Here is my code : tensorboard dev upload --logdir gs://bioasq_clean --name "bioasq ...
Read more >Collaborating with TensorBoard.dev | Analytics Vidhya - Medium
Collaborating with TensorBoard.dev. Collaboration is a key aspect of Deep Learning and it requires sharing the details such as visualizing ...
Read more >How to Make Your TensorBoard Projects Easy to Share and ...
Firstly, TensorFlow has its own toolkit (TensorBoard.dev) for TensorBoard sharing. It's a good option to consider, but keep in mind that your TensorBoard ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Great work @DavidGOrtega! I had a feeling the authentication was going to take a little work. Looks like a similar approach to authenticating with GDrive as a DVC remote?
I’ll give your solution a go. Really cool
@andronovhopf this is a very interesting case. Probably a candidate to have its own cml wrapper @dmpetrov
First of all Tensorboard dev is expecting you to auth using OAuth, this process will generate a file inside your machine under
~/.config/tensorboard/credentials/uploader-creds.json
ala google drive or gs credentials.So, you must copy those JSON credentials and add them as a secret. Then within your approach you still need a Ctrl+c to cancel sending data to TB.
However this might not be the best approach. One of the best features is watching your model logs in real time so TB should be started first (as a fg process) and then train. However this procedure had a lots of caveats failing in many ways due to failures in the pipes. Also is very important to know whats the url to be checked during the training. Finally after some iterations this is actually the solution:
This solution is very good in a PR since it’s going to generate a comment telling you where to go aside of printing the url in the command line before start training.
Then is generating the final report also.
with secrets just replace
with