tensorflow / tensorflow/tensorboard
FR: support for x-axis semantics other than "step"
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 7.2k
- Forks
- 1.7k
- Avg merge
- 4d 22h
- Merged PRs (30d)
- 1
Description
This issue had been migrated from tensorflow/tensorflow#10292.
Often I log scalar summaries at intervals that are meaningful in their own right — e.g. at epochs or min-batch boundaries — and report this, rather than the global step, as the x-value with something like
some_writer.add_summary(a_value, epoch_number)or
some_writer.add_summary(a_value, batch_number)But the API has no way of indicating that these x-values are not "steps", and reports them in the TensorBoard UI as "Steps", which they are not.
It would be nice to have a way of changing the "Steps" label to some other string (here, for example "Epoch" or "Batch").
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the add_summary call patterns in the issue and trace how the supplied x-value reaches the TensorBoard UI. Identify where the fixed “Steps” label and the related public API behavior are defined; done means users can supply meaningful x-axis semantics such as epochs or batches and see the corresponding label in the UI.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100