Engineering Papers⌕ Search

SEARCH · Engineering Papers

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 595 records · Page 33

Appendix E: Parallel Pascal development system

The Parallel Pascal Development System enables Parallel Pascal programs to be developed and tested on a conventional computer. It consists of several system programs, including a Parallel Pascal to standard Pascal translator, and a library of Parallel Pascal subprograms. The library includes subprograms for using Parallel Pascal on a parallel system with a fixed degree of parallelism, such as the Massively Parallel Processor, to conveniently manipulate arrays which have dimensions than the hardware. Programs can be conveninetly tested with small sized arrays on the conventional computer before attempting to run on a parallel system.

Source record↗

Evaluation of automated decisionmaking methodologies and development of an integrated robotic system simulation, appendix B

The purpose of the Robotics Simulation (ROBSIM) program is to provide a broad range of computer capabilities to assist in the design, verification, simulation, and study of robotic systems. ROBSIM is programmed in FORTRAN 77 and implemented on a VAX 11/750 computer using the VMS operating system. This programmer's guide describes the ROBSIM implementation and program logic flow, and the functions and structures of the different subroutines. With this manual and the in-code documentation, and experienced programmer can incorporate additional routines and modify existing ones to add desired capabilities.

Haley, D. C.↗

Evaluation of automated decisionmaking methodologies and development of an integrated robotic system simulation. Appendix A: ROBSIM user's guide

The purpose of the Robotics Simulation Program is to provide a broad range of computer capabilities to assist in the design, verification, simulation, and study of robotics systems. ROBSIM is program in FORTRAN 77 for use on a VAX 11/750 computer under the VMS operating system. This user's guide describes the capabilities of the ROBSIM programs, including the system definition function, the analysis tools function and the postprocessor function. The options a user may encounter with each of these executables are explained in detail and the different program prompts appearing to the user are included. Some useful suggestions concerning the appropriate answers to be given by the user are provided. An example user interactive run in enclosed for each of the main program services, and some of the capabilities are illustrated.

Haley, D. C.↗

Evaluation of automated decisionmaking methodologies and development of an integrated robotic system simulation. Appendix B: ROBSIM programmer's guide

The purpose of the Robotic Simulation (ROBSIM) program is to provide a broad range of computer capabilities to assist in the design, verification, simulation, and study of robotic systems. ROBSIM is programmed in FORTRAM 77 and implemented on a VAX 11/750 computer using the VMS operating system. The programmer's guide describes the ROBSIM implementation and program logic flow, and the functions and structures of the different subroutines. With the manual and the in-code documentation, an experienced programmer can incorporate additional routines and modify existing ones to add desired capabilities.

Haley, D. C.↗

Filament wound data base development, revision 1, appendix A

Data are presented in tabular form for the High Performance Nozzle Increments, Filament Wound Case (FWC) Systems Tunnel Increments, Steel Case Systems Tunnel Increments, FWC Stiffener Rings Increments, Steel Case Stiffener Rings Increments, FWC External Tank (ET) Attach Ring Increments, Steel Case ET Attach Ring Increments, and Data Tape 8. The High Performance Nozzle are also presented in graphical form. The tabular data consist of six-component force and moment coefficients as they vary with angle of attack at a specific Mach number and roll angle. The six coefficients are normal force, pitching moment, side force, yawing moment, axial force, and rolling moment. The graphical data for the High Performance Nozzle Increments consist of a plot of a coefficient increment as a function of angle of attack at a specific Mach number and at a roll angle of 0 deg.

Sharp, R. Scott↗

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.↗