tensorflow / tensorflow/tensorboard
FR: better handling for out-of-order and duplicate steps
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 7.2k
- Forks
- 1.7k
- Avg merge
- 4d 22h
- Merged PRs (30d)
- 1
Description
Hi there,
For our particular application, we process metrics in a way that makes it hard to integrate with tensorboard without some finagling. Two features would be rad:
-
Out of order steps : we process / write metrics asynchronously, meaning that the steps in the associated tf.Event files are written out of order, causing garbled tensorboard plots. It'd be awesome if tensorboard had a way to digest steps out of order, and plot using just step as the x-value, order-independent.
-
Overwriting stale steps : we aggregate our metrics from different rounds of computation, meaning a metric written for a particular step (which we're overloading to mean something else for our application) can become stale. We need a way to overwrite this information as it becomes stale.
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
No files, tests, or entry points are named. Start by tracing how TensorBoard ingests tf.Event files and produces plots, then define completion as handling out-of-order steps and replacing stale values for duplicate steps.
Written by the indexing model from the issue text.
Assessment
- Domain
- data-visualization
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100