Episodes_SampleEpisodeSeries
const url = 'https://dev-api.qualiastudios.dev/v1/accounts/example/datasets/example/episodes/example:sampleSeries';const options = {method: 'GET', headers: {'X-API-Key': '<X-API-Key>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url https://dev-api.qualiastudios.dev/v1/accounts/example/datasets/example/episodes/example:sampleSeries \ --header 'X-API-Key: <X-API-Key>'The episode’s joint series: each state and action channel sampled evenly over the take’s current content: the joints drawer’s charts, and the arm’s motion the camera lag drawer sets each camera’s offset against. Its window says where those samples sit in the episode’s recording. A handheld take resolved at its TCP also has the hands’ TCP poses, when streams names TCP. A take in no published version yet answers unpublished, with no channels; FAILED_PRECONDITION means the published content cannot be sampled (a column type it cannot read, say).
Authorizations
Section titled “Authorizations ”Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters ”The account id.
The dataset id.
The episode id.
Query Parameters
Section titled “Query Parameters ”Samples to return at most, 2 to 2000; 400 when unset. A take with fewer frames returns every frame. The first and last frame are always samples.
The vectors to sample, each at most once; STATE and ACTION when empty (TCP only when named). A take whose action cannot be read still answers for its state alone, and one with no TCP (not a handheld take resolved at its TCP) answers for the rest without it.
Read as this version froze it (QUA-3539): a tag, stable, v0 or a
digest prefix; empty or head reads the episode as it is now. As
GetEpisodeRequest.version: the series of the member that version holds.
Responses
Section titled “ Responses ”OK
Response for Episodes.SampleEpisodeSeries.
object
Seconds from the first frame sampled, one per sample: a sample’s second of the episode’s recording is this plus window_start_seconds.
Every channel the recording carries, on time_seconds.
One channel: one component of the state or the action vector.
object
Which vector.
Its positional key, “state[3]” or “action[3]”; the dataset’s robot interface names the positions. A TCP channel is named, “left.tcp.x”.
One value per sample; 0 where valid is false.
Per sample: false where the recording holds no finite value.
The recording’s frames per second.
Frames sampled: the take’s, or what its applied trim keeps.
True when the take is in no published version yet (a split child before its publish): it has no channels to sample.
Where the first frame sampled sits in the episode’s recording, in seconds of the recording (the clock its trim, subtasks and markers are in), on that frame: 0 until a trim is applied, the trim’s start once one is; a split’s piece is a recording of its own, so 0. Unset with unpublished.
Where the frames sampled end in the recording, in the same seconds: the end of the last one (window_start_seconds plus frame_count / fps). Unset with unpublished.
Example
{ "channels": [ { "stream": "STREAM_UNSPECIFIED" } ]}default
Section titled “default ”Default error response
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
The status code, which should be an enum value of [google.rpc.Code][google.rpc.Code].
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.
A list of messages that carry the error details. There is a common set of message types for APIs to use.
Contains an arbitrary serialized message along with a @type that describes the type of the serialized message.
object
The type of the serialized message.
Example generated
{ "code": 1, "message": "example", "details": [ { "@type": "example" } ]}