Search NASA⌕ Search

SEARCH · Search NASA

Results for “components”

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 37 records · Page 2
All sourcesNASA NTRSDOE OSTI
NASA NTRS1947

Analysis of Performance of Jet Engine from Characteristics of Components I : Aerodynamic and Matching Characteristics of Turbine Component Determined with Cold Air

The performance of the turbine component of an NACA research jet engine was investigated with cold air. The interaction and the matching of the turbine with the NACA eight-stage compressor were computed with the combination considered as a jet engine. The over-all performance of the engine was then determined. The internal aerodynamics were studied to the extent of investigating the performance of the first stator ring and its influence on the turbine performance. For this ring, the stream-filament method for computing velocity distribution permitted efficient sections to be designed, but the design condition of free-vortex flow with uniform axial velocities was not obtained.

Goldstein, Arthur W↗
NASA NTRS2009

Ceramic material suitable for repair of a space vehicle component in a microgravity and vacuum environment, method of making same, and method of repairing a space vehicle component

A precursor of a ceramic adhesive suitable for use in a vacuum, thermal, and microgravity environment. The precursor of the ceramic adhesive includes a silicon-based, preceramic polymer and at least one ceramic powder selected from the group consisting of aluminum oxide, aluminum nitride, boron carbide, boron oxide, boron nitride, hafnium boride, hafnium carbide, hafnium oxide, lithium aluminate, molybdenum silicide, niobium carbide, niobium nitride, silicon boride, silicon carbide, silicon oxide, silicon nitride, tin oxide, tantalum boride, tantalum carbide, tantalum oxide, tantalum nitride, titanium boride, titanium carbide, titanium oxide, titanium nitride, yttrium oxide, zirconium diboride, zirconium carbide, zirconium oxide, and zirconium silicate. Methods of forming the ceramic adhesive and of repairing a substrate in a vacuum and microgravity environment are also disclosed, as is a substrate repaired with the ceramic adhesive.

Riedell, James A.↗
NASA NTRSDate not supplied

Component Level Regression Testing in a Hierarchical Architecture

The Goddard Earth Observing System (GEOS) is an Earth system model consisting of a large suite of individual model components that can be coupled in a flexible manner to investigate a variety of Earth science issues. Specific GEOS model configurations are composed as a hierarchical collection of components based on the Earth System Modeling Framework (ESMF). Regression testing of GEOS is currently limited to (1) full system tests that are poor at isolating specific defects and (2) a suite of unit tests which have very limited coverage. As part of our approach to improve upon the current testing situation, we have prototyped the capability to perform regression tests on individual GEOS components by leveraging and extending existing checkpoint/restart capabilities. In our implementation, each ESMF component has 3 states: Import (what it needs to run), Export (which it needs to provide to other components), and Internal (the component state proper). By capturing, Import, Export and Internal states for a given component during a ull run of GEOS, a generic driver can then rerun the component offline and compare expected exports with those that have been saved. The hierarchical structure of GEOS introduces an interesting wrinkle when trying to test components that in turn drive interacting child components. To fully isolate a parent component, we use the approach of software mocks, in which the exports of children are also saved during the initial capture run of GEOS. Then when testing the parent component, the children components are replaced by a generic mock component that produces exports from the previously saved data and ensures that that all interdependencies among children components are satisfied.

Thomas Clune↗
NASA NTRSDate not supplied

Component Level Testing in a Hierarchical Architecture

The Goddard Earth Observing System (GEOS) is an Earth system model consisting of a large suite of individual model components that can be coupled in a flexible manner to investigate a variety of Earth science issues. Specific GEOS model configurations are composed as a hierarchical collection of components based on the Earth System Modeling Framework (ESMF). Regression testing of GEOS is currently limited to (1) full system tests that are poor at isolating specific defects and (2) a suite of unit tests which have very limited coverage. As part of our approach to improve upon the current testing situation, we have prototyped the capability to perform regression tests on individual GEOS components by leveraging and extending existing checkpoint/restart capabilities. In our implementation, each ESMF component has 3 states: Import (what it needs to run), Export (which it needs to provide to other components), and Internal (the component state proper). By capturing, Import, Export and Internal states for a given component during a ull run of GEOS, a generic driver can then rerun the component offline and compare expected exports with those that have been saved. The hierarchical structure of GEOS introduces an interesting wrinkle when trying to test components that in turn drive interacting child components. To fully isolate a parent component, we use the approach of software mocks, in which the exports of children are also saved during the initial capture run of GEOS. Then when testing the parent component, the children components are replaced by a generic mock component that produces exports from the previously saved data and ensures that that all interdependencies among children components are satisfied.

Tom Clune↗
NASA NTRS2001

Jet Stability and the Generation of Superluminal and Stationary Components

We present a numerical simulation of the response of an expanding relativistic jet to the ejection of a superluminal component. The simulation has been performed with a relativistic time-dependent hydrodynamical code from which simulated radio maps are computed by integrating the transfer equations for synchrotron radiation. The interaction of the superluminal component with the underlying jet results in the formation of multiple conical shocks behind the main perturbation. These trailing components can be easily distinguished because they appear to be released from the primary superluminal component instead of being ejected from the core. Their oblique nature should also result in distinct polarization properties. Those appearing closer to the core show small apparent motions and a very slow secular decrease in brightness and could be identified as stationary components. Those appearing farther downstream are weaker and can reach superluminal apparent motions. The existence of these trailing components indicates that not all observed components necessarily represent major perturbations at the jet inlet; rather, multiple emission components can be generated by a single disturbance in the jet. While the superluminal component associated with the primary perturbation exhibits a rather stable pattern speed, trailing components have velocities that increase with distance from the core but move at less than the jet speed. The trailing components exhibit motion and structure consistent with the triggering of pinch modes by the superluminal component. The increase in velocity of the trailing components is an indirect consequence of the acceleration of the expanding fluid, which is assumed to be relativistically hot; if observed, such accelerations would therefore favor an electron-positron (as opposed to proton rest mass) dominated jet.

Agudo, Ivan↗
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 NTRS2002

Method for distributed object communications based on dynamically acquired and assembled software components

A method for acquiring and assembling software components at execution time into a client program, where the components may be acquired from remote networked servers is disclosed. The acquired components are assembled according to knowledge represented within one or more acquired mediating components. A mediating component implements knowledge of an object model. A mediating component uses its implemented object model knowledge, acquired component class information and polymorphism to assemble components into an interacting program at execution time. The interactions or abstract relationships between components in the object model may be implemented by the mediating component as direct invocations or indirect events or software bus exchanges. The acquired components may establish communications with remote servers. The acquired components may also present a user interface representing data to be exchanged with the remote servers. The mediating components may be assembled into layers, allowing arbitrarily complex programs to be constructed at execution time.

Sundermier, Amy↗
DOE OSTI2024

Riveted assemblies and methods for riveting components

Riveted assemblies are provided that can include: a first component having opposing first and second sidewalls; a second component having opposing third and fourth sidewalls, wherein the second sidewall of the first component abuts the third sidewall of the second component to bind and form an affixing interface comprising the second and third sidewall between the first component to the second component; and a rivet extending between a head along a shank to an end, the rivet piercing the first sidewall with the end of the rivet being between the first and fourth sidewalls. Methods for affixing at least two components using a rivet are also provided. The methods can include: providing a first component having opposing first and second sidewalls; providing a second component having opposing third and fourth sidewalls; abutting the second sidewall of the first component to the third sidewall of the second component; providing a rivet extending between a head along a shank to an end; projecting the rivet through at least the first sidewall of the first component to form an affixing interface comprising the second and third sidewalls.

Joshi, Vineet V.↗
NASA NTRS1990

Evaluation of composite components on the Bell 206L and Sikorsky S-76 helicopters

Progress on two programs to evaluate structural composite components in flight service on Bell 206L and Sikorsky S-76 commercial helicopters is described. Forty ship sets of composite components that include the litter door, baggage door, forward fairing, and vertical fin have been installed on Bell Model 206L helicopters that are operating in widely different climates. Component installation started in 1981 and selected components were removed and tested at prescribed intervals over a ten year evaluation. Four horizontal stabilizers and eleven tail rotor spars that are production components on the S-76 helicopter were tested after prescribed periods of service to determine the effects of the operating environment on their performance. Concurrent with the flight evaluation, materials used to fabricate the components were exposed in ground racks and tested at specified intervals to determine the effects of outdoor environments. Results achieved from 123,000 hours of accumulated service on the Bell 206L components and 53,000 hours on the Sikorsky S-76 components are reported. Seventy-eight Bell 206L components were removed and tested statically. Results of seven years of ground exposure of materials used to fabricate the Bell 206L components are presented. Results of tests on four Sikorsky S-76 horizontal stabilizers and eleven tail rotor spars are also presented. Panels of material used to fabricate the Sikorsky S-76 components that were exposed for six years were tested and results are presented.

Baker, Donald J.↗