How mmsk-sbrain/aeb_demo works
Project Type and Purpose
• This is a standalone desktop educational simulation platform (not a web app) for teaching Autonomous Emergency Braking (AEB) systems.
• It combines a GUI (PyQt5-based), a simulation “core” (physics engine + scenario loader + plugin manager), and plugin points where students drop in their AEB logic and brake controller code.
• The purpose is to let students load scenario JSON files and their own AEB/brake modules, run a real-time simulation, see gauges/logs, and export data.
File Structure
• Top-level:
• src/main.py – entry point, application bootstrap
• src/core/ – core simulation components
• src/ui/ – GUI windows/widgets
• scenarios/ – JSON scenario definitions
• templates/ – starter code for student modules
• requirements.txt – external deps (PyQt5, numpy, etc.)
• In src/core:
• scenario_loader.py – loads/interpolates scenario JSON
• student_code_manager.py – dynamic import of student modules
• physics_engine.py – simulation loop, vehicle dynamics, invoking AEB logic & brake controller
• data_logger.py – logs time-series and exports CSV
• In src/ui:
• main_window.py – design of main window, menus, controls
• widgets.py – custom gauges, debug console, log panel
README Insights
• The README describes a “GUI → Load student code & scenario → START → run simulation → CSV export” flow.
• It references features like real-time displays, CSV export, debug console, crash indicator.
• It hints at an MVC-style separation: UI triggers actions on core components; core returns data back to UI for display.
Elements
– Blue for UI components
– Green for core services
– Yellow for plugin interfaces
– Gray for data stores (JSON/CSV)