Search NASA⌕ Search

SEARCH · Search NASA

Results for “ground 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 253 records · Page 14

Using virtual reality for science mission planning: A Mars Pathfinder case

NASA's Mars Pathfinder Project requires a Ground Data System (GDS) that supports both engineering and scientific payloads with reduced mission operations staffing, and short planning schedules. Also, successful surface operation of the lander camera requires efficient mission planning and accurate pointing of the camera. To meet these challenges, a new software strategy that integrates virtual reality technology with existing navigational ancillary information and image processing capabilities. The result is an interactive workstation based applications software that provides a high resolution, 3-dimensial, stereo display of Mars as if it were viewed through the lander camera. The design, implementation strategy and parametric specification phases for the development of this software were completed, and the prototype tested. When completed, the software will allow scientists and mission planners to access simulated and actual scenes of Mars' surface. The perspective from the lander camera will enable scientists to plan activities more accurately and completely. The application will also support the sequence and command generation process and will allow testing and verification of camera pointing commands via simulation.

Kim, Jacqueline H.↗

Autonomous mission planning and scheduling: Innovative, integrated, responsive

Autonomous mission scheduling, a new concept for NASA ground data systems, is a decentralized and distributed approach to scientific spacecraft planning, scheduling, and command management. Systems and services are provided that enable investigators to operate their own instruments. In autonomous mission scheduling, separate nodes exist for each instrument and one or more operations nodes exist for the spacecraft. Each node is responsible for its own operations which include planning, scheduling, and commanding; and for resolving conflicts with other nodes. One or more database servers accessible to all nodes enable each to share mission and science planning, scheduling, and commanding information. The architecture for autonomous mission scheduling is based upon a realistic mix of state-of-the-art and emerging technology and services, e.g., high performance individual workstations, high speed communications, client-server computing, and relational databases. The concept is particularly suited to the smaller, less complex missions of the future.

Sary, Charisse↗

Mars Observer Orbit Insertion Briefing

Steve Wall is the host of this video entitled, "Return to the Red Planet". Live animation of the Mars Observer orbiting Mars is presented. Steve Wall explains the spacecraft insertion maneuver and also explains the purpose for the Mars Observer launch. Live coverage of the Cape Canaveral launch of the Mars Observer is also presented. Suzanne Dodd, Chief of the Mission Planning team describes the burn start and how the spacecraft will be captured by Mars' gravity. Glenn Cunningham, Mars Observer Project Manager, gives background information on the Mars Observer and describes the organizations behind the Mars Observer Spacecraft, such as the Deep Space Network, the Mission Operation Support Office, Science Investigators, the Flight Engineering Office, Operations Office, and the Ground Data System Office. Dr. William Piotrowski, Acting Director, Solar System Exploration Division, NASA, talks about the purpose of the Mars Pathfinder which is to develop the technology and systems for landing small science packages on Mars. Mr. Roger Gibbs, Former Mars Observer Spacecraft Systems Engineer, tells us how the Mars Observer was built and describes the structural elements on the Mars Observer. The 11-month cruise period for the spacecraft is given by Joseph Beerer, Manager of the Engineering office. The thrust for the Mars Orbit Insertion is described by Ronald Klemetson, Technical Manager, Propulsion Subsystem Jet Propulsion Laboratory (JPL). George Chen, Lead Engineer Attitude and Articulation Subsystem Spacecraft Team, explains the importance of the attitude control engines on the Spacecraft. Marvin Traxler, Manager of Tracking and Data Acquisition, describes how searching for a signal from the Mars Observer works. See NONP-NASA-VT-2000081555 for a continuation of this discussion with Marvin Traxler.

Source record↗

Operation of MRO's High Resolution Imaging Science Experiment (HiRISE): Maximizing Science Participation

Science return from the Mars Reconnaissance Orbiter (MRO) High Resolution Imaging Science Experiment (HiRISE) will be optimized by maximizing science participation in the experiment. MRO is expected to arrive at Mars in March 2006, and the primary science phase begins near the end of 2006 after aerobraking (6 months) and a transition phase. The primary science phase lasts for almost 2 Earth years, followed by a 2-year relay phase in which science observations by MRO are expected to continue. We expect to acquire approx. 10,000 images with HiRISE over the course of MRO's two earth-year mission. HiRISE can acquire images with a ground sampling dimension of as little as 30 cm (from a typical altitude of 300 km), in up to 3 colors, and many targets will be re-imaged for stereo. With such high spatial resolution, the percent coverage of Mars will be very limited in spite of the relatively high data rate of MRO (approx. 10x greater than MGS or Odyssey). We expect to cover approx. 1% of Mars at approx. 1m/pixel or better, approx. 0.1% at full resolution, and approx. 0.05% in color or in stereo. Therefore, the placement of each HiRISE image must be carefully considered in order to maximize the scientific return from MRO. We believe that every observation should be the result of a mini research project based on pre-existing datasets. During operations, we will need a large database of carefully researched 'suggested' observations to select from. The HiRISE team is dedicated to involving the broad Mars community in creating this database, to the fullest degree that is both practical and legal. The philosophy of the team and the design of the ground data system are geared to enabling community involvement. A key aspect of this is that image data will be made available to the planetary community for science analysis as quickly as possible to encourage feedback and new ideas for targets.

E Eliason↗

Functions Performed by Mission Operations

We propose the series of three presentations described above for inclusion in your symposium. These presentations are similar to those we presented last November in plenary session at the Third International Symposium on Space Mission Operations and Ground Data Systems. Each presentation lasts 40 minutes and the presentations are designed to be given in order. The information in our presentations is extracted from a book of the same title scheduled for publication in August, 1995. Please note that since we have a book covering this topic, we will not prepare separate papers. An overview of each presentation is shown below.

Cost-Effective Mission↗

Juno Mission Simulation

The Juno spacecraft is planned to launch in August of 2012 and would arrive at Jupiter four years later. The spacecraft would spend more than one year orbiting the planet and investigating the existence of an ice-rock core; determining the amount of global water and ammonia present in the atmosphere, studying convection and deep- wind profiles in the atmosphere; investigating the origin of the Jovian magnetic field, and exploring the polar magnetosphere. Juno mission management is responsible for mission and navigation design, mission operation planning, and ground-data-system development. In order to ensure successful mission management from initial checkout to final de-orbit, it is critical to share a common vision of the entire mission operation phases with the rest of the project teams. Two major challenges are 1) how to develop a shared vision that can be appreciated by all of the project teams of diverse disciplines and expertise, and 2) how to continuously evolve a shared vision as the project lifecycle progresses from formulation phase to operation phase. The Juno mission simulation team addresses these challenges by developing agile and progressive mission models, operation simulations, and real-time visualization products. This paper presents mission simulation visualization network (MSVN) technology that has enabled a comprehensive mission simulation suite (MSVN-Juno) for the Juno project.

space vehicles↗

Internet Distribution of Spacecraft Telemetry Data

Remote Access Multi-mission Processing and Analysis Ground Environment (RAMPAGE) is a Java-language server computer program that enables near-real-time display of spacecraft telemetry data on any authorized client computer that has access to the Internet and is equipped with Web-browser software. In addition to providing a variety of displays of the latest available telemetry data, RAMPAGE can deliver notification of an alarm by electronic mail. Subscribers can then use RAMPAGE displays to determine the state of the spacecraft and formulate a response to the alarm, if necessary. A user can query spacecraft mission data in either binary or comma-separated-value format by use of a Web form or a Practical Extraction and Reporting Language (PERL) script to automate the query process. RAMPAGE runs on Linux and Solaris server computers in the Ground Data System (GDS) of NASA's Jet Propulsion Laboratory and includes components designed specifically to make it compatible with legacy GDS software. The client/server architecture of RAMPAGE and the use of the Java programming language make it possible to utilize a variety of competitive server and client computers, thereby also helping to minimize costs.

Specht, Ted↗

Kepler Science Operations Center Architecture

We give an overview of the operational concepts and architecture of the Kepler Science Data Pipeline. Designed, developed, operated, and maintained by the Science Operations Center (SOC) at NASA Ames Research Center, the Kepler Science Data Pipeline is central element of the Kepler Ground Data System. The SOC charter is to analyze stellar photometric data from the Kepler spacecraft and report results to the Kepler Science Office for further analysis. We describe how this is accomplished via the Kepler Science Data Pipeline, including the hardware infrastructure, scientific algorithms, and operational procedures. The SOC consists of an office at Ames Research Center, software development and operations departments, and a data center that hosts the computers required to perform data analysis. We discuss the high-performance, parallel computing software modules of the Kepler Science Data Pipeline that perform transit photometry, pixel-level calibration, systematic error-correction, attitude determination, stellar target management, and instrument characterization. We explain how data processing environments are divided to support operational processing and test needs. We explain the operational timelines for data processing and the data constructs that flow into the Kepler Science Data Pipeline.

Middour, Christopher↗

Checking Flight Rules with TraceContract: Application of a Scala DSL for Trace Analysis

Typically during the design and development of a NASA space mission, rules and constraints are identified to help reduce reasons for failure during operations. These flight rules are usually captured in a set of indexed tables, containing rule descriptions, rationales for the rules, and other information. Flight rules can be part of manual operations procedures carried out by humans. However, they can also be automated, and either implemented as on-board monitors, or as ground based monitors that are part of a ground data system. In the case of automated flight rules, one considerable expense to be addressed for any mission is the extensive process by which system engineers express flight rules in prose, software developers translate these requirements into code, and then both experts verify that the resulting application is correct. This paper explores the potential benefits of using an internal Scala DSL for general trace analysis, named TRACECONTRACT, to write executable specifications of flight rules. TRACECONTRACT can generally be applied to analysis of for example log files or for monitoring executing systems online.

temporal logic↗

MaROS Strategic Relay Planning and Coordination Interfaces

The Mars Relay Operations Service (MaROS) is designed to provide planning and analysis tools in support of ongoing Mars Network relay operations. Strategic relay planning requires coordination between lander and orbiter mission ground data system (GDS) teams to schedule and execute relay communications passes. MaROS centralizes this process, correlating all data relevant to relay coordination to provide a cohesive picture of the relay state. Service users interact with the system through thin-layer command line and web user interface client applications. Users provide and utilize data such as lander view periods of orbiters, Deep Space Network (DSN) antenna tracks, and reports of relay pass performance. Users upload and download relevant relay data via formally defined and documented file structures including some described in Extensible Markup Language (XML). Clients interface with the system via an http-based Representational State Transfer (ReST) pattern using Javascript Object Notation (JSON) formats. This paper will provide a general overview of the service architecture and detail the software interfaces and considerations for interface design.

Allard, Daniel A.↗

Astrobee: Space Station Robotic Free Flyer

Astrobee is a free flying robot that will fly inside the International Space Station and primarily serve as a research platform for robotics in zero gravity. Astrobee will also provide mobile camera views to ISS flight and payload controllers, and collect various sensor data within the ISS environment for the ISS Program. Astrobee consists of two free flying robots, a dock, and ground data system. This presentation provides an overview, high level design description, and project status.

Free flight↗

Extreme Mapping: Looking for Water on the Moon

There are many challenges when exploring extreme environments. Gathering accurate data to build maps about places that you cannot go is incredibly complex. NASA supports scientists by remotely operating robotic rovers to explore uncharted territories. One potential upcoming mission is to look for water near a lunar pole (the Resource Prospector mission). Learn about the technical hurdles and research steps that NASA takes before the mission. NASA practices on Earth with Mission Analogs which simulate the proposed mission. This includes going to lunar-type landscapes, building field networks, testing out rovers, instruments and operational procedures. NASA sets up remote science back rooms just as there are for actual missions. NASA develops custom Ground Data Systems software to support scientific mission planning and monitoring over variable time delays, and separate commanding software and infrastructure to operate the rovers.

MOON↗

The Kepler Science Data Processing Pipeline Source Code Road Map

We give an overview of the operational concepts and architecture of the Kepler Science Processing Pipeline. Designed, developed, operated, and maintained by the Kepler Science Operations Center (SOC) at NASA Ames Research Center, the Science Processing Pipeline is a central element of the Kepler Ground Data System. The SOC consists of an office at Ames Research Center, software development and operations departments, and a data center which hosts the computers required to perform data analysis. The SOC's charter is to analyze stellar photometric data from the Kepler spacecraft and report results to the Kepler Science Office for further analysis. We describe how this is accomplished via the Kepler Science Processing Pipeline, including, the software algorithms. We present the high-performance, parallel computing software modules of the pipeline that perform transit photometry, pixel-level calibration, systematic error correction, attitude determination, stellar target management, and instrument characterization.

Kepler pipeline software↗

Traverse Planning with Temporal-Spatial Constraints

We present an approach to planning rover traverses in a domain that includes temporal-spatial constraints. We are using the NASA Resource Prospector mission as a reference mission in our research. The objective of this mission is to explore permanently shadowed regions at a Lunar pole. Most of the time the rover is required to avoid being in shadow. This requirement depends on where the rover is located and when it is at that location. Such a temporal-spatial constraint makes traverse planning more challenging for both humans and machines. We present a mixed-initiative traverse planner which addresses this challenge. This traverse planner is part of the Exploration Ground Data Systems (xGDS), which we have enhanced with new visualization features, new analysis tools, and new automation for path planning, in order to be applicable to the Re-source Prospector mission. The key concept that is the basis of the analysis tools and that supports the automated path planning is reachability in this dynamic environment due to the temporal-spatial constraints.

temporal-spatial constraints↗

Finding Stuff Underwater: Open-Source Tools for Underwater Field Science

Since 2009, we have been developing and testing Exploration Ground Data Systems (xGDS). xGDS is a software suite, built on open-source web technologies, for supporting NASA terrestrial field science analog missions. We will describe our recent work supporting underwater mapping and dive operations at the Pavilion Lake Research Project (PLRP - www.pavilionlake.com). At PLRP we used open-source mapping technologies to meet an operational need to quickly guide divers and underwater vehicles to locations of interest, and the scientific goal of building a map showing the locations and characteristics of the microbialites at the bottom of the lake. We will discuss some of the benefits and lessons-learned from our recent transition from Google Earth to OpenLayers as the primary mapping engine to support our work. Well also explain the challenges we faced and solutions weve developed to support mapping and data collection in an underwater environment.Beyond their immediate value for advancing scientific research on Earth, NASA analogs explore new ideas for supporting scientists working in extreme environments (e.g. underwater) to develop best practices for future human missions to the Moon or Mars. Science at PLRP involved imaging, sampling and characterizing microbialites growing beneath the surface of an alpine lake in British Columbia. To support PLRP operations and science, xGDS helped plan data collection tasks and provided accurate tracking and mapping of the locations of the underwater assets (human-piloted submersibles, remotely operated vehicles (ROVs) and human divers) collecting imagery and samples from the lake. The data collected during our field work was registered with precursor bathymetry data collected by an autonomous underwater vehicle (AUV) and was globally located on a satellite base layer map of the area surrounding the lake.

Earth analogs↗

Using Science Operations Tools and Methods from NASA for Remote Presence Ocean Exploration on Earth: E/V Nautilus Cruise NA108

NASA Ames' Exploration Ground Data Systems (xGDS) supports rapid scientific decision making by synchronizing information in time and space, including video and still images, scientific instrument data, and science and operations notes in geographic and temporal context. We have deployed xGDS at multiple NASA field analog missions over the past decade.In the last two years, we have participated in SUBSEA, a multi-institution collaborative project. SUBSEA used the research ship E/V Nautilus along with its two remotely operated vehicles (ROVs), Hercules and Argus, to explore deep ocean volcanic vents as an analog for ocean worlds (e.g. Enceladus). This work allowed us to compare the existing oceanographic operations methods and technologies used for ocean exploration with corresponding tools and approaches developed and used at NASA. In the first year of SUBSEA we observed existing remote science operations from the Inner Space Center (ISC). In the second year, we deployed xGDS at ISC to complement existing capabilities with xGDS tools designed to support remote Nautilus science operations from the ISC. During operations, video, ROV position and instrument telemetry were streamed from the ship to the ISC. As the science team watched dive operations, they could annotate the data with observations that were relevant to their work domain. Later, the team members could review the data at their own pace to collaboratively develop a dive plan for the next day, which had to be delivered on a fixed daily schedule.The opportunity to compare operations under different conditions enabled us to make several key observations about conducting remote science and planning operations efficiently: (i) Reviewing data collaboratively and interactively with temporal and spatial context was critical for the remote science team's ability to plan dive operations on the Nautilus. (ii) Science team members were actively engaged with the remote dive operations because they could interact with the collected data and visualize it as they desired. (iii) Being able to replay past events at accelerated speeds, and jump to points in time and spaced based on search results, provided efficient access to critical points of interest in a massive volume of data, so the remote science team could deliver plans on time. SUBSEA (Systematic Underwater Biogeochemical Science and Exploration Analog) is a multi-institution collaboration supported by NASA, NOAA's Office of Exploration Research (OER), the Ocean Exploration Trust (OET) and the University of Rhode Island's Graduate School of Oceanography (GSO). ISC is GSO's telepresence operations facility.

Lees, David S.↗