tensorflow / tensorflow/tensorboard

Display: Width of the image scroll slider is incorrect when samples_per_plugin is large

Open
#2,142 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

plugin:images stat:contributions welcome type:bug
Dominant language
TypeScript
Stars
7.2k
Forks
1.7k
Avg merge
4d 22h
Merged PRs (30d)
1

Description

TensorBoard version: 1.13.0.
TensorFlow version: I am using PyTorch 1.0.0 with TensorBoardX, but since it is a display issue, the backend should be irrelevant.
OS: Linux, 5.0.5-1-MANJARO
Python version: 3.7
Browser: Chrome 73.0.3683.103


I am running an adversarial attack with 3000 iterations, and I want to visualize the current image in each iteration (since a rapid change may occur between two iterations). The default setting only shows images in 10 steps, which is too sparse for me.

When I run tensorboard --logdir attack_mnist/ --samples_per_plugin=images=3000, the slider is rendered as follows:
image

Note that 2999 is the maximum value.

For reference, if I run tensorboard --logdir attack_mnist/ --samples_per_plugin=images=300, the display is normal:
image

If I run tensorboard --logdir attack_mnist/ --samples_per_plugin=images=500:
image

If I run tensorboard --logdir attack_mnist/ --samples_per_plugin=images=1000:
image

It seems that the width of the scroll slider is getting larger, while the range of the slidable area keeps the same.

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

Reproduce the image display with samples_per_plugin=images=3000 in Chrome and compare it with 300, 500, and 1000. Trace the image plugin's slider rendering, then verify that the slider width and usable range remain correct for large sample counts.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
data-visualization, frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.