How pegasussimulator/pegasussimulator works
Project type and purpose
• Pegasus Simulator is a simulation framework (an open-source tool) built as an NVIDIA Omniverse/IsaacSim extension.
• It provides a Python API for multi-rotor vehicle dynamics, autopilot integration (PX4, ArduPilot), and custom control interfaces.
File structure
• Top level:
• .github, .gitignore, workflows → CI/CD for tests and docs
• docs/ → Sphinx documentation and tutorials
• examples/ → Python scripts and notebooks demonstrating usage
• extensions/pegasus.simulator/pegasus/simulator/… → core code of Omniverse extension
• tools/packman, tools/scripts → packaging and linking scripts
• Core extension layout (extensions/pegasus.simulator/pegasus/simulator):
• assets/Backends, Robots, Worlds → USD assets for simulation
• logic/ → simulation logic: backends, dynamics, sensors, vehicles, people, graphs
• parser/ → YAML/TOML to internal representation parsers
• ui/ → user interface layer (UI delegate & window)
• params.py → configuration management
• extension.py → entry point for Omniverse plugin registration
• tests/ → unit tests
• Examples instantiate the API, build graphs, spawn vehicles, attach sensors, and run autopilot loops.
README for additional insights
• Key external dependencies: NVIDIA Omniverse/IsaacSim, PX4-Autopilot, ArduPilot, ROS2 (optional)
• The README emphasizes multi-rotor dynamics, plugin interfaces, Python control, and autopilot integration.
• Clear labels for: Omniverse Engine, Pegasus Plugin submodules, Control Interfaces, External Systems, Examples/Tools
– Configuration files → Parsers → Simulation logic
– Simulation logic → Sensor data → Backends → Autopilots/Python
– Control commands ← Backends ← User Scripts/Autopilots