From 26216f7f72cc02a33754eb7e6ca73826bd389748 Mon Sep 17 00:00:00 2001 From: Malcolm Slaney Date: Wed, 28 Jul 2021 20:45:27 -0700 Subject: [PATCH 1/4] Update README.md to include no-data example Added an example of what good and bad event files might contain. As a less than full-time user of TB, I see this problem a lot, and I would really love to see good and bad examples so I more easily know what I'm seeing. Alternative suggestions welcome. --- README.md | 24 ++++++++++++++++++++++++ 1 file changed, 24 insertions(+) diff --git a/README.md b/README.md index d645fc056a..0bbfbf4760 100644 --- a/README.md +++ b/README.md @@ -254,6 +254,30 @@ tensorboard in inspect mode to inspect the contents of your event files. `tensorboard --inspect --logdir DIRECTORY_PATH` +An empty event file (from a Keras job that starts output at batch 2) might look like this: + +``` +tensor + first_step 0 + last_step 2 + max_step 2 + min_step 0 + num_steps 2 + outoforder_steps [(2, 0), (2, 0), (2, 0)] +``` + +while an event file with more data might look like this: + +``` +tensor + first_step 0 + last_step 55 + max_step 250 + min_step 0 + num_steps 60 + outoforder_steps [(2, 0), (2, 0), (2, 0), (2, 0), (50, 9), (100, 19), (150, 29), (200, 39), (250, 49)] +``` + ### TensorBoard is showing only some of my data, or isn't properly updating! > **Update:** After [2.3.0 release][2-3-0], TensorBoard no longer auto reloads From 005d49dcb40934eaaec014a04e96a7db9c7b84da Mon Sep 17 00:00:00 2001 From: Malcolm Slaney Date: Mon, 2 Aug 2021 16:18:45 -0700 Subject: [PATCH 2/4] Better description of the state of the event files. --- README.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 0bbfbf4760..3799b1b36d 100644 --- a/README.md +++ b/README.md @@ -254,8 +254,9 @@ tensorboard in inspect mode to inspect the contents of your event files. `tensorboard --inspect --logdir DIRECTORY_PATH` -An empty event file (from a Keras job that starts output at batch 2) might look like this: - +The output for an event file corresponding to a blank TensorBoard may still sometimes +show a few steps, representing a few initial events that aren't shown by TensorBoard +(for example, when using the Keras TensorBoard callback): ``` tensor first_step 0 @@ -266,7 +267,7 @@ tensor outoforder_steps [(2, 0), (2, 0), (2, 0)] ``` -while an event file with more data might look like this: +In contrast, the output for an event file with more data might look like this: ``` tensor From 4dca28b2f1ea453d4b8a1884bd8ad67f7ae826b4 Mon Sep 17 00:00:00 2001 From: Malcolm Slaney Date: Mon, 2 Aug 2021 16:27:59 -0700 Subject: [PATCH 3/4] Better explanation of empty event file --- README.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 3799b1b36d..c9b5c0f64c 100644 --- a/README.md +++ b/README.md @@ -254,9 +254,10 @@ tensorboard in inspect mode to inspect the contents of your event files. `tensorboard --inspect --logdir DIRECTORY_PATH` -The output for an event file corresponding to a blank TensorBoard may still sometimes -show a few steps, representing a few initial events that aren't shown by TensorBoard -(for example, when using the Keras TensorBoard callback): +The output for an event file corresponding to a blank TensorBoard may +still sometimes show a few steps, representing a few initial events that +aren't shown by TensorBoard (for example, when using the Keras TensorBoard callback): + ``` tensor first_step 0 From c6f63cb99f09f6481a52a0bb32d4fe3ce18707da Mon Sep 17 00:00:00 2001 From: Malcolm Slaney Date: Wed, 4 Aug 2021 12:50:37 -0700 Subject: [PATCH 4/4] Removing white space at the end of the line --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index c9b5c0f64c..8b36e1e5bf 100644 --- a/README.md +++ b/README.md @@ -254,8 +254,8 @@ tensorboard in inspect mode to inspect the contents of your event files. `tensorboard --inspect --logdir DIRECTORY_PATH` -The output for an event file corresponding to a blank TensorBoard may -still sometimes show a few steps, representing a few initial events that +The output for an event file corresponding to a blank TensorBoard may +still sometimes show a few steps, representing a few initial events that aren't shown by TensorBoard (for example, when using the Keras TensorBoard callback): ```