Search NASA⌕ Search

SEARCH · Search NASA

Results for “data delivery status tracking”

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.

6 records
All sourcesNASA NTRSDOE OSTI
NASA NTRS2005

Response to MRO's end-to-end data accountability challenges

(MRO) on August 12, 2005. It carries six science instruments and three engineering payloads. Because MRO will produce an unprecedented number of science products, it will transmit a much higher data volume via high data rate than any other deep space mission to date. Keeping track of MRO products as well as relay products would be a daunting, expensive task without a well-planned data-product tracking strategy. To respond to this challenge, the MRO project developed the End-to- End Data Accountability System by utilizing existing information available from both ground and flight elements. Therefore, a capability to perform first-order problem diagnosis is essential in order for MRO to answer the questions, where is my data? and when will my data be available? This paper details the approaches taken, design and implementation of the tools, procedures and teams that track data products from the time they are predicted until they arrive in the hands of the end users.

data delivery status tracking↗
NASA NTRS2003

The MER/CIP Portal for Ground Operations

We developed the Mars Exploration Rover/Collaborative Information Portal (MER/CIP) to facilitate MER operations. MER/CIP provides a centralized, one-stop delivery platform integrating science and engineering data from several distributed heterogeneous data sources. Key issues for MER/CIP include: 1) Scheduling and schedule reminders; 2) Tracking the status of daily predicted outputs; 3) Finding and analyzing data products; 4) Collaboration; 5) Announcements; 6) Personalization.

Chan, Louise↗
NASA NTRS2011

Final Report: MaRSPlus Sensor System Electrical Cable Management and Distributed Motor Control Computer Interface

The success of JPL's Next Generation Imaging Spectrometer (NGIS) in Earth remote sensing has inspired a follow-on instrument project, the MaRSPlus Sensor System (MSS). One of JPL's responsibilities in the MSS project involves updating the documentation from the previous JPL airborne imagers to provide all the information necessary for an outside customer to operate the instrument independently. As part of this documentation update, I created detailed electrical cabling diagrams to provide JPL technicians with clear and concise build instructions and a database to track the status of cables from order to build to delivery. Simultaneously, a distributed motor control system is being developed for potential use on the proposed 2018 Mars rover mission. This system would significantly reduce the mass necessary for rover motor control, making more mass space available to other important spacecraft systems. The current stage of the project consists of a desktop computer talking to a single "cold box" unit containing the electronics to drive a motor. In order to test the electronics, I developed a graphical user interface (GUI) using MATLAB to allow a user to send simple commands to the cold box and display the responses received in a user-friendly format.

data cubes↗
NASA NTRS2001

Status of the Direct Data Distribution (D(exp 3)) Experiment

NASA Glenn Research Center's Direct Data Distribution (D3) project will demonstrate an advanced, high-performance communications system that transmits information from an advanced technology payload carried by a NASA spacecraft in low Earth orbit (LEO) to a small receiving terminal on Earth. The space-based communications package will utilize a solid-state, K-band phased-array antenna that electronically steers the radiated energy beam toward a low-cost, tracking ground terminal, thereby providing agile, vibration-free, electronic steering at reduced size and weight with increased reliability. The array-based link will also demonstrate new digital processing technology that will allow the transmission of substantially increased amounts of latency-tolerant data collected from the LEO spacecraft directly to NASA field centers, principal investigators, or into the commercial terrestrial communications network. The technologies demonstrated by D3 will facilitate NASA's transition from using Government-owned communication assets to using commercial communication services. The hardware for D3 will incorporate advanced technology components developed under the High Rate Data Delivery (HRDD) Thrust Area of NASA's Office of Aerospace Technology Space Base Program at Glenn's Communications Technology Division. The flight segment components will include the electrically steerable phased-array antenna, which is being built by the Raytheon System Corporation and utilizes monolithic microwave integrated circuit (MMIC) technology operating at 19.05 GHz; and the digital encoder/modulator chipset, which uses four-channel orthogonal frequency division multiplexing (OFDM). The encoder/modulator will use a chipset developed by SICOM, Inc., which is both bandwidth and power efficient. The ground segment components will include a low-cost, open-loop tracking ground terminal incorporating a cryoreceiver to minimize terminal size without compromising receiver capability. The project is planning to hold a critical design review in the second quarter of fiscal year 2002.

Wald, Lawrence↗
NASA NTRS2008

The NASA Orbiting Carbon Observatory (OCO) Mission: Objectives, Approach, and Status

The Orbiting Carbon Observatory (OCO) is a NASA Earth System Science Pathfinder (ESSP) mission that is currently under development at the Jet Propulsion Laboratory (JPL). OCO will make global, space-based measurements of atmospheric carbon dioxide (CO2) with the precision, resolution, and coverage needed to characterize regional-scale sources and sinks of this important greenhouse gas. The observatory consists of a dedicated spacecraft bus that carries a single instrument. The bus employs single-string version of Orbital Sciences Corporation (OSC) LEOStar-2 architecture. This 3-axis stabilized bus includes a propulsion system for orbit insertion and maintenance, provides power, points the instrument, receives and processes commands from the ground, and records, stores, and downlinks science and engineering data. The OCO instrument incorporates 3 oboresighted, high resolution grating spectrometers that will make coincident measurements of reflected sunlight in near-infrared CO2 and molecular oxygen (O2) bands. The instrument was designed and manufactured by Hamilton Sundstrand (Pomona, CA), and then integrated, flight qualified, and calibrated by JPL. It is scheduled for delivery to OSC (Dulles, VA) for integration with the spacecraft bus in the spring of 2008. OCO will be launched from the Vandenberg Air Force Base on a dedicated OSC Taurus XL launch vehicle in December 2008. It will fly in formation with the Earth Observing System Afternoon Constellation, a group of satellites that files in a 98.8 minute, 705 km altitude, sun-synchronous orbit. This orbit provides coverage of the sunlit hemisphere with a 16-day ground track repeat cycle. OCO will fly approx.4 minutes ahead of the EOS Aqua platform, with an ascending nodal crossing time of approx.1:26 PM. The OCO science data will be transmitted to the NASA Ground Network Stations in Alaska and Virginia, and then transferred to the OCO Ground Data System at JPL. There, the CO2 and O2 spectra will be analyzed by the OCO Science Team to provide spatially resolved estimates of the column-averaged CO2 dry air mole fraction, XCO2. These measurements are expected to improve our understanding of the nature and processes that regulate atmospheric CO2 enabling more reliable forecasts of CO2 buildup and its impact on climate change.

global measurements↗
NASA NTRS2022

Flight Software Dictionary Development for the Mars2020 Rover

The Mars2020 project, developed and operated by the Jet Propulsion Laboratory (JPL), successfully landed the Perseverance rover and its flying companion Ingenuity on the surface of Mars on February 18th 2021. Perseverance combines heritage and cutting-edge flight software and hardware to accomplish crucial mission requirements related to Martian surface sampling. The design, development, and operation of NASA’s large strategic science missions require the ability to communicate spacecraft capabilities to hundreds of engineers across multiple disciplines. The interaction between flight and ground software development, Verification and Validation (V&V), Assembly, Test, and Launch Operations (ATLO), and management each demand quick understanding of unique slices of information for each discipline. This information includes the current capabilities of the flight system as well as future capabilities and their status as they are developed and tested. Despite the fundamental and critical nature of this information, the flight software dictionaries used to track it are a stumbling block for many projects. These dictionaries provide the cornerstone for the interpretation of data sent from the spacecraft, allowing for quick comprehension by engineers on the ground. During both spacecraft development and operations, flight software dictionary management includes significant challenges due to the large number of interfacing systems and the subtle yet distinct needs of each.The engineering of flight software dictionaries for Mars2020 had numerous challenges, most-notably: parallel dictionary development to support simultaneous separate flight software build campaigns for each mission phase (cruise and surface), managing requests for operations-enabling information without perturbing the heritage interface with the rover, and the introduction of new tools by the dictionary stakeholders that forced the dictionary team to innovate and redesign the heritage tool chain. These challenges generated guiding principles for the dictionary development effort: emphasize coding best practices and unit testing in the dictionary code development tool chain, use institutionally provided COTS (commercial-off-the-shelf) tools whenever possible, and maintain the heritage flight-ground interface all while advancing operations-enabling information via a loosely coupled interface.Throughout development and operations, the Mars2020 dictionary toolchain included IBM DOORS Next Generation, GitHub, Microsoft Excel, Docker, Jenkins, and a significant custom-built Python codebase. Significant interfaces included JPL’s command and control software, heritage flight software team tools and processes, and the many cloud-based ground tools developed for the mission.This paper will discuss the requirements for the Mars2020 dictionary development, the development team’s response to those requirements, lessons learned throughout the process, steps taken towards automated deliveries and continuous integration of stakeholder inputs, potential toolchain improvements for Mars2020, and key takeaways that could be applied to future missions.

Pyrzak, Guy↗