How tmlmarj/carla_simulator_manager works
CARLA Simulator Manager is a Tkinter desktop client for managing a CARLA server. The user launches the GUI, connects to a local or remote server, and issues world, actor, sensor, simulation, movement, and scenario operations; CARLA work runs through the application’s dedicated worker. The graph includes the documented feature areas even where implementation excerpts were unavailable. Arrows are limited to README statements and source-index references; relationships within unsampled feature areas are not inferred.
Main entry points: controller.py CARLA worker · application.py Tkinter application · state_store.py Shared state · tabs Feature tabs
Components 26
Application entry
- Application entry
app.py
Desktop interface
- Tkinter application
gui/application.py - Main view
gui/main_view.py - Feature tabs
gui/tabs - Actor editor
gui/windows/actor_editor.py - Movement controls
gui/windows/movement_control.py - Sensor preview
gui/windows/sensor_preview.py
Worker and state
- CARLA worker
core/controller.py - Command dispatch
core/command_bus.py - Shared state
core/state_store.py - Actor registry
core/registries.py
Simulation and movement
- World services
services/world.py - Actor services
services/actors.py - Sensor services
services/sensors.py - Simulation control
simulation/manager.py - Simulation dashboard
simulation/dashboard.py - Movement runtime
movement/runtime.py - Movement session
movement/session.py - Destination planning
movement/destination.py - Map and previews
preview/map.py
Scenario lifecycle
- Scenario coordinator
scenarios/manager.py - Scenario runtime
scenarios/runtime.py - Scenario file lifecycle
scenarios - Scenario model
models/scenarios.py
Other components
- Operator
- CARLA server
Connections 31
- Operator → Application entry: launches
README.md - Application entry → Tkinter application: starts
app.py - Tkinter application → CARLA worker: creates
gui/application.py - Tkinter application → Main view: builds
gui/application.py - Main view → Feature tabs: assembles
gui/main_view.py - Feature tabs → Actor editor: opens
gui/tabs/vehicles.py - Feature tabs → Movement controls: opens
- Sensor preview → Shared state: reads buffers
gui/windows/sensor_preview.py - Tkinter application → Shared state: uses
gui/application.py - CARLA worker → Command dispatch: dispatches
core/controller.py - CARLA worker → Shared state: updates
core/controller.py - CARLA worker → Movement runtime: delegates to
core/controller.py - CARLA worker → Scenario runtime: delegates to
core/controller.py - CARLA worker → Simulation control: uses
core/controller.py - CARLA worker → Simulation dashboard: uses
core/controller.py - CARLA worker → Map and previews: queues generation
core/controller.py - CARLA worker → CARLA server: performs operations
README.md - CARLA worker → World services: delegates to
core/controller.py - CARLA worker → Actor services: delegates to
core/controller.py - CARLA worker → Sensor services: delegates to
core/controller.py - Actor services → Actor registry: uses
core/registries.py - Movement session → Movement runtime: uses
movement/session.py - Movement runtime → Destination planning: uses
movement/runtime.py - Destination planning → Map and previews: transforms map
movement/destination.py - Movement controls → Movement session: configures
- Scenario runtime → Scenario coordinator: executes operations
scenarios/runtime.py - Scenario coordinator → Scenario file lifecycle: coordinates
scenarios/manager.py - Scenario coordinator → Scenario model: validates data
scenarios/manager.py - Scenario runtime → Scenario model: uses
scenarios/runtime.py - Simulation control → CARLA server: controls ticks
- Simulation dashboard → Shared state: reads state
core/state_store.py