Search NASA⌕ Search

SEARCH · Search NASA

Results for “Integral Experiment”

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 163 records · Page 9
All sourcesNASA NTRSDOE OSTI
NASA NTRS1993

Space Applications Industrial Laser System (SAILS)

A program is underway to develop a YAG laser based materials processing workstation to fly in the cargo bay of the Space Shuttle. This workstation, called Space Applications Industrial Laser System (SAILS), will be capable of cutting and welding steel, aluminum, and Inconel alloys of the type planned for use in constructing the Space Station Freedom. As well as demonstrating the ability of a YAG laser to perform remote (fiber-optic delivered) repair and fabrication operations in space, fundamental data will be collected on these interactions for comparison with terrestrial data and models. The flight system, scheduled to fly in 1996, will be constructed as three modules using standard Get-Away-Special (GAS) canisters. The first module holds the laser head and cooling system, while the second contains a high peak power electrical supply. The third module houses the materials processing workstation and the command and data acquisition subsystems. The laser head and workstation cansisters are linked by a fiber-optic cable to transmit the laser light. The team assembled to carry out this project includes Lumonics Industrial Products (laser), Tennessee Technological University (structural analysis and fabrication), Auburn University Center for Space Power (electrical engineering), University of Waterloo (low-g laser process consulting), and CSTAR/UTSI (data acquisition, control, software, integration, experiment design). This report describes the SAILS program and highlights recent activities undertaken at CSTAR.

Mccay, T. D.↗
NASA NTRS1997

Case Study of an Object-Oriented System: EOSDIS

Mission to Planet Earth (MTPE) is a long-term NASA research mission to study the processes leading to global climate change. The Earth Observing System (EOS) is a NASA campaign of satellite observatories that are a major component of MTPE. The EOS Data and Information System (EOSDIS) is another component of MTPE that will provide the Earth science community with easy, affordable, and reliable access to Earth science data. EOSDIS is a distributed system, with major facilities at six Distributed Active Archive Centers (DAACS) located throughout the United States. The EOSDIS software architecture is being designed to receive, process, and archive several terabytes of science data on a daily basis. Thousands of science users and perhaps several hundred thousands of non-science users are expected to access the system. While there are many segments in EOSDIS (e.g., flight operations, network) this case study discusses the development of the science data processing segment (SDPS). We briefly review the architecture of the system, the goals of the SDPS, and the development progress to date. This study highlights key software development challenges, experiences integrating COTS, and the difficulties of managing a complex system development effort.

Behnke, Jeanne↗
NASA NTRS1999

Design of the NASA Robonaut Hand

The design of a highly anthropomorphic human scale robot hand for space based operations is described. This five finger hand combined with its integrated wrist and forearm has fourteen independent degrees of freedom. The device approximates very well the kinematics and required strength of an astronaut's hand when operating through a pressurized space suit glove. The mechanisms used to meet these requirements are explained in detail along with the design philosophy behind them. Integration experiences reveal the challenges associated with obtaining the required capabilities within the desired size. The initial finger control strategy is presented along with examples of obtainable grasps.

Lovchik, Chris S.↗
NASA NTRS2002

Activity Tracking for Pilot Error Detection from Flight Data

This report presents an application of activity tracking for pilot error detection from flight data, and describes issues surrounding such an application. It first describes the Crew Activity Tracking System (CATS), in-flight data collected from the NASA Langley Boeing 757 Airborne Research Integrated Experiment System aircraft, and a model of B757 flight crew activities. It then presents an example of CATS detecting actual in-flight crew errors.

Callantine, Todd J.↗
NASA NTRS2002

ARIES: NASA Langley's Airborne Research Facility

In 1994, the NASA Langley Research Center (LaRC) acquired a B-757-200 aircraft to replace the aging B-737 Transport Systems Research Vehicle (TSRV). The TSRV was a modified B-737-100, which served as a trailblazer in the development of glass cockpit technologies and other innovative aeronautical concepts. The mission for the B-757 is to continue the three-decade tradition of civil transport technology research begun by the TSRV. Since its arrival at Langley, this standard 757 aircraft has undergone extensive modifications to transform it into an aeronautical research "flying laboratory". With this transformation, the aircraft, which has been designated Airborne Research Integrated Experiments System (ARIES), has become a unique national asset which will continue to benefit the U.S. aviation industry and commercial airline customers for many generations to come. This paper will discuss the evolution of the modifications, detail the current capabilities of the research systems, and provide an overview of the research contributions already achieved.

Wusk, Michael S.↗
NASA NTRS2003

Initial SVS Integrated Technology Evaluation Flight Test Requirements and Hardware Architecture

This document presents the flight test requirements for the Initial Synthetic Vision Systems Integrated Technology Evaluation flight Test to be flown aboard NASA Langley's ARIES aircraft and the final hardware architecture implemented to meet these requirements. Part I of this document contains the hardware, software, simulator, and flight operations requirements for this light test as they were defined in August 2002. The contents of this section are the actual requirements document that was signed for this flight test. Part II of this document contains information pertaining to the hardware architecture that was realized to meet these requirements as presented to and approved by a Critical Design Review Panel prior to installation on the B-757 Airborne Research Integrated Experiments Systems (ARIES) airplane. This information includes a description of the equipment, block diagrams of the architecture, layouts of the workstations, and pictures of the actual installations.

Harrison, Stella V.↗
NASA NTRS1998

Overview of the Neurolab Spacelab mission

Neurolab is a NASA Spacelab mission with multinational cooperative participation that is dedicated to research on the nervous system. The nervous systems of all animal species have evolved in a one-g environment and are functionally influenced by the presence of gravity. The absence of gravity presents a unique opportunity to gain new insights into basic neurologic functions as well as an enhanced understanding of physiological and behavioral responses mediated by the nervous system. The primary goal of Neurolab is to expand our understanding of how the nervous system develops, functions in, and adapts to microgravity space flight. Twenty-six peer reviewed investigations using human and nonhuman test subjects were assigned to one of eight science discipline teams. Individual and integrated experiments within these teams have been designed to collect a wide range of physiological and behavior data in flight as well as pre- and postflight. Information from these investigations will be applicable to enhancing the well being and performance of future long duration space travelers, will contribute to our understanding of normal and pathological functioning of the nervous system, and may be applied by the medical community to enhance the health of humans on Earth.

manned↗
NASA NTRS2004

NASA-Langley Research Center's Aircraft Condition Analysis and Management System Implementation

This document describes the hardware implementation design and architecture of Aeronautical Radio Incorporated (ARINC)'s Aircraft Condition Analysis and Management System (ACAMS), which was developed at NASA-Langley Research Center (LaRC) for use in its Airborne Research Integrated Experiments System (ARIES) Laboratory. This activity is part of NASA's Aviation Safety Program (AvSP), the Single Aircraft Accident Prevention (SAAP) project to develop safety-enabling technologies for aircraft and airborne systems. The fundamental intent of these technologies is to allow timely intervention or remediation to improve unsafe conditions before they become life threatening.

Frye, Mark W.↗
NASA NTRS2006

Leveraging Existing Mission Tools in a Re-Usable, Component-Based Software Environment

Emerging methods in component-based software development offer significant advantages but may seem incompatible with existing mission operations applications. In this paper we relate our positive experiences integrating existing mission applications into component-based tools we are delivering to three missions. In most operations environments, a number of software applications have been integrated together to form the mission operations software. In contrast, with component-based software development chunks of related functionality and data structures, referred to as components, can be individually delivered, integrated and re-used. With the advent of powerful tools for managing component-based development, complex software systems can potentially see significant benefits in ease of integration, testability and reusability from these techniques. These benefits motivate us to ask how component-based development techniques can be relevant in a mission operations environment, where there is significant investment in software tools that are not component-based and may not be written in languages for which component-based tools even exist. Trusted and complex software tools for sequencing, validation, navigation, and other vital functions cannot simply be re-written or abandoned in order to gain the advantages offered by emerging component-based software techniques. Thus some middle ground must be found. We have faced exactly this issue, and have found several solutions. Ensemble is an open platform for development, integration, and deployment of mission operations software that we are developing. Ensemble itself is an extension of an open source, component-based software development platform called Eclipse. Due to the advantages of component-based development, we have been able to vary rapidly develop mission operations tools for three surface missions by mixing and matching from a common set of mission operation components. We have also had to determine how to integrate existing mission applications for sequence development, sequence validation, and high level activity planning, and other functions into a component-based environment. For each of these, we used a somewhat different technique based upon the structure and usage of the existing application.

Greene, Kevin↗
NASA NTRS2006

Zero to Integration in Eight Months, the Dawn Ground Data System Engineering Challange

The Dawn Project has presented the Ground Data System (GDS) with technical challenges driven by cost and schedule constraints commonly associated with National Aeronautics and Space Administration (NASA) Discovery Projects. The Dawn mission consists of a new and exciting Deep Space partnership among: the Jet Propulsion Laboratory (JPL), responsible for project management and flight operations; Orbital Sciences Corporation (OSC), spacecraft builder and responsible for flight system test and integration; and the University of California, at Los Angeles (UCLA), responsible for science planning and operations. As a cost-capped mission, one of Dawn s implementation strategies is to leverage from both flight and ground heritage. OSC's ground data system is used for flight system test and integration as part of the flight heritage strategy. Mission operations, however, are to be conducted with JPL s ground system. The system engineering challenge of dealing with two heterogeneous ground systems emerged immediately. During the first technical interchange meeting between the JPL s GDS Team and OSC's Flight Software Team, August 2003, the need to integrate the ground system with the flight software was brought to the table. This need was driven by the project s commitment to enable instrument engineering model integration in a spacecraft simulator environment, for both demonstration and risk mitigation purposes, by April 2004. This paper will describe the system engineering approach that was undertaken by JPL's GDS Team in order to meet the technical challenge within a non-negotiable eight-month schedule. Key to the success was adherence to an overall systems engineering process and fundamental systems engineering practices: decomposition of the project request into manageable requirements; definition of a structured yet flexible development process; integration of multiple ground disciplines and experts into a focused team effort; in-process risk management; and aggregation of the intermediate products to an integrated final product. In addition, this paper will highlight the role of lessons learned from the integration experience. The lessons learned from an early GDS deployment have served as the foundation for the design and implementation of the Dawn Ground Data System.

systems engineering↗
NASA NTRS2006

Zero to Integration in Eight Months, the Dawn Ground Data System Engineering Challenge

The Dawn Project has presented the Ground Data System (GDS) with technical challenges driven by cost and schedule constraints commonly associated with National Aeronautics and Space Administration (NASA) Discovery Projects. The Dawn mission consists of a new and exciting Deep Space partnership among: the Jet Propulsion Laboratory (JPL), manages the project and is responsible for flight operation; Orbital Sciences Corporation (OSC), is the spacecraft builder and is responsible for flight system test and integration; and the University of California, at Los Angeles (UCLA), is responsible for science planning and operations. As a cost-capped mission, one of Dawn's implementation strategies is to leverage from both flight and ground heritage. OSC's ground data system is used for flight system test and integration as part of the flight heritage strategy. Mission operations, however, are to be conducted with JPL's ground system. The system engineering challenge of dealing with two heterogeneous ground systems emerged immediately. During the first technical interchange meeting between the JPL's GDS Team and OSC's Flight Software Team, August 2003, the need to integrate the ground system with the flight software was brought to the table. This need was driven by the project's commitment to enable instrument engineering model integration in a spacecraft simulator environment, for both demonstration and risk mitigation purposes, by April 2004. This paper will describe the system engineering approach that was undertaken by JPL's GDS Team in order to meet the technical challenge within a non-negotiable eight-month schedule. Key to the success was adherence to fundamental systems engineering practices: decomposition of the project request into manageable requirements; integration of multiple ground disciplines and experts into a focused team effort; definition of a structured yet flexible development process; definition of an in-process risk reduction plan; and aggregation of the intermediate products to an integrated final product. In addition, this paper will highlight the role of lessons learned from the integration experience. The lessons learned from an early GDS deployment have served as the foundation for the design and implementation of the Dawn Ground Data System.

Ground Data System (GDS)↗
NASA NTRS2010

Inlet Flow Control and Prediction Technologies for Embedded Propulsion Systems

Fail-safe inlet flow control may enable high-speed cruise efficiency, low noise signature, and reduced fuel-burn goals for hybrid wing-body aircraft. The objectives of this program are to develop flow control and prediction methodologies for boundary-layer ingesting (BLI) inlets used in these aircraft. This report covers the second of a three year program. The approach integrates experiments and numerical simulations. Both passive and active flow-control devices were tested in a small-scale wind tunnel. Hybrid actuation approaches, combining a passive microvane and active synthetic jet, were tested in various geometric arrangements. Detailed flow measurements were taken to provide insight into the flow physics. Results of the numerical simulations were correlated against experimental data. The sensitivity of results to grid resolution and turbulence models was examined. Aerodynamic benefits from microvanes and microramps were assessed when installed in an offset BLI inlet. Benefits were quantified in terms of recovery and distortion changes. Microvanes were more effective than microramps at improving recovery and distortion.

McMillan, Michelle L.↗
NASA NTRSDate not supplied

LIRA: Probing the Lunar Surface for Resources.

The thermal, compositional and electrical properties of the lunar regolith, such as the triboelectric properties of lunar dust, the volatile content and the thermophysical properties of the polar regolith are essential to understand from a scientific perspective as well as for resource extraction and hazard mitigation. Understanding these properties specifically requires in situ measurement, as these properties are inherent in the ambient environment. With the Lunar In situ Regolith Analyzer (LIRA) we will combine mature surface sensor technologies from previous spacecraft missions (TECP) with new sensors (ClO4- ) and battery capability to achieve a compact in situ analysis package. The surface instrument suite is adapted for lunar conditions from a sensor developed as part of the Microscopy, Electrochemistry, and Conductivity Analyzer (MECA) instrument on the 2007 Mars Phoenix mission, as well as supplemental sensors. • The Thermal and Electrical Conductivity Probe (TECP), flown on MECA/Phoenix, which measures heat capacity, thermal conductivity, electrical resistance, and electrical permittivity between needles inserted into the soil. The TECP also measured atmospheric humidity, a capability that will be retained to search for subsurface H2O ice. The Mars TECP weighed 100-gram and by definition was at TRL 9. The lunar version (LIRA) is TRL 4. • The Perchlorate (ClO4) sensor is based on the fluorescence property of perchlorate (Mg, Fe, Na). We added a light source to excite the perchlorate (ClO4) and a photo diode to collect the emission wavelength. A sun-shade over the photo diode blocks out the ambient light during day light hours. The unifying goal of LIRA is to deliver a complete, integrated experiment suite that investigates properties that must be measured in situ, and provides the capability to power the suite at night or in PSRs, as well as a means to simulate aspects of the diurnal transition by delivering an optical pulse to the surface with intensity comparable to sunlight. We describe the scientific context of LIRA, touching on the electrical state of the near-surface environment, the thermal properties of the undisturbed regolith, and the distribution, geochemistry, and mobility of water. We also address the exploration implications of the work, examining hazards and resources in the context of strategic knowledge gaps (SKGs).

Heather Smith↗
NASA NTRSDate not supplied

The Response of the Quasi-Biennial Oscillation to Increased CO and its Modulation by Composition Feedbacks

The Quasi-Biennial Oscillation (QBO) impacts the large-scale circulation by altering lower stratospheric meridional temperature gradients which alter the propagation of upward propagating planetary waves. Proposed teleconnections of the QBO include impacts on the stratospheric polar vortices, extratropical surface winter climate, and the Madden-Julian Oscillation. However, long-term projections of the QBO remain highly uncertain. While recent multi-model investigations (Richter et al. 2019, Butchart et al. 2020) show that the amplitude of the QBO weakens robustly among models, changes in QBO period and stability remain highly uncertain. Here we examine the QBO response to increased greenhouse gases using the NASA Goddard Institute for Space Studies Middle Atmosphere Model E2.2 (Rind et al., 2020; Orbe et al. 2020). Compared to lower vertical resolution versions of ModelE, E2.2 also has a higher model top (0.002 hPa) and employs additional interactive non-orographic gravity wave drag sources from convection and shear, which produce a sufficiently realistic QBO, thus rendering it suitable for use in climate change studies. Overall, we find that both the QBO period and amplitude decrease in response to increased CO , the former related to increased lower stratospheric momentum fluxes (associated with convection) and the latter associated partly with a stronger residual mean circulation. Experiments integrated using fully interactive chemistry also reveal that ozone feedbacks significantly impact the magnitude of the QBO amplitude response. Finally, integrations using fixed (pre-industrial) sea surface temperatures (SST) show that the QBO amplitude responds differently to rapid adjustments versus SST feedbacks, as compared to the QBO period.

Quasi-Biennial Oscillation↗
NASA NTRS1995

Microgravity Experiments Safety and Integration Requirements Document Tree

This report is a document tree of the safety and integration documents required to develop a space experiment. Pertinent document information for each of the top level (tier one) safety and integration documents, and their applicable and reference (tier two) documents has been identified. This information includes: document title, revision level, configuration management, electronic availability, listed applicable and reference documents, source for obtaining the document, and document owner. One of the main conclusions of this report is that no single document tree exists for all safety and integration documents, regardless of the Shuttle carrier. This document also identifies the need for a single point of contact for customers wishing to access documents. The data in this report serves as a valuable information source for the NASA Lewis Research Center Project Documentation Center, as well as for all developers of space experiments.

Hogan, Jean M.↗
NASA NTRS1975

Experience with integrally-cast compressor and turbine components for a small, low-cost, expendable-type turbojet engine

A discussion regarding experiences with integrally-cast compressor and turbine components during fabrication and testing of four engine assemblies of a small (29 cm (11-1/2 in.) maximum diameter) experimental turbojet engine design for an expendable application is presented. Various operations such as metal removal, welding, and re-shaping of these components are performed in preparation of full-scale engine tests. Engines with these components have been operated for a total of 157 hours at engine speeds as high as 38,000 rpm and at turbine inlet temperatures as high as 1256 K (1800 F).

Dengler, R. P.↗
NASA NTRS1993

Static Computer Memory Integrity Testing (SCMIT): An experiment flown on STS-40 as part of GAS payload G-616

This experiment investigated the integrity of static computer memory (floppy disk media) when exposed to the environment of low earth orbit. The experiment attempted to record soft-event upsets (bit-flips) in static computer memory. Typical conditions that exist in low earth orbit that may cause soft-event upsets include: cosmic rays, low level background radiation, charged fields, static charges, and the earth's magnetic field. Over the years several spacecraft have been affected by soft-event upsets (bit-flips), and these events have caused a loss of data or affected spacecraft guidance and control. This paper describes a commercial spin-off that is being developed from the experiment.

Hancock, Thomas↗
NASA NTRS1991

The integration of microgravity science experiments into shared or previously existing experiment facilities

The overall flow for integrating a sample into an experiment facility, specifically materials science is discussed using the Crystal Growth Furnace as an example. A typical preflight timeline for an experiment is discussed, including identification of all documentation and hardware deliveries. Each of the items presented is discussed in detail including the experiment requirements document, the announcement opportunity response, the experiment specific equipment, safety reviews, mission plan, and hardware integration plan. These items are addressed both individualy and with respect to their relevance to the program as a whole.

Baer-Peckham, M. S.↗