Repository navigation
Home
This purpose of this wiki is to provide an overview of the EO-Sim project and documentation. It also keeps track of the high-level project goals, and tasks.
The purpose of EO-Sim is to provide satellite mission data useful in mission design and operations. The current status and planned revisions are described below.
Presently there are 3 packages (and corresponding repos):
InstruPy Produces functionality to model instruments, and produce expected data metrics given the target geometry and the instrument specifications.
OrbitPy Provides orbit-propagation, coverage (different types), line-of-sight ground-station contact, eclipse, pixel-projection (under-dev) calculations. The orbit propagation and coverage core functionality is provided by the C++ package propcov.
EOSim GUI Provides a graphical user interface to set basic mission parameters, simulate and visualize 2d plots and animation with CesiumJS. This is based on Tkinter.
InstruPy Continue as is.
OrbitPy
- Disband the
propcovpackage. - Switch to third-party orbit-propagation libraries (e.g., skyfield, GMAT) for high fidelity orbit propagation calculations. OrbitPy shall only provide a wrapper, which can produce propagation data at a standard format, for limited set of coordinate frames.
- Core coverage library would be provided through the
CoverageKinematicslibrary (under dev). OrbitPy shall provide an wrapper (which shall also function as the Earth coverage applications layer).
EOSim GUI
- Archive the EOSim GUI package.
- Start a new package called as MissionEvaluator, whose function is to provide evaluation of mission data (coverage metrics, revisit time, new proposed metrics, etc.)
- Utilize the visualization scripts in the EOSim GUI (2d and animations based) to provide visualization of the mission data.
Compatibility with TAT-C
- Start a new
SystemModelPylibrary, which would contain the schemas for initialization of the various objects used in EO-Sim, such as Satellite, Orbit, etc. - Start using
pydantic,typing,uuid,enumandgeojson_pydanticpackages in a similar way to how it has been used in TAT-C (see theschemas.pyfiles). docs link