tensorflow / tensorflow/tensorboard

Ability to Collapse Sub-Runs with Hierarchical Naming Convention

Open
#6,225 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

core:frontend type:feature
Dominant language
TypeScript
Stars
7.2k
Forks
1.7k
Avg merge
4d 22h
Merged PRs (30d)
1

Description

Summary

As a user of TensorBoard, I find it challenging to navigate and analyze data when working with many runs or custom logs. I would like TensorBoard to have a built-in feature that allows me to collapse sub-runs with a hierarchical naming convention. This would enable me to better organize and visualize my runs and significantly improve my user experience.

Background

TensorBoard currently lacks the ability to collapse sub-runs in this way. Although the "Regex Filter" feature can group runs based on a regular expression, it is not as intuitive or convenient as the proposed feature. By collapsing sub-runs with hierarchical names, I would be able to easily see the relationship between different runs and better understand how they fit into my overall analysis.

Proposed Solution

I propose that TensorBoard add a feature to collapse sub-runs with the naming convention of "parent_run/child_run/...". Ideally, the collapsed sub-runs would appear as a single entry with a toggle button to expand or collapse the view. This feature would make it easier for users to visualize and organize their runs and improve the overall usability of TensorBoard.

Current solution:
image

Proposed solution:
Screenshot 2023-03-08 010316

Conclusion

As a researcher who frequently works with deep learning models, I rely on TensorBoard to monitor the performance of my experiments. By adding the ability to collapse sub-runs with a hierarchical naming convention, TensorBoard would become a more efficient tool for organizing and analyzing data. I hope this feature request can be considered for implementation in a future release. Thank you.

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 reviewing TensorBoard's existing Regex Filter and the run visualization shown in the issue. Define how slash-separated parent_run/child_run names should appear, how expansion and collapse should work, and how the behavior should be validated against the proposed UI.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
data-visualization, frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.