Skip to main content
Version: 4.9

Models

This page include an up-to-date, high-level description of some of the various models used in Sedaro. Looking for information about a model not listed here? Or need higher fidelity in a certain area? Please contact us and we'll be happy to help.

Orbit​

The orbital force model considers the following contributions:

  • Earth Gravity Model 2008 (EGM-2008) with variable degree and order. The 40/40 gravity model in Low-Earth Orbit decreases linearly to 4/4 at Geosynchronous Orbit.
  • Lunar and Solar gravity perturbations.
  • Panelized drag forces based on the spacecraft attitude, surface articulation, and surface properties defined by the user and the COESA-76 atmosphere.
  • Panelized solar radiation pressure forces based on the spacecraft spacecraft attitude, surface articulation, and surface properties defined by the user.
  • Thrust forces based on the user defined thrust profile.

Attitude​

The attitude force model considers the following contributions:

  • Gravity gradient torques based on the user-defined intertia tensor.
  • Panelized drag torques based on the spacecraft attitude, surface articulation, and surface properties defined by the user and the COESA-76 atmosphere.
  • Panelized solar radiation pressure torques based on the spacecraft attitude, surface articulation, and surface properties defined by the user.
  • Reaction wheel torques as driven by the attitude controller.
  • Magnetic torques based on the attitude controller commands, spacecraft attitude, and component properties defined by the user. The magnetic field is derived from the International Geomagnetic Reference Field (IGRF) Release 13 model with order 6.
  • Thrust torques based on the user defined thrust profile and thruster configuration.

Data Handling​

The Sedaro data simulation allows the user to model data handling within individual components, internal transfers onboard the vehicle, and transfers between agents in the broader simulation scenario. Users define any number of data types to categorize information flowing through the system and aid in onboard decision-making. Each component can store these data types, subject to capacity constraints, and also serve as a data producer, consumer, or transformer. Interfaces between components transfer specific data types between them according the the current operational mode of the vehicle at assigned data rates. Additionally, external interfaces can be assigned to use a a communications device to transfer data to or from other agents in the simulation, subject to field of view constraints and communication state of the partner agent