Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “high-level overview”

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 73 records · Page 4

RAPID and DDS

This talk gives an overview of the the Robot Applications Programmers Interface Delegate (RAPID) as well as the distributed systems middleware Data Distribution Service (DDS). DDS is an open software standard, RAPID is cleared for open-source release under NOSA. RAPID specifies data-structures and semantics for high-level telemetry published by NASA robotic software. These data-structures are supported by multiple robotic platforms at Johnson Space Center (JSC), Jet Propulsion Laboratory (JPL) and Ames Research Center (ARC), providing high-level interoperability between those platforms. DDS is used as the middleware for data transfer. The feature set of the middleware heavily influences the design decision made in the RAPID specification. So it is appropriate to discuss both in this introductory talk.

Utz, Hans Heinrich↗

Airborne Precision Spacing: A Trajectory-based Approach to Improve Terminal Area Operations

Airborne Precision Spacing has been developed by the National Aeronautics and Space Administration (NASA) over the past seven years as an attempt to benefit from the capabilities of the flight deck to precisely space their aircraft relative to another aircraft. This development has leveraged decades of work on improving terminal area operations, especially the arrival phase. With APS operations, the air traffic controller instructs the participating aircraft to achieve an assigned inter-arrival spacing interval at the runway threshold, relative to another aircraft. The flight crew then uses airborne automation to manage the aircraft s speed to achieve the goal. The spacing tool is designed to keep the speed within acceptable operational limits, promote system-wide stability, and meet the assigned goal. This reallocation of tasks with the controller issuing strategic goals and the flight crew managing the tactical achievement of those goals has been shown to be feasible through simulation and flight test. A precision of plus or minus 2-3 seconds is generally achievable. Simulations of long strings of arriving traffic show no signs of instabilities or compression waves. Subject pilots have rated the workload to be similar to current-day operations and eye-tracking data substantiate this result. This paper will present a high-level review of research results over the past seven years from a variety of tests and experiments. The results will focus on the precision and accuracy achievable, flow stability and some major sources of uncertainty. The paper also includes a summary of the flight crew s procedures and interface and a brief concept overview.

Barmore, Bryan↗

JSC Safety and Mission Assurance Data Analysis Overview

These slides describe the data analysis methods that are used to determine inputs for probabilistic risk models supporting the Space Shuttle Program. Other applications can follow a similar path probably using different data sources. Statistical approaches are different and not addressed here. Topics included here: 1) Prior Distribution; 2) Likelihood Data; 3) Bayesian Updating; and 4) Uncertainty and Error. Note: This is a high-level discussion and is not intended to be a tutorial.

Roelant, Henk↗

Strategic Analysis Overview

NASA s Constellation Program employs a strategic analysis methodology in providing an integrated analysis capability of Lunar exploration scenarios and to support strategic decision-making regarding those scenarios. The strategic analysis methodology integrates the assessment of the major contributors to strategic objective satisfaction performance, affordability, and risk and captures the linkages and feedbacks between all three components. Strategic analysis supports strategic decision making by senior management through comparable analysis of alternative strategies, provision of a consistent set of high level value metrics, and the enabling of cost-benefit analysis. The tools developed to implement the strategic analysis methodology are not element design and sizing tools. Rather, these models evaluate strategic performance using predefined elements, imported into a library from expert-driven design/sizing tools or expert analysis. Specific components of the strategic analysis tool set include scenario definition, requirements generation, mission manifesting, scenario lifecycle costing, crew time analysis, objective satisfaction benefit, risk analysis, and probabilistic evaluation. Results from all components of strategic analysis are evaluated a set of pre-defined figures of merit (FOMs). These FOMs capture the high-level strategic characteristics of all scenarios and facilitate direct comparison of options. The strategic analysis methodology that is described in this paper has previously been applied to the Space Shuttle and International Space Station Programs and is now being used to support the development of the baseline Constellation Program lunar architecture. This paper will present an overview of the strategic analysis methodology and will present sample results from the application of the strategic analysis methodology to the Constellation Program lunar architecture.

Cirillo, William M.↗

The preliminary SOL (Sizing and Optimization Language) reference manual

The Sizing and Optimization Language, SOL, a high-level special-purpose computer language has been developed to expedite application of numerical optimization to design problems and to make the process less error-prone. This document is a reference manual for those wishing to write SOL programs. SOL is presently available for DEC VAX/VMS systems. A SOL package is available which includes the SOL compiler and runtime library routines. An overview of SOL appears in NASA TM 100565.

Lucas, Stephen H.↗

A review of future weather data for assessing climate change impacts on buildings and energy systems

The effectiveness of climate change impact assessments and the development of adaptation strategies depend on the availability of high-quality future weather data. However, significant gaps exist between the needs of the energy research community and the focus of the climate modeling community, primarily due to a historical lack of communication and collaboration between the two groups. Here, to address this issue, this work provides a comprehensive overview of the critical aspects involved in creating future weather data for building and energy system modeling, including emissions scenarios, general circulation models, downscaling methods, categories of future weather data, and uncertainties in climate simulations. Moreover, it critically evaluates the applicability and suitability of various types of future weather data in five key application scenarios: energy use analysis, resilience analysis, HVAC design, utility-scale analysis, and renewable energy analysis. Finally, this work presents recommendations for high-level actions and research directions to foster collaboration between the energy research and climate modeling communities and to promote the integration of future weather data into energy codes and the design practices of buildings and energy systems.

Climate change↗

Performance Evaluation of Communication Software Systems for Distributed Computing

In recent years there has been an increasing interest in object-oriented distributed computing since it is better quipped to deal with complex systems while providing extensibility, maintainability, and reusability. At the same time, several new high-speed network technologies have emerged for local and wide area networks. However, the performance of networking software is not improving as fast as the networking hardware and the workstation microprocessors. This paper gives an overview and evaluates the performance of the Common Object Request Broker Architecture (CORBA) standard in a distributed computing environment at NASA Ames Research Center. The environment consists of two testbeds of SGI workstations connected by four networks: Ethernet, FDDI, HiPPI, and ATM. The performance results for three communication software systems are presented, analyzed and compared. These systems are: BSD socket programming interface, IONA's Orbix, an implementation of the CORBA specification, and the PVM message passing library. The results show that high-level communication interfaces, such as CORBA and PVM, can achieve reasonable performance under certain conditions.

Fatoohi, Rod↗

Communications Dashboard (Control Rooms Take a Cue from Facebook), Chapter 1

Papers published via IEEE and AIAA conferences have presented an overview of how social media could benefit NASA working environments in general and proposed three specific social applications to benefit space flight control operations. One of them, Communications Dashboard, would help a real time flight controller keep up with both the "big picture" and significant details of operations via a cohesive interface similar to those of social networking services (SNS). Instead of recreational social features, "CommDash" would support functions like console logging, categorized and threaded text chat streams with enhanced accountability and graphics display features, high-level status displays driven by telemetry or other events, and an on-screen hailing function for requesting voice or text stream conversation. Moving certain voice conversations to text streams would reduce confusion and stress in two ways. Within text conversations, there would be far less repetition of content since text conversations have visual persistence and are reviewable instantly, e.g., there s no need to brief new participants to a discussion -- they just read what s already there. Remaining voice traffic would stand out more clearly, and quieter voice loops means fewer "say again" calls and less distraction from visual and mental tasks, thus less stress. (Most flight controllers monitor 4 or 5 voice loops at once.) Links could be created from console log entries to chat selections so that underlying details are readily available yet unobtrusive. This would reduce the confusion that rises from having multiple and sometimes divergent copies of the same information due to cut/copy and paste operations, attachments, and asynchronous editing. This concept could apply to a plethora of real time control environments and to other settings with lots of information juggling. This paper explores the dashboard concept in further detail and chronicles the first phase of a NASA IT Labs (Information Technology) project that could lead to a working system

Scott, David w.↗

Robotic Lunar Exploration

This presentation describes current Lunar Exploration plans and objectives. It begins with specific statements from the President s vision for U.S. Space Exploration which pertain to robotic lunar missions. An outline of missions objectives is provided, along with a high-level schedule of events through the year 2025. Focus is then given to the Lunar Robotic and Precursor Program (LPRP) to describe objectives and goals. Recent developments in the Program are explained - specifically, the renaming of the RLEP program to "LPRP" and the movement of the program office to MSFC. A brief summary of the synergy expected between the robotic and crewed missions, with the LSAM descent stage Project is given. The Lunar Reconnaissance Orbiter mission, with its co-manifested Lunar Crater Observation and Sensing Satellite (LCROSS), is then described with an overview of the payloads and mission objectives. Finally, information is given about the expected future of the LPRP program and Exploration and the development of a compressive Lunar Exploration Architecture.

Echols, Raymond↗

Mission Design Overview for Mars 2003/2005 Sample Return Mission

In May 2003, a new and exciting chapter in Mars exploration will begin with the launch of the first of three spacecraft that will collectively contribute toward the goal of delivering samples from the Red Planet to Earth. This mission is called Mars Sample Return (MSR) and will utilize both the 2003 and 2005 launch opportunities with an expected sample return in October 2008. NASA and CNES are major partners in this mission. The baseline mission mode selected for MSR is Mars orbit rendezvous (MOR), analogous in concept to the lunar orbit rendezvous (LOR) mode used for Apollo in the 1960s. Specifically, MSR will employ two NASA-provided landers of nearly identical design and one CNES-provided orbiter carrying a NASA payload of rendezvous sensors, orbital capture mechanisms, and an Earth entry vehicle (EEV). The high-level concept is that the landers will launch surface samples into Mars orbit, and the orbiter will retrieve the samples in orbit and then carry them back to Earth. The first element to depart for Mars will be one of the two landers. Currently, it is proposed that an intermediate class launch vehicle, such as the Boeing Delta 3 or Lockheed Martin Atlas 3A, will launch this 1800-kg lander from Cape Canaveral during the May 2003 opportunity. The lander will utilize a Type-1 transfer trajectory with an arrival at Mars in mid-December 2003. Landing will be aided by precision approach navigation and a guided hypersonic entry to achieve a touchdown accuracy of 10 km or better. Although the exact landing site has not yet been determined, it is estimated that lander resource constraints will limit the site to between 15 degrees north and south latitudes. Following touchdown, the lander will deploy a six-wheeled, 60-kg rover carrying an extensive suite of instruments designed to aid in the analysis of the local terrain and collection of core samples from selected rocks. The surface mission is currently designed around a concept called the surface traverse. Each traverse will involve the rover exploring a selected area of terrain up to 100 meters from the lander, the collection of rock core samples, and the delivery of the samples from the traverse back to a sample canister on the lander. Planning estimates indicate that up to three traverses may be possible during the expected 90-sol lifetime of the lander. The canister that will receive the samples from the rover will be attached to the top stage of a small solid-fueled rocket mounted to the deck of the lander. This rocket is called the Mars Ascent Vehicle (MAV) and consists of three stages weighing a total of about 140 kg. After the conclusion of the surface mission, the MAV will lift-off and insert the sample canister into a near-circular orbit with an altitude of about 600 km and inclination of 45 degrees. The sample canister will wait in this orbit until it is retrieved by the orbiter sometime in early 2007. In August 2005, the second lander and a CNES-provided orbiter weighing 2700 kg will depart for Mars. Currently, it is proposed that a single Ariane 5 provided by CNES will launch both of these two elements onto a Type-2 transfer trajectory. Although the orbiter and lander will be launched together, they will separate shortly after injection and will fly to Mars as two independent spacecraft. However, both spacecraft will perform a maneuver between 10 and 15 days after launch so that their arrival times at Mars differ by between 12 and 24 hours. This scheme will reduce the operational complexity at the encounter date. A set of four 60-kg surface probes will ride piggyback on the orbiter to Mars. These CNES-provided probes are called Netlanders and will serve as surface stations for scientific investigations independent of the Mars Sample Return goals. Starting approximately one month prior to arrival at Mars, the orbiter will begin to release the Netlanders one at a time. Each release cycle will take several days, and will include time for precision navigation to execute one or two maneuvers that will target the Netlanders to their proper landing site. All four deployment cycles will be completed prior to 10 days before arrival. Both the orbiter and lander will arrive in late-July 2006. Upon arrival, the lander will perform a precision landing and surface mission similar in concept to the one that was executed during the 2003 opportunity. Although the landing site for the 2005 opportunity has not been selected, it is expected to be different from the 2003 site to enhance the diversity of the collected samples. The orbiter's arrival at Mars will be highlighted by the first use of aerocapture to insert a spacecraft into a capture orbit around another planet. The choice of aerocapture, as opposed to a propulsive orbit insertion, was considered mission enabling due to a reduction of over 2000 m/s in mission AV. Aerocapture will be targeted to produce a 250 km x 1400 km capture orbit with an inclination of 45 degrees. Current analysis indicates that achieving this goal will require approximately six minutes of flight deep in the atmosphere with a targeted periapsis of approach of about 43 km. After factoring into account the penalty for carrying a heat shield to survive aerocapture, the net savings compared to a propulsive orbital insertion amounts to several hundred kilograms.

Lee, Wayne J.↗

An overview of reference user services during the ATDRSS (Advanced Tracking and Data Relay Satellite System) era

The Tracking and Data Relay Satellite System (TDRSS) is an integral part of the overall NASA Space Network (SN) that will continue to evolve into the 1990's. Projections for the first decade of the 21st century indicate the need for an SN evolution that must accommodate growth int he LEO user population and must further support the introduction of new/improved user services. A central ingredient of this evolution is an Advanced TDRSS (ATDRSS) follow-on to the current TDRSS that must initiate operations by the late 1990's in a manner that permits an orderly transition from the TDRSS to the ATDRSS era. An SN/ATDRSS architectural and operational concept that will satisfy the above goals is being developed. To this date, an SN/ATDRSS baseline concept was established that provides users with an end-to-end data transport (ENDAT) service. An expanded description of the baseline ENDAT concept, from the user perspective, is provided with special emphasis on the TDRSS/ATDRSS evolution. A high-level description of the end-to-end system that identifies the role of ATDRSS is presented; also included is a description of the baseline ATDRSS architecture and its relationship with the TDRSS 1996 baseline. Other key features of the ENDAT service are then expanded upon, including the multiple grades of service, and the RF telecommunications/tracking services to be available. The ATDRSS service options are described.

Weinberg, Aaron↗

Overview of NASA GRC Stirling Technology Development

The Stirling Radioisotope Generator (SRG) is currently being developed by Lockheed Martin Astronautics (LMA) under contract to the Depar1ment of Energy (DOE). The generator will be a high efficiency electric power source for NASA Space Science missions with the capability to operate in the vacuum of deep space or in an atmosphere such as on the surface of Mars. High system efficiency is obtained through the use of free-piston Stirling power conversion technology. Power output of the generator will be greater than 100 watts at the beginning of life with the decline in power being largely due to the decay of the plutonium heat source. In suppOl1 of the DOE SRG project, the NASA Glenn Research Center (GRC) has established a near-term technology effort to provide some of the critical data to ensure a successful transition to flight for what will be the first dynamic power system used in space. Initially, a limited number of technical areas were selected for the GRC effort, however this is now being expanded to more thoroughly cover a range of technical issues. The tasks include in-house testing of Stirling convertors and controllers, materials evaluation and heater head life assessment, structural dynamics, electromagnetic interference, organics evaluation, and reliability analysis. Most of these high-level tasks have several subtasks within. There is also an advanced technology effort that is complementary near-term technology effort. Many of the tests make use of the 55-We Technology Demonstration Convel10r (TDC). There have been multiple controller tests to support the LMA flight controller design effort. Preparation is continuing for a thermal/vacuum system demonstration. A pair of flight prototype TDC's have recently been placed on an extended test with unattended, continuous operation. Heater head life assessment efforts continue, with the material data being refined and the analysis moving toward the system perspective. Long-term magnet aging tests are continuing to characterize any possible aging in the strength or demagnetization resistance of the permanent magnets used in the linear alternator. In a parallel effort, higher performance magnets are also being evaluated. A reliability effort is being initiated that will help to guide the development activities with an increased focus on the necessary components and subsystems. Some other disciplines that are active in the GRC technology effort include structural dynamics, linear alternator analysis, EMI/EMC, controls, and mechanical design evaluation. This paper will provide an overview of some of the GRC technical efforts, including the current status, and a description of future efforts.

Schreiber, Jeffrey↗

Optical and digital pattern recognition; Proceedings of the Meeting, Los Angeles, CA, Jan. 13-15, 1987

The papers presented in this volume provide an overview of current research in both optical and digital pattern recognition, with a theme of identifying overlapping research problems and methodologies. Topics discussed include image analysis and low-level vision, optical system design, object analysis and recognition, real-time hybrid architectures and algorithms, high-level image understanding, and optical matched filter design. Papers are presented on synthetic estimation filters for a control system; white-light correlator character recognition; optical AI architectures for intelligent sensors; interpreting aerial photographs by segmentation and search; and optical information processing using a new photopolymer.

Liu, Hua-Kuang↗

A summary of image segmentation techniques

Machine vision systems are often considered to be composed of two subsystems: low-level vision and high-level vision. Low level vision consists primarily of image processing operations performed on the input image to produce another image with more favorable characteristics. These operations may yield images with reduced noise or cause certain features of the image to be emphasized (such as edges). High-level vision includes object recognition and, at the highest level, scene interpretation. The bridge between these two subsystems is the segmentation system. Through segmentation, the enhanced input image is mapped into a description involving regions with common features which can be used by the higher level vision tasks. There is no theory on image segmentation. Instead, image segmentation techniques are basically ad hoc and differ mostly in the way they emphasize one or more of the desired properties of an ideal segmenter and in the way they balance and compromise one desired property against another. These techniques can be categorized in a number of different groups including local vs. global, parallel vs. sequential, contextual vs. noncontextual, interactive vs. automatic. In this paper, we categorize the schemes into three main groups: pixel-based, edge-based, and region-based. Pixel-based segmentation schemes classify pixels based solely on their gray levels. Edge-based schemes first detect local discontinuities (edges) and then use that information to separate the image into regions. Finally, region-based schemes start with a seed pixel (or group of pixels) and then grow or split the seed until the original image is composed of only homogeneous regions. Because there are a number of survey papers available, we will not discuss all segmentation schemes. Rather than a survey, we take the approach of a detailed overview. We focus only on the more common approaches in order to give the reader a flavor for the variety of techniques available yet present enough details to facilitate implementation and experimentation.

Spirkovska, Lilly↗

Overview of Intelligent Systems and Operations Development

To achieve NASA's ambitious mission objectives for the future, aircraft and spacecraft will need intelligence to take the correct action in a variety of circumstances. Vehicle intelligence can be defined as the ability to "do the right thing" when faced with a complex decision-making situation. It will be necessary to implement integrated autonomous operations and low-level adaptive flight control technologies to direct actions that enhance the safety and success of complex missions despite component failures, degraded performance, operator errors, and environment uncertainty. This paper will describe the array of technologies required to meet these complex objectives. This includes the integration of high-level reasoning and autonomous capabilities with multiple subsystem controllers for robust performance. Future intelligent systems will use models of the system, its environment, and other intelligent agents with which it interacts. They will also require planners, reasoning engines, and adaptive controllers that can recommend or execute commands enabling the system to respond intelligently. The presentation will also address the development of highly dependable software, which is a key component to ensure the reliability of intelligent systems.

Pallix, Joan↗

Design Methods and Practices for Fault Prevention and Management in Spacecraft

Integrated Systems Health Management (ISHM) is intended to become a critical capability for all space, lunar and planetary exploration vehicles and systems at NASA. Monitoring and managing the health state of diverse components, subsystems, and systems is a difficult task that will become more challenging when implemented for long-term, evolving deployments. A key technical challenge will be to ensure that the ISHM technologies are reliable, effective, and low cost, resulting in turn in safe, reliable, and affordable missions. To ensure safety and reliability, ISHM functionality, decisions and knowledge have to be incorporated into the product lifecycle as early as possible, and ISHM must be considered as an essential element of models developed and used in various stages during system design. During early stage design, many decisions and tasks are still open, including sensor and measurement point selection, modeling and model-checking, diagnosis, signature and data fusion schemes, presenting the best opportunity to catch and prevent potential failures and anomalies in a cost-effective way. Using appropriate formal methods during early design, the design teams can systematically explore risks without committing to design decisions too early. However, the nature of ISHM knowledge and data is detailed, relying on high-fidelity, detailed models, whereas the earlier stages of the product lifecycle utilize low-fidelity, high-level models of systems and their functionality. We currently lack the tools and processes necessary for integrating ISHM into the vehicle system/subsystem design. As a result, most existing ISHM-like technologies are retrofits that were done after the system design was completed. It is very expensive, and sometimes futile, to retrofit a system health management capability into existing systems. Last-minute retrofits result in unreliable systems, ineffective solutions, and excessive costs (e.g., Space Shuttle TPS monitoring which was considered only after 110 flights and the Columbia disaster). High false alarm or false negative rates due to substandard implementations hurt the credibility of the ISHM discipline. This paper presents an overview of the current state of ISHM design,and a review of formal design methods to make recommendations about possible approaches to enable the ISHM capabilities to be designed-in at the system-level, from the very beginning of the vehicle design process.

Tumer, Irem Y.↗

An Overview of Starfish: A Table-Centric Tool for Interactive Synthesis

Engineering is an interactive process that requires intelligent interaction at many levels. My thesis [1] advances an engineering discipline for high-level synthesis and architectural decomposition that integrates perspicuous representation, designer interaction, and mathematical rigor. Starfish, the software prototype for the design method, implements a table-centric transformation system for reorganizing control-dominated system expressions into high-level architectures. Based on the digital design derivation (DDD) system a designer-guided synthesis technique that applies correctness preserving transformations to synchronous data flow specifications expressed as co- recursive stream equations Starfish enhances user interaction and extends the reachable design space by incorporating four innovations: behavior tables, serialization tables, data refinement, and operator retiming. Behavior tables express systems of co-recursive stream equations as a table of guarded signal updates. Developers and users of the DDD system used manually constructed behavior tables to help them decide which transformations to apply and how to specify them. These design exercises produced several formally constructed hardware implementations: the FM9001 microprocessor, an SECD machine for evaluating LISP, and the SchemEngine, garbage collected machine for interpreting a byte-code representation of compiled Scheme programs. Bose and Tuna, two of DDD s developers, have subsequently commercialized the design derivation methodology at Derivation Systems, Inc. (DSI). DSI has formally derived and validated PCI bus interfaces and a Java byte-code processor; they further executed a contract to prototype SPIDER-NASA's ultra-reliable communications bus. To date, most derivations from DDD and DRS have targeted hardware due to its synchronous design paradigm. However, Starfish expressions are independent of the synchronization mechanism; there is no commitment to hardware or globally broadcast clocks. Though software back-ends for design derivation are limited to the DDD stream-interpreter, targeting synchronous or real-time software is not substantively different from targeting hardware.

Tsow, Alex↗

Lunar Exploration Architecture Level Key Drivers and Sensitivities

Strategic level analysis of the integrated behavior of lunar transportation and lunar surface systems architecture options is performed to assess the benefit, viability, affordability, and robustness of system design choices. This analysis employs both deterministic and probabilistic modeling techniques so that the extent of potential future uncertainties associated with each option are properly characterized. The results of these analyses are summarized in a predefined set of high-level Figures of Merit (FOMs) so as to provide senior NASA Constellation Program (CxP) and Exploration Systems Mission Directorate (ESMD) management with pertinent information to better inform strategic level decision making. The strategic level exploration architecture model is designed to perform analysis at as high a level as possible but still capture those details that have major impacts on system performance. The strategic analysis methodology focuses on integrated performance, affordability, and risk analysis, and captures the linkages and feedbacks between these three areas. Each of these results leads into the determination of the high-level FOMs. This strategic level analysis methodology has been previously applied to Space Shuttle and International Space Station assessments and is now being applied to the development of the Constellation Program point-of-departure lunar architecture. This paper provides an overview of the strategic analysis methodology and the lunar exploration architecture analyses to date. In studying these analysis results, the strategic analysis team has identified and characterized key drivers affecting the integrated architecture behavior. These key drivers include inclusion of a cargo lander, mission rate, mission location, fixed-versus- variable costs/return on investment, and the requirement for probabilistic analysis. Results of sensitivity analysis performed on lunar exploration architecture scenarios are also presented.

Goodliff, Kandyce↗