Search NASA⌕ Search

SEARCH · Search NASA

Results for “Bill of materials”

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.

147 records · Page 9
All sourcesNASA NTRSDOE OSTI
NASA NTRS1995

MPI-IO: A Parallel File I/O Interface for MPI Version 0.3

Thanks to MPI [9], writing portable message passing parallel programs is almost a reality. One of the remaining problems is file I/0. Although parallel file systems support similar interfaces, the lack of a standard makes developing a truly portable program impossible. Further, the closest thing to a standard, the UNIX file interface, is ill-suited to parallel computing. Working together, IBM Research and NASA Ames have drafted MPI-I0, a proposal to address the portable parallel I/0 problem. In a nutshell, this proposal is based on the idea that I/0 can be modeled as message passing: writing to a file is like sending a message, and reading from a file is like receiving a message. MPI-IO intends to leverage the relatively wide acceptance of the MPI interface in order to create a similar I/0 interface. The above approach can be materialized in different ways. The current proposal represents the result of extensive discussions (and arguments), but is by no means finished. Many changes can be expected as additional participants join the effort to define an interface for portable I/0. This document is organized as follows. The remainder of this section includes a discussion of some issues that have shaped the style of the interface. Section 2 presents an overview of MPI-IO as it is currently defined. It specifies what the interface currently supports and states what would need to be added to the current proposal to make the interface more complete and robust. The next seven sections contain the interface definition itself. Section 3 presents definitions and conventions. Section 4 contains functions for file control, most notably open. Section 5 includes functions for independent I/O, both blocking and nonblocking. Section 6 includes functions for collective I/O, both blocking and nonblocking. Section 7 presents functions to support system-maintained file pointers, and shared file pointers. Section 8 presents constructors that can be used to define useful filetypes (the role of filetypes is explained in Section 2 below). Section 9 presents how the error handling mechanism of MPI is supported by the MPI-IO interface. All this is followed by a set of appendices, which contain information about issues that have not been totally resolved yet, and about design considerations. The reader can find there the motivation behind some of our design choices. More information on this would definitely be welcome and will be included in a further release of this document. The first appendix contains a description of MPI-I0's 'hints' structure which is used when opening a file. Appendix B is a discussion of various issues in the support for file pointers. Appendix C explains what we mean in talking about atomic access. Appendix D provides detailed examples of filetype constructors, and Appendix E contains a collection of arguments for and against various design decisions.

Corbett, Peter↗
NASA NTRS2009

Multimodal Friction Ignition Tester

The multimodal friction ignition tester (MFIT) is a testbed for experiments on the thermal and mechanical effects of friction on material specimens in pressurized, oxygen-rich atmospheres. In simplest terms, a test involves recording sensory data while rubbing two specimens against each other at a controlled normal force, with either a random stroke or a sinusoidal stroke having controlled amplitude and frequency. The term multimodal in the full name of the apparatus refers to a capability for imposing any combination of widely ranging values of the atmospheric pressure, atmospheric oxygen content, stroke length, stroke frequency, and normal force. The MFIT was designed especially for studying the tendency toward heating and combustion of nonmetallic composite materials and the fretting of metals subjected to dynamic (vibrational) friction forces in the presence of liquid oxygen or pressurized gaseous oxygen test conditions approximating conditions expected to be encountered in proposed composite material oxygen tanks aboard aircraft and spacecraft in flight. The MFIT includes a stainless-steel pressure vessel capable of retaining the required test atmosphere. Mounted atop the vessel is a pneumatic cylinder containing a piston for exerting the specified normal force between the two specimens. Through a shaft seal, the piston shaft extends downward into the vessel. One of the specimens is mounted on a block, denoted the pressure block, at the lower end of the piston shaft. This specimen is pressed down against the other specimen, which is mounted in a recess in another block, denoted the slip block, that can be moved horizontally but not vertically. The slip block is driven in reciprocating horizontal motion by an electrodynamic vibration exciter outside the pressure vessel. The armature of the electrodynamic exciter is connected to the slip block via a horizontal shaft that extends into the pressure vessel via a second shaft seal. The reciprocating horizontal motion can be chosen to be random with a flat spectrum over the frequency range of 10 Hz to 1 kHz, or to be sinusoidal at any peak-to-peak amplitude up to 0.8 in. (.2 cm) and fixed or varying frequency up to 1 kHz. The temperatures of the specimen and of the vessel are measured by thermocouples. A digital video camera mounted outside the pressure vessel is aimed into the vessel through a sapphire window, with its focus fixed on the interface between the two specimens. A position transducer monitors the displacement of the pneumatic-cylinder shaft. The pressure in the vessel is also monitored. During a test, the output of the video camera, the temperatures, and the pneumatic-shaft displacement are monitored and recorded. The test is continued for a predetermined amount of time (typically, 10 minutes) or until either (1) the output of the position transducer shows a sudden change indicative of degradation of either or both specimens, (2) ignition or another significant reaction is observed, or (3) pressure in the vessel increases beyond a pre-set level that triggers an automatic shutdown.

Davis, Eddie↗
NASA NTRS1995

Continuation: The EOSDIS testbed data system

The continuation of the EOSDIS testbed ('Testbed') has materialized from a multi-task system to a fully functional stand-alone data archive distribution center that once was only X-Windows driven to a system that is accessible by all types of users and computers via the World Wide Web. Throughout the past months, the Testbed has evolved into a completely new system. The current system is now accessible through Netscape, Mosaic, and all other servers that can contact the World Wide Web. On October 1, 1995 we will open to the public and we expect that the statistics of the type of user, where they are located, and what they are looking for will drastically change. What is the most important change in the Testbed has been the Web interface. This interface will allow more users access to the system and walk them through the data types with more ease than before. All of the callbacks are written in such a way that icons can be used to easily move around in the programs interface. The homepage offers the user the opportunity to go and get more information about each satellite data type and also information on free programs. These programs are grouped into categories for types of computers that the programs are compiled for, along with information on how to FTP the programs back to the end users computer. The heart of the Testbed is still the acquisition of satellite data. From the Testbed homepage, the user selects the 'access to data system' icon, which will take them to the world map and allow them to select an area that they would like coverage on by simply clicking that area of the map. This creates a new map where other similar choices can be made to get the latitude and longitude of the region the satellite data will cover. Once a selection has been made the search parameters page will appear to be filled out. Afterwards, the browse image will be called for once the search is completed and the images for viewing can be selected. There are several other option pages, but once an order has been selected the Testbed will bring up the order list page and the user will then be able to place their order. After the order has been completed, the Testbed will mail the user to notify them of the completed order and how the images can be picked up.

Emery, Bill↗