A load tester data frame.
Properties
Property | Type | Description |
---|---|---|
Counter
|
ushort[] |
Gets the counter array. This is a ReceivedWords-long array of incrementing integers that is used for simulating the bandwidth of physical data sources. |
HubClockDelta
|
ulong |
Gets the difference between the hub clock and the loopback value at the moment the loopback value was received. This value is the result of subtracting the loopback value written by the LoadTesterLoopback operator from the device's hub clock counter value at the moment that the loop back value was received. Typically, the HubClock member is sent to LoadTesterLoopback operator such that this value is a hardware-timed measurement value of real-time latency. This value is only updated when a new loopback value is sent to the device using the LoadTesterLoopback operator. |
Clock
|
ulong |
Gets the acquisition clock count. Acquisition clock count that is synchronous for all frames collected within an ONI context created using CreateContext. The acquisition clock rate is given by AcquisitionClockHz. This clock value provides a common, synchronized time base for all data collected with an single ONI context. |
HubClock
|
ulong |
Gets the hub clock count. Local, potentially asynchronous, clock count. Aside from the synchronous Clock value, data frames also contain a local clock count produced within the oni.Hub that the data was actually produced within. For instance, a headstage may contain an onboard controller for controlling devices and arbitrating data stream that runs asynchronously from the AcquisitionClockHz. This value is therefore the most precise way to compare the sample time of data collected within a given oni.Hub. However, the delay between time of data collection and synchronous time stamping by Clock is very small (sub-microsecond) and this value can therefore be disregarded in most scenarios in favor of Clock. |