diff options
author | A. Unique TensorFlower <gardener@tensorflow.org> | 2017-05-26 16:08:42 -0700 |
---|---|---|
committer | TensorFlower Gardener <gardener@tensorflow.org> | 2017-05-26 20:13:00 -0700 |
commit | 649040011e628a93f0b6894d2a8c8cbb05b6d640 (patch) | |
tree | 83f53959fa13d152c20cd1368954b86eaa1b5d18 /third_party/hadoop | |
parent | 1f9529b8dc1868a980297b7843d2fbae97062179 (diff) |
Create a set of sample data for the scalars plugin
We aim to provide for each plugin a set of sample data satisfying the
following properties:
- The data is of a realistic form.
- The data is sufficient to exercise all capabilities of the plugin.
- The data is not completely boring.
Such data then serves many purposes: it is documentation for this
particular plugin; it is documentation for TensorFlow and TensorBoard in
general; it can be used for manual testing of TensorBoard; and it can be
used in the plugin's unit tests. Ideally, we'll also be able to create a
script to aggregate the test data from all first-party plugins,
providing a single data set that can be used to comprehensively test
TensorBoard.
To start us off, this change adds such data for the scalars plugin. It's
realistic in that it has a few thousand steps and a few dozen runs. It
enables testing smoothing (due to the added noise), tag groups (due to
the various summary names), and run filters (due to the combinatorial
run parameters). And it's implementing a tiny physics simulation, so
it's not _entirely_ boring!
PiperOrigin-RevId: 157274669
Diffstat (limited to 'third_party/hadoop')
0 files changed, 0 insertions, 0 deletions