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

Support ignoring certain directories under the logdir #70

Open
wchargin opened this issue Jun 16, 2017 · 9 comments
Open

Support ignoring certain directories under the logdir #70

wchargin opened this issue Jun 16, 2017 · 9 comments
Labels
core:backend theme:ui-polish Features or fixes that make core UI more pleasant. theme:usability Areas to reduce confusion and frustration. type:feature

Comments

@wchargin
Copy link
Contributor

Migrated from tensorflow/tensorflow#7385.

@cipri-tom
Copy link

cipri-tom commented Jan 21, 2018

so, any plans to support this ? :) it would be very welcome

I had a look at the code and I think it doesn't require too much knowledge of the inner workings. I think this part, where it takes a path_filter, is the relevant one. My confusion is that it is called from both event_accumulator.py and the plugin_event_accumulator.

So, I would be happy to contribute this small feature, provided that someone from the team can:

  1. decide on which of the previous approaches to take
  2. explain the difference between the event_accumulator and its corresponding plugin_...

To re-state the options:

  1. If there is special character(like #) in folder name, just ignore it.
  2. Like git, .ignore file manage folders to ignore.
  3. If .nolog file in the folder to ignore.(Like .nomedia file)

@eliorc
Copy link

eliorc commented Aug 15, 2018

This feature would help a lot.

Once you get to over 15 different models, the tensorboard takes too long to load and fails to load all the logs often.
Also the colors cycle start to get confusing

@stefan-falk
Copy link

stefan-falk commented Oct 8, 2018

Totally agree. :) Wouldn't hurt if one could just use wildcards e.g.

tensorboard --logdir modelname_*/ 

@gabegrand
Copy link

Any plans to support this feature in 2019? It would be most welcome.

@fuzihaofzh
Copy link

Also need this feature.

@bileschi bileschi added core:backend theme:ui-polish Features or fixes that make core UI more pleasant. theme:usability Areas to reduce confusion and frustration. labels Jan 2, 2020
@shtratos
Copy link

Here's a workaround for specifying path patterns with some bash-fu and a "discouraged" --logdir_spec option which supports loading a comma-separated list of multiple directories :

tensorboard --logdir_spec $(ls -m -d ./runs/2020-01-* | tr -d ' \n')

We use 2 ls flags here: -m sets delimiter to , (comma, space) and -d lists directories without their contents.

It assumes there are no commas or spaces in your log directory paths. You can use find for more complex cases.
More ways to concatenate list of paths with a comma

@wchargin
Copy link
Contributor Author

@shtratos: The main point of this feature request is that the globs be
resolved dynamically by TensorBoard, such that if you were to add a new
./runs/2020-01-* directory at runtime it would show up without having
to restart the process.

If you’re satisfied with invocation-time glob resolution, you can use
the multitb shell function from the following comment, which is safer,
does not have restrictions on the characters in your path name, does not
use --logdir_spec, and works even if you have runs of the same name in
different sub-logdirs:
#179 (comment)

@LarsHill
Copy link

LarsHill commented May 6, 2022

Any updates on this in 2022?

@roj4s
Copy link

roj4s commented Jun 2, 2022

You can create symbolic links of the selected list of experiments you want to upload. Let say you have a folder with experiments A, B, C and D, create a folder E and fill it with symbolic links to A and B only .. then run tensorboard dev upload on folder E.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
core:backend theme:ui-polish Features or fixes that make core UI more pleasant. theme:usability Areas to reduce confusion and frustration. type:feature
Projects
None yet
Development

No branches or pull requests

10 participants