How connor-a-casey/fso-simulation works
Main Components
• • Satellite Passes Module: Handles satellite orbit simulation using TLE data (src/satellite_passes). It reads the TLE file (e.g., terra.tle) together with key parameters from the data/input folder.
• • Turbulence Module: Analyzes turbulence effects using FITS files (src/turbulence). Contains unique scripts to calculate turbulence strength.
• • Cloud Cover Module: Computes cloud cover, interacting with the EUMETSAT API to get cloud data (src/cloud_cover).
• • Data Integrator: Merges outputs from the preceding modules, linking simulation results (src/data_integrator).
• • Dynamic Analysis Module: Performs further calculations using the integrated data and original satellite parameters (src/dynamic_analysis).
Data Sources and Supporting Items
• "data" folder containing both input parameters and output directories.
• Configuration files, such as the satelliteParameters.txt (data/input) and the TLE file in the satellite_passes folder.
• That there is a Dockerfile along with a run_simulation.zsh script (under scripts) to enable both container-based and traditional setups.
1. Data flows from "satelliteParameters.txt" and TLE into the Satellite Passes Module.
2. Output then flows into the Turbulence and Cloud Cover Modules.
3. Their respective outputs then converge in the Data Integrator.
4. Finally, the integrated data (along with the original parameters) feeds into the Dynamic Analysis module.
• Optionally, include an external interaction block showing the API call to the EUMETSAT gateway from the Cloud Cover module.
Architectural Patterns and Design Principles
• This design follows a modular pipeline approach where each step’s output becomes the next step’s input.
• Sequential model execution order, which helps in clearly separating simulation components.
• That this is a specialized simulation system rather than a general full-stack application. It leverages focused submodules that are interconnected through well-defined data dependencies.