How sparcians/map works
• Sparta – a C++ modeling framework for building, binding, and executing full simulation designs.
• Helios – a Python-based visualization and data analysis toolset (also called Argos in some parts) that is used to view and deep dive into the results generated by Sparta.
Main Components
a. Sparta Framework:
– Represent this as a core simulation engine. It consists of a large set of C++ classes (organized under directories such as “sparta”, “sparta/src”, “sparta/test”, etc.) that handle simulation models, event scheduling, report generation (output to text, databases, HDF5) and resource management.
b. Helios/Argos Viewer:
– Represent this as the visualization/analysis layer. Helios (found under directories “helios” and “helios/pipeViewer”) processes simulation outputs from Sparta for graphical display and analysis.
c. Build & Integration Infrastructure:
– Include CI/CD pipelines (with configurations in .circleci, .github, .azure-pipelines, etc.) showing how automated test and build scripts are integrated.
d. Packaging and Environment Management:
– Show the Conda recipes (“conda.recipe” and associated scripts) and other build scripts located in “.scripts” and “scripts” which help in setting up the environment for both Sparta and Helios.
e. Support Libraries and External Dependencies:
Establish Relationships and Interactions
a. Data Flow:
– Include directional flows where the Helios component “consumes” simulation results.
b. Build Dependency & Integration:
– Show integration points with CI/CD components, which are configured to build and test both parts.
– Include connections with external systems such as conda environments, indicating that developers can trigger builds and tests.
c. External Dependencies:
– Illustrate how the build system uses CMake and underlying OS package managers to incorporate the needed libraries for Sparta.
Architectural Patterns and Design Principles
a. Separation of Concerns:
– Emphasize that the simulation (Sparta) and visualization (Helios) parts are decoupled. Sparta is a lower-level C++ engine that produces plain data, while Helios is a higher-level Python tool that processes and visualizes this data.
b. Modularity:
– Indicate the modularity of the system through distinct directories and submodules. For example, within Sparta there are dedicated areas for event triggers, simulation configuration, and reporting.
c. Build & Test Driven Development:
– Reflect the CI configuration files and testing directories to demonstrate the modern software engineering practice of continuous integration and thorough testing.
Relevant Technologies, Frameworks, and Libraries
a. Under Sparta: C++17, CMake, Boost, YAML-CPP, RapidJSON, SQLite, HDF5, and Clang.
b. Under Helios: Python (with related build and installation details) along with its integration via CMake.
c. CI/CD Scripts and Integration: Usage of CircleCI, Azure Pipelines, GitHub actions, and conda environment management.
d. Packaging Tools: Conda recipes and additional helper scripts that help in managing dependencies.