docs.unity3d.com
Search Results for

    Show / Hide Table of Contents

    Glossary

    Learn about terms relevant to Simulation Pro.

    Term Definition
    ArticulationBody Unity's physics component for jointed, robot-like structures. The URDF importer creates a RevoluteJoint, PrismaticJoint, or FixedJoint ArticulationBody for each link, and transform broadcasting builds an ArticulationBody-based TransformTree when it finds one in the hierarchy.
    Compass direction The project-wide setting that tells Simulation Pro which Unity world axis represents geographic north. NED and ENU coordinate space conversions depend on it, because neither Unity nor ROS defines a default compass heading. Configured through CompassDirection.UnityZAxisDirection and persisted as a ScriptableObject asset.
    Connector The runtime object that implements IConnector and provides the actual publish/subscribe transport. For example, RosEndpointConnector. ConnectorInjector locates the active connector in the scene so publishers and subscribers don't need to reference it directly.
    Coordinate space A named axis convention (RUF, FLU, FRD, NED, ENU, and their local variants) used to disambiguate position and rotation data. Refer to Coordinate types reference for the full list and Introduction to coordinate spaces for how the typed Vector3<C>/Quaternion<C> wrappers prevent coordinate frame mismatches.
    ENU / NED Global geographic coordinate spaces: East-North-Up and North-East-Down. Both require a configured compass direction to map onto Unity's axes; ENULocal and NEDLocal are body-fixed variants that don't.
    FLU / FRD ROS-standard coordinate spaces: Forward-Left-Up (ground vehicles, per REP-103) and Forward-Right-Down (aerial vehicles, the NED body frame).
    Headless simulation Running Unity on a machine with no display, so cameras and sensors render to an off-screen back-buffer instead of a window. Used to scale batch simulation and synthetic-data generation across cloud and CI machines. For more information, refer to Run simulations headlessly.
    IMessage The interface every message type implements. Requires WriteTo(IMessageSerializer) and a MessageTypeId, and is what lets a message be published, subscribed to, or serialized to the wire.
    Publisher An IPublisher registered on a topic via IConnector.RegisterPublisher<T>(). Call Publish(IMessage) to send a message to every subscriber on that topic. For more information, refer to Introduction to messaging.
    ROS Robot Operating System. The open-source robotics middleware and message/topic conventions Simulation Pro is compatible with, spanning both ROS 1 and ROS 2.
    RUF Unity's native coordinate space (Right-Up-Forward). All other coordinate spaces are defined as conversions to and from RUF via ICoordinateSpace.
    Service A ROS-style request/response call, as opposed to the fire-and-forget publish/subscribe model. Implement one with IConnector.ImplementService<TReq, TRes>(), or call one with an IServiceClient from RegisterServiceClient<TReq, TRes>().
    Subscriber A callback registered on a topic via IConnector.Subscribe<T>(topic, callback). The callback runs once for every message published on that topic.
    Topic A named channel that messages are published to and subscribed from, following ROS conventions (for example, /cmd_vel). A topic carries exactly one message type at a time.
    Transform tree The frame hierarchy built by TransformTree when transform broadcasting walks a robot's GameObject hierarchy. Converted to a TFMessageMsg and published on /tf every FixedUpdate by TfBroadcasterComponent.
    URDF Unified Robot Description Format. The XML format ROS uses to describe a robot's links, joints, visuals, collisions, and sensors. Simulation Pro's URDF importer turns a .urdf file into a Unity GameObject hierarchy automatically on import. Xacro macros are not supported; export to plain URDF first.
    V-HACD Volumetric-Hierarchical Approximate Convex Decomposition. The algorithm the URDF importer uses to break a collision mesh into a set of convex hulls, because Unity's physics engine requires convex colliders.
    In This Article
    Back to top
    Copyright © 2026 Unity Technologies — Trademarks and terms of use
    • Legal
    • Privacy Policy
    • Cookie Policy
    • Do Not Sell or Share My Personal Information
    • Your Privacy Choices (Cookie Settings)