SEARCH · Search NASA
Results for “Ground Systems”
Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.
Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.
The Flight Dynamics Operations Concept and Ground System for the James Webb Space Telescope
Explore the source record for details and available documents.
Exploration Ground System Outreach Presentation: NASA Overview
Explore the source record for details and available documents.
Analysis and Validation of Multiphase CFD Predictions of SLS Ground System Loads Using Artemis I Launch Data
Explore the source record for details and available documents.
Analysis and Validation of Multiphase CFD Predictions of SLS Ground System Loads Using Artemis I Launch Data
Explore the source record for details and available documents.
The Earth Observing System (EOS) SAR ground data system
NASA, in association with ESA and NASDA, will launch the Space Station Freedom in 1993. As a complement to the Space Station, several unmanned Polar-Orbit Platforms (POPs) will be developed, built and launched with suites of instruments devoted to remote-sensing for earth surface and atmosphere observations or to planetary and deep-space studies. Attention is presently given to the POPs-associated Earth Observing System SAR Ground Data System, which encompasses a SAR processor, a postprocessing subsystem, a geophysical processor, and a data management and control subsystem.
System Testing of Ground Cooling System Components
This internship focused primarily upon software unit testing of Ground Cooling System (GCS) components, one of the three types of tests (unit, integrated, and COTS/regression) utilized in software verification. Unit tests are used to test the software of necessary components before it is implemented into the hardware. A unit test determines that the control data, usage procedures, and operating procedures of a particular component are tested to determine if the program is fit for use. Three different files are used to make and complete an efficient unit test. These files include the following: Model Test file (.mdl), Simulink SystemTest (.test), and autotest (.m). The Model Test file includes the component that is being tested with the appropriate Discrete Physical Interface (DPI) for testing. The Simulink SystemTest is a program used to test all of the requirements of the component. The autotest tests that the component passes Model Advisor and System Testing, and puts the results into proper files. Once unit testing is completed on the GCS components they can then be implemented into the GCS Schematic and the software of the GCS model as a whole can be tested using integrated testing. Unit testing is a critical part of software verification; it allows for the testing of more basic components before a model of higher fidelity is tested, making the process of testing flow in an orderly manner.
Exploration Medical System Technical Architecture Overview
The Exploration Medical Capability (ExMC) Element Systems Engineering (SE) goals include defining the technical system needed to support medical capabilities for a Mars exploration mission. A draft medical system architecture was developed based on stakeholder needs, system goals, and system behaviors, as captured in an ExMC concept of operations document and a system model. This talk will discuss a high-level view of the medical system, as part of a larger crew health and performance system, both of which will support crew during Deep Space Transport missions. Other mission components, such as the flight system, ground system, caregiver, and patient, will be discussed as aspects of the context because the medical system will have important interactions with each. Additionally, important interactions with other aspects of the crew health and performance system are anticipated, such as health & wellness, mission task performance support, and environmental protection. This talk will highlight areas in which we are working with other disciplines to understand these interactions.
Integration of a satellite ground support system based on analysis of the satellite ground support domain
This analysis defines a complete set of ground support functions based on those practiced in real space flight operations during the on-orbit phase of a mission. These functions are mapped against ground support functions currently in use by NASA and DOD. Software components to provide these functions can be hosted on RISC-based work stations and integrated to provide a modular, integrated ground support system. Such modular systems can be configured to provide as much ground support functionality as desired. This approach to ground systems has been widely proposed and prototyped both by government institutions and commercial vendors. The combined set of ground support functions we describe can be used as a standard to evaluate candidate ground systems. This approach has also been used to develop a prototype of a modular, loosely-integrated ground support system, which is discussed briefly. A crucial benefit to a potential user is that all the components are flight-qualified, thus giving high confidence in their accuracy and reliability.
Using Quality Attributes to Bridge Systems Engineering Gaps : A Juno Ground Data Systems Case Study
The Juno Mission to Jupiter is the second mission selected by the NASA New Frontiers Program. Juno launched August 2011 and will reach Jupiter July 2016. Juno's payload system is composed of nine instruments plus a gravity science experiment. One of the primary functions of the Juno Ground Data System (GDS) is the assembly and distribution of the CFDP (CCSDS File Delivery Protocol) product telemetry, also referred to as raw science data, for eight out of the nine instruments. The GDS accomplishes this with the Instrument Data Pipeline (IDP). During payload integration, the first attempt to exercise the IDP in a flight like manner revealed that although the functional requirements were well understood, the system was unable to meet latency requirements with the as-is heritage design. A systems engineering gap emerged between Juno instrument data delivery requirements and the assumptions behind the heritage flight-ground interactions. This paper describes the use of quality attributes to measure and overcome this gap by introducing a new systems engineering activity, and a new monitoring service architecture that successfully delivered the performance metrics needed to validate Juno IDP.
Science data visualization tools for the Tropospheric Emissions Spectrometer Ground Data System
The TES instrument seeks to analyze the chemical composition of the atmosphere based on the transmission of radiation.
Using Quality Attributes to Bridge Systems Engineering Gaps : a Juno Ground Data Systems Case Study
No abstract available