Results for “Mission Data System” — Page 26

NASA NTRS1992

TDS and BMT for CASES ADF (ADF RAMS), acceptance test

The Controls, Astrophysics, and Structures Experiment (CASES) is a proposed experiment to collect x ray images of the galactic center and solar disk with unprecedented resolution. This requires precision pointing and suppression of vibrations in the long, flexible structure that comprises the 32-m x ray telescope optical bench. Two separate electro-optical sensors systems are provided for the ground test facility (GTF). The Boom Motion Tracker (BMT) measures eigenvector data for post-mission use in system identification. The Tip Displacement Sensor (TDS) measures boom tip position and is used as feedback for the closed-loop control system that stabilizes the boom. The deployment and testing of the BMT and TDS systems is summarized.

Davis, Hugh W.↗

NASA NTRS1993

Structural control sensors for the CASES GTF

CASES (Controls, Astrophysics and Structures Experiment in Space) is a proposed space experiment to collect x-ray images of the galactic center and solar disk with unprecedented resolution. This requires precision pointing and suppression of vibrations in the long flexible structure that comprises the 32-m x-ray telescope optical bench. Two separate electro-optical sensor systems are provided for the ground test facility (GTF). The Boom Motion Tracker (BMT) measures eigenvector data for post-mission use in system identification. The Tip Displacement Sensor (TDS) measures boom tip position and is used as feedback for the closed-loop control system that stabilizes the boom. Both the BMT and the TDS have met acceptance specifications and were delivered to MSFC in February 1992. This paper describes the sensor concept, the sensor configuration as implemented in the GTF, and the results of characterization and performance testing.

Davis, Hugh W.↗

NASA NTRS1992

Planetary data analysis and display system: A version of PC-McIDAS

We propose to develop a system for access and analysis of planetary data from past and future space missions based on an existing system, the PC-McIDAS workstation. This system is now in use in the atmospheric science community for access to meteorological satellite and conventional weather data. The proposed system would be usable by not only planetary atmospheric researchers but also by the planetary geologic community. By providing the critical tools of an efficient system architecture, newer applications and customized user interfaces can be added by the end user within such a system.

Limaye, Sanjay S.↗

NASA NTRS1993

Planetary data analysis and display system: A version of PC-McIDAS

We propose to develop a system for access and analysis of planetary data from past and future space missions based on an existing system, the PC-McIDAS workstation. This system is now in use in the atmospheric science community for access to meteorological satellite and conventional weather data. The proposed system would be usable not only by planetary atmospheric researchers but also by the planetary geologic community. By providing the critical tools of an efficient system architecture, newer applications and customized user interfaces can be added by the end user within such a system.

Limaye, Sanjay S.↗

NASA NTRS1996

Trans-Global Mission Architectures

Mission operations include the utilization of both space and ground resources to achieve mission objectives. Future architectures will make the spacecraft a node on a distributed system, thus expanding the scope of missions beyond the global scale. The history and evolution of planetary mission operations are outlined, together with the current global involvement in planetary missions. The modular nature and reuse of the supporting ground data systems, and the inclusion of automation and dedicated software in space missions, are discussed. A trans-global mission architecture is presented, and consists of an extension of a layered reusable mission operations architecture to create an open ground/space operations system. Concurrent mission engineering with such trans-global structures is discussed.

Anderson, Barbara V.↗

NASA NTRS1997

CCSDS - SFCG Efficient Modulation Methods Study at NASA/JPL, Phase 3

This report contains results from Phase 3 of the CCSDS - SFCG Efficient Modulation Methods Study conducted at the Jet Propulsion Laboratory (JPL). Simulations were used to measure the end-to-end performance of a telemetry data transmission and capture system for Category A missions.

modulation methods spectrum improvement data rate↗

NASA NTRS2021

Automated Data Accountability for Missions in Mars Rover Data

As the Mars Curiosity Rover transmits data to the JPL Ground Data System (GDS), it frequently observes data loss and corruption, requiring re-transmits from the rover and Ground Data System Analysts (GDSA) to monitor the downlink process. As new missions are launched, the GDSA team redistributes analysts to these new missions, causing shortages in previous missions. The GDSA team can significantly benefit from the automation and optimization of the downlink process of telemetry data. In fact, there is a need for a better understanding of why the data is corrupted, so that the GDSA team can best determine the root cause of the issues in the GDS. This paper presents machine learning and deep learning based approaches to automate and optimize the detection of data loss. We first created a pipeline to automatically accumulate data from the telemetry databases (MAROS, Telemetry Data Storage, and GDS Elastic Search Database) in the downlink process. With our newly created datasets, we perform feature selection to supplement the GDSA understanding of the downlink process and provide supplemental analysis on the importance of different features. We implement various machine learning and deep learning based models, including support vector machines, ensemble methods, and deep neural networks and evaluate their accuracies in identifying whether a downlink process is complete or incomplete. We utilize fast hyperparameter optimization methods that allow our models to quickly be re-trained, allowing them to quickly be tuned and optimized on daily incoming data in real time. This hyperparameter optimization also allows our methods to be quickly integrated into other JPL missions. Our results show that our best-performing machine learning and deep learning based models outperform the existing GDSA detection software by 6 accuracy points and can aid analysts by providing insights into the data accountability problem. Since these various machine learning and deep learning approaches vary significantly in interpretability, we provide a discussion on the tradeoffs between their performance and trustworthiness in helping detect issues in data transmission.

Divsalar, Dariush↗

NASA NTRS1994

Simplifying operations with an uplink/downlink integration toolkit

The Operations Engineering Lab (OEL) at JPL has developed a simple, generic toolkit to integrate the uplink/downlink processes, (often called closing the loop), in JPL's Multimission Ground Data System. This toolkit provides capabilities for integrating telemetry verification points with predicted spacecraft commands and ground events in the Mission Sequence Of Events (SOE) document. In the JPL ground data system, the uplink processing functions and the downlink processing functions are separate subsystems that are not well integrated because of the nature of planetary missions with large one-way light times for spacecraft-to-ground communication. Our new closed-loop monitoring tool allows an analyst or mission controller to view and save uplink commands and ground events with their corresponding downlinked telemetry values regardless of the delay in downlink telemetry and without requiring real-time intervention by the user. An SOE document is a time-ordered list of all the planned ground and spacecraft events, including all commands, sequence loads, ground events, significant mission activities, spacecraft status, and resource allocations. The SOE document is generated by expansion and integration of spacecraft sequence files, ground station allocations, navigation files, and other ground event files. This SOE generation process has been automated within the OEL and includes a graphical, object-oriented SOE editor and real-time viewing tool running under X/Motif. The SOE toolkit was used as the framework for the integrated implementation. The SOE is used by flight engineers to coordinate their operations tasks, serving as a predict data set in ground operations and mission control. The closed-loop SOE toolkit allows simple, automated integration of predicted uplink events with correlated telemetry points in a single SOE document for on-screen viewing and archiving. It automatically interfaces with existing real-time or non real-time sources of information, to display actual values from the telemetry data stream. This toolkit was designed to greatly simplify the user's ability to access and view telemetry data, and also provide a means to view this data in the context of the commands and ground events that are used to interpret it. A closed-loop system can prove especially useful in small missions with limited resources requiring automated monitoring tools. This paper will discuss the toolkit implementation, including design trade-offs and future plans for enhancing the automated capabilities.

Murphy, Susan C.↗

NASA NTRSDate not supplied

NASA Delay Tolerant Networks: Operational, Evolving, an Ready for Expansion

The future of humanity’s presence beyond Earth depends on the successful commercialization of space. For commercialization to succeed, companies need cost-efficient architectures to support their business models and minimize risks for human capital, design, development, and operations. An ongoing challenge to any space enterprise is the reality that terrestrial network technologies are insufficient to provide reliable communications between assets in space. Whether you need to ensure your valuable data is safely transmitted to the ground or reliably delivered between platforms in orbit, ensuring data integrity over intermittent communication links is a necessity. Current solutions to space communications rely heavily on manual recording, storing, and retrieval of data from spacecraft. The current standard in space communication protocols, Consultative Committee for Space Data Systems (CCSDS) Space Packet standard, is reliant on inflexible network architectures based around mission-critical infrastructure to ensure data delivery. However, by automating the recording, storing, retrieval, and verification of data with Delay Tolerant Networks (DTN), the operator is freed from the dependence on manual data management and expensive mission critical infrastructure. NASA has been developing delay tolerant systems since the late 1990’s. Multiple DTN implementations have been established during that time, each suited to different use cases. Most notably, the DTN deployment for the International Space Station (ISS) includes demonstration of two DTN technologies: Interplanetary Overlay Network (ION) and Delay Tolerant Network Marshall Enterprise (DTNME). Beyond ISS, there are even more NASA DTN deployments being considered. Now that DTN implementations are maturing, it is appropriate to reflect upon these decades of work, review the integration and performance of the existing ISS deployment, and explore the future possibilities for DTN deployment industry-wide. The ISS DTN deployment is a complex architecture consisting of different DTN implementations for the onboard and ground network environments. The ION DTN implementation is being used in the on-board network. The Huntsville Operations Support Center (HOSC) DTN implementation, DTNME, is used by the ground network supporting ISS and will soon be a second onboard gateway too. The two implementations work cooperatively to provide high fidelity data services to flight operations users and payload developers across the globe. Though the two implementations yield a quality service, limitations are evident. Data rate, data storage, and device management are constrained by the services themselves and the complex nature of the deployment. Evolution of operations concepts will improve system capabilities and stability, but significant improvement will require additional development to the implementations themselves and to the overall deployment architecture. Taking advantage of the ongoing development and operation of the ISS DTN service will be central to the success of the future evolutions of NASA DTN deployments while demonstrating the benefits of DTN’s low-cost reliable data communication protocols for the growing commercial space industry. A broad effort on DTN integration and support is necessary to promote expansion beyond existing applications. NASA is developing several useful DTN implementations across a number of different systems: ION, DTNME, High-Rate DTN (HDTN), Bundle Protocol Library (BPLib), and others. To prevent fragmentation, DTN implementation teams need to communicate, collaborate, and integrate with one another to build a solid operational foundation for new DTN deployments. The establishment of a group that can assist new DTN users with understanding the purpose of each DTN implementation, provide best practices, and serve as a general knowledge base is paramount. Potential use of DTN on Gateway and other future NASA missions further drives the need for streamlined communication between DTN implementation teams. A well-integrated and highly engaged NASA DTN working group should help provide system architects the best DTN solutions for future commercial space efforts. This paper will first review the history of DTN implementations, explore the shortcoming of current space networking solutions given available limits in technology, and therefore establish the need for Delay Tolerant Networking in space communications. Secondly, the authors will explore NASA’s array of DTN implementations and highlight their usefulness to space applications. Thirdly, this paper will establish general DTN implementation distinguishing factors. Fourthly, the authors will discuss attempts to create a generic DTN comparison matrix, and the authors will review potential future topics in DTN innovation and collaboration, highlighting several key future efforts. Finally, this paper will describe how the institution of a NASA DTN Working Group will benefit DTN adoption across the governmental and commercial space sector. The goal of this paper is to encourage enthusiasm for DTN, share strategies for improving DTN on both current and future applications, promote the collaboration of DTN implementation groups within the international space operations community, and open the conversations about DTN, priorities, complexities, and innovation to the wider spaceflight industry.

DTN↗

NASA NTRSDate not supplied

NASA Delay Tolerant Networks: Operational, Evolving, an Ready for Expansion

The future of humanity’s presence beyond Earth depends on the successful commercialization of space. For commercialization to succeed, companies need cost-efficient architectures to support their business models and minimize risks for human capital, design, development, and operations. An ongoing challenge to any space enterprise is the reality that terrestrial network technologies are insufficient to provide reliable communications between assets in space. Whether you need to ensure your valuable data is safely transmitted to the ground or reliably delivered between platforms in orbit, ensuring data integrity over intermittent communication links is a necessity. Current solutions to space communications rely heavily on manual recording, storing, and retrieval of data from spacecraft. The current standard in space communication protocols, Consultative Committee for Space Data Systems (CCSDS) Space Packet standard, is reliant on inflexible network architectures based around mission-critical infrastructure to ensure data delivery. However, by automating the recording, storing, retrieval, and verification of data with Delay Tolerant Networks (DTN), the operator is freed from the dependence on manual data management and expensive mission critical infrastructure. NASA has been developing delay tolerant systems since the late 1990’s. Multiple DTN implementations have been established during that time, each suited to different use cases. Most notably, the DTN deployment for the International Space Station (ISS) includes demonstration of two DTN technologies: Interplanetary Overlay Network (ION) and Delay Tolerant Network Marshall Enterprise (DTNME). Beyond ISS, there are even more NASA DTN deployments being considered. Now that DTN implementations are maturing, it is appropriate to reflect upon these decades of work, review the integration and performance of the existing ISS deployment, and explore the future possibilities for DTN deployment industry-wide. The ISS DTN deployment is a complex architecture consisting of different DTN implementations for the onboard and ground network environments. The ION DTN implementation is being used in the on-board network. The Huntsville Operations Support Center (HOSC) DTN implementation, DTNME, is used by the ground network supporting ISS and will soon be a second onboard gateway too. The two implementations work cooperatively to provide high fidelity data services to flight operations users and payload developers across the globe. Though the two implementations yield a quality service, limitations are evident. Data rate, data storage, and device management are constrained by the services themselves and the complex nature of the deployment. Evolution of operations concepts will improve system capabilities and stability, but significant improvement will require additional development to the implementations themselves and to the overall deployment architecture. Taking advantage of the ongoing development and operation of the ISS DTN service will be central to the success of the future evolutions of NASA DTN deployments while demonstrating the benefits of DTN’s low-cost reliable data communication protocols for the growing commercial space industry. A broad effort on DTN integration and support is necessary to promote expansion beyond existing applications. NASA is developing several useful DTN implementations across a number of different systems: ION, DTNME, High-Rate DTN (HDTN), Bundle Protocol Library (BPLib), and others. To prevent fragmentation, DTN implementation teams need to communicate, collaborate, and integrate with one another to build a solid operational foundation for new DTN deployments. The establishment of a group that can assist new DTN users with understanding the purpose of each DTN implementation, provide best practices, and serve as a general knowledge base is paramount. Potential use of DTN on Gateway and other future NASA missions further drives the need for streamlined communication between DTN implementation teams. A well-integrated and highly engaged NASA DTN working group should help provide system architects the best DTN solutions for future commercial space efforts. This paper will first review the history of DTN implementations, explore the shortcoming of current space networking solutions given available limits in technology, and therefore establish the need for Delay Tolerant Networking in space communications. Secondly, the authors will explore NASA’s array of DTN implementations and highlight their usefulness to space applications. Thirdly, this paper will establish general DTN implementation distinguishing factors. Fourthly, the authors will discuss attempts to create a generic DTN comparison matrix, and the authors will review potential future topics in DTN innovation and collaboration, highlighting several key future efforts. Finally, this paper will describe how the institution of a NASA DTN Working Group will benefit DTN adoption across the governmental and commercial space sector. The goal of this paper is to encourage enthusiasm for DTN, share strategies for improving DTN on both current and future applications, promote the collaboration of DTN implementation groups within the international space operations community, and open the conversations about DTN, priorities, complexities, and innovation to the wider spaceflight industry.

DTN↗

NASA NTRS1990

The Small Explorer Data System - A data system based on standard interfaces

The Small Explorer Data System was developed by NASA Goddard Space Flight Center using a 'standard interfaces' approach. Standard interfaces make it adaptable to a wide variety of missions. The paper describes the Small Explorer Data System with particular emphasis on the standard interfaces incorporated in both the hardware and software.

Smith, Brian S.↗

NASA NTRSDate not supplied

Risk Characterization Research for Artemis II: Human Factors and Behavioral Performance

BACKGROUND Artemis II will be the first time NASA astronauts go beyond low-Earth orbit (LEO) since the Apollo era, and the first astronauts heading into space in the Orion vehicle. As such, it provides a critical opportunity to refine our understanding of the likelihood and consequences associated with the Behavioral Medicine (BMed), Team, Human System Integration Architecture (HSIA), and Sleep Risks, and prepare for future Moon and Mars missions. However, Artemis II research efforts are uniquely shaped by in-mission data collection constraints. There is currently no in-mission crew time available to complete measures. In-mission data will need to be collected unobtrusively from available data streams (e.g., audiovisual, existing records such as schedules, and actigraphy). Accordingly, the overarching goal of our research is to utilize Artemis II data to further define the likelihood and consequences of these risks, and to create an unobtrusive research infrastructure that can be expanded to include future Artemis missions. This goal spans four aims across three research phases: (1) identify and operationally define key performances metrics and constructs across the four aforementioned risks, (2) develop an unobtrusive methodology and coding scheme for in-mission data collection, (3) characterize performance decrements due to Bmed, Team, HSIA, and Sleep Risks, and (4) develop a data infrastructure for future Artemis missions. The following details results of Phase I efforts in which we address Aims 1 and 2 to develop an unobtrusive measurement plan and coding scheme to capture key constructs, contributing factors, and performance decrements across each risk area. METHOD As part of Phase I, we conducted an interdisciplinary literature review and consulted with SMEs to identify unobtrusive methodologies that leverage text, audio, and/or video data as well as conceptualize key performance metrics, contributing factors, and BMed, Team, HSIA, and Sleep risk constructs related to performance decrements. The Phase I effort resulted in a finalized pre- and post-mission protocol for Artemis II, along with a measurement and coding scheme for in-mission Artemis II data. Phase II will involve data collection from the upcoming Artemis II mission. Phase III will include data processing, coding, depiction, analysis, and report writing of the Artemis II data. RESULTS & DISCUSSION To date, we have completed Phase I efforts. Specifically, we identified BMed, Team, HSIA, and Sleep risk constructs related to performance metrics, summarized how these constructs can be measured using audiovisual data collected during the mission, and worked with NASA’s HFBP Element to finalize a data collection protocol that leverages audiovisual input from the Orion spacecraft system. Our protocol includes novel unobtrusive methodologies that adhere to in-mission data streams and subsequent constraints (e.g., limited storage space on GoPro cameras, ambient noise impeding audio files) to best capture in-mission phenomena across each risk area. We will present our results from Phase I efforts, namely best practices for unobtrusive measurement as identified through literature reviews and SME consultation as well as codebook excerpts for use in Artemis II. We will include a description of planned work as we prepare for Phase II and Phase III of this research plan and the Artemis II mission itself. SUMMARY We describe progress on our Human Factors and Behavioral Performance Research for Artemis II study.

behavioral health↗

NASA NTRS1975

Data management for Large Space Telescope

The data management system for the Large Space Telescope (LST) must be capable of meeting requirements of 160 million bits per 95 min orbit with a bit error rate of less than 0.00001 for data. The system will be supported by the Tracking and Data Relay Satellite System of the Space Tracking and Data Network. The on-board system includes a general purpose computer that controls the vehicle as a stable observation platform and the array of instruments used for data collection. The ground-based system comprises a Mission Operations Center (MOC), a Science Institute where instrument data is processed, and a communications service for the space and point-to-point data flow. The allocation of hardware and software between on-board and ground-based components to achieve design objectives of maximum flexibility at minimum cost is discussed.

Hope, G. R., Jr.↗

NASA NTRS2019

Developing Data Assimilated 4D Global Precipitation Products from the GEOS system in Support of the GPM Mission

This presentation is to report on the progresses made for the NASA Precipitation Measurement Mission (PMM) science team research tasks that are recently funded by NASA HQ. These tasks include (1) extending the existing GEOS all-sky analysis system to assimilate radiance data from other microwave sensors in GPM constellation satellites, (2) producing improved GEOS analyses of precipitation and downscaling of satellite precipitation estimates, and (3) providing the GEOS analyses to PMM Science team as prototype of GPM Level-4 products.

Kim, Min-Jeong↗

NASA NTRS2006

Asynchronous Message Service for Deep Space Mission Operations

While the CCSDS (Consultative Committee for Space Data Systems) File Delivery Protocol (CFDP) provides internationally standardized file transfer functionality that can offer significant benefits for deep space mission operations, not all spacecraft communication requirements are necessarily best met by file transfer. In particular, continuous event-driven asynchronous message exchange may also be useful for communications with, among, and aboard spacecraft. CCSDS has therefore undertaken the development of a new Asynchronous Message Service (AMS) standard, designed to provide common functionality over a wide variety of underlying transport services, ranging from shared memory message queues to CCSDS telemetry systems. The present paper discusses the design concepts of AMS, their applicability to deep space mission operations problems, and the results of preliminary performance testing obtained from exercise of a prototype implementation.

asynchronous message exchanges↗

NASA NTRS2004

Assessment of in-flight anomalies of long life outer plant mission

Thee unmanned planetary spacecraft to the outer planets have been controlled and operated successfully in space for an accumulated total of 66 years. The Voyager 1 and 2 spacecraft each have been in space for more than 26 years. The Galileo spacecraft was in space for 14 years, including eight years in orbit about Jupiter. During the flight operations for these missions, anomalies for the ground data system and the flight systems have been tracked using the anomaly reporting tool at the Jet Propulsion Laboratory. A total of 3300 incidents, surprises, and anomaly reports have been recorded in the database. This paper describes methods and results for classifying and identifying trends relative to ground system vs. flight system, software vs. hardware, and corrective actions. There are several lessons learned from these assessments that significantly benefit the design and planning for long life missions of the future. These include the necessity for having redundancy for successful operation of the spacecraft, awareness that anomaly reporting is dependent on mission activity not the age of the spacecraft, and the need for having a program to maintain and transfer operation knowledge and tools to replacement flight team members.

anomalies↗

NASA NTRS1991

The 1991 EOS reference handbook

The following topics are covered: (1) The Global Change Research Program; (2) The Earth Observing System (EOS) goal and objectives; (3) primary EOS mission requirements; (4) EOS science; (5) EOS Data and Information System (EOSDIS) architecture; (6) data policy; (7) international cooperation; (8) plans and status; (9) the role of the National Oceanic and Atmospheric Administration; (10) The Global Fellowship Program; (11) management of EOS; (12) mission elements; (13) EOS instruments; (14) interdisciplinary science investigations; (15) points of contact; and (16) acronyms and abbreviations.

Dokken, David↗

NASA NTRS1983

Implementation Strategy

Meeting the identified needs of Earth science requires approaching EOS as an information system and not simply as one or more satellites with instruments. Six elements of strategy are outlined as follows: implementation of the individual discipline missions as currently planned; use of sustained observational capabilities offered by operational satellites without waiting for the launch of new mission; put first priority on the data system; deploy an Advanced Data Collection and Location System; put a substantial new observing capability in a low Earth orbit in such a way as to provide for sustained measurements; and group instruments to exploit their capabilities for synergism; maximize the scientific utility of the mission; and minimize the costs of implementation where possible.

Source record↗