Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “MER”

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 775 records · Page 43

Supporting Increased Autonomy for a Mars Rover

This paper presents an architecture and a set of technology for performing autonomous science and commanding for a planetary rover. The MER rovers have outperformed all expectations by lasting over 1100 sols (or Martian days), which is an order of magnitude longer than their original mission goal. The longevity of these vehicles will have significant effects on future mission goals, such as objectives for the Mars Science Laboratory rover mission (scheduled to fly in 2009) and the Astrobiology Field Lab rover mission (scheduled to potentially fly in 2016). Common objectives for future rover missions to Mars include the handling of opportunistic science, long-range or multi-sol driving, and onboard fault diagnosis and recovery. To handle these goals, a number of new technologies have been developed and integrated as part of the CLARAty architecture. CLARAty is a unified and reusable robotic architecture that was designed to simplify the integration, testing and maturation of robotic technologies for future missions. This paper focuses on technology comprising the CLARAty Decision Layer, which was designed to support and validate high-level autonomy technologies, such as automated planning and scheduling and onboard data analysis.

autonomous science↗

MSLICE Science Activity Planner for the Mars Science Laboratory Mission

MSLICE (Mars Science Laboratory InterfaCE) is the tool used by scientists and engineers on the Mars Science Laboratory rover mission to visualize the data returned by the rover and collaboratively plan its activities. It enables users to efficiently and effectively search all mission data to find applicable products (e.g., images, targets, activity plans, sequences, etc.), view and plan the traverse of the rover in HiRISE (High Resolution Imaging Science Experiment) images, visualize data acquired by the rover, and develop, model, and validate the activities the rover will perform. MSLICE enables users to securely contribute to the mission s activity planning process from their home institutions using off-the-shelf laptop computers. This software has made use of several plug-ins (software components) developed for previous missions [e.g., Mars Exploration Rover (MER), Phoenix Mars Lander (PHX)] and other technology tasks. It has a simple, intuitive, and powerful search capability. For any given mission, there is a huge amount of data and associated metadata that is generated. To help users sort through this information, MSLICE s search interface is provided in a similar fashion as major Internet search engines. With regard to the HiRISE visualization of the rover s traverse, this view is a map of the mission that allows scientists to easily gauge where the rover has been and where it is likely to go. The map also provides the ability to correct or adjust the known position of the rover through the overlaying of images acquired from the rover on top of the HiRISE image. A user can then correct the rover s position by collocating the visible features in the overlays with the same features in the underlying HiRISE image. MSLICE users can also rapidly search all mission data for images that contain a point specified by the user in another image or panoramic mosaic. MSLICE allows the creation of targets, which provides a way for scientists to collaboratively name features on the surface of Mars. These targets can also be used to convey instrument-pointing information to the activity plan. The software allows users to develop a plan of what they would like the rover to accomplish for a given time period. When developing the plan, the user can input constraints between activities or groups of activities. MSLICE will enforce said constraints and ensure that all mission flight rules are satisfied.

Powell, Mark W.↗

Detecting Airborne Mercury by Use of Polymer/Carbon Films

Films made of certain polymer/carbon composites have been found to be potentially useful as sensing films for detecting airborne elemental mercury at concentrations on the order of tens of parts per billion or more. That is to say, when the polymer/carbon composite films are exposed to air containing mercury vapor, their electrical resistances decrease by measurable amounts. Because airborne mercury is a health hazard, it is desirable to detect it with great sensitivity, especially in enclosed environments in which there is a risk of a mercury leak from lamps or other equipment. The present effort to develop polymerbased mercury-vapor sensors complements the work reported in NASA Tech Briefs Detecting Airborne Mercury by Use of Palladium Chloride (NPO- 44955), Vol. 33, No. 7 (July 2009), page 48 and De tecting Airborne Mer cury by Use of Gold Nanowires (NPO-44787), Vol. 33, No. 7 (July 2009), page 49. Like those previously reported efforts, the present effort is motivated partly by a need to enable operation and/or regeneration of sensors under relatively mild conditions more specifically, at temperatures closer to room temperature than to the elevated temperatures (greater than 100 C ) needed for regeneration of sensors based on noble-metal films. The present polymer/carbon films are made from two polymers, denoted EYN1 and EYN2 (see Figure 1), both of which are derivatives of poly-4-vinyl pyridine with amine functional groups. Composites of these polymers with 10 to 15 weight percent of carbon were prepared and solution-deposited onto the JPL ElectronicNose sensor substrates for testing. Preliminary test results showed that the resulting sensor films gave measurable indications of airborne mercury at concentrations on the order of tens of parts per billion (ppb) or more. The operating temperature range for the sensing films was 28 to 40 C and that the sensor films regenerated spontaneously, without heating above operating temperature (see Figure 2).

Shevade, Abhijit↗

Mineralogy of SNC Meteorite EET79001 by Simultaneous Fitting of Moessbauer Backscatter Spectra

We have acquired M ssbauer spectra for SNC meteorite EET79001 with a MIMOS II backscatter M ssbauer spectrometer [1] similar to those now operating on Mars as part of the Mars Exploration Rover (MER) missions. We are working to compare the Fe mineralogical composition of martian meteorites with in-situ measurements on Mars. Our samples were hand picked from the >1 mm size fraction of saw fines on the basis of lithology, color, and grain size (Table 1). The chips were individually analyzed at approx.300K by placing them on a piece of plastic that was in turn supported by the contact ring of the instrument (oriented vertically). Tungsten foil was used to mask certain areas from analysis. As shown in Figure 1, a variety of spectra was obtained, each resulting from different relative contributions of the Fe-bearing minerals present in the sample. Because the nine samples are reasonably mixtures of the same Fe-bearing phases in variable proportions, the nine spectra were fit simultaneously (simfit) with a common model, adjusting parameters to a single minimum chi-squared convergence criterion [2]. The starting point for the fitting model and values of hyperfine parameters was the work of Solberg and Burns [3], who identified olivine, pyroxene, and ferrous glass as major, and ilmenite and a ferric phase as minor (<5%), Fe-bearing phases in EET79001.

Morris, Richard V.↗

Chemical Alteration on Mars Indicated by the Iron-Manganese Ratio

The Alpha Particle X-ray Spectrometers (APXS) onboard the Mars Exploration Rovers (MER) have measured the chemical compositions of over 400 samples on the surface of Mars. Fe and Mn are among the elements which are well established by this instrumentation. Fe 2+ and Mn2+ have nearly the same ionic radii and distribute similarly in primary igneous rocks, maintaining a consistent Fe:Mn ratio. Upon exposure to an oxidative weathering environment, Fe 3+ and Mn4+ are commonly formed, and elemental fractionation can occur. Thus, altered samples will typically exhibit a Fe:Mn ratio different from precursor materials.

Yen, A. S.↗

Chemical Alteration on Mars Indicated by the Iron-Manganese Ratio

The Alpha Particle X-ray Spectrometers (APXS) onboard the Mars Exploration Rovers (MER) have measured the chemical compositions of over 400 samples on the surface of Mars. Fe and Mn are among the elements which are well established by this instrumentation. Fe2+ and Mn2+ have nearly the same ionic radii and distribute similarly in primary igneous rocks, maintaining a consistent Fe:Mn ratio. Upon exposure to an oxidative weathering environment, Fe 3+ and Mn4+ are commonly formed, and elemental fractionation can occur. Thus, altered samples will typically exhibit a Fe:Mn ratio different from precursor materials.

Yen, A. S.↗

AutoGen Version 5.0

Version 5.0 of the AutoGen software has been released. Previous versions, variously denoted Autogen and autogen, were reported in two articles: Automated Sequence Generation Process and Software (NPO-30746), Software Tech Briefs (Special Supplement to NASA Tech Briefs), September 2007, page 30, and Autogen Version 2.0 (NPO- 41501), NASA Tech Briefs, Vol. 31, No. 10 (October 2007), page 58. To recapitulate: AutoGen (now signifying automatic sequence generation ) automates the generation of sequences of commands in a standard format for uplink to spacecraft. AutoGen requires fewer workers than are needed for older manual sequence-generation processes, and greatly reduces sequence-generation times. The sequences are embodied in spacecraft activity sequence files (SASFs). AutoGen automates generation of SASFs by use of another previously reported program called APGEN. AutoGen encodes knowledge of different mission phases and of how the resultant commands must differ among the phases. AutoGen also provides means for customizing sequences through use of configuration files. The approach followed in developing AutoGen has involved encoding the behaviors of a system into a model and encoding algorithms for context-sensitive customizations of the modeled behaviors. This version of AutoGen addressed the MRO (Mars Reconnaissance Orbiter) primary science phase (PSP) mission phase. On previous Mars missions this phase has more commonly been referred to as mapping phase. This version addressed the unique aspects of sequencing orbital operations and specifically the mission specific adaptation of orbital operations for MRO. This version also includes capabilities for MRO s role in Mars relay support for UHF relay communications with the MER rovers and the Phoenix lander.

Gladden, Roy E.↗

Automatic Command Sequence Generation

Automatic Sequence Generator (Autogen) Version 3.0 software automatically generates command sequences for the Mars Reconnaissance Orbiter (MRO) and several other JPL spacecraft operated by the multi-mission support team. Autogen uses standard JPL sequencing tools like APGEN, ASP, SEQGEN, and the DOM database to automate the generation of uplink command products, Spacecraft Command Message Format (SCMF) files, and the corresponding ground command products, DSN Keywords Files (DKF). Autogen supports all the major multi-mission mission phases including the cruise, aerobraking, mapping/science, and relay mission phases. Autogen is a Perl script, which functions within the mission operations UNIX environment. It consists of two parts: a set of model files and the autogen Perl script. Autogen encodes the behaviors of the system into a model and encodes algorithms for context sensitive customizations of the modeled behaviors. The model includes knowledge of different mission phases and how the resultant command products must differ for these phases. The executable software portion of Autogen, automates the setup and use of APGEN for constructing a spacecraft activity sequence file (SASF). The setup includes file retrieval through the DOM (Distributed Object Manager), an object database used to store project files. This step retrieves all the needed input files for generating the command products. Depending on the mission phase, Autogen also uses the ASP (Automated Sequence Processor) and SEQGEN to generate the command product sent to the spacecraft. Autogen also provides the means for customizing sequences through the use of configuration files. By automating the majority of the sequencing generation process, Autogen eliminates many sequence generation errors commonly introduced by manually constructing spacecraft command sequences. Through the layering of commands into the sequence by a series of scheduling algorithms, users are able to rapidly and reliably construct the desired uplink command products. With the aid of Autogen, sequences may be produced in a matter of hours instead of weeks, with a significant reduction in the number of people on the sequence team. As a result, the uplink product generation process is significantly streamlined and mission risk is significantly reduced. Autogen is used for operations of MRO, Mars Global Surveyor (MGS), Mars Exploration Rover (MER), Mars Odyssey, and will be used for operations of Phoenix. Autogen Version 3.0 is the operational version of Autogen including the MRO adaptation for the cruise mission phase, and was also used for development of the aerobraking and mapping mission phases for MRO.

Fisher, Forest↗

Improved Path Planning Onboard the Mars Exploration Rovers

A revised version of the AutoNav (autonomous navigation with hazard avoidance) software running onboard each Mars Exploration Rover (MER) affords better obstacle avoidance than does the previous version. Both versions include GESTALT (Grid-based Estimation of Surface Traversability Applied to Local Terrain), a navigation program that generates local-terrain models from stereoscopic image pairs captured by onboard rover cameras; uses this information to evaluate candidate arcs that extend across the terrain from the current rover location; ranks the arcs with respect to hazard avoidance, minimization of steering time, and the direction towards the goal; and combines the rankings in a weighted vote to select an arc, along which the rover is then driven. GESTALT works well in navigating around small isolated obstacles, but tends to fail when the goal is on the other side of a large obstacle or multiple closely spaced small obstacles. When that occurs, the goal seeking votes and hazard avoidance votes conflict severely. The hazard avoidance votes will not allow the rover to drive through the unsafe area, and the waypoint votes will not allow enough deviation from the straight-line path for the rover to get around the hazard. The rover becomes stuck and is unable to reach the goal. The revised version of AutoNav utilizes a global path-planning program, Field D*, to evaluate the cost of traveling from the end of each GESTALT arc to the goal. In the voting process, Field D* arc votes supplant GESTALT goal-seeking arc votes. Hazard avoidance, steering bias, and Field D* votes are merged and the rover is driven a preset distance along the arc with the highest vote. Then new images are acquired and the process as described is repeated until the goal is reached. This new technology allows the rovers to autonomously navigate around much more complex obstacle arrangements than was previously possible. In addition, this improved autonomy enables longer traverses per Sol (a day on Mars), and can make planning drives easier for operators on Earth.

Stentz, Anthony↗

Distributed Operations Planning

Maestro software provides a secure and distributed mission planning system for long-term missions in general, and the Mars Exploration Rover Mission (MER) specifically. Maestro, the successor to the Science Activity Planner, has a heavy emphasis on portability and distributed operations, and requires no data replication or expensive hardware, instead relying on a set of services functioning on JPL institutional servers. Maestro works on most current computers with network connections, including laptops. When browsing down-link data from a spacecraft, Maestro functions similarly to being on a Web browser. After authenticating the user, it connects to a database server to query an index of data products. It then contacts a Web server to download and display the actual data products. The software also includes collaboration support based upon a highly reliable messaging system. Modifications made to targets in one instance are quickly and securely transmitted to other instances of Maestro. The back end that has been developed for Maestro could benefit many future missions by reducing the cost of centralized operations system architecture.

Fox, Jason↗

Geologic Mapping of the Meridiani Region of Mars

The Mars Exploration Rover Opportunity observed an upper layer of a more than 600-m-thick sequence of light toned outcrops that characterize the Meridiani region of Mars. Results from the rover analyses have shown that the bedrock contains mineral and textural characteristics that require at least the interaction of, and possibly an overall formation by, water-related mechanisms in order to be explained [1]. Additionally, remote sensing studies of the region have suggested that the rocks sampled in places by the MER rover consist of many distinct layers extending over an area of more than 3 10(exp 5) sq km spanning 20deg of longitude [2].

DiAchille, G.↗

Software for Collaborative Use of Large Interactive Displays

The MERBoard Collaborative Workspace, which is currently being deployed to support the Mars Exploration Rover (MER) Missions, is the first instantiation of a new computing architecture designed to support collaborative and group computing using computing devices situated in NASA mission operations room. It is a software system for generation of large-screen interactive displays by multiple users

Trimble, Jay↗

Ground-Based Localization of Mars Rovers

The document discusses a procedure for localizing the Mars rovers in site frame, a locally defined reference frame on the Martian surface. MER onboard position within a site frame is estimated onboard and is based on wheel odometry. Odometry estimation of rover position is only reliable over relatively short distances assuming no wheel slip, sinkage, etc. As the rover traverses, its onboard estimate of position in the current site frame accumulates errors and will need to be corrected on occasions via relocalization on the ground (mission operations). The procedure provides a systematic process for ground operators to localize the rover. The method focuses on analysis of acquired images used to declare a site frame and images acquired post-drive. Target selection is performed using two main steps. In the first step, the user identifies features of interest from the images used to declare the current site. Each of the selected target s position in site frame is recorded. In the second step, post-traverse measurements of the selected features positions are recorded again, this time in rover frame, using images acquired post-traverse. In the third step, we transform the post-traverse target s positions to local level frame. In the fourth step, we compute the delta differences in the pre- and post-traverse target s position. In the fifth step, we analyze the delta differences with techniques that compute their statistics to determine the rover s position in the site frame.

Trebi-Ollennu, Ashitey↗

Verification and Implementation of Operations Safety Controls for Flight Missions

Approximately eleven years ago, the International Space Station launched the first module from Russia, the Functional Cargo Block (FGB). Safety and Mission Assurance (S&MA) Operations (Ops) Engineers played an integral part in that endeavor by executing strict flight product verification as well as continued staffing of S&MA's console in the Mission Evaluation Room (MER) for that flight mission. How were these engineers able to conduct such a complicated task? They conducted it based on product verification that consisted of ensuring that safety requirements were adequately contained in all flight products that affected crew safety. S&MA Ops engineers apply both systems engineering and project management principles in order to gain a appropriate level of technical knowledge necessary to perform thorough reviews which cover the subsystem(s) affected. They also ensured that mission priorities were carried out with a great detail and success.

Jones, Cheryl L.↗

Polyphony: A Workflow Orchestration Framework for Cloud Computing

Cloud Computing has delivered unprecedented compute capacity to NASA missions at affordable rates. Missions like the Mars Exploration Rovers (MER) and Mars Science Lab (MSL) are enjoying the elasticity that enables them to leverage hundreds, if not thousands, or machines for short durations without making any hardware procurements. In this paper, we describe Polyphony, a resilient, scalable, and modular framework that efficiently leverages a large set of computing resources to perform parallel computations. Polyphony can employ resources on the cloud, excess capacity on local machines, as well as spare resources on the supercomputing center, and it enables these resources to work in concert to accomplish a common goal. Polyphony is resilient to node failures, even if they occur in the middle of a transaction. We will conclude with an evaluation of a production-ready application built on top of Polyphony to perform image-processing operations of images from around the solar system, including Mars, Saturn, and Titan.

Space Exploration,↗

Soil Components in Heterogeneous Impact Glass in Martian Meteorite EETA79001

Martian soil composition can illuminate past and ongoing near-surface processes such as impact gardening [2] and hydrothermal and volcanic activity [3,4]. Though the Mars Exploration Rovers (MER) have analyzed the major-element composition of Martian soils, no soil samples have been returned to Earth for detailed chemical analysis. Rao et al. [1] suggested that Martian meteorite EETA79001 contains melted Martian soil in its impact glass (Lithology C) based on sulfur enrichment of Lithology C relative to the meteorite s basaltic lithologies (A and B) [1,2]. If true, it may be possible to extract detailed soil chemical analyses using this meteoritic sample. We conducted high-resolution (~0.3 m/pixel) element mapping of Lithology C in thin section EETA79001,18 by energy dispersive spectrometry (EDS). We use these data for principal component analysis (PCA).

Schrader, C. M.↗

Planetary Image Geometry Library

The Planetary Image Geometry (PIG) library is a multi-mission library used for projecting images (EDRs, or Experiment Data Records) and managing their geometry for in-situ missions. A collection of models describes cameras and their articulation, allowing application programs such as mosaickers, terrain generators, and pointing correction tools to be written in a multi-mission manner, without any knowledge of parameters specific to the supported missions. Camera model objects allow transformation of image coordinates to and from view vectors in XYZ space. Pointing models, specific to each mission, describe how to orient the camera models based on telemetry or other information. Surface models describe the surface in general terms. Coordinate system objects manage the various coordinate systems involved in most missions. File objects manage access to metadata (labels, including telemetry information) in the input EDRs and RDRs (Reduced Data Records). Label models manage metadata information in output files. Site objects keep track of different locations where the spacecraft might be at a given time. Radiometry models allow correction of radiometry for an image. Mission objects contain basic mission parameters. Pointing adjustment ("nav") files allow pointing to be corrected. The object-oriented structure (C++) makes it easy to subclass just the pieces of the library that are truly mission-specific. Typically, this involves just the pointing model and coordinate systems, and parts of the file model. Once the library was developed (initially for Mars Polar Lander, MPL), adding new missions ranged from two days to a few months, resulting in significant cost savings as compared to rewriting all the application programs for each mission. Currently supported missions include Mars Pathfinder (MPF), MPL, Mars Exploration Rover (MER), Phoenix, and Mars Science Lab (MSL). Applications based on this library create the majority of operational image RDRs for those missions. A Java wrapper around the library allows parts of it to be used from Java code (via a native JNI interface). Future conversions of all or part of the library to Java are contemplated.

Deen, Robert C.↗

Space Shuttle Missions Summary

This document has been produced and updated over a 21-year period. It is intended to be a handy reference document, basically one page per flight, and care has been exercised to make it as error-free as possible. This document is basically "as flown" data and has been compiled from many sources including flight logs, flight rules, flight anomaly logs, mod flight descent summary, post flight analysis of mps propellants, FDRD, FRD, SODB, and the MER shuttle flight data and inflight anomaly list. Orbit distance traveled is taken from the PAO mission statistics.

Bennett, Floyd V.↗