tensorflow / tensorflow/tensorboard

Prioritize loading an events file

Open
#917 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

theme:performance theme:ui-polish
Dominant language
TypeScript
Stars
7.2k
Forks
1.7k
Avg merge
4d 22h
Merged PRs (30d)
1

Description

Lets of experiments

/some/path/mnist_experiments/
/some/path/mnist_experiments/run1/
/some/path/mnist_experiments/run1/events.out.tfevents.1456525581.name
/some/path/mnist_experiments/run1/events.out.tfevents.1456525585.name
/some/path/mnist_experiments/run2/
/some/path/mnist_experiments/run2/events.out.tfevents.1456525385.name

I would like it so that in the tensorflow gui I could tell tensorboard to load a specific events file first.
I would eventually like all of them to load but sometimes after I restart my computer I am in the middle of a training run and it loads that one last when I would like that one loaded first and then the other ones so I can compare and make sure it is doing the correct thing.

For example I have the list above

/tensorboard --logdir /some/path/mnist_experiments
Then I run this command but in the gui I can click something like "Load Now" next to the events file I want to load first. Like events.out.tfevents.1456525581.name

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing how TensorBoard discovers event files from the provided --logdir path and how the GUI currently loads them. Identify the loading order and the control that would need to trigger one selected file first; done means a user can choose an event file to load before the remaining files and compare the resulting runs.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.