Skip to content
Qualia Docs

Datasets_GetCameraLags

GET
/v1/accounts/{account}/datasets/{dataset}/cameraLags
 
curl --request GET \
  --url https://dev-api.qualiastudios.dev/v1/accounts/example/datasets/example/cameraLags \
  --header 'X-API-Key: <X-API-Key>'

Reads per-camera lag estimates and current stamp offsets for an upload, or every upload held by a merged dataset. Untrusted estimates are reported but never applied implicitly.

Authorizations

Section titled “Authorizations ”

Parameters

Section titled “ Parameters ”

Path Parameters

Section titled “Path Parameters ”
account
required
string

The account id.

dataset
required
string

The dataset id.

Responses

Section titled “ Responses ”

200

Section titled “200 ”

OK

Media type application/json

The per-camera lag estimates and the current setting for each topic.

object
name

The camera lag view for the dataset requested.

string
cameras

Entries are grouped by upload; merged dataset topics are member-local.

Array<object>

One camera topic’s aggregate lag and current correction.

object
upload

The upload containing this camera.

string
topic

Camera topic in this upload.

string
estimatedLagMs

Median trusted per-episode lag; positive means camera content is late. Unset if no trusted estimate exists.

number format: double
confidence

Median confidence among trusted estimates.

number format: double
sampleCount

Episodes with a stored lag entry for this camera.

integer format: int32
trustedSampleCount

Episodes with a trusted, finite lag and confidence.

integer format: int32
appliedOffsetMs

Published channel stamp_offset_ms; unset means ingest uses zero.

number format: double
estimateApplicable

Whether the stored estimate can safely determine an absolute offset.

boolean
estimateUnavailableReason

Why the estimate cannot be applied; empty when it can be applied.

string
topicAvailable

Whether the ingest report proved this camera’s native topic mapping.

boolean
source

Provenance aggregated from stored per-episode values: recorded, estimated, mixed, or unknown.

string
method

Stored estimator/event method, mixed when multiple methods were recorded.

string
Example generated
{
  "name": "example"
}

default

Section titled “default ”

Default error response

Media type application/json

The Status type defines a logical error model that is suitable for different programming environments, including REST APIs and RPC APIs. It is used by gRPC. Each Status message contains three pieces of data: error code, error message, and error details. You can find out more about this error model and how to work with it in the API Design Guide.

object
code

The status code, which should be an enum value of [google.rpc.Code][google.rpc.Code].

integer format: int32
message

A developer-facing error message, which should be in English. Any user-facing error message should be localized and sent in the [google.rpc.Status.details][google.rpc.Status.details] field, or localized by the client.

string
details

A list of messages that carry the error details. There is a common set of message types for APIs to use.

Array<object>

Contains an arbitrary serialized message along with a @type that describes the type of the serialized message.

object
@type

The type of the serialized message.

string
key
additional properties
any
Example generated
{
  "code": 1,
  "message": "example",
  "details": [
    {
      "@type": "example"
    }
  ]
}