Terminology =========== This documentation uses certain terminology - please see below for an explanation of what each of these terms mean Actor ----- An actor represents a physical human in the capture input. They can have a height as well as a unique identifier. When used in an Actor Skeleton Run will generate resources that more accurately represent the actors skeleton. Actor Skeleton -------------- .. warning:: **Not yet implemented** An actor with a skeleton attached. The skeleton can be generated via an Actor Skeleton Run Actor Skeleton Run ------------------ .. warning:: **Not yet implemented** The process of taking an actor object and generating a skeleton resource. A skeleton is used by the Mocap Run to more accurately model how an actor moves. Camera Settings --------------- Defines the capture device camera settings. This includes attributes such as resolution, focal length and distortion coefficients. This camera settings can be used across multiple Capture Devices. Camera Settings are optional for singlecam captures - but required for multicam captures Capture ------- A capture contains a list of Video Capture Sources (and optionally Capture Sources). This is used to group Capture Sources together for processing. Capture Device -------------- This defines the physical capture device used in a shooting setup. A capture device consist of it’s camera settings and a device id. Capture Input ------------- A Capture Input links a Resource to a specific Capture Device. A Capture Input Resource could be any type of non-video resource (i.e. depth data) Video Capture Input ------------------- A Capture Input that is used specifically for video resources Clap Audio Sync --------------- A sync method which defines the times to use for syncing when multiple Video Capture Sources exist on a Capture Time Code Sync -------------- A sync method which defines the time codes to use for syncing when Video Capture Sources exist on a Capture Options ------- Boolean values that affect how compute processes the Mocap Run. These options could differ depending on whether there is a single Video Capture Source or multiple Mocap Run --------- Combines Capture Inputs, Actors, Options and a volume into a single entity that will be given to an compute instance to process. The output of this will be the requested mocap resources Resource -------- A Resource is either an input or an output to a type of Run (Mocap, Aruco Volume, Actor Volume). A Resource consists of a uri as a full identifier as well as the type of resource and the service that is used to store this Resource. Capture Volume -------------- A capture volume is created by an Aruco Volume Run or an Actor Volume Run. It takes the specified input Resources and will generate volume calibration resources that are stored in the requested uri-prefix as Resources. The resource names are handled by the SDK. Aruco Volume Run ---------------- A run that creates volume calibration resources using an aruco board Actor Volume Run ---------------- A run that creates volume calibration resources using an actor EC2 Compute ----------- A specific compute class that can be used to provision a Mocap Run using EC2 EC2 Region ---------- Region configuration for the AWS region in which the EC2 instance will be provisioned