How tudelft-cns-atm/bluesky works
BlueSky is an open air-traffic-management simulator for research, visualization, and traffic-flow analysis. Users enter commands in a console or run timestamped scenario files; the command stack delivers simulation actions, and the simulation advances aircraft traffic using performance, navigation, and separation logic. Results can be viewed through a GUI or console, while client/server networking supports distributed operation. Plugins extend simulation and command behavior. The README documents these capabilities; sampled source and the source index support startup, command, plugin, and networking links, but many domain internals were not excerpted, so some documented links are cited to the README.
Main entry points: traffic.py Aircraft Traffic · simulation.py Simulation Engine · cmdparser.py Command Stack · plugin.py Plugin System
Components 24
User Interaction
- Command Stack
bluesky/stack/cmdparser.py - Command Arguments
bluesky/stack/argparser.py - Client Commands
bluesky/stack/clientstack.py - Visualization
bluesky/ui/qtgl - Pygame Display
bluesky/ui/pygame/screen.py - Console UI
bluesky/ui/console/consoleui.py
Simulation Domain
- Simulation Engine
bluesky/simulation/simulation.py - Aircraft Traffic
bluesky/traffic/traffic.py - Flight Routes
bluesky/traffic/route.py - Aircraft Performance
bluesky/traffic/performance - Conflict Detection
bluesky/traffic/asas - Conflict Resolution
bluesky/traffic/asas/resolution.py
Extensions and Data
- Navigation Database
bluesky/navdatabase/navdatabase.py - Aero Calculations
bluesky/tools/aero.py - Plugin System
bluesky/core/plugin.py
Runtime Infrastructure
- Configuration
bluesky/settings.py - Signals
bluesky/core/signal.py - Callback Wrapper
bluesky/core/funcobject.py
Distributed Operation
- State Publisher
bluesky/network/publisher.py - State Subscriber
bluesky/network/subscriber.py - Network Node
bluesky/network/node.py - Simulation Server
bluesky/network/server.py
Other components
- Operator
- Scenario Files
Connections 26
- Operator → Command Stack: enters commands
- Scenario Files → Command Stack: provides commands
- Command Stack → Command Arguments: parses arguments
bluesky/stack/cmdparser.py - Client Commands → Command Stack: dispatches commands
bluesky/stack/clientstack.py - Simulation Engine → Command Stack: uses sim stack
bluesky/simulation/simulation.py - Simulation Engine → Aircraft Traffic: advances traffic
- Aircraft Traffic → Flight Routes: uses routes
bluesky/traffic/route.py - Aircraft Traffic → Aircraft Performance: models performance
- Aircraft Traffic → Conflict Detection: checks conflicts
- Conflict Detection → Conflict Resolution: resolves conflicts
- Aircraft Traffic → Navigation Database: uses navigation data
- Aircraft Traffic → Aero Calculations: uses aero functions
- Operator → Visualization: views traffic
- Operator → Pygame Display: views traffic
- Operator → Console UI: enters commands
- Plugin System → Command Stack: adds commands
bluesky/core/plugin.py - Plugin System → Configuration: reads configuration
bluesky/core/plugin.py - Plugin System → Simulation Engine: extends simulation
bluesky/simulation/simulation.py - Simulation Engine → State Publisher: publishes state
bluesky/simulation/simulation.py - State Subscriber → State Publisher: subscribes to state
bluesky/network/subscriber.py - Network Node → Client Commands: processes commands
bluesky/network/client.py - Simulation Server → Network Node: manages nodes
bluesky/network/server.py - Simulation Server → Simulation Engine: starts simulation nodes
bluesky/network/server.py - Signals → Callback Wrapper: wraps callbacks
bluesky/core/signal.py - Simulation Engine → Signals: uses signals
bluesky/simulation/simulation.py - Visualization → State Subscriber: receives state