Skip to main content
Skip table of contents

Diagnostics

Command

NONE
StartDiagnostic(File = Absolute file path) 
.....
StopDiagnostic() 

Data.csv is stored in the file path when StopDiagnostic is called.

Breeze Client

Start Breeze Client and go into the “Diagnostic” tab.

Start diagnostics by clicking on the “Start diagnostics” button:

image-20241014-100024.png

When stopping diagnostics it will automatically generate statistics plots in the specified breeze-runtime-statistics folder:

image-20241014-100227.png

The diagnostic information overview

Name

Description

Unit

Index

Incrementing number started at 1

Number

Seconds

Seconds from diagnostic start

Seconds

FrameNumber

Frame number from camera

Number

CameraTime

Not implemented

InDiff

Time difference between two In frames from camera

Ms

DroppedFrames

Number of dropped frames

Number

BufferSize

Elements in camera line buffer

Number

QueueSize

Elements in prediction frame queue

Number

PredictionTime

Prediction time

Ms

OutDiff

Time difference between two Out frames

Ms

Delta

Time difference between In and Out Time

Ms

TransferTime

Transfer time to client

Ms

Logging

The Breeze Runtime log file is located in the {home directory}/.Prediktera folder and is called BreezeRuntime.log

The default logging is in Debug level in the log file and Info level for the console.

For more logging, this level can be changed to for example Trace in the NLog.config file. This file is located in the {program files}/Prediktera/Breeze/Runtime folder.

Current settings in NLog.config file:

XML
<rules> 
  <logger name="*" minlevel="Debug" writeTo="logfile" />
  <logger name="*" minlevel="Info" writeTo="console" />
</rules> 

The log file logging can also be accessed from Breeze Client under Diagnostics. This log information is updated manually by clicking and the “Refresh” button and can be exported by clicking on the “Save” button.

image-20241014-100419.png

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.