ALBERT

Description: The National Aeronautics and Space Administration (NASA) Goddard Space Flight Center (GSFC) has proposed a set of spacecraft flying in close formation around the Earth in order to measure the behavior of the auroras. The mission, named Auroral Lites, consists of four spacecraft configured to start at the vertices of a tetrahedron, flying over three mission phases. During the first phase, the distance between any two spacecraft in the formation is targeted at 10 kilometers (km). The second mission phase is much tighter, requiring satellite interrange spacing targeted at 500 meters. During the final phase of the mission, the formation opens to a nominal 100-km interrange spacing. In this paper, we present the strategy employed to initialize and model such a close formation during each of these phases. The analysis performed to date provides the design and characteristics of the reference orbit, the evolution of the formation during Phases I and II, and an estimate of the total mission delta-V budget. AI Solutions' mission design tool, FreeFlyer(R), was used to generate each of these analysis elements. The tool contains full force models, including both impulsive and finite duration maneuvers. Orbital maintenance can be fully modeled in the system using a flexible, natural scripting language built into the system. In addition, AI Solutions is in the process of adding formation extensions to the system facilitating mission analysis for formations like Auroral Lites. We will discuss how FreeFlyer(R) is used for these analyses.

Description: Early in 2002, Goddard Space Flight Center (GSFC) began to identify requirements for the flight dynamics software needed to fly upcoming missions that use formations of spacecraft to collect data. These requirements ranged from low level modeling features to large scale interoperability requirements. In 2003 we began work on a system designed to meet these requirement; this system is GMAT. The General Mission Analysis Tool (GMAT) is a general purpose flight dynamics modeling tool built on open source principles. The GMAT code is written in C++, and uses modern C++ constructs extensively. GMAT can be run through either a fully functional Graphical User Interface (GUI) or as a command line program with minimal user feedback. The system is built and runs on Microsoft Windows, Linux, and Macintosh OS X platforms. The GMAT GUI is written using wxWidgets, a cross platform library of components that streamlines the development and extension of the user interface Flight dynamics modeling is performed in GMAT by building components that represent the players in the analysis problem that is being modeled. These components interact through the sequential execution of instructions, embodied in the GMAT Mission Sequence. A typical Mission Sequence will model the trajectories of a set of spacecraft evolving over time, calculating relevant parameters during this propagation, and maneuvering individual spacecraft to maintain a set of mission constraints as established by the mission analyst. All of the elements used in GMAT for mission analysis can be viewed in the GMAT GUI or through a custom scripting language. Analysis problems modeled in GMAT are saved as script files, and these files can be read into GMAT. When a script is read into the GMAT GUI, the corresponding user interface elements are constructed in the GMAT GUI. The GMAT system was developed from the ground up to run in a platform agnostic environment. The source code compiles on numerous different platforms, and is regularly exercised running on Windows, Linux and Macintosh computers by the development and analysis teams working on the project. The system can be run using either a graphical user interface, written using the open source wxWidgets framework, or from a text console. The GMAT source code was written using open source tools. GSFC has released the code using the NASA open source license.

Description: This document serves as the System Test Approach for the GMAT Project. Preparation for system testing consists of three major stages: 1) The Test Approach sets the scope of system testing, the overall strategy to be adopted, the activities to be completed, the general resources required and the methods and processes to be used to test the release. It also details the activities, dependencies and effort required to conduct the System Test. 2) Test Planning details the activities, dependencies and effort required to conduct the System Test. 3) Test Cases documents the tests to be applied, the data to be processed, the automated testing coverage and the expected results. This document covers the first two of these items, and established the framework used for the GMAT test case development. The test cases themselves exist as separate components, and are managed outside of and concurrently with this System Test Plan.

Description: This document provides instructions about how to configure the Eclipse IDE to build GMAT on Windows based PCs. The current instructions are preliminary; the Windows builds using Eclipse are currently a bit crude. These instructions are intended to give you enough information to get Eclipse setup to build wxWidgets based executables in general, and GMAT in particular.

Description: From a flight dynamics perspective, the EOS AM-1 mission design and maneuver operations present a number of interesting challenges. The mission design itself is relatively complex for a low Earth mission, requiring a frozen, Sun-synchronous, polar orbit with a repeating ground track. Beyond the need to design an orbit that meets these requirements, the recent focus on low-cost, "lights out" operations has encouraged a shift to more automated ground support. Flight dynamics activities previously performed in special facilities created solely for that purpose and staffed by personnel with years of design experience are now being shifted to the mission operations centers (MOCs) staffed by flight operations team (FOT) operators. These operators' responsibilities include flight dynamics as a small subset of their work; therefore, FOT personnel often do not have the experience to make critical maneuver design decisions. Thus, streamlining the analysis and planning work required for such a complicated orbit design and preparing FOT personnel to take on the routine operation of such a spacecraft both necessitated increasing the automation level of the flight dynamics functionality. The FreeFlyer(trademark) software developed by AI Solutions provides a means to achieve both of these goals. The graphic interface enables users to interactively perform analyses that previously required many parametric studies and much data reduction to achieve the same result. In addition, the fuzzy logic engine .enables the simultaneous evaluation of multiple conflicting constraints, removing the analyst from the loop and allowing the FOT to perform more of the operations without much background in orbit design. Modernized techniques were implemented for EOS AM-1 flight dynamics support in several areas, including launch window determination, orbit maintenance maneuver control strategies, and maneuver design and calibration automation. The benefits of implementing these techniques include increased fuel available for on-orbit maneuvering, a simplified orbit maintenance process to minimize science data downtime, and an automated routine maneuver planning process. This paper provides an examination of the modernized techniques implemented for EOS AM-1 to achieve these benefits.

Description: A software library has been developed to enable high-fidelity computational simulation of the dynamics of multiple spacecraft distributed over a region of outer space and acting with a common purpose. All of the modeling capabilities afforded by this software are available independently in other, separate software systems, but have not previously been brought together in a single system. A user can choose among several dynamical models, many high-fidelity environment models, and several numerical-integration schemes. The user can select whether to use models that assume weak coupling between spacecraft, or strong coupling in the case of feedback control or tethering of spacecraft to each other. For weak coupling, spacecraft orbits are propagated independently, and are synchronized in time by controlling the step size of the integration. For strong coupling, the orbits are integrated simultaneously. Among the integration schemes that the user can choose are Runge-Kutta Verner, Prince-Dormand, Adams-Bashforth-Moulton, and Bulirsh- Stoer. Comparisons of performance are included for both the weak- and strongcoupling dynamical models for all of the numerical integrators.

Description: The General Mission Analysis Tool (GMAT) is a software system for trajectory optimization, mission analysis, trajectory estimation, and prediction developed by NASA, the Air Force Research Lab, and private industry. GMAT's design and implementation are based on four basic principles: open source visibility for both the source code and design documentation; platform independence; modular design; and user extensibility. The system, released under the NASA Open Source Agreement, runs on Windows, Mac and Linux. User extensions, loaded at run time, have been built for optimization, trajectory visualization, force model extension, and estimation, by parties outside of GMAT's development group. The system has been used to optimize maneuvers for the Lunar Crater Observation and Sensing Satellite (LCROSS) and ARTEMIS missions and is being used for formation design and analysis for the Magnetospheric Multiscale Mission (MMS).

Description: From a flight dynamics perspective, the EOS AM-1 mission design and maneuver operations present a number of interesting challenges. The mission design itself is relatively complex for a low Earth mission, requiring a frozen, Sun-synchronous, polar orbit with a repeating ground track. Beyond the need to design an orbit that meets these requirements, the recent focus on low-cost, 'lights out' operations has encouraged a shift to more automated ground support. Flight dynamics activities previously performed in special facilities created solely for that purpose and staffed by personnel with years of design experience are now being shifted to the mission operations centers (MOCs) staffed by flight operations team (FOT) operators. These operators' responsibilities include flight dynamics as a small subset of their work; therefore, FOT personnel often do not have the experience to make critical maneuver design decisions. Thus, streamlining the analysis and planning work required for such a complicated orbit design and preparing FOT personnel to take on the routine operation of such a spacecraft both necessitated increasing the automation level of the flight dynamics functionality. The FreeFlyer(TM) software developed by AI Solutions provides a means to achieve both of these goals. The graphic interface enables users to interactively perform analyses that previously required many parametric studies and much data reduction to achieve the same result In addition, the fuzzy logic engine enables the simultaneous evaluation of multiple conflicting constraints, removing the analyst from the loop and allowing the FOT to perform more of the operations without much background in orbit design. Modernized techniques were implemented for EOS AM-1 flight dynamics support in several areas, including launch window determination, orbit maintenance maneuver control strategies, and maneuver design and calibration automation. The benefits of implementing these techniques include increased fuel available for on-orbit maneuvering, a simplified orbit maintenance process to minimize science data downtime, and an automated routine maneuver planning process. This paper provides an examination of the modernized techniques implemented for EOS AM-1 to achieve these benefits.

Description: The National Aeronautics and Space Administration (NASA) Goddard Space Flight Center (GSFC) has proposed a set of spacecraft flying in close formation around the Earth in order to measure the behavior of the auroras. The mission, named Auroral Lites, consists of four spacecraft configured to start at the vertices of a tetrahedron, flying over three mission phases. During the first phase, the distance between any two spacecraft in the formation is targeted at 10 kilometers (km). The second mission phase is much tighter, requiring satellite interrange spacing targeted at 500 meters. During the final phase of the mission, the formation opens to a nominal 100-km interrange spacing. In this paper, we present the strategy employed to initialize and model such a close formation during each of these phases. The analysis performed to date provides the design and characteristics of the reference orbit, the evolution of the formation during Phases I and II, and an estimate of the total mission delta-V budget. AI Solutions' mission design tool, FreeFlyer, was used to generate each of these analysis elements. The tool contains full force models, including both impulsive and finite duration maneuvers. Orbital maintenance can be fully modeled in the system using a flexible, natural scripting language built into the system. In addition, AI Solutions is in the process of adding formation extensions to the system facilitating mission analysis for formations like Auroral Lites. We will discuss how FreeFlyer is used for these analyses.

Description: This is a software tutorial and presentation demonstrating the application of the General Mission Analysis Tool (GMAT). These slides will be used to accompany the demonstration. The demonstration discusses GMAT basics, then presents a detailed example of GMAT application to the Transiting Exoplanet Survey Satellite (TESS) mission. This talk is a combination of existing presentations and material; system user guide and technical documentation; a GMAT basics and overview, and technical presentations from the TESS projects on their application of GMAT to critical mission design. The GMAT basics slides are taken from the open source training material. The TESS slides are a streamlined version of the CDR package provided by the project with SBU and ITAR data removed by the TESS project. Slides for navigation and optimal control are borrowed from system documentation and training material.