Search NASA⌕ Search

SEARCH · Search NASA

Results for “appendix”

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 793 records · Page 44

Filament wound data base development, revision 1, appendix B

The data tape 8 data are presented in tabular form. Each page consists of six-component force and moment coefficients as they vary with angle of attack at a specific Mach number and roll angle. The angle of attack range is from 0 to 180 deg in 5 deg increments. The six coefficients are normal force, pitching moment, side force, yawing moment, axial force, and rolling moment. Each successive page is incremented for roll angle in 45 deg increments for a roll angle range from 0 to 360 deg. The cycle is then repeated for the next Mach number. The Mach numbers in the data base are 0.4, 0.5, 0.55, 0.6, 0.7, 0.8, 0.9, 0.95, 1.05, 1.1, 1.2, 1.4, 1.96, 2.5, 3.0, and 3.48.

Sharp, R. Scott↗

Radiation pattern analysis of the tapered slot antenna, appendix 1

A theoretical model for the tapered slot antenna is presented. The model is valid for any smooth taper of the slot. The problem is solved by modeling the slot electric field and using the half plane Green's function to compute the far fields. The aperture field is obtained by affecting a stepped approximation to the continuous taper and utilizing the uniform wide slot line data. The uniform wide slot line is solved by the spectral Galerkin's technique and closed form experssions are developed for the slot wave length and the slot characteristic impedance. Numerous comparisons with measurement are made to demonstrate the versatility of the model in treating an arbitrary slot taper.

Janaswamy, Ramakrishna↗

ENCOMPASS: A SAGA based environment for the compositon of programs and specifications, appendix A

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.

Terwilliger, Robert B.↗

An example of a constructive specification of a queue, preliminary report, appendix B

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.

Benzinger, Leonora↗

Tree-oriented interactive processing with an application to theorem-proving, appendix E

The concept of unstructured structure editing and ted, an editor for unstructured trees, is described. Ted is used to manipulate hierarchies of information in an unrestricted manner. The tool was implemented and applied to the problem of organizing formal proofs. As a proof management tool, it maintains the validity of a proof and its constituent lemmas independently from the methods used to validate the proof. It includes an adaptable interface which may be used to invoke theorem provers and other aids to proof construction. Using ted, a user may construct, maintain, and verify formal proofs using a variety of theorem provers, proof checkers, and formatters.

Hammerslag, David↗

PCG: A prototype incremental compilation facility for the SAGA environment, appendix F

A programming environment supports the activity of developing and maintaining software. New environments provide language-oriented tools such as syntax-directed editors, whose usefulness is enhanced because they embody language-specific knowledge. When syntactic and semantic analysis occur early in the cycle of program production, that is, during editing, the use of a standard compiler is inefficient, for it must re-analyze the program before generating code. Likewise, it is inefficient to recompile an entire file, when the editor can determine that only portions of it need updating. The pcg, or Pascal code generation, facility described here generates code directly from the syntax trees produced by the SAGA syntax directed Pascal editor. By preserving the intermediate code used in the previous compilation, it can limit recompilation to the routines actually modified by editing.

Kimball, Joseph John↗

Writing filter processes for the SAGA editor, appendix G

The SAGA editor provides a mechanism by which separate processes can be invoked during an editing session to traverse portions of the parse tree being edited. These processes, termed filter processes, read, analyze, and possibly transform the parse tree, returning the result to the editor. By defining new commands with the editor's user defined command facility, which invoke filter processes, authors of filter can provide complex operations as simple commands. A tree plotter, pretty printer, and Pascal tree transformation program were already written using this facility. The filter processes are introduced, parse tree structure is described and the library interface made available to the programmer. Also discussed is how to compile and run filter processes. Examples are presented to illustrate aspect of each of these areas.

Kirslis, Peter A.↗

System analysis study of space platform and station accommodations for life sciences research facilities. Volume 2: Study results. Appendix E: Work breakdown structure and dictionary

A work breakdown structure for the Space Station Life Sciences Research Facility (LSRF) is presented up to level 5. The purpose is to provide the framework for task planning and control and to serve as a basis for budgeting, task assignment, cost collection and report, and contractual performance measurement and tracking of the Full Scale Development Phase tasks.

Wiley, Lowell F.↗

System analysis study of space platform and station accommodations for life sciences research facilities. Volume 2: Study results. Appendix D: Life sciences research facility requirements

The purpose of this requirements document is to develop the foundation for concept development for the Life Sciences Research Facility (LSRF) on the Space Station. These requirements are developed from the perspective of a Space Station laboratory module outfitter. Science and mission requirements including those related to specimens are set forth. System requirements, including those for support, are detailed. Functional and design requirements are covered in the areas of structures, mechanisms, electrical power, thermal systems, data management system, life support, and habitability. Finally, interface requirements for the Command Module and Logistics Module are described.

Wiley, Lowell F.↗

Orbital transfer vehicle concept definition and system analysis study. Volume 4, Appendix A: Space station accommodations. Revision 1

Orbit Transfer Vehicle (OTV) processing at the space station is divided into two major categories: OTV processing and assembly operations, and support operations. These categories are further subdivided into major functional areas to allow development of detailed OTV processing procedures and timelines. These procedures and timelines are used to derive the specific space station accommodations necessary to support OTV activities. The overall objective is to limit impact on OTV processing requirements on space station operations, involvement of crew, and associated crew training and skill requirements. The operational concept maximizes use of automated and robotic systems to perform all required OTV servicing and maintenance tasks. Only potentially critical activities would require direct crew involvement or supervision. EVA operations are considered to be strictly contingency back-up to failure of the automated and robotic systems, with the exception of the initial assembly of Space-Based OTV accommodations at the space station, which will require manned involvement.

Randall, Roger M.↗

SRB/SLEEC (Solid Rocket Booster/Shingle Lap Extendible Exit Cone) feasibility study, volume 2. Appendix A: Design study for a SLEEC actuation system

The results are presented of a design feasibility study of a self-contained (powered) actuation system for a Shingle Lap Extendible Exit Cone (SLEEC) for Transportation System (STS). The evolution of the SLEEC actuation system design is reviewed, the final design concept is summarized, and the results of the detailed study of the final concept of the actuation system are treated. A conservative design using proven mechanical components was established as a major program priority. The final mechanical design has a very low development risk since the components, which consist of ballscrews, gearing, flexible shaft drives, and aircraft cables, have extensive aerospace applications and a history of proven reliability. The mathematical model studies have shown that little or no power is required to deploy the SLEEC actuation system because acceleration forces and internal pressure from the rocket plume provide the required energies. A speed control brake is incorporated in the design in order to control the rate of deployment.

Thompson, D. S.↗

Fatigue crack growth model RANDOM2 user manual. Appendix 1: Development of advanced methodologies for probabilistic constitutive relationships of material strength models

FORTRAN program RANDOM2 is presented in the form of a user's manual. RANDOM2 is based on fracture mechanics using a probabilistic fatigue crack growth model. It predicts the random lifetime of an engine component to reach a given crack size. Details of the theoretical background, input data instructions, and a sample problem illustrating the use of the program are included.

Boyce, Lola↗

Fatigue strength reduction model: RANDOM3 and RANDOM4 user manual. Appendix 2: Development of advanced methodologies for probabilistic constitutive relationships of material strength models

FORTRAN programs RANDOM3 and RANDOM4 are documented in the form of a user's manual. Both programs are based on fatigue strength reduction, using a probabilistic constitutive model. The programs predict the random lifetime of an engine component to reach a given fatigue strength. The theoretical backgrounds, input data instructions, and sample problems illustrating the use of the programs are included.

Boyce, Lola↗

Conjugating binary systems for spacecraft thermal control. Appendix C: Aeroassist Flight Experiment Carrier Vehicle preliminary stress analysis

An assessment of the static strength of the Aeroassist Flight Experiment (AFE) Carrier Vehicle is presented. The Carrier Vehicle is the structural component which provides the mounting platform for the experiments, on-board computers, batteries, and other black boxes. In addition, the Solid Rocket Motor (SRM), the Thrusters, and the Aerobrake are all attached directly to the Carrier Vehicle. The basic approach in this analysis was to develop a NASTRAN Finite Element Model as a parallel effort to the preliminary design, and to use the internal loads from this model to perform the stress analysis. The NASTRAN method of Inertial Relief was employed. This method involves either specifying a set of CG (center of gravity) accelerations or applying forces at the CG and representing the Carrier Vehicle and all its mounted devices with the proper stiffness and mass properties.

Ingram, J. E.↗

Liquid rocket booster study. Volume 2, book 5, appendix 9: LRB alternate applications and evolutionary growth

The analyses performed in assessing the merit of the Liquid Rocket Booster concept for use in alternate applications such as for Shuttle C, for Standalone Expendable Launch Vehicles, and possibly for use with the Air Force's Advanced Launch System are presented. A comparison is also presented of the three LRB candidate designs, namely: (1) the LO2/LH2 pump fed, (2) the LO2/RP-1 pump fed, and (3) the LO2/RP-1 pressure fed propellant systems in terms of evolution along with design and cost factors, and other qualitative considerations. A further description is also presented of the recommended LRB standalone, core-to-orbit launch vehicle concept.

Source record↗

Liquid rocket booster study. Volume 2, book 6, appendix 10: Vehicle systems effects

Three tasks were undertaken by Eagle Engineering as a part of the Liquid Rocket Booster (LRB) study. Task 1 required Eagle to supply current data relative to the Space Shuttle vehicle and systems affected by an LRB substitution. Tables listing data provided are presented. Task 2 was to evaluate and compare shuttle impacts of candidate LRB configuration in concert with overall trades of analysis activity. Three selected configurations with emphasis on flight loads, separation dynamics, and cost comparison are presented. Task 3 required the development of design guidelines and requirements to minimize impacts to the Space Shuttle system from all LRB substitution. Results are presented for progress to date.

Source record↗