How kit-mrt/arbitration_graphs works
Core Library Components
• Arbitrators (Priority, Random, Cost-based)
• Behavior Components
• Coordinators (Conjunctive, Joint)
• Verification System
• Types and Exceptions
GUI Components
• Web Server (Crow-based)
• WebSocket Server
• Static WebApp Files
• SVG Renderer
Demo Application
• A "PacMan Demo" container showing:
• Environment Model
• Agent Behaviors
• Cost Estimator
• Verifier
• Game Engine Integration
Design Guidelines:
Use a Layered Architecture
• Demo |
• GUI |
• Core Library |
Specific Elements
a. Core Layer:
• Core Library |
• Arbitrators | |
• Behaviors | |
• Verification | |
b. GUI Layer:
• GUI |
• Web Server | |
• WebApp UI | |
Important Details to Highlight
• Header-only nature of the core library
• Websocket communication between GUI and core
• Verification flow for behavior safety
• Hierarchical structure of arbitrators
• External dependency connections (glog, yaml-cpp, etc.)
• ▢ Core Component
• ◇ Optional Component
• → Direct Dependency
• ⟶ Data Flow
• ⟵⟶ Bidirectional Communication