Visualisation with TensorBoard
Support the site!
You can also support LearningTensorFlow.com by becoming a patron at Patreon. If we have saved you trawling through heavy documentation, or given you a pointer on where to go next, help us to create new lessons and keep the site running.
In this lesson we will look at how to create and visualise a graph using TensorBoard. We lightly went over TensorBoard in our 1st lesson on variables
So what is TensorBoard and why would we want to use it?
TensorBoard is a suite of web applications for inspecting and understanding your TensorFlow runs and graphs. TensorBoard currently supports five visualizations: scalars, images, audio, histograms, and graphs. The computations you will use in TensorFlow for things such as training a massive deep neural network, can be fairly complex and confusing, TensorBoard will make this a lot easier to understand, debug, and optimize your TensorFlow programs.
To see a TensorBoard in action, click here.
This is what a TensorBoard graph looks like:
The basic script
Below we have the basic script for building a TensorBoard graph. Right now, all this will return if you run it in a python interpreter, is 63.
Now we add a
SummaryWriter to the end of our code, this will create a folder in your given directory, Which will contain the information for TensorBoard to build the graph.
If you were to run the TensorBoard now, with
tensorboard --logdir=path/to/logs/directory, you would see that in your given directory you get a folder named ‘output’.
If you navigate to the ip address in your terminal, It will take you to your TensorBoard, Then if you click graphs you will see your graph.
At this point the graph is kind of all over the place and is fairly hard to read. So lets name some of the parts to make it more readable.
In the code below we have only added one
parameter a few times.
parameter will take the selected area and give it a name on the graph.
Now if you re-run your python file and then run
tensorboard --logdir=path/to/logs/directory again, you will now see that your graph has some names on
the specific parts you named. However it is still very messy and if this was a huge neural network it would be next to impossible to read.
If we give the graph a name by typing
with tf.name_scope("MyOperationGroup"): and give the graph a scope like this
when you re-run your TensorBoard you will see something very different. The graph is now much more easier to read, and you can see that it all comes under the
graph header, In this case that is MyOperationGroup, and then you have your scopes A and B, Which have there operations within them.
As you can see, the graph is now a lot easier to read.
TensorBoard has a wide range of features, some of which we will cover in future lessons. If you want to dive deeper, start by watching this video from the 2017 TensorFlow Developers Conference.
In this lesson we looked at:
- The basic layout for a TensorBoard graph
- Adding the Summary writer to build a TensorBoard
- Adding names to the TensorBoard graph
- Adding a name and scopes to the TensorBoard
There’s a great 3rd party tool called TensorDebugger (TDB), TBD is as it says a debugger. But unlike the standard debuggers that are built into the TensorBoard, TBD interfaces directly with the execution of a TensorFlow graph, and allows for stepping through execution one node at a time. Where as the standard TensorBoard debugger cannot be used concurrently with running a TensorFlow graph and log files must be written first.
- Install TBD from here and read the material (try the demo!).
- Use TBD with this gradient descent code, Plot a graph showing the debugger working through the results and print the predicted model. ( Note: this is 2.7 compatible only )
These special icons are used for constants and summary nodes.
We have an increasing set of lessons that we hope guides you through learning this powerful library. Follow these links to keep going to our next lesson.
You can also use the nav menu at the top of the page to go directly to a specific lesson.
Coming soon (although not written by us):