Skip to main content

tempo-sim

Python client API for the Tempo simulation server.

This package provides generated gRPC wrappers (built on protobuf and grpcio) for interacting with Tempo simulation servers, exposing both synchronous and asynchronous surfaces.

Installation

pip install tempo-sim

Visualization helpers and the example clients need extra dependencies:

pip install tempo-sim[examples]

Quick start

import tempo_sim
import tempo_sim.TempoSensors  # generated protobuf modules nest under the package

# Point the client at a running Tempo server.
tempo_sim.set_server("localhost", 10001)

# Or, for a server on this machine listening on a Unix domain socket (Linux/macOS):
tempo_sim.set_socket("sim-a.sock")

# Use the generated API modules, e.g. tempo_sensors, tempo_world.
from tempo_sim import tempo_sensors

The API is organized into per-service modules:

  • tempo_core / tempo_core_editor
  • tempo_agents / tempo_agents_editor
  • tempo_geographic
  • tempo_movement
  • tempo_sensors
  • tempo_world

Each wrapper takes its request's fields as keyword arguments, and works from synchronous and asynchronous code alike:

from tempo_sim import tempo_world

rig = tempo_world.spawn_actor(actor_type="BP_SensorRig")
tempo_world.destroy_actor(actor=rig.name)

Common helpers (set_server, set_socket, run_async) are re-exported at the package root. Prefer brevity? import tempo_sim as tempo.

The reflected API

The package also carries the runtime of Tempo's reflected API, which reaches a build's properties and functions through generated, type-checked classes:

  • tempo_sim.unreal: Unreal's value types (FVector, FRotator, FTransform, ...), in centimeters, degrees and left-handed, and the handle every generated class is built on.
  • tempo_sim.world: finding, spawning and moving actors through those handles.
  • tempo_sim.conversion: ue_to_si and si_to_ue, between Unreal's values and the API's meters, radians and right-handed frame.

The classes themselves are generated per project, from its packaged build, and ship in that project's own package (Packaged/API/Python/<project>/), which depends on this one.

License

Licensed under the Apache License, Version 2.0.

Metadata

Release files for tempo-sim 0.4.3

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for tempo-sim 0.4.3
File Size Uploaded Provenance Actions
tempo_sim-0.4.3.tar.gz 123.1 kB Without provenance Details for tempo_sim-0.4.3.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for tempo-sim 0.4.3
File Interpreter ABI Platform Actions
tempo_sim-0.4.3-py3-none-any.whl Python 3 none any Details for tempo_sim-0.4.3-py3-none-any.whl

Total release size: 273.0 kB

Release files / tempo_sim-0.4.3.tar.gz

Download URL tempo_sim-0.4.3.tar.gz
Size 123.1 kB
Tags Source
SHA-256 checksum
How to use checksums
f31e03bb41dbd02cac37e2cd401a3e8898297db157b73fde3937fb44423046fa
BLAKE2b-256 checksum
How to use checksums
1d1b1d536d4f0434c4a1a8f26bd484ad439bb8995ba9f4460c5366ba5fcc1d8c
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.9.6

Release files / tempo_sim-0.4.3-py3-none-any.whl

Download URL tempo_sim-0.4.3-py3-none-any.whl
Size 149.9 kB
Tags Python 3
SHA-256 checksum
How to use checksums
4fb4043e1cc2798e68756f512d857c78c3f5d33014235246e877a463396917d7
BLAKE2b-256 checksum
How to use checksums
6d2d9ed2d5b6e7d2189c0215f60682861a2af8385497bc69d2197e7e546a156d
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.9.6

Security for tempo-sim 0.4.3

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page