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_editortempo_agents/tempo_agents_editortempo_geographictempo_movementtempo_sensorstempo_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_siandsi_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.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| tempo_sim-0.4.2.tar.gz | 121.5 kB | Without provenance | Details for tempo_sim-0.4.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| tempo_sim-0.4.2-py3-none-any.whl | Python 3 | none | any | Details for tempo_sim-0.4.2-py3-none-any.whl |
Total release size: 269.4 kB
Release files / tempo_sim-0.4.2.tar.gz
| Download URL | tempo_sim-0.4.2.tar.gz |
|---|---|
| Size | 121.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
77c6f71bfe78c4741803daaa8d00c55f6c19b47532a933b855aac89a9a99166c
|
|
BLAKE2b-256 checksum How to use checksums |
8c06c3cb46d616c58041d10a9ba9ffe20c12f1683b2490ba58db0ced9c71c891
|
| 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.2-py3-none-any.whl
| Download URL | tempo_sim-0.4.2-py3-none-any.whl |
|---|---|
| Size | 147.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4230a540f48c1ca7d38d57305f5c30eb64d226c7700f35fec387070523cef2d9
|
|
BLAKE2b-256 checksum How to use checksums |
b91a63dc19a3070ce1d258ba59bd3e083b4c1639b04457ebfd39ace01f4f27a9
|
| 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.2
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.