Definitions of common Tritium platform terms. For Animator-specific vocabulary, see the Animator glossary. For a product overview, see Understanding Tritium.
The process that determines which Demand gets to control any given part of the robot. Arbitration resolves conflicts when, for example, different Scripts try to drive the same joint in different ways. See Arbitration.
Any piece of content that can be used and re-used for animating a robot, such as audio files, Poses, Clips, or Projects. Assets can be transferred between shared repositories and a robot's local storage, from where they can be used by the robot. See Tritium UI — Assets.
A segment of animation. Clips are Assets that can be used on a Timeline to animate various parts of the robot. They consist of a set of Controls each following a Curve through various Keyframes.
An abstraction used to set and get the position of one or more parts of a robot. Controls can be thought of as knobs that can go from a minimum to a maximum value. Different Controls can address the same body parts, or one Control could affect multiple body parts. Controls are organised in Namespaces. See Tritium OS — Controls.
A description of how an individual Control changes value over time during an animation. Curves start and end at Keyframes and can be Step, Linear, or Bezier.
A request by some part of the system to set a given Parameter to a specific value. Because of Arbitration and physical or simulated speed limits, the real-time Parameter value may differ from or lag the Demand.
A piece of hardware within the robot which can be individually addressed. Script Devices are scripts which expose Parameters to the system, allowing live reading or writing of such Parameters exactly like hardware Devices. See Script devices.
A Node which is responsible for interfacing with Devices. It implements communication with Devices over their own protocol, translating requests from the rest of the system into the Device's protocol and transport. A Device Host publishes detailed information on each Device, in the form of Parameter metadata, to the rest of the system.
A machine running Tritium OS.
An instant in an animation that defines the starting, ending, or a midway point in the animation. All other instants are interpolated from keyframes.
A collection of Parameters that have been selected to be displayed on the Devices page. Saving and using Layouts removes the need to find the appropriate Parameters to display one by one.
A related set of Controls which address the robot in a logically similar way. Namespaces allow addressing the robot in the most intuitive or appropriate way for the task at hand — for example, a Namespace where eyelid Controls go from 0 to 1 instead of one where Controls deal with raw motor positions.
A self-contained building block of a Tritium system that runs in its own process, providing a specific service or capability. For example, the Scripts Node is the process that runs all Python scripts on a robot. See Tritium OS — Nodes.
A value exposed by a Device (or Script Device) which can be read or written in real time. See Tritium OS — Parameters.
An Asset specifying a set of Controls and a value for each. Poses are useful for driving animation from Scripts, or recalling a specific robot position. See Tritium UI — Poses.
A variable in a Script that has been marked as watchable for monitoring and debugging purposes. Probes appear live in Tritium UI and in logs. See Tritium UI — Scripts.
The top-level Asset that describes an animation. Projects contain copies of all other Assets that are necessary to reproduce the animation.
The set of 3D objects present in an animation, such as robots, lights, and their layout in 3D space.
A Python script that can be run within a Tritium system. Scripts have a user-friendly, easily debuggable API to interact with the robot and the rest of the Tritium platform. See Tritium OS — Scripts.
A source of media input, such as a microphone or a camera.
An animation Project which can be played by Scripts or Telepresence.
A mode of teleoperation whereby the operator can speak through the robot's speaker, see through the robot's eyes, and play Sequences for the robot to perform, together with the Tritium software tools that enable such teleoperation. See Telepresence.
A collection of animation Tracks displayed together. A Project can contain multiple timelines.
A linear sequence along a Timeline where different Track Items are placed for editing purposes. Each track is independently editable, but when played together, all tracks contribute to the final combined result of the animation.
An individual Asset placed on a Track, such as audio or animation Clips.