org.platanios.tensorflow.api.io.events
Calls flush()
and then closes the current event file.
Calls flush()
and then closes the current event file.
Returns true
if this event file writer has been closed.
Returns true
if this event file writer has been closed.
Filename suffix to use for the event file.
Filename suffix to use for the event file.
Pushes outstanding events to disk.
Pushes outstanding events to disk.
Specifies how often to flush the written events to disk (in seconds).
Specifies how often to flush the written events to disk (in seconds).
Maximum number of events pending to be written to disk before a call to write()
blocks.
Maximum number of events pending to be written to disk before a call to write()
blocks.
Reopens this event file writer.
Reopens this event file writer.
Directory in which to write the event file.
Directory in which to write the event file.
Writes the provided event to the event file.
Writes the provided event to the event file.
Writes a Graph to the event file along with its meta-information.
Writes a Graph to the event file along with its meta-information.
This method wraps the provided graph in an Event
protocol buffer and writes it to the event file. The provided
graph will be displayed by TensorBoard. Most users pass a graph in the constructor instead.
Graph to write.
Global step number to record with the graph.
Writes a GraphDef to the event file.
Writes a GraphDef to the event file.
This method wraps the provided GraphDef in an Event
protocol buffer and writes it to the event file.
GraphDef to write.
Global step number to record with the GraphDef.
Writes a MetaGraphDef to the event file.
Writes a MetaGraphDef to the event file.
This method wraps the provided MetaGraphDef in an Event
protocol buffer and writes it to the event file.
MetaGraphDef to write.
Global step number to record with the MetaGraphDef.
Writes run metadata information for a single Session.run()
call to the event file.
Writes run metadata information for a single Session.run()
call to the event file.
Run metadata to write.
Tag name for these metadata.
Global step number to record with the summary.
IllegalArgumentException
If the provided tag has already been used for this event type.
Writes a SessionLog to the event file.
Writes a SessionLog to the event file.
This method wraps the provided session log in an Event
protocol buffer and writes it to the event file.
Session log to write.
Global step number to record with the session log.
Writes a Summary
protocol buffer to the event file.
Writes a Summary
protocol buffer to the event file.
This method wraps the provided summary in an Event
protocol buffer and writes it to the event file.
Summary to write.
Global step number to record with the summary.
Writes a Summary
protocol buffer to the event file given a string representation of that protocol buffer.
Writes a Summary
protocol buffer to the event file given a string representation of that protocol buffer.
This method wraps the provided summary in an Event
protocol buffer and writes it to the event file.
You can pass the result of evaluating any summary op (e.g., using Session.run()
) to this function.
String representation of the summary to write.
Global step number to record with the summary.
Writes
Summary
protocol buffers to event files for use with TensorBoard.The SummaryFileWriter class provides a mechanism to create an event file in a given directory and add summaries and events to it. The class updates the file contents asynchronously. This allows a training program to call methods to add data to the file directly from the training loop, without slowing down training.
On construction the summary writer creates a new event file in
workingDir
. This event file will containEvent
protocol buffers constructed when you call one of the following functions:writeGraph()
,writeSummary()
,writeSessionLog()
, orwriteRunMetadata()
.If you pass a
Graph
to the constructor it is write to the event file, which is equivalent to callingwriteGraph()
later on.TensorBoard will pick up the graph from the file and display it graphically so you can interactively explore it. You will usually pass the graph from the session in which you launched it: