-
Notifications
You must be signed in to change notification settings - Fork 863
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
add_embedding expected hierarchy #10
Comments
This will be fixed together with #5. Maybe this weekend. |
I did not see it, my bad :) Keep up the good work :) |
Of course! |
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello again
I'm currently experimenting with the embeddings' visualization, and i'm having some troubles with the expected folder hierarchy. As far as I have understand, the add_embedding function does not have any timestep parameters (although there is one in the function called with value None), so it does not provide a time distributed visualization. The current hierarchy of my loggings is the following:
-project
--runs
---August14_11:24:12
----event.out
---August14_11:28:12
----event.out
i.e. every running gets his own directory with the SummaryWriter events (file event.out), and i can run everything using tensorboard from the project dir (tensorboard --logdir runs).
If I use add_embedding for one of the experiments with the following notation
I get one warning each time complaining about the fact the dir already exists, and the embedding log file get overwritten each time, so I can see only the last one written.
However if I log to a subdir with the following notation
I can't see any embedding in the visualization's page, and i have to run tensorboard directly in the embedding log directory (e.g. tensorboard --logdir runs/August14_11:28:12/emb0), which is a bit of a pain if I log every 25 batch.
Any solutions of best practices?
The text was updated successfully, but these errors were encountered: