Search NASA⌕ Search

SEARCH · Search NASA

Results for “Programming Practices”

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 523 records · Page 29
All sourcesNASA NTRSDOE OSTI
NASA NTRS2018

The Effects of Long-Duration Spaceflight on Training Retention and Transfer

Training our crew members for long duration, exploration-class missions will have to maximize long-term retention and transfer of the trained skills. The expected duration of the missions, our inability to predict all the possible tasks the crew will be called upon to perform, and the low training-to-mission time ratio require that the training be maximally effective such that the skills acquired during training will be retained and will be transferrable across a wide range of specific tasks that are different from the particular tasks used during training. However, to be able to design training that can achieve these ambitious goals, we must first understand the ways in which long-duration spaceflight affects training retention and transfer. Current theories of training retention and transfer are largely based on experimental studies conducted at university laboratories using undergraduate students as participants. Furthermore, all such studies have been conducted on Earth. We do not know how well the results of these studies predict the performance of crew members. More specifically, we do not know how well the results of these studies predict the performance of crew members in space and especially during long-duration missions. To address this gap in our knowledge, the current on-going study seeks to test the null hypothesis that performance of university undergraduate students on Earth on training retention and transfer tests do in fact predict accurately the performance of crew members during long-duration spaceflights. To test this hypothesis, the study employs a single 16-month long experimental protocol with 3 different participant groups: undergraduate university students, crew members on the ground, and crew members in space. Results from this study will be presented upon its completion. This poster presents results of study trials of the two tasks used in this study: a data entry task and a mapping task. By researching established training principles, by examining future needs, and by using current practices in spaceflight training as test beds, this research project is mitigating program risks and generating templates and requirements to meet future training needs.

training↗
NASA NTRS2021

Implementation Requirements for Nasa Approved Workmanship Standards

This NASA technical standard provides uniform engineering and technical requirements for processes, procedures, practices, and methods that have been endorsed as standard for NASA facilities, programs, and projects, including requirements for selecting, applying, and designing hardware for manufacturability and reliability. This standard establishes NASA workmanship requirements, and clarifications, additions, and exceptions to requirements specified in NASA adopted industry consensus standards identified as required for use by NPR 8735.2, Hardware Quality Assurance Program Requirements for Programs and Projects

workmanship standards↗
NASA NTRS1996

Development and Demonstration of an Ada Test Generation System

In this project we have built a prototype system that performs Feasible Path Analysis on Ada programs: given a description of a set of control flow paths through a procedure, and a predicate at a program point feasible path analysis determines if there is input data which causes execution to flow down some path in the collection reaching the point so that tile predicate is true. Feasible path analysis can be applied to program testing, program slicing, array bounds checking, and other forms of anomaly checking. FPA is central to most applications of program analysis. But, because this problem is formally unsolvable, syntactic-based approximations are used in its place. For example, in dead-code analysis the problem is to determine if there are any input values which cause execution to reach a specified program point. Instead an approximation to this problem is computed: determine whether there is a control flow path from the start of the program to the point. This syntactic approximation is efficiently computable and conservative: if there is no such path the program point is clearly unreachable, but if there is such a path, the analysis is inconclusive, and the code is assumed to be live. Such conservative analysis too often yields unsatisfactory results because the approximation is too weak. As another example, consider data flow analysis. A du-pair is a pair of program points such that the first point is a definition of a variable and the second point a use and for which there exists a definition-free path from the definition to the use. The sharper, semantic definition of a du-pair requires that there be a feasible definition-free path from the definition to the use. A compiler using du-pairs for detecting dead variables may miss optimizations by not considering feasibility. Similarly, a program analyzer computing program slices to merge parallel versions may report conflicts where none exist. In the context of software testing, feasibility analysis plays an important role in identifying testing requirements which are infeasible. This is especially true for data flow testing and modified condition/decision coverage. Our system uses in an essential way symbolic analysis and theorem proving technology, and we believe this work represents one of the few successful uses of a theorem prover working in a completely automatic fashion to solve a problem of practical interest. We believe this work anticipates an important trend away from purely syntactic-based methods for program analysis to semantic methods based on symbolic processing and inference technology. Other results demonstrating the practical use of automatic inference is being reported in hardware verification, although there are significant differences between the hardware work and ours. However, what is common and important is that general purpose theorem provers are being integrated with more special-purpose decision procedures to solve problems in analysis and verification. We are pursuina commercial opportunities for this work, and will use and extend the work in other projects we are engaged in. Ultimately we would like to rework the system to analyze C, C++, or Java as a key step toward commercialization.

Source record↗
NASA NTRS1998

Explaining Synthesized Software

Motivated by NASA's need for high-assurance software, NASA Ames' Amphion project has developed a generic program generation system based on deductive synthesis. Amphion has a number of advantages, such as the ability to develop a new synthesis system simply by writing a declarative domain theory. However, as a practical matter, the validation of the domain theory for such a system is problematic because the link between generated programs and the domain theory is complex. As a result, when generated programs do not behave as expected, it is difficult to isolate the cause, whether it be an incorrect problem specification or an error in the domain theory. This paper describes a tool we are developing that provides formal traceability between specifications and generated code for deductive synthesis systems. It is based on extensive instrumentation of the refutation-based theorem prover used to synthesize programs. It takes augmented proof structures and abstracts them to provide explanations of the relation between a specification, a domain theory, and synthesized code. In generating these explanations, the tool exploits the structure of Amphion domain theories, so the end user is not confronted with the intricacies of raw proof traces. This tool is crucial for the validation of domain theories as well as being important in everyday use of the code synthesis system. It plays an important role in validation because when generated programs exhibit incorrect behavior, it provides the links that can be traced to identify errors in specifications or domain theory. It plays an important role in the everyday use of the synthesis system by explaining to users what parts of a specification or of the domain theory contribute to what pieces of a generated program. Comments are inserted into the synthesized code that document these explanations.

VanBaalen, Jeffrey↗
NASA NTRSDate not supplied

Validation of Kestrel IDDES Simulations for SLS Transition Analysis

Complex computational simulations are needed to support the Space Launch System (SLS) program, and the fidelity of the computational results must be defended. More specifically, a number of databases are produced for the transition phase of flight, which occurs after the rocket clears the tower but before reaching transonic speeds. In an effort to reduce computational uncertainty, many of the computational parameters were altered to determine the sensitivity of the results to the value of the parameter and then updating the best practice procedures. The baseline routines were developed over many years through the maturation of the SLS program, and this paper delivers a detailed discussion of these baseline results. This section is followed by demonstration of perturbing some of the more significant parameters, including time step and turbulence model, and concluded with a summary of the herein determined best practices for such analysis.

CFD↗
NASA NTRS1997

Modified Fully Utilized Design (MFUD) Method for Stress and Displacement Constraints

The traditional fully stressed method performs satisfactorily for stress-limited structural design. When this method is extended to include displacement limitations in addition to stress constraints, it is known as the fully utilized design (FUD). Typically, the FUD produces an overdesign, which is the primary limitation of this otherwise elegant method. We have modified FUD in an attempt to alleviate the limitation. This new method, called the modified fully utilized design (MFUD) method, has been tested successfully on a number of designs that were subjected to multiple loads and had both stress and displacement constraints. The solutions obtained with MFUD compare favorably with the optimum results that can be generated by using nonlinear mathematical programming techniques. The MFUD method appears to have alleviated the overdesign condition and offers the simplicity of a direct, fully stressed type of design method that is distinctly different from optimization and optimality criteria formulations. The MFUD method is being developed for practicing engineers who favor traditional design methods rather than methods based on advanced calculus and nonlinear mathematical programming techniques. The Integrated Force Method (IFM) was found to be the appropriate analysis tool in the development of the MFUD method. In this paper, the MFUD method and its optimality are presented along with a number of illustrative examples.

Patnaik, Surya↗
NASA NTRS2011

NASA Risk Management Handbook

The purpose of this handbook is to provide guidance for implementing the Risk Management (RM) requirements of NASA Procedural Requirements (NPR) document NPR 8000.4A, Agency Risk Management Procedural Requirements [1], with a specific focus on programs and projects, and applying to each level of the NASA organizational hierarchy as requirements flow down. This handbook supports RM application within the NASA systems engineering process, and is a complement to the guidance contained in NASA/SP-2007-6105, NASA Systems Engineering Handbook [2]. Specifically, this handbook provides guidance that is applicable to the common technical processes of Technical Risk Management and Decision Analysis established by NPR 7123.1A, NASA Systems Engineering Process and Requirements [3]. These processes are part of the \Systems Engineering Engine. (Figure 1) that is used to drive the development of the system and associated work products to satisfy stakeholder expectations in all mission execution domains, including safety, technical, cost, and schedule. Like NPR 7123.1A, NPR 8000.4A is a discipline-oriented NPR that intersects with product-oriented NPRs such as NPR 7120.5D, NASA Space Flight Program and Project Management Requirements [4]; NPR 7120.7, NASA Information Technology and Institutional Infrastructure Program and Project Management Requirements [5]; and NPR 7120.8, NASA Research and Technology Program and Project Management Requirements [6]. In much the same way that the NASA Systems Engineering Handbook is intended to provide guidance on the implementation of NPR 7123.1A, this handbook is intended to provide guidance on the implementation of NPR 8000.4A. 1.2 Scope and Depth This handbook provides guidance for conducting RM in the context of NASA program and project life cycles, which produce derived requirements in accordance with existing systems engineering practices that flow down through the NASA organizational hierarchy. The guidance in this handbook is not meant to be prescriptive. Instead, it is meant to be general enough, and contain a sufficient diversity of examples, to enable the reader to adapt the methods as needed to the particular risk management issues that he or she faces. The handbook highlights major issues to consider when managing programs and projects in the presence of potentially significant uncertainty, so that the user is better able to recognize and avoid pitfalls that might otherwise be experienced.

Dezfuli, Homayoon↗
NASA NTRS2011

Demonstration/Validation of Environmentally-Preferable Coatings for Launch Facilities

Kennedy Space Center (KSC) is responsible for a number of facilities/structures with metallic structural and non-structural components in a highly corrosive environment. Metals require periodic maintenance activity to guard against the insidious effects of corrosion and thus ensure that structures meet or exceed design or performance life. The standard practice for protecting metallic substrates in atmospheric environments is the application of an applied coating system. Applied coating systems work via a variety of methods (barrier, galvanic and/or inhibitor) and adhere to the substrate through a combination of chemical and physical bonds. Maintenance at KSC and other NASA Centers is governed by NASA-STD-50088 (Protective Coating of Carbon Steel, Stainless Steel, and Aluminum on Launch Structures, Facilities, and Ground Support Equipment) which establishes practices for the protective coating of ground support equipment and related facilities used by or for NASA programs and projects. The Standard is for the design of non-flight hardware used to support the operations of receiving, transportation, handling, assembly, inspection, test, checkout, service, and launch of space vehicles and payloads at NASA launch, landing, or retrieval sites. These criteria and practices contained within the Standard may be used for items used at the manufacturing, development, and test sites upstream of the launch, landing, or retrieval sites. The objective of this effort is to demonstrate and validate environmentally-preferable alternatives in accordance with NASA-STD-50088 and KSC requirements which can then be added to the Approved Products List. This Test Protocol contains the critical requirements and tests necessary to qualify alternatives for structural steel applications. These tests were derived from engineering, performance, and operational impact (supportability) requirements defined by a consensus of KSC participants. A Test Report will document the results of the testing as well as any test modifications made during the execution of the testing. Users of this Test Protocol should check the project's Test Report for additional test details or minor modifications that may have been necessary in the execution of the testing. The technical stakeholders will have agreed upon test procedures modifications documented in the Test Report.

Lewis, Pattie↗
NASA NTRS2011

Using Technical Performance Measures

All programs have requirements. For these requirements to be met, there must be a means of measurement. A Technical Performance Measure (TPM) is defined to produce a measured quantity that can be compared to the requirement. In practice, the TPM is often expressed as a maximum or minimum and a goal. Example TPMs for a rocket program are: vacuum or sea level specific impulse (lsp), weight, reliability (often expressed as a failure rate), schedule, operability (turn-around time), design and development cost, production cost, and operating cost. Program status is evaluated by comparing the TPMs against specified values of the requirements. During the program many design decisions are made and most of them affect some or all of the TPMs. Often, the same design decision changes some TPMs favorably while affecting other TPMs unfavorably. The problem then becomes how to compare the effects of a design decision on different TPMs. How much failure rate is one second of specific impulse worth? How many days of schedule is one pound of weight worth? In other words, how to compare dissimilar quantities in order to trade and manage the TPMs to meet all requirements. One method that has been used successfully and has a mathematical basis is Utility Analysis. Utility Analysis enables quantitative comparison among dissimilar attributes. It uses a mathematical model that maps decision maker preferences over the tradeable range of each attribute. It is capable of modeling both independent and dependent attributes. Utility Analysis is well supported in the literature on Decision Theory. It has been used at Pratt & Whitney Rocketdyne for internal programs and for contracted work such as the J-2X rocket engine program. This paper describes the construction of TPMs and describes Utility Analysis. It then discusses the use of TPMs in design trades and to manage margin during a program using Utility Analysis.

Garrett, Christopher J.↗
NASA NTRS2001

Institutionalizing Lessons Learned

The NASA Integrated Action Team (NIAT) was formed by the NASA Administrator in March 2000. The purpose of this team was to identify the actions that NASA must take to address systemic findings reported in 4 different anomaly investigations. Team membership represented senior managers from all the field centers and NASA Headquarters. NIAT report addressed 165 findings and developed 17 action plans that are described in five themes: people and teams, technology, risk, formulation rigor, and communications. The NIAT actions present a systems solution for strengthening formulation and implementation of programs and improving the environment for their support. NIAT results included: enhancing success by avoiding failures that could have been prevented through good planning and sound practice; ensuring that prudent risks do not compromise safety; and ensuring that mission risks are objectively assessed, appropriately mitigated and consciously accepted by the program team and customers. Definitions of Faster, Better, Cheaper and Success Criteria were also developed and included as part of the NIAT report. As a result of the NIAT report, program and project management process changes were incorporated into NASA's quality system documentation, including NPG 7120.513, "NASA Program and Project Management Processes and Requirements. This paper describes the NIAT results and the resulting updates to NPG 7120.5 that keep this program and project management description a living process.

McBrayer, Robert O.↗
NASA NTRS2009

Maneuver Automation Software

The Maneuver Automation Software (MAS) automates the process of generating commands for maneuvers to keep the spacecraft of the Cassini-Huygens mission on a predetermined prime mission trajectory. Before MAS became available, a team of approximately 10 members had to work about two weeks to design, test, and implement each maneuver in a process that involved running many maneuver-related application programs and then serially handing off data products to other parts of the team. MAS enables a three-member team to design, test, and implement a maneuver in about one-half hour after Navigation has process-tracking data. MAS accepts more than 60 parameters and 22 files as input directly from users. MAS consists of Practical Extraction and Reporting Language (PERL) scripts that link, sequence, and execute the maneuver- related application programs: "Pushing a single button" on a graphical user interface causes MAS to run navigation programs that design a maneuver; programs that create sequences of commands to execute the maneuver on the spacecraft; and a program that generates predictions about maneuver performance and generates reports and other files that enable users to quickly review and verify the maneuver design. MAS can also generate presentation materials, initiate electronic command request forms, and archive all data products for future reference.

Uffelman, Hal↗
NASA NTRS1989

Machine learning in motion control

The existing methodologies for robot programming originate primarily from robotic applications to manufacturing, where uncertainties of the robots and their task environment may be minimized by repeated off-line modeling and identification. In space application of robots, however, a higher degree of automation is required for robot programming because of the desire of minimizing the human intervention. We discuss a new paradigm of robotic programming which is based on the concept of machine learning. The goal is to let robots practice tasks by themselves and the operational data are used to automatically improve their motion performance. The underlying mathematical problem is to solve the problem of dynamical inverse by iterative methods. One of the key questions is how to ensure the convergence of the iterative process. There have been a few small steps taken into this important approach to robot programming. We give a representative result on the convergence problem.

Su, Renjeng↗
NASA NTRS1961

Development of Ceramic Fibers for Reinforcement in Composite Materials

Refinements of the vertical arc fiberizing apparatus resulted in its ability to fiberize very different refractory glasses having wide ranges of properties. Although the apparatus, was originally designed as a laboratory research tool for the evaluation of many compositions daily, up to one quarter pound of fibers of a single composition could be produced in an 8-hour day. Fibers up to six and a half feet long were produced with the apparatus. Studies were conducted of two methods of fiberizing refractory glasses requiring rapid freezing from the melt. The first method consisted of fiberizing droplets of molten glass passing through an annular nozzle. The second method consisted of reconstructing the annular nozzle in. the shape of a horseshoe to achieve a shorter delay in blasting a molten droplet from the tip of a rod. Both methods were judged feasible for producing fibers of glasses requiring rapid freezing. The first method would be more amenable to volume fiber production. Studies of induction heating for fiber formation did not lead to its designation as a very efficient heating method. Problems. remain to be solved, in the design of a suitable susceptor for a higher heating rate, in protecting the susceptor from oxidation with an inert gas, in contamination of the melt from a refractory crucible, and in the protective radiation shielding of the induction concentrator coil. It is not considered practical to continue studies of this heating method. In the course of this program 151 refractory glass compositions were evaluated for fiber, forming characteristics. Of the various types of materials studied, the following showed promise in producing acceptable refractory fibers: sIlica- spinel (magnesium aluminate), silica- spinel-zirconia, silica-zirconia, silica-zinc spinel, aluminum phosphate glasses, and fluoride glasses. Compositions which did not produce acceptable fibers were high zirconia materials, barium spinels, and calcium aluminates. Improvements in the. testing apparatus for single fiber tensile strength increased the precision. of tests conducted on nine fibers. The highest mean tensile strength, a value of 295,000 pounds per square inch, was obtained with R-141 fibers. Treatment of R-74 fibers with anhydrous Linde A-1100 silane finish improved its mean fiber tensile strength by 25 percent. The lapse of time after fiber formation had no measurable effect on tensile strength. A static heating test conducted with various high melting fibers indicated that Fiberfrax and R-108 underwent no significant changes in bulk volume or resiliency on exposure to 2750 degrees Fahrenheit (1510 degrees Centigrade) in an oxidizing atmosphere. For fiber-resin composition fabrication, ten fiber materials were selected on the bases of high fiber yield, fusion temperature, and type of composition. Fiberfrax, a commercial ceramic fiber, was included for comparison. A new, more effective method of removing pellets from blown fibers was developed. The de-pelletized fibers were treated with a silane finish and felted into ten-inch diameter felts prior to resin impregnation. Composites containing 30 percent by weight of CTL 91-LD phenolic resin were molded under high pressure from the impregnated felts and post-cured to achieve optimum properties. Flexural strength, flexural modules of elasticity, and punch shear strength tests were conducted on the composite specimens. The highest average flexural strength obtained was 19,958 pounds per square inch with the R-74-fiber-resin composite. This compares very favorably with the military specification of 13,000 pounds per square inch flexural strength for randomly oriented fiber reinforced composites. The highest punch shear strength (11,509 pounds per square inch) was obtained with the R-89 fiber-resin composite. The effects of anhydrous fiber finishes on composite strength were not clearly indicated. Plasma arc tests at a heat flux of 550 British Thermal Units per square foot per second on eight composite materials indicated ablation rates generally equivalent to Fiberglas-Micarta No. 259-2. The composite reinforced with R-99 fibers had an average ablation rate of 0.008 inch per second and appears quite promising on the basis of these tests. Preliminary studies for processing fibers into yarn and fabric were conducted with R-99 fibers. The use of certain organic gums aided in 2 fabricating by hand several relatively strong yarns and a crude fabric swatch. This indicated the practicality of developing techniques for processing these fibers into yarn and fabric without significant damage to the fibers.

Gates, L. E.↗
NASA NTRS2011

A Bootstrap Approach to an Affordable Exploration Program

This paper examines the potential to build an affordable sustainable exploration program by adopting an approach that requires investing in technologies that can be used to build a space infrastructure from very modest initial capabilities. Human exploration has had a history of flight programs that have high development and operational costs. Since Apollo, human exploration has had very constrained budgets and they are expected be constrained in the future. Due to their high operations costs it becomes necessary to consider retiring established space facilities in order to move on to the next exploration challenge. This practice may save cost in the near term but it does so by sacrificing part of the program s future architecture. Human exploration also has a history of sacrificing fully functional flight hardware to achieve mission objectives. An affordable exploration program cannot be built when it involves billions of dollars of discarded space flight hardware, instead, the program must emphasize preserving its high value space assets and building a suitable permanent infrastructure. Further this infrastructure must reduce operational and logistics cost. The paper examines the importance of achieving a high level of logistics independence by minimizing resource consumption, minimizing the dependency on external logistics, and maximizing the utility of resources available. The approach involves the development and deployment of a core suite of technologies that have minimum initial needs yet are able expand upon initial capability in an incremental bootstrap fashion. The bootstrap approach incrementally creates an infrastructure that grows and becomes self sustaining and eventually begins producing the energy, products and consumable propellants that support human exploration. The bootstrap technologies involve new methods of delivering and manipulating energy and materials. These technologies will exploit the space environment, minimize dependencies, and minimize the need for imported resources. They will provide the widest range of utility in a resource scarce environment and pave the way to an affordable exploration program.

Oeftering, Richard C.↗
NASA NTRS2013

Management Approach for NASA's Earth Venture-1 (EV-1) Airborne Science Investigations

The Earth System Science Pathfinder (ESSP) Program Office (PO) is responsible for programmatic management of National Aeronautics and Space Administration's (NASA) Science Mission Directorate's (SMD) Earth Venture (EV) missions. EV is composed of both orbital and suborbital Earth science missions. The first of the Earth Venture missions is EV-1, which are Principal Investigator-led, temporally-sustained, suborbital (airborne) science investigations costcapped at $30M each over five years. Traditional orbital procedures, processes and standards used to manage previous ESSP missions, while effective, are disproportionally comprehensive for suborbital missions. Conversely, existing airborne practices are primarily intended for smaller, temporally shorter investigations, and traditionally managed directly by a program scientist as opposed to a program office such as ESSP. In 2010, ESSP crafted a management approach for the successful implementation of the EV-1 missions within the constructs of current governance models. NASA Research and Technology Program and Project Management Requirements form the foundation of the approach for EV-1. Additionally, requirements from other existing NASA Procedural Requirements (NPRs), systems engineering guidance and management handbooks were adapted to manage programmatic, technical, schedule, cost elements and risk. As the EV-1 missions are nearly at the end of their successful execution and project lifecycle and the submission deadline of the next mission proposals near, the ESSP PO is taking the lessons learned and updated the programmatic management approach for all future Earth Venture Suborbital (EVS) missions for an even more flexible and streamlined management approach.

Guillory, Anthony R.↗
NASA NTRS1998

F-Nets and Software Cabling: Deriving a Formal Model and Language for Portable Parallel Programming

Parallel programming is still being based upon antiquated sequence-based definitions of the terms "algorithm" and "computation", resulting in programs which are architecture dependent and difficult to design and analyze. By focusing on obstacles inherent in existing practice, a more portable model is derived here, which is then formalized into a model called Soviets which utilizes a combination of imperative and functional styles. This formalization suggests more general notions of algorithm and computation, as well as insights into the meaning of structured programming in a parallel setting. To illustrate how these principles can be applied, a very-high-level graphical architecture-independent parallel language, called Software Cabling, is described, with many of the features normally expected from today's computer languages (e.g. data abstraction, data parallelism, and object-based programming constructs).

DiNucci, David C.↗
NASA NTRS1994

Re-engineering NASA's space communications to remain viable in a constrained fiscal environment

Along with the Red and Blue Teams commissioned by the NASA Administrator in 1992, NASA's Associate Administrator for Space Communications commissioned a Blue Team to review the Office of Space Communications (Code O) Core Program and determine how the program could be conducted faster, better, and cheaper. Since there was no corresponding Red Team for the Code O Blue Team, the Blue Team assumed a Red Team independent attitude and challenged the status quo, including current work processes, functional distinctions, interfaces, and information flow, as well as traditional management and system development practices. The Blue Team's unconstrained, non-parochial, and imaginative look at NASA's space communications program produced a simplified representation of the space communications infrastructure that transcends organizational and functional boundaries, in addition to existing systems and facilities. Further, the Blue Team adapted the 'faster, better, cheaper' charter to be relevant to the multi-mission, continuous nature of the space communications program and to serve as a gauge for improving customer services concurrent with achieving more efficient operations and infrastructure life cycle economies. This simplified representation, together with the adapted metrics, offers a future view and process model for reengineering NASA's space communications to remain viable in a constrained fiscal environment. Code O remains firm in its commitment to improve productivity, effectiveness, and efficiency. In October 1992, the Associate Administrator reconstituted the Blue Team as the Code O Success Team (COST) to serve as a catalyst for change. In this paper, the COST presents the chronicle and significance of the simplified representation and adapted metrics, and their application during the FY 1993-1994 activities.

Hornstein, Rhoda Shaller↗
NASA NTRS1977

V/STOL Conference, Palo Alto, Calif., June 6-8, 1977, Technical Papers

Papers are presented on practical aspects of commercial STOL operations, a Vertical Attitude Takeoff and Landing (VATOL) program, powered-lift STOL ground effects, conceptual design studies of Navy Type A V/STOL aircraft, and a V/STOL shaft propulsion system analytical performance model. Also considered are the management of swirling flows with application to wind tunnel design and V/STOL testing, flight control testing of the VAK-191B, and surface fluctuating pressure measurements on a 1/4-scale YC-14 boilerplate model.

Source record↗