Search NASA⌕ Search

SEARCH · Search NASA

Results for “Mission Data System”

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.

At least 325 records · Page 18
All sourcesNASA NTRSDOE OSTI
NASA NTRS1991

Advanced automation in space shuttle mission control

The Real Time Data System (RTDS) Project was undertaken in 1987 to introduce new concepts and technologies for advanced automation into the Mission Control Center environment at NASA's Johnson Space Center. The project's emphasis is on producing advanced near-operational prototype systems that are developed using a rapid, interactive method and are used by flight controllers during actual Shuttle missions. In most cases the prototype applications have been of such quality and utility that they have been converted to production status. A key ingredient has been an integrated team of software engineers and flight controllers working together to quickly evolve the demonstration systems.

Heindel, Troy A.↗
NASA NTRS2019

Computing observation geometry for small satellites

Most solar system science missions need a variety of observation geometry–quantities such as position and velocity, range and altitude, viewing latitude and longitude, and lighting angles– to support mission engineering, science planning, and science data analysis activities. NASA's "SPICE" system offers one popular, multi-mission means for doing just that. SPICE comprises both data files, called kernels, and a SPICE software Toolkit that is available in many popular languages. A mission operations center produces the SPICE kernel files. Scientists and engineers write their own applications programs to address some need, and they include a few SPICE subroutines within that code to do the needed geometry computations. The SPICE system has been in use throughout NASA’s planetary science mission domain since 1991, and it has slowly spread to most major space agencies around the globe since then. The SPICE software is available in most popular languages, and for most popular platforms. The code is thoroughly tested before being released, and new versions of the Toolkit are always backwards compatible. The SPICE components are freely offered to everyone, and have no export, licensing or similar restrictions. Maybe using SPICE would work for your CubeSat or SmallSat mission?

Acton, Charles H.↗
NASA NTRS2009

CCSDS Spacecraft Monitor and Control Mission Operations Interoperability Prototype

We are entering a new era in space exploration. Reduced operating budgets require innovative solutions to leverage existing systems to implement the capabilities of future missions. Custom solutions to fulfill mission objectives are no longer viable. Can NASA adopt international standards to reduce costs and increase interoperability with other space agencies? Can legacy systems be leveraged in a service oriented architecture (SOA) to further reduce operations costs? The Operations Technology Facility (OTF) at the Johnson Space Center (JSC) is collaborating with Deutsches Zentrum fur Luft- und Raumfahrt (DLR) to answer these very questions. The Mission Operations and Information Management Services Area (MOIMS) Spacecraft Monitor and Control (SM&C) Working Group within the Consultative Committee for Space Data Systems (CCSDS) is developing the Mission Operations standards to address this problem space. The set of proposed standards presents a service oriented architecture to increase the level of interoperability among space agencies. The OTF and DLR are developing independent implementations of the standards as part of an interoperability prototype. This prototype will address three key components: validation of the SM&C Mission Operations protocol, exploration of the Object Management Group (OMG) Data Distribution Service (DDS), and the incorporation of legacy systems in a SOA. The OTF will implement the service providers described in the SM&C Mission Operation standards to create a portal for interaction with a spacecraft simulator. DLR will implement the service consumers to perform the monitor and control of the spacecraft. The specifications insulate the applications from the underlying transport layer. We will gain experience with a DDS transport layer as we delegate responsibility to the middleware and explore transport bridges to connect disparate middleware products. A SOA facilitates the reuse of software components. The prototype will leverage the capabilities of existing legacy systems. Various custom applications and middleware solutions will be combined into one system providing the illusion of a set of homogenous services. This paper will document our journey as we implement the interoperability prototype. The team consists of software engineers with experience on the current command, telemetry and messaging systems that support the International Space Station (ISS) and Space Shuttle programs. Emphasis will be on the objectives, results and potential cost saving benefits.

Lucord, Steve↗
NASA NTRS1966

Surveyor mission operations system

Functional description of launch vehicle, tracking and data acquisition, spacecraft, and mission operations of Surveyor mission

LAUNCH VEHICLE↗
NASA NTRS2019

Visualization and Analysis of Data from Small-Body Missions with NASA's Solar System Treks Portals

The portals of NASA's Solar System Trek Project (SSTP) provide web-based suites of interactive visualization and analysis tools enabling mission planners, planetary scientists, students, and the general public to explore planetary surfaces as seen through the eyes of many different instruments aboard a wide range of spacecraft. The portals present a vast collection of mapped data products from past and current missions for a growing number of planetary bodies. As web-based toolsets, the portals do not require users to purchase or install any software beyond current web browsers. They feature a common user interface and are available through a single integrated website at https://trek.nasa.gov. This presentation will highlight 4 portals focusing on small bodies. We will provide an overview of established portals for (1) Ceres and (4) Vesta, and present the early capabilities for new portals being introduced for (162173) Ryugu and (101955) Bennu.

Day, Brian↗
NASA NTRS2002

An Overview of the Earth Observing System MODIS Instrument and Associated Data Systems Performance

The Moderate Resolution Imaging Spectroradiometer (MODIS) on the Earth Observing System (EOS) Terra Mission began to produce data in February 2000. Now a little over 2 years from that time, the instrument continues to produce good data and products for land, oceans, and atmospheres studies are reaching or achieved maturity for science and applications studies. All subsystems of the instrument are performing as expected: the signal-to-noise (S/N) performance meets or exceeds specifications, band-to-band registration meets specifications, geodetic registration of observations is nearing 50 meters (one sigma) and the spectral bands are located where they were intended to be pre-launch and attendant gains and offsets are stable to date. Some problems with electronic noise, optical leaks, etc. have been identified and solutions to compensate or eliminate these effects have been successful. The data systems have produced a complete year or more for all data products extending from November 2000. Efforts are underway to provide data sets for the greater Earth science community and to improve access to these products at the various Distributed Active Archive Centers (DAAC's). The MODIS instrument on the EOS Aqua mission should also be expected to be in orbit and functioning in the Spring of 2002.

Salomonson, Vincent V.↗
NASA NTRS1991

SHARP: Automated monitoring of spacecraft health and status

Briefly discussed here are the spacecraft and ground systems monitoring process at the Jet Propulsion Laboratory (JPL). Some of the difficulties associated with the existing technology used in mission operations are highlighted. A new automated system based on artificial intelligence technology is described which seeks to overcome many of these limitations. The system, called the Spacecraft Health Automated Reasoning Prototype (SHARP), is designed to automate health and status analysis for multi-mission spacecraft and ground data systems operations. The system has proved to be effective for detecting and analyzing potential spacecraft and ground systems problems by performing real-time analysis of spacecraft and ground data systems engineering telemetry. Telecommunications link analysis of the Voyager 2 spacecraft was the initial focus for evaluation of the system in real-time operations during the Voyager spacecraft encounter with Neptune in August 1989.

Atkinson, David J.↗
NASA NTRS1990

SHARP - Automated monitoring of spacecraft health and status

Briefly discussed here are the spacecraft and ground systems monitoring process at the Jet Propulsion Laboratory (JPL). Some of the difficulties associated with the existing technology used in mission operations are highlighted. A new automated system based on artificial intelligence technology is described which seeks to overcome many of these limitations. The system, called the Spacecraft Health Automated Reasoning Prototype (SHARP), is designed to automate health and status analysis for multi-mission spacecraft and ground data systems operations. The system has proved to be effective for detecting and analyzing potential spacecraft and ground systems problems by performing real-time analysis of spacecraft and ground data systems engineering telemetry. Telecommunications link analysis of the Voyager 2 spacecraft was the initial focus for evaluation of the system in real-time operations during the Voyager spacecraft encounter with Neptune in August 1989.

Atkinson, David J.↗
NASA NTRS1973

Tracking and data relay satellite system /TDRSS/

Plans for a new way of providing tracking and data acquisition support for future earth orbital missions, the Tracking and Data Relay Satellite System (TDRSS), are reviewed. This system is to become the principal support facility for all NASA R&D missions below about 5000 km altitude. Current plans call for a 2-satellite system that is to provide upwards of 85% coverage of all orbits above 200 km and 100% coverage above 1200 km.

Barritt, P. F.↗
NASA NTRS2010

NAIF Toolkit - Extended

The Navigation Ancillary Infor ma tion Facility (NAIF) at JPL, acting under the direction of NASA s Office of Space Science, has built a data system named SPICE (Spacecraft Planet Instrument Cmatrix Events) to assist scientists in planning and interpreting scientific observations (see figure). SPICE provides geometric and some other ancillary information needed to recover the full value of science instrument data, including correlation of individual instrument data sets with data from other instruments on the same or other spacecraft. This data system is used to produce space mission observation geometry data sets known as SPICE kernels. It is also used to read SPICE kernels and to compute derived quantities such as positions, orientations, lighting angles, etc. The SPICE toolkit consists of a subroutine/ function library, executable programs (both large applications and simple utilities that focus on kernel management), and simple examples of using SPICE toolkit subroutines. This software is very accurate, thoroughly tested, and portable to all computers. It is extremely stable and reusable on all missions. Since the previous version, three significant capabilities have been added: Interactive Data Language (IDL) interface, MATLAB interface, and a geometric event finder subsystem.

Acton, Charles H., Jr.↗
NASA NTRS2018

RESTful CFDP: Managing GDS Complexity with Microservices

NASA's Advanced Multi-Mission Operations System (AMMOS) is currently adding capability to support the CCSDS File Delivery Protocol (CFDP). This feature is being added as part of the AMMOS Mission Data Processing and Control System (AMPCS). In order to address the system’s increasing complexity, AMPCS has recently been re-architected to break down its monolithic applications into smaller, individually deployable microservices. The CFDP capability is the first new AMPCS feature to leverage this new architecture. The CFDP microservice provides a web-based Representational State Transfer (REST) application programming interface (API) for complete monitor and control of its operations, and this enables it to be decoupled from other AMPCS microservices. This also results in better scalability for redundancy and load balancing. AMPCS's CFDP microservice is designed to support generic CFDP operations, agnostic to AMPCS's legacy concept of Downlink Products. An optional runtime plug-in allows the CFDP microservice to simulate CFDP artifacts as Downlink Products. Applying the microservices software architecture pattern both in the latest release of AMPCS and in providing the new CFDP capability has resulted in a more flexible system with improved extensibility and maintainability. System complexity has also become more manageable.

Choi, Joshua S.↗
NASA NTRS1992

SEDS1 mission software verification using a signal simulator

The first flight of the Small Expendable Deployer System (SEDS1) is schedule to fly as the secondary payload of a Delta 2 in March, 1993. The objective of the SEDS1 mission is to collect data to validate the concept of tethered satellite systems and to verify computer simulations used to predict their behavior. SEDS1 will deploy a 50 lb. instrumented satellite as an end mass using a 20 km tether. Langley Research Center is providing the end mass instrumentation, while the Marshall Space Flight Center is designing and building the deployer. The objective of the experiment is to test the SEDS design concept by demonstrating that the system will satisfactorily deploy the full 20 km tether without stopping prematurely, come to a smooth stop on the application of a brake, and cut the tether at the proper time after it swings to the local vertical. Also, SEDS1 will collect data which will be used to test the accuracy of tether dynamics models used to stimulate this type of deployment. The experiment will last about 1.5 hours and complete approximately 1.5 orbits. Radar tracking of the Delta II and end mass is planned. In addition, the SEDS1 on-board computer will continuously record, store, and transmit mission data over the Delta II S-band telemetry system. The Data System will count tether windings as the tether unwinds, log the times of each turn and other mission events, monitor tether tension, and record the temperature of system components. A summary of the measurements taken during the SEDS1 are shown. The Data System will also control the tether brake and cutter mechanisms. Preliminary versions of two major sections of the flight software, the data telemetry modules and the data collection modules, were developed and tested under the 1990 NASA/ASEE Summer Faculty Fellowship Program. To facilitate the debugging of these software modules, a prototype SEDS Data System was programmed to simulate turn count signals. During the 1991 summer program, the concept of simulating signals produced by the SEDS electronics systems and circuits was expanded and more precisely defined. During the 1992 summer program, the SEDS signal simulator was programmed to test the requirements of the SEDS Mission software, and this simulator will be used in the formal verification of the SEDS Mission Software. The formal test procedures specification was written which incorporates the use of the signal simulator to test the SEDS Mission Software and which incorporates procedures for testing the other major component of the SEDS software, the Monitor Software.

Pierson, William E.↗
NASA NTRS1993

NASA's spacecraft data system

The NASA Small Explorer Data System (SEDS), a space flight data system developed to support the Small Explorer (SMEX) project, is addressed. The system was flown on the Solar Anomalous Magnetospheric Particle Explorer (SAMPEX) SMEX mission, and with reconfiguration for different requirements will fly on the X-ray Timing Explorer (XTE) and the Tropical Rainfall Measuring Mission (TRMM). SEDS is also foreseen for the Hubble repair mission. Its name was changed to Spacecraft Data System (SDS) in view of expansions. Objectives, SDS hardware, and software are described. Each SDS box contains two computers, data storage memory, uplink (command) reception circuitry, downlink (telemetry) encoding circuitry, Instrument Telemetry Controller (ITC), and spacecraft timing circuitry. The SDS communicates with other subsystems over the MIL-STD-1773 data bus. The SDS software uses a real time Operating System (OS) and the C language. The OS layer, communications and scheduling layer, application task layer, and diagnostic software, are described. Decisions on the use of advanced technologies, such as ASIC's (Application Specific Integrated Circuits) and fiber optics, led to technical improvements, such as lower power and weight, without increasing the risk associated with the data system. The result was a successful SAMPEX development, integration and test, and mission using SEDS, and the upgrading of that system to SDS for TRMM and XTE.

Cudmore, Alan↗
NASA NTRS1990

Artificial intelligence for multi-mission planetary operations

A brief introduction is given to an automated system called the Spacecraft Health Automated Reasoning Prototype (SHARP). SHARP is designed to demonstrate automated health and status analysis for multi-mission spacecraft and ground data systems operations. The SHARP system combines conventional computer science methodologies with artificial intelligence techniques to produce an effective method for detecting and analyzing potential spacecraft and ground systems problems. The system performs real-time analysis of spacecraft and other related telemetry, and is also capable of examining data in historical context. Telecommunications link analysis of the Voyager II spacecraft is the initial focus for evaluation of the prototype in a real-time operations setting during the Voyager spacecraft encounter with Neptune in August, 1989. The preliminary results of the SHARP project and plans for future application of the technology are discussed.

Atkinson, David J.↗
NASA NTRS1979

Orbiter data reduction complex data processing requirements for the OFT mission evaluation team (level C)

This document addresses requirements for post-test data reduction in support of the Orbital Flight Tests (OFT) mission evaluation team, specifically those which are planned to be implemented in the ODRC (Orbiter Data Reduction Complex). Only those requirements which have been previously baselined by the Data Systems and Analysis Directorate configuration control board are included. This document serves as the control document between Institutional Data Systems Division and the Integration Division for OFT mission evaluation data processing requirements, and shall be the basis for detailed design of ODRC data processing systems.

Source record↗
NASA NTRS2019

Architecture and Dynamics of Kepler's Multi-Transiting Planet Systems.III. Comprehensive Investigation Using All Four Years of Kepler Mission Data

We study the orbital architectures of planetary systems orbiting within ∼1 AU of their stars by analyzing the ensemble of Kepler systems having two or more planet candidates. We use data from the entire Kepler mission, and in many cases we apply improved analysis techniques (e.g., replacing histograms by top-hat Kernel Density Estimators that avoid the loss of information resulting from choosing a particular phase for the bin boundaries) to extend and enhance the studies of Lissauer et al. (2011, ApJS 197, 8) and Fabrycky et al. (2014, ApJ 790, 146).These data show ~ 1700 transiting planet candidates in > 600 multiple-planet systems, far more than were available for our previous two studies. The increased numbers and better information about planetary radii and the properties of stellar hosts made possible by Gaia DR2 allow more statistically-robust analyses of the entire ensemble of Kepler multis as well as independent analyses of subsets of the population. We are thus able to contrast the dynamical configurations of small and large planets, short-period and longer-period planets, and planets orbiting various types of host stars. We reinforce our previous findings that most pairs of planets within the same system are neither in nor near low-order mean motion resonances and that there is a substantial excess of planets having period ratios slightly larger than those of first-order mean-motion resonances. However, neglecting three systems whose planets are locked in 3- body resonances and summing over all first-order mean motion resonances, the deficit of planet pairs with period ratios just narrow of resonance is as large as the excess of planets wide of resonance (within statistical uncertainties), suggesting that overall there is no overall excess of planet pairs in the vicinity of resonance. Other aspects of our study, including estimates of the typical relative inclinations of planetary orbits and their variations as functions of orbital period, planet sizes and stellar properties, are in progress, with results expected to be available for presentation by the time of the conference.

Lissauer, Jack↗
NASA NTRS2014

A Space Data System Standard for Telerobotic Operations

The Telerobotics Working Group of the Mission Operations and Information Management Services Area of the Consultative Committee for Space Data Systems is drafting a document that will help bound the scope of an eventual international standard for telerobotic operations services. This paper will present the work in progress and provide background for how the international community is beginning to define standards in telerobotic operations that will help ensure the success of complex missions to explore beyond Earth orbit.

Mittman, David S.↗