SEARCH · Engineering Papers
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.
Guidance is provided to the DELMAT user in the areas of purpose, use and limitations of DELMAT tapes and software. The DELMAT tape specifications is also provided. The ERB-7, ERB MAT and tape characteristics applicable to the DELMAT tapes are also summarized.
The operation of a physiological monitoring system (PMS) is described. Specifications were established for performance, design, interface, and test requirements. The PMS is a compact, microprocessor-based system, which can be worn in a pack on the body or may be mounted on a Spacelab rack or other appropriate structure. It consists of two modules, the Data Control Unit (DCU) and the Remote Control/Display Unit (RCDU). Its purpose is to collect and distribute data from physiological experiments in the Spacelab and in the Orbiter.
Modern jet engine design imposes extremely high loadings and temperatures on hot section components. A series of interdisciplinary modeling and analysis techniques which were specialized to address three specific components (combustor burner linings, hollow air-cooled turbine blades, and air-cooled turbine vanes) were developed and verified. These techniques will incorporate data as well as theoretical methods from many diverse areas, including cycle and performance analysis, heat transfer analysis, linear and nonlinear stress analysis, and mission analysis. Building on the proven techniques already available in these fields, the new methods developed will be integrated to predict temperature, deformation, stress, and strain histories throughout a complete flight mission.
The HP PASCAL source code contained in pages 6 through 104 was developed for the Mission Planning and Analysis Division (MPAD) and takes the place of detailed flow charts defining the specifications for a Utility Software Unit designed to support orbital flight simulators such as MANHANDLE and GREAS (General Research and Engineering Analysis Simulator). Besides providing basic input/output, mathematical, vector, matrix, quaternion, and statistical routines for such simulators, one of the primary functions of the Utility Software Unit is to isolate all system-dependent code in one well-defined compartment, thereby facilitating transportation of the simulations from one computer to another. Directives to the PASCAL compilers of the HP-9000 Series 200 PASCAL 3.0 operating system and the HP-9000 Series 500 HP-UX 5.0 operations systems are also provided.
The HP PASCAL source code was developed for the Mission Planning and Analysis Division (MPAD) of NASA/JSC, and takes the place of detailed flow charts defining the host computer software specifications for MANHANDLE, a digital/graphical simulator that can be used to analyze the dynamics of onorbit (zero-g) payload manhandling operations. Input and output data for representative test cases are contained.
The HP PASCAL source code defines the specifications for a Utility Software Unit (USU) designed to support orbital flight simulators such as MANHANDLE and GREAS (General Research and Engineering Analysis Simulator). Besides providing basic input/output, mathematical, matrix, quaternion, and statistical routines for such simulators, one of the primary functions of the USU is to isolate all system-dependent codes in one well-defined compartment, thereby facilitating transportation of the simulations from one computer to another. Directives are given for the PASCAL compilers of the HP-9000 Series 200 Pascal 3.0 and the HP-9000 Series 500 HP-UX 5.0 operating systems that produce a single file of relocatable code from four separate files of source code. Three of the source code files are common to both operating systems. The fourth source code file (utilspif.I) contains all of the system-dependent PASCAL code for the USU. A fifth file of source code written in C is required to interface utilspif.I with the HP-UX I/O package. The Pascal 3.0 compiler directives and the driver source code for a unit rest program and counterparts for the HP-UX 5.0 operating system are given. The major portion of the unit test program source code is common to both operating systems. Unit test results from the Pascal 3.0 operating system and results from the HP-UX operating system are given.
The requirements for performance, design, test, and qualification of a computer program identified as NICBES, Nickel Cadmium Battery Expert System, is established. The specific spacecraft power system configuration selected was the Hubble Space Telescope (HST) Electrical Power System (EPS) Testbed. Power for the HST comes from a system of 13 Solar Panel Arrays (SPAs) linked to 6 Nickel Cadmium Batteries which are connected to 3 Busses. An expert system, NICBES, will be developed at Martin Marietta Aerospace to recognize a testbed anomaly, identify the malfunctioning component and recommend a course of action. Besides fault diagnosis, NICBES will be able to evaluate battery status, give advice on battery status and provide decision support for the operator. These requirements are detailed.
Recent developments in computer engineering have greatly enhanced the capabilities of display technology. As displays are no longer limited to simple alphanumeric output, they can present a wide variety of graphic information, using either static or dynamic presentation modes. At the same time that interface designers exploit the increased capabilities of these displays, they must be aware of the inherent limitation of these displays. Generally, these limitations can be divided into those that reflect limitations of the medium (e.g., reducing three-dimensional representations onto a two-dimensional projection) and those reflecting the perceptual and conceptual biases of the operator. The advantages and limitations of static and dynamic graphic displays are considered. Rather than enter into the discussion of whether dynamic or static displays are superior, general advantages and limitations are explored which are contextually specific to each type of display.
The preliminary Contract End Item (CEI) specification presents the performance, design, and verification requirements for Morton Thiokol's Space Shuttle Block 2 Solid Rocket Motor (SRM).
The features of atmospheric disturbances that are significant to aircraft flying qualities are discussed. Next follows a survey of proposed models. Lastly, there is a discussion of the content and application of the model contained in the current flying qualities specification and the forthcoming MIL-Standard.
Attempts to explain the fundamental crustal dichotomy on Mars range from purely endogenic to extreme exogenic processes, but to date no satisfactory theory has evolved. What is accepted is: (1) the dichotomy is an ancient feature of the Martian crust, and (2) the boundary between the cratered highlands and northern plains which marks the dichotomy in parts of Mars has undergone significant and variable modification during the observable parts of Martian history. Some ascribe it to a single mega-impact event, essentially an instantaneous rearrangement of the crustal structures (topography and lithospheric thickness). Others prefer an internal mechanism: a period of vigorous convection subcrustally erodes the northern one third of Mars, causing foundering and isostatic lowering of that part of Mars. The evidence for each theory is reviewed, with the conclusion that there is little to recommend either. An alternative is suggested: the formation of the crustal dichotomy on Mars was not a specific tectonic event but a byproduct of the accretionary process and therefore a primordial characteristic of the Martian crust, predating the oldest recognizable landforms.
ENCOMPASS is an example integrated software engineering environment being constructed by the SAGA project. ENCOMPASS supports the specification, design, construction and maintenance of efficient, validated, and verified programs in a modular programming language. The life cycle paradigm, schema of software configurations, and hierarchical library structure used by ENCOMPASS is presented. In ENCOMPASS, the software life cycle is viewed as a sequence of developments, each of which reuses components from the previous ones. Each development proceeds through the phases planning, requirements definition, validation, design, implementation, and system integration. The components in a software system are modeled as entities which have relationships between them. An entity may have different versions and different views of the same project are allowed. The simple entities supported by ENCOMPASS may be combined into modules which may be collected into projects. ENCOMPASS supports multiple programmers and projects using a hierarchical library system containing a workspace for each programmer; a project library for each project, and a global library common to all projects.
An example is presented of the constructive specification of a queue which is done in the style of (Jones 80) using the Vienna Development Method. The basic approach is that of data type refinement. The techniques used are not restricted to those used by Jones, particularly with respect to the method for proving properties of the retrieve function for linked lists, however the notation is consistent with his.
The preliminary design of an across-the-bay Flight Support Structure optimized to the specific requirements of the Spartan program has been completed. Although approximately 15 percent heavier than the initial goal, preliminary analysis indicate very low stress levels and significant reduction in weight should be possible in the final design. This structure is capable of supporting two Spartan 200-class spacecraft or attached payloads of equivalent total weight. The inherent structural efficiency of monocoque type construction is utilized. The minimization of fabrication and assembly costs and provision for simple and versatile payload interfacing where given significant considerations. Modularity of this structure allows it to be readily adapted for use as the primary structure of an Aries-class Spartan free-flyer utilizing the Orbit trunning latch mechanisms, thus eliminating the need for a flight support structure.
A recently initiated research project concerned with the concurrent detection of software errors and errors due to physical failures in the hardware of multiprocessor systems is described in this paper. An approach to error detection is described, which is specification based and relies on the structural verification of program control flow and data structure integrity. The techniques discussed utilize the hardware redundancy inherent in parallel processing systems to provide verification of both program structure and data concurrently with program execution.
This report was a followup to, Collection and Analysis of Specific ELINT Signal Parameters, DTIC A166507, 23 June 1985. The programs and hardware assembled for the above mentioned report were used to analyze two types of radar, the PPS-6 and the HOOD radars. The typical ELINT parameters of frequency, pulse width, and pulse repetition rate were collected and analyzed.
The objective is to develop and verify a series of interdisciplinary modeling and analysis techniques that have been specialized to address three specific hot section components. These techniques will incorporate data as well as theoretical methods from many diverse areas including cycle and performance analysis, heat transfer analysis, linear and nonlinear stress analysis, and mission analysis. The new methods developed will be integrated to provide an accurate, efficient, and unified approach to analyzing combustor burner liners, hollow air-cooled turbine blades, and air-colled turbine vanes. For these components, the methods developed will predict temperature, deformation, stress, and strain histories throughout a complete flight mission.
An automatic program generator which creates Prolog programs from input/output specifications is presented. The generator takes as input descriptions of the input and output data types, a set of tests, a set of transformations and the input/out relation. Abstract data types are used as models. The tests, the transformations and the input/out relation are also specified by equations. The heuristics used by the automatic propram generator in building Prolog programs are discussed.