Get desktop application:
View/edit binary Protocol Buffers messages
Service to store evaluation metrics
===== GET ENDPOINTS, for external fetch =============
Get loglines, based on query
Get evaluation metrics records, based on query
Add evaluation metrics record
Add log line record
Add evaluation metrics record
Add log line record
Delete all evaluation metrics belonging to a training job or user id
Delete all log lines belonging to a training job or user id
Delete all log lines belonging to a training job or user id
===== In case you want it to say "Hello" =========
(message has no fields)
***
Used as response type in: TrainingData.AddEMetrics, TrainingData.AddEMetricsBatch, TrainingData.AddLogLine, TrainingData.AddLogLineBatch
Used in:
Used in:
The following two options are exclusive
Used as response type in: TrainingData.DeleteEMetrics, TrainingData.DeleteJob, TrainingData.DeleteLogLines
Used as request type in: TrainingData.AddEMetrics
Used as response type in: TrainingData.GetEMetrics
Used as field type in:
Repeated, order-dependent list of temporal keys Example: {"iteration": 209}
Group label, such as test, train, or validate
/ {"cross_entropy": 0.4430539906024933, "accuracy": 0.8999999761581421}
Used as request type in: TrainingData.AddLogLine
Used as response type in: TrainingData.GetLogs
Used as field type in:
Used in:
, ,Unique id identifying the training job
Unique id identifying the user
Time that the metric occured: representing the number of millisecond since midnight January 1, 1970.
Sequential index
Optional subid
Playing with semi-generalized query request.
Used as request type in: TrainingData.DeleteEMetrics, TrainingData.DeleteJob, TrainingData.DeleteLogLines, TrainingData.GetEMetrics, TrainingData.GetLogs
The following three options are exclusive
representing the number of milliseconds since midnight January 1, 1970.
Only get this many records
The starting position. If positive or zero, count from beginning, if negative, count from end.
Used in: