Engineering Papers⌕ Search

SEARCH · Engineering Papers

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 109 records · Page 6
All sourcesNASA NTRSDOE OSTI
NASA NTRS1994

Third International Symposium on Artificial Intelligence, Robotics, and Automation for Space 1994

The Third International Symposium on Artificial Intelligence, Robotics, and Automation for Space (i-SAIRAS 94), held October 18-20, 1994, in Pasadena, California, was jointly sponsored by NASA, ESA, and Japan's National Space Development Agency, and was hosted by the Jet Propulsion Laboratory (JPL) of the California Institute of Technology. i-SAIRAS 94 featured presentations covering a variety of technical and programmatic topics, ranging from underlying basic technology to specific applications of artificial intelligence and robotics to space missions. i-SAIRAS 94 featured a special workshop on planning and scheduling and provided scientists, engineers, and managers with the opportunity to exchange theoretical ideas, practical results, and program plans in such areas as space mission control, space vehicle processing, data analysis, autonomous spacecraft, space robots and rovers, satellite servicing, and intelligent instruments.

Source record↗
NASA NTRS1985

NASA's New Technology Reporting System: A Review and Future Prospects

This report represents a systematic effort to describe how NASA's new technology reporting system operates today, and how that system might be enhanced. Although the system has run for more than two decades, it is not well documented in terms of organization, operational practices, or other program benchmarks. The study seeks to identify and assess incentives or disincentives to reporting, program management, program follow through, and the feasibility of various means for improving the general process. Initially, it was hoped that the study team might uncover the kind of information that would permit the determination of some 'average' sequence of events (or a time line) from the point of identifying a solution to technical 'need' to the point where its solution was actually reported to NASA. Information regarding this objective proved to be too elusive, primarily because early probes revealed that con- tractor awareness of the new technology requirements generally was too poor to provide useful information. The report that follows is based primarily upon documents furnished by NASA Headquarters, by Field Center technology utilization officers, and interviews with persons knowledgeable about the system. Visits were made to seven Field Centers: Ames Research Center, Goddard Space Flight Center, Jet Propulsion Laboratory, Johnson Space Center, Langley Research Center, Lewis Research Center, and Marshall Space Flight Center. Other documents were furnished by officials of major aerospace corporations. Detailed interviews were conducted with Field Center technology utilization officials, project engineers or scientists, patent counsels, and other Field Center officials who had knowledge about the new technology reporting system. Interviews also were conducted with knowledgeable officials from a number of the primary aerospace companies. Numeric data was obtained from regular NASA reports, from original sources such as, NASA Tech Briefs, or from contractor reports. I am indebted to dozens of persons in both NASA and industry who took time to assist in the data collection by being interviewed, and through answering follow up questions on the telephone. Individuals interviewed and their affiliations are shown in Appendix A. I am most grateful to them for their kind assistance. A note of thanks is due to the other members of the DRI study team: Jody Briles, Kathy Hirst, and Joel Johnson. The responsibility for this report, its accuracy, and the nature of the observations and conclusions rest solely with the author. Text or citations in the numbered footnotes are to be found at the end of each chapter.

Chapman, Richard L.↗
NASA NTRS1998

Electrical Grounding Architecture for Unmanned Spacecraft

This handbook is approved for use by NASA Headquarters and all NASA Centers and is intended to provide a common framework for consistent practices across NASA programs. This handbook was developed to describe electrical grounding design architecture options for unmanned spacecraft. This handbook is written for spacecraft system engineers, power engineers, and electromagnetic compatibility (EMC) engineers. Spacecraft grounding architecture is a system-level decision which must be established at the earliest point in spacecraft design. All other grounding design must be coordinated with and be consistent with the system-level architecture. This handbook assumes that there is no one single 'correct' design for spacecraft grounding architecture. There have been many successful satellite and spacecraft programs from NASA, using a variety of grounding architectures with different levels of complexity. However, some design principles learned over the years apply to all types of spacecraft development. This handbook summarizes those principles to help guide spacecraft grounding architecture design for NASA and others.

Source record↗
NASA NTRS1999

Flight Test of an Adaptive Configuration Optimization System for Transport Aircraft

A NASA Dryden Flight Research Center program explores the practical application of real-time adaptive configuration optimization for enhanced transport performance on an L-1011 aircraft. This approach is based on calculation of incremental drag from forced-response, symmetric, outboard aileron maneuvers. In real-time operation, the symmetric outboard aileron deflection is directly optimized, and the horizontal stabilator and angle of attack are indirectly optimized. A flight experiment has been conducted from an onboard research engineering test station, and flight research results are presented herein. The optimization system has demonstrated the capability of determining the minimum drag configuration of the aircraft in real time. The drag-minimization algorithm is capable of identifying drag to approximately a one-drag-count level. Optimizing the symmetric outboard aileron position realizes a drag reduction of 2-3 drag counts (approximately 1 percent). Algorithm analysis of maneuvers indicate that two-sided raised-cosine maneuvers improve definition of the symmetric outboard aileron drag effect, thereby improving analysis results and consistency. Ramp maneuvers provide a more even distribution of data collection as a function of excitation deflection than raised-cosine maneuvers provide. A commercial operational system would require airdata calculations and normal output of current inertial navigation systems; engine pressure ratio measurements would be optional.

Gilyard, Glenn B.↗
NASA NTRS2003

Collaborative Software Development in Support of Fast Adaptive AeroSpace Tools (FAAST)

A collaborative software development approach is described. The software product is an adaptation of proven computational capabilities combined with new capabilities to form the Agency's next generation aerothermodynamic and aerodynamic analysis and design tools. To efficiently produce a cohesive, robust, and extensible software suite, the approach uses agile software development techniques; specifically, project retrospectives, the Scrum status meeting format, and a subset of Extreme Programming's coding practices are employed. Examples are provided which demonstrate the substantial benefits derived from employing these practices. Also included is a discussion of issues encountered when porting legacy Fortran 77 code to Fortran 95 and a Fortran 95 coding standard.

Kleb, William L.↗
NASA NTRS2008

Leading Your Leaders

Even though working on a problem has been your primary effort for the past year, your leadership may have heard about this once in a briefing a decade ago. Now they are basically clueless. Pretend that you are talking to your daughter's fifth-grade class. Explain how your complicated gizmo works. If possible, do not use acronyms. Define your terms. Put your work in context. Assume your leader has no idea what you do, who you work for, or what your gizmo does. That is a good place to start. Remember, taking the next century to study the problem or spending the Gross National Product to invent a new solution are probably not going to be acceptable solutions. Real engineers and technicians build real hardware that works in the real world in a reasonable manner within a reasonable time at a reasonable cost. True, skimping on time or money can cause mistakes, but folks whose gizmos are delayed unreasonably or cost more than is practical get their programs canceled, force the business into bankruptcy, or give the market over to the competition. Real engineers and technicians always consider cost and schedule in their work. Raising questions is important. However, we are in the business of doing things. Engineers and technicians are paid to get things done. Yes, you have to identify the problem, frame the design, identify the tests, perform the analysis, and assemble the hardware. But the goal is to solve the problem. Nobody ever said flying in space was easy. We make it look easy the same way that an Olympic champion makes her sport look easy: by working hard at improving performance every day. Better are the results of a well-defined test. Remember that a test on a laboratory bench is always an approximation of reality, and rules similar to those for good analysis also apply. One should always be mindful of Mechelay's rule: "It is better to be stupid than to run a stupid test." Often we try to overtest. If a piece of hardware passes an unbelievably difficult test, then life is good. More often when an unbelievably difficult test fails, we are left with a very long discussion of why and what was wrong in the design or execution of the test. Make sure that the test is well defined. Even then, it is important to explain to your leaders what inherent accuracy (or error) the test conditions or equipment have and what the assumptions or initial conditions were for the test. Test results without a good understanding of the test's accuracy or the pedigree of the test assumptions are worth very little. Finally, there is flight test data. Always limited, never at the edge of the envelope, it still shows how the real hardware works in a combined environment. Flight experience is dangerous because it typically doesn't show how close to the edge of the cliff the equipment is operating, but it does demonstrate how the hardware really works. A flight test is the ultimate test, again taken with the knowledge that it is probably not the extreme but something more like the middle of the environmental and systems performance. Good understanding of a problem and its solution always relies on a combination of all these methods. Be sure to lead your leaders by using all the tools you have at your disposal. At the end of the day, decisions in space flight always come down to a risk trade. Our business is not remotely safe, not in the sense that the public, the media, or our legislators use the term. Everything we do has a risk, cost, schedule, or performance trade-off. For your leaders to make an appropriate decision, you need to educate them, lead them, talk with them, and engage them in the discussion until full understanding takes place. It's your job. *

Hale, Wayne N.↗
NASA NTRS2003

Software for Better Documentation of Other Software

The Literate Programming Extraction Engine is a Practical Extraction and Reporting Language- (PERL-)based computer program that facilitates and simplifies the implementation of a concept of self-documented literate programming in a fashion tailored to the typical needs of scientists. The advantage for the programmer is that documentation and source code are written side-by-side in the same file, reducing the likelihood that the documentation will be inconsistent with the code and improving the verification that the code performs its intended functions. The advantage for the user is the knowledge that the documentation matches the software because they come from the same file. This program unifies the documentation process for a variety of programming languages, including C, C++, and several versions of FORTRAN. This program can process the documentation in any markup language, and incorporates the LaTeX typesetting software. The program includes sample Makefile scripts for automating both the code-compilation (when appropriate) and documentation-generation processes into a single command-line statement. Also included are macro instructions for the Emacs display-editor software, making it easy for a programmer to toggle between editing in a code or a documentation mode.

Pinedo, John↗
NASA NTRS2012

Human Systems Integration in Practice: Constellation Lessons Learned

NASA's Constellation program provided a unique testbed for Human Systems Integration (HSI) as a fundamental element of the Systems Engineering process. Constellation was the first major program to have HSI mandated by NASA's Human Rating document. Proper HSI is critical to the success of any project that relies on humans to function as operators, maintainers, or controllers of a system. HSI improves mission, system and human performance, significantly reduces lifecycle costs, lowers risk and minimizes re-design. Successful HSI begins with sufficient project schedule dedicated to the generation of human systems requirements, but is by no means solely a requirements management process. A top-down systems engineering process that recognizes throughout the organization, human factors as a technical discipline equal to traditional engineering disciplines with authority for the overall system. This partners with a bottoms-up mechanism for human-centered design and technical issue resolution. The Constellation Human Systems Integration Group (HSIG) was a part of the Systems Engineering and Integration (SE&I) organization within the program office, and existed alongside similar groups such as Flight Performance, Environments & Constraints, and Integrated Loads, Structures and Mechanisms. While the HSIG successfully managed, via influence leadership, a down-and-in Community of Practice to facilitate technical integration and issue resolution, it lacked parallel top-down authority to drive integrated design. This presentation will discuss how HSI was applied to Constellation, the lessons learned and best practices it revealed, and recommendations to future NASA program and project managers. This presentation will discuss how Human Systems Integration (HSI) was applied to NASA's Constellation program, the lessons learned and best practices it revealed, and recommendations to future NASA program and project managers on how to accomplish this critical function.

Zumbado, Jennifer Rochlis↗
NASA NTRS2002

The Impact of Urbanization on the Precipitation Component of the Water Cycle: A New Perspective

It is estimated that by the year 2025, 60% of the world s population will live in cities (UNFP, 1999). As cities continue to grow, urban sprawl (e.g., the expansion of urban surfaces outward into rural surroundings) creates unique problems related to land use, transportation, agriculture, housing, pollution, and development. Urban expansion also has measurable impacts on environmental processes. Urban areas modify boundary layer processes through the creation of an urban heat island (UHI). The literature indicates that the signature of the urban heat island effect may be resolvable in rainfall patterns over and downwind of metropolitan areas. However, a recent U.S. Weather Research Program panel concluded that more observational and modeling research is needed in this area (Dabberdt et al. 2000). NASA and other agencies initiated programs such as the Atlanta Land-use Analysis: Temperature and Air Quality Project (ATLANTA) (Quattrochi et al. 1998) which aimed to identify and understand how urban heat islands impact the environment. However, a comprehensive assessment of the role of urban-induced rainfall in the global water and energy cycle (GWEC) and cycling of freshwater was not a primary focus of these efforts. NASA's Earth Science Enterprise (ESE) seeks to develop a scientific understanding of the Earth system and its response to natural or human-induced changes to enable improved prediction capability for climate, weather, and natural hazards (NASA, 2000). Within this mission, the ESE has three basic thrusts: science research to increase Earth system knowledge; an applications program to transfer science knowledge to practical use in society; and a technology program to enable new, better, and cheaper capabilities for observing the earth. Within this framework, a research program is underway to further address the co-relationship between land cover use and change (e.g. urban development) and its impact on key components of the GWEC (e.g., precipitation). This presentation discusses the feasibility of using the TRMM or GPM satellite to identify precipitation anomalies likely caused by urbanization (Shepherd et al. 2002). Recent results from analyses of TRMM data around several major U.S. cities (e.g. Dallas, Atlanta, Houston) will be discussed. The presentation also summarizes a NASA-funded research effort to investigate the phenomenon of urban-induced precipitation anomalies using TRMM (future GPM) satellite-based remote sensing, an intensive ground observation/validation effort near Atlanta, and coupled atmosphere-land numerical modeling techniques.

Shephard, J. Marshal↗
NASA NTRS1997

Improving Search Properties in Genetic Programming

With the advancing computer processing capabilities, practical computer applications are mostly limited by the amount of human programming required to accomplish a specific task. This necessary human participation creates many problems, such as dramatically increased cost. To alleviate the problem, computers must become more autonomous. In other words, computers must be capable to program/reprogram themselves to adapt to changing environments/tasks/demands/domains. Evolutionary computation offers potential means, but it must be advanced beyond its current practical limitations. Evolutionary algorithms model nature. They maintain a population of structures representing potential solutions to the problem at hand. These structures undergo a simulated evolution by means of mutation, crossover, and a Darwinian selective pressure. Genetic programming (GP) is the most promising example of an evolutionary algorithm. In GP, the structures that evolve are trees, which is a dramatic departure from previously used representations such as strings in genetic algorithms. The space of potential trees is defined by means of their elements: functions, which label internal nodes, and terminals, which label leaves. By attaching semantic interpretation to those elements, trees can be interpreted as computer programs (given an interpreter), evolved architectures, etc. JSC has begun exploring GP as a potential tool for its long-term project on evolving dextrous robotic capabilities. Last year we identified representation redundancies as the primary source of inefficiency in GP. Subsequently, we proposed a method to use problem constraints to reduce those redundancies, effectively reducing GP complexity. This method was implemented afterwards at the University of Missouri. This summer, we have evaluated the payoff from using problem constraints to reduce search complexity on two classes of problems: learning boolean functions and solving the forward kinematics problem. We have also developed and implemented methods to use additional problem heuristics to fine-tune the searchable space, and to use typing information to further reduce the search space. Additional improvements have been proposed, but they are yet to be explored and implemented.

Janikow, Cezary Z.↗
NASA NTRS2001

Aerospace Technology Innovation

Commercializing technology is a daunting task. Of every 11 new product ideas, only one will successfully make it to the marketplace. Fully 46% of new product investment becomes sunk in cost. Yet, a few good companies consistently attain an 80% technology commercialization success rate and have lead the way in establishing best practices. The NASA Incubator program consists of nine incubators, each residing near a NASA research center. The purpose of the incubators is to use the best practices is to use the best practices of technology commercialization to help early stage businesses successfully launch new products that incorporate NASA technology.

Turner, Janelle↗
NASA NTRS2006

Logistics Lessons Learned in NASA Space Flight

The Vision for Space Exploration sets out a number of goals, involving both strategic and tactical objectives. These include returning the Space Shuttle to flight, completing the International Space Station, and conducting human expeditions to the Moon by 2020. Each of these goals has profound logistics implications. In the consideration of these objectives,a need for a study on NASA logistics lessons learned was recognized. The study endeavors to identify both needs for space exploration and challenges in the development of past logistics architectures, as well as in the design of space systems. This study may also be appropriately applied as guidance in the development of an integrated logistics architecture for future human missions to the Moon and Mars. This report first summarizes current logistics practices for the Space Shuttle Program (SSP) and the International Space Station (ISS) and examines the practices of manifesting, stowage, inventory tracking, waste disposal, and return logistics. The key findings of this examination are that while the current practices do have many positive aspects, there are also several shortcomings. These shortcomings include a high-level of excess complexity, redundancy of information/lack of a common database, and a large human-in-the-loop component. Later sections of this report describe the methodology and results of our work to systematically gather logistics lessons learned from past and current human spaceflight programs as well as validating these lessons through a survey of the opinions of current space logisticians. To consider the perspectives on logistics lessons, we searched several sources within NASA, including organizations with direct and indirect connections with the system flow in mission planning. We utilized crew debriefs, the John Commonsense lessons repository for the JSC Mission Operations Directorate, and the Skylab Lessons Learned. Additionally, we searched the public version of the Lessons Learned Information System (LLIS) and verified that we received the same result using the internal version of LLIS for our logistics lesson searches. In conducting the research, information from multiple databases was consolidated into a single spreadsheet of 300 lessons learned. Keywords were applied for the purpose of sorting and evaluation. Once the lessons had been compiled, an analysis of the resulting data was performed, first sorting it by keyword, then finding duplication and root cause, and finally sorting by root cause. The data was then distilled into the top 7 lessons learned across programs, centers, and activities.

Evans, William A.↗
NASA NTRS2002

The National Aeronautics and Space Administration's Earth Science Applications Program: Exploring Partnerships to Enhance Decision Making in Public Health Practice

The National Aeronautics and Space Administration (NASA), Earth Science Enterprise is engaged in applications of NASA Earth science and remote sensing technologies for public health. Efforts are focused on establishing partnerships with those agencies and organizations that have responsibility for protecting the Nation's Health. The program's goal is the integration of NASA's advanced data and technology for enhanced decision support in the areas of disease surveillance and environmental health. A focused applications program, based on understanding partner issues and requirements, has the potential to significantly contribute to more informed decision making in public health practice. This paper intends to provide background information on NASA's investment in public health and is a call for partnership with the larger practice community.

Vann, Timi S.↗
NASA NTRS1989

Two stage gear tooth dynamics program

The epicyclic gear dynamics program was expanded to add the option of evaluating the tooth pair dynamics for two epicyclic gear stages with peripheral components. This was a practical extension to the program as multiple gear stages are often used for speed reduction, space, weight, and/or auxiliary units. The option was developed for either stage to be a basic planetary, star, single external-external mesh, or single external-internal mesh. The two stage system allows for modeling of the peripherals with an input mass and shaft, an output mass and shaft, and a connecting shaft. Execution of the initial test case indicated an instability in the solution with the tooth paid loads growing to excessive magnitudes. A procedure to trace the instability is recommended as well as a method of reducing the program's computation time by reducing the number of boundary condition iterations.

Boyd, Linda S.↗
NASA NTRS1974

Assessment of the technology required to develop photovoltaic power system for large scale national energy applications

A technical assessment of a program to develop photovoltaic power system technology for large-scale national energy applications was made by analyzing and judging the alternative candidate photovoltaic systems and development tasks. A program plan was constructed based on achieving the 10 year objective of a program to establish the practicability of large-scale terrestrial power installations using photovoltaic conversion arrays costing less than $0.50/peak W. Guidelines for the tasks of a 5 year program were derived from a set of 5 year objectives deduced from the 10 year objective. This report indicates the need for an early emphasis on the development of the single-crystal Si photovoltaic system for commercial utilization; a production goal of 5 x 10 to the 8th power peak W/year of $0.50 cells was projected for the year 1985. The developments of other photovoltaic conversion systems were assigned to longer range development roles. The status of the technology developments and the applicability of solar arrays in particular power installations, ranging from houses to central power plants, was scheduled to be verified in a series of demonstration projects. The budget recommended for the first 5 year phase of the program is $268.5M.

Lutwack, R.↗
NASA NTRS1973

Apollo experience report: Reliability and quality assurance

The reliability of the Apollo spacecraft resulted from the application of proven reliability and quality techniques and from sound management, engineering, and manufacturing practices. Continual assessment of these techniques and practices was made during the program, and, when deficiencies were detected, adjustments were made and the deficiencies were effectively corrected. The most significant practices, deficiencies, adjustments, and experiences during the Apollo Program are described in this report. These experiences can be helpful in establishing an effective base on which to structure an efficient reliability and quality assurance effort for future space-flight programs.

Sperber, K. P.↗