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.0

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.0
File Size Uploaded Provenance Actions
tempo_sim-0.4.0.tar.gz 118.0 kB Without provenance Details for tempo_sim-0.4.0.tar.gz

Built distribution (wheel)

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

Total release size: 260.3 kB

Release files / tempo_sim-0.4.0.tar.gz

Download URL tempo_sim-0.4.0.tar.gz
Size 118.0 kB
Tags Source
SHA-256 checksum
How to use checksums
1c855c8daa06a5e9c75e6df8737bc2bfeacad38be2d83f8a3e017c3c0863457d
BLAKE2b-256 checksum
How to use checksums
3a46671f0820e56dfeb21ff324cd7630b371adfbe3d1a5d089c8d8edf4c57b25
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.0-py3-none-any.whl

Download URL tempo_sim-0.4.0-py3-none-any.whl
Size 142.3 kB
Tags Python 3
SHA-256 checksum
How to use checksums
080538f11df2e4c1132fb10a02fedb95823d4678bc45c47d168b6198ec2992bc
BLAKE2b-256 checksum
How to use checksums
e380b39f2c514daabf449aba031972794767130e1d457f638baddcff2918afff
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.0

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