SEARCH · Engineering Papers

Results for “personal”

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.

SourceResearch connectionFrom yearThrough year

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 829 records · Page 46

All sources NASA NTRS DOE OSTI

NASA NTRS1994

A biased historical perspective of women in the engineering field at Dryden from 1946 to November 1992

Being a woman in engineering, and in particular, being the woman with the dubious distinction of having the most years at Dryden, gives the author a long-term perspective on the women who worked in the engineering field and their working environment. The working environment for the women was influenced by two main factors. One factor was the Dryden's growth of 14 persons (2 of them women) at the end of 1946 to the present size. The other factor was the need for programming knowledge when the digital computers came into use. Women have been involved with flight research at Dryden since the days of the first transonic and supersonic airplanes. This paper uses available records, along with memory, to document the number of women in engineering at Dryden, to comment about observed trends, and to make personal observations.

Powers, Sheryll Goecke↗

NASA NTRS1994

A solar photovoltaic power system for use in Antarctica

A solar photovoltaic power system was designed and built at the NASA Lewis Research Center as part of the NASA/NSF Antarctic Space Analog Program. The system was installed at a remote field camp at Lake Hoare in the Dry Valleys and provided a six-person field team with the power to run personal computers and printers, lab equipment, lightning, and a small microwave oven. The system consists of three silicon photovoltaic sub-arrays delivering 1.5 kW peak power, three lead-acid gel battery modules supplying 2.4 kWh, and electrical distribution system which delivers 120 Vac and 12 Vdc to the user. The system was modularized for each of deployment and operation. Previously the camp has been powered by diesel generators, which have proven to be both noisy and polluting. The NSF, in an effort to reduce their dependence on diesel fuel from both and environmental and cost standpoint is interested in the use of alternate forms of energy, such as solar power. Such a power system will also provide NASA with important data on system level deployment and operation in a remote location by a minimally trained crew, as well as validate initial integration concepts.

Kohout, Lisa L.↗

NASA NTRS1992

Crew decision making under stress

Flight crews must make decisions and take action when systems fail or emergencies arise during flight. These situations may involve high stress. Full-missiion flight simulation studies have shown that crews differ in how effectively they cope in these circumstances, judged by operational errors and crew coordination. The present study analyzed the problem solving and decision making strategies used by crews led by captains fitting three different personality profiles. Our goal was to identify more and less effective strategies that could serve as the basis for crew selection or training. Methods: Twelve 3-member B-727 crews flew a 5-leg mission simulated flight over 1 1/2 days. Two legs included 4 abnormal events that required decisions during high workload periods. Transcripts of videotapes were analyzed to describe decision making strategies. Crew performance (errors and coordination) was judged on-line and from videotapes by check airmen. Results: Based on a median split of crew performance errors, analyses to date indicate a difference in general strategy between crews who make more or less errors. Higher performance crews showed greater situational awareness - they responded quickly to cues and interpreted them appropriately. They requested more decision relevant information and took into account more constraints. Lower performing crews showed poorer situational awareness, planning, constraint sensitivity, and coordination. The major difference between higher and lower performing crews was that poorer crews made quick decisions and then collected information to confirm their decision. Conclusion: Differences in overall crew performance were associated with differences in situational awareness, information management, and decision strategy. Captain personality profiles were associated with these differences, a finding with implications for crew selection and training.

Orasanu, J.↗

NASA NTRS1994

Efficient mission control for the 48-satellite Globalstar Constellation

The Globalstar system is being developed by Globalstar, Limited Partnership and will utilize 48 satellites in low earth orbit (See Figure 1) to create a world-wide mobile communications system consistent with Vice President Gore's vision of a Global Information Infrastructure. As a large long term commercial system developed by a newly formed organization, Globalstar provides an excellent opportunity to explore innovative solutions for highly efficient satellite command and control. Design and operational concepts being developed are unencumbered by existing physical and organizational infrastructures. This program really is 'starting with a clean sheet of paper'. Globalstar operations challenges can appear enormous. Clearly, assigning even a single person around the clock to monitor and control each satellite is excessive for Globalstar (it would require a staff of 200! . Even with only a single contact per orbit per satellite, data acquisitions will start or stop every 45 seconds! Although essentially identical, over time the satellites will develop their own 'personalities'and will re quire different data calibrations and levels of support. This paper discusses the Globalstar system and challenges and presents engineering concepts, system design decisions, and operations concepts which address the combined needs and concerns of satellite, ground system, and operations teams. Lessons from past missions have been applied, organizational barriers broken, partnerships formed across the mission segments, and new operations concepts developed for satellite constellation management. Control center requirements were then developed from the operations concepts.

Smith, Dan↗

NASA NTRS1994

Document analysis with neural net circuits

Document analysis is one of the main applications of machine vision today and offers great opportunities for neural net circuits. Despite more and more data processing with computers, the number of paper documents is still increasing rapidly. A fast translation of data from paper into electronic format is needed almost everywhere, and when done manually, this is a time consuming process. Markets range from small scanners for personal use to high-volume document analysis systems, such as address readers for the postal service or check processing systems for banks. A major concern with present systems is the accuracy of the automatic interpretation. Today's algorithms fail miserably when noise is present, when print quality is poor, or when the layout is complex. A common approach to circumvent these problems is to restrict the variations of the documents handled by a system. In our laboratory, we had the best luck with circuits implementing basic functions, such as convolutions, that can be used in many different algorithms. To illustrate the flexibility of this approach, three applications of the NET32K circuit are described in this short viewgraph presentation: locating address blocks, cleaning document images by removing noise, and locating areas of interest in personal checks to improve image compression. Several of the ideas realized in this circuit that were inspired by neural nets, such as analog computation with a low resolution, resulted in a chip that is well suited for real-world document analysis applications and that compares favorably with alternative, 'conventional' circuits.

Graf, Hans Peter↗

NASA NTRS1995

NASA/DOD Aerospace Knowledge Diffusion Research Project. Report 35: The use of computer networks in aerospace engineering

This research used survey research to explore and describe the use of computer networks by aerospace engineers. The study population included 2000 randomly selected U.S. aerospace engineers and scientists who subscribed to Aerospace Engineering. A total of 950 usable questionnaires were received by the cutoff date of July 1994. Study results contribute to existing knowledge about both computer network use and the nature of engineering work and communication. We found that 74 percent of mail survey respondents personally used computer networks. Electronic mail, file transfer, and remote login were the most widely used applications. Networks were used less often than face-to-face interactions in performing work tasks, but about equally with reading and telephone conversations, and more often than mail or fax. Network use was associated with a range of technical, organizational, and personal factors: lack of compatibility across systems, cost, inadequate access and training, and unwillingness to embrace new technologies and modes of work appear to discourage network use. The greatest positive impacts from networking appear to be increases in the amount of accurate and timely information available, better exchange of ideas across organizational boundaries, and enhanced work flexibility, efficiency, and quality. Involvement with classified or proprietary data and type of organizational structure did not distinguish network users from nonusers. The findings can be used by people involved in the design and implementation of networks in engineering communities to inform the development of more effective networking systems, services, and policies.

Bishop, Ann P.↗

NASA NTRS1994

An experiment to assess the cost-benefits of code inspections in large scale software development

This experiment (currently in progress) is designed to measure costs and benefits of different code inspection methods. It is being performed with a real development team writing software for a commercial product. The dependent variables for each code unit's inspection are the elapsed time and the number of defects detected. We manipulate the method of inspection by randomly assigning reviewers, varying the number of reviewers and the number of teams, and, when using more than one team, randomly assigning author repair and non-repair of detected defects between code inspections. After collecting and analyzing the first 17 percent of the data, we have discovered several interesting facts about reviewers, about the defects recorded during reviewer preparation and during the inspection collection meeting, and about the repairs that are eventually made. (1) Only 17 percent of the defects that reviewers record in their preparations are true defects that are later repaired. (2) Defects recorded at the inspection meetings fall into three categories: 18 percent false positives requiring no author repair, 57 percent soft maintenance where the author makes changes only for readability or code standard enforcement, and 25 percent true defects requiring repair. (3) The median elapsed calendar time for code inspections is 10 working days - 8 working days before the collection meeting and 2 after. (4) In the collection meetings, 31 percent of the defects discovered by reviewers during preparation are suppressed. (5) Finally, 33 percent of the true defects recorded are discovered at the collection meetings and not during any reviewer's preparation. The results to date suggest that inspections with two sessions (two different teams) of two reviewers per session (2sX2p) are the most effective. These two-session inspections may be performed with author repair or with no author repair between the two sessions. We are finding that the two-session, two-person with repair (2sX2pR) inspections are the most expensive, taking 15 working days of calendar time from the time the code is ready for review until author repair is complete, whereas two-session, two-person with no repair (2sX2pN) inspections take only 10 working days, but find about 10 percent fewer defects.

Porter, A.↗

NASA NTRS1995

Ku-Band Data-Communication Adapter

Data-communication adapter circuit on single printed-circuit board serves as general-purpose interface between personal computer and satellite communication system. Designed as direct interface with Ku-band data-communication system for payloads on space shuttle, also used with any radio-frequency transmission systems. Readily installed in almost any personal computer via widely used Industry Standard Architecture (ISA) bus.

Schadelbauer, Steve↗

NASA NTRS1995

Electronic collection system for spacelab mission timeline requirements

This paper describes the Functional Objective Requirements Collection System (FORCS) software tool that has been developed for use by Principal Investigators (PI's) and Payload Element Developers (PED's) on their own personal computers to develop on-orbit timelining requirements for their payloads. The FORCS tool can be used either in a totally stand-alone mode, storing the information in a local file on the user's personal computer hard disk or in a remote mode where the user's computer is linked to a host computer containing the integrated database of the timeline requirements for all of the payloads on a mission. There are a number of features incorporated in the FORCS software to assist the user. The user may move freely back and forth between the various forms for inputting the data. Several methods are used to input the information, depending on the type of the information. These methods range from filling in text boxes, using check boxes and radio buttons, to inputting information into a spreadsheet format. There are automated features provided to assist in developing the proper format for the data, ranging from limit checking on some of the parameters to automatic conversion of different formats of time data inputs to the one standard format used for the timeline scheduling software.

Lindberg, James P.↗

NASA NTRS1996

Flying Cars

Flying cars have nearly mythical appeal to nonpilots, a group that includes almost the whole human race. The appeal resides in the perceived utility of flying cars, vehicles that offer portal-to-portal transportation, yet break the bonds of road and traffic and travel freely through the sky at the drivers will. Part of the appeal is an assumption that flying cars can be as easy to fly as to drive. Flying cars have been part of the dream of aviation since the dawn of powered flight. Glenn Curtiss built, displayed, and maybe even flew a flying car in 1917, the Curtiss Autoplane. Many roadable airplanes were built in the 1930's, like the Waterman Arrowbile and the Fulton Airphibian. Two flying cars came close to production in the early 1950's. Ted Hall built a series of flying cars culminating in the Convaircar, sponsored by Consolidated Vultee, General Motors, and Hertz. Molt Taylor built and certified his Aerocar, and Ford came close to producing them. Three Aerocars are still flyable, two in museums in Seattle and Oshkosh, and the third owned and flown by Ed Sweeny. Flying cars do have problems, which so far have prevented commercial success. An obvious problem is complexity of the vehicle, the infrastructure, or both. Another is the difficulty of matching low power for normal driving with high power in flight. An automobile uses only about 20 hp at traffic speeds, while a personal airplane needs about 160 hp at speeds typical of flight. Many automobile engines can deliver 160 hp, but not for very long. A more subtle issue involves the drag of automobiles and airplanes. A good personal airplane can fly 30 miles per gallon of fuel at 200 mph. A good sports car would need 660 hp at the same speed and would travel only 3 miles per gallon. The difference is drag area, about 4.5 sq ft for the automobile and 1.4 sq ft for the airplane. A flying car better have the drag area of the airplane, not the car!

Crow, Steven↗

NASA NTRS1995

The CAVE (TM) automatic virtual environment: Characteristics and applications

Virtual reality may best be defined as the wide-field presentation of computer-generated, multi-sensory information that tracks a user in real time. In addition to the more well-known modes of virtual reality -- head-mounted displays and boom-mounted displays -- the Electronic Visualization Laboratory at the University of Illinois at Chicago recently introduced a third mode: a room constructed from large screens on which the graphics are projected on to three walls and the floor. The CAVE is a multi-person, room sized, high resolution, 3D video and audio environment. Graphics are rear projected in stereo onto three walls and the floor, and viewed with stereo glasses. As a viewer wearing a location sensor moves within its display boundaries, the correct perspective and stereo projections of the environment are updated, and the image moves with and surrounds the viewer. The other viewers in the CAVE are like passengers in a bus, along for the ride. 'CAVE,' the name selected for the virtual reality theater, is both a recursive acronym (Cave Automatic Virtual Environment) and a reference to 'The Simile of the Cave' found in Plato's 'Republic,' in which the philosopher explores the ideas of perception, reality, and illusion. Plato used the analogy of a person facing the back of a cave alive with shadows that are his/her only basis for ideas of what real objects are. Rather than having evolved from video games or flight simulation, the CAVE has its motivation rooted in scientific visualization and the SIGGRAPH 92 Showcase effort. The CAVE was designed to be a useful tool for scientific visualization. The Showcase event was an experiment; the Showcase chair and committee advocated an environment for computational scientists to interactively present their research at a major professional conference in a one-to-many format on high-end workstations attached to large projection screens. The CAVE was developed as a 'virtual reality theater' with scientific content and projection that met the criteria of Showcase.

Kenyon, Robert V.↗

NASA NTRS1995

Emergency vehicle alert system (EVAS)

The Emergency Vehicle Alert System (EVAS) program is sponsored by the NASA/MSFC Technology Utilization (TU) office. The program was conceived to support the needs of hearing impaired drivers. The objective of the program is to develop a low-cost, small device which can be located in a personal vehicle and warn the driver, via a visual means, of the approach of an emergency vehicle. Many different technologies might be developed for this purpose and each has its own advantages and drawbacks. The requirements for an acoustic detection system, appear to be pretty stringent and may not allow the development of a reliable, low-cost device in the near future. The problems include variations in the sirens between various types of emergency vehicles, distortions due to wind and surrounding objects, competing background noise, sophisticated signal processing requirements, and omni-directional coverage requirements. Another approach is to use a Radio Frequency (RF) signal between the Emergency Vehicle (EV) and the Personal Vehicle (PV). This approach requires a transmitter on each EV and a receiver in each PV, however it is virtually assured that a system can be developed which works. With this approach, the real technology issue is how to make a system work as inexpensively as possible. This report gives a brief summary of the EVAS program from its inception and concentrates on describing the activities that occurred during Phase 4. References 1-3 describe activities under Phases 1-3. In the fourth phase of the program, the major effort to be expended was in development of the microcontroller system for the PV, refinement of some system elements and packaging for demonstration purposes. An EVAS system was developed and demonstrated which used standard spread spectrum modems with minor modifications.

Reed, Bill↗

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 NTRS1996

Building Satellites is Easier

'Building Satellites' is a story about Jim Marsh's recovery from a severe head injury told by his wife Phyllis from the moment she learned of its happening, through the ups and downs of a lengthy rehabilitation, until his return to work and daily living. It continues on, however, and narrates his battle with the more insidious Grave's disease. Told in the first person, 'Building Satellites' vividly portrays Phyllis's thoughts and feelings throughout this experience with scrupulous honestly. This is a story worth reading for many reasons. First of all, Jim was an accomplished scientist, respected by his colleagues both in this country and abroad. Secondly, it narrates the many stages of his recovery from head injury with detailed readable accuracy; it informs us as well as inspires. Finally, 'Building Satellites" also tells us the story of Phyllis Marsh's remarkable creative response to this crisis. It narrates her personal experiences as she progresses through the strange and somewhat bizarre world of medicine and rehabilitation, guided by a few basic beliefs, which she learned as a child in Iowa, that provided her with the strength to endure. 'Building Satellites' seems to reaffirm our unconscious, but settled conviction, that when confornted overnight with adversity, we are somehow given the means for coping, supported by our basic beliefs, strengthened by family and friends, and eventually learning to accept any outcome.

Marsh, Phyllis Nimmo↗

NASA NTRS1996

Thermal Excitation System for Shearography (TESS)

One of the most convenient and effective methods of stressing a part or structure for shearographic evaluation is thermal excitation. This technique involves heating the part, often convectively with a heat gun, and then monitoring with a shearography device the deformation during cooling. For a composite specimen, unbonds, delaminations, inclusions, or matrix cracking will deform during cooling differently than other more structurally sound regions and thus will appear as anomalies in the deformation field. However, one of the difficulties that cause this inspection to be dependent on the operator experience is the conventional heating process. Fanning the part with a heat gun by hand introduces a wide range of variability from person to person and from one inspection to the next. The goal of this research effort was to conduct research in the methods of thermal excitation for shearography inspection. A computerized heating system was developed for inspection of 0.61 m (24 in.) square panels. The Thermal Excitation System for Shearography (TESS) provides radiant heating with continuous digital measurement of the surface temperature profile to ensure repeatability. The TESS device functions as an accessory to any electronic shearography device.

Lansing, Matthew D.↗

NASA NTRS1995

A Comparison of Three Determinants of an Engagement Index for Use in a Simulated Flight Environment

The following report details a project design that is to be completed by the end of the year. Determining how engaged a person is at a task is rather difficult. There are many different ways to assess engagement. One such method is to use psychophysical measures. The current study focuses on three determinants of an engagement index proposed by researchers at NASA-Langley (Pope, A. T., Bogart, E. H., and Bartolome, D. S., 1995). The index (20 Beta/(Alpha+Theta)) uses EEG power bands to determine a person's level of engagement while performs a compensatory tracking task. The tracking task switches between manual and automatic modes. Participants each experience both positive and negative feedback within each trial of the three trials. The tracking task is altered in terms of difficulty depending on the participants current engagement index. The rationale of this study is to determine the optimal level of engagement to gain peak performance. The three determinants are based on an absolute index which differs from the past research which uses a slope index.

Hitt, James M., II↗

NASA NTRS1996

LTCP 2D Graphical User Interface. Application Description and User's Guide

A graphical user interface (GUI) written for NASA's LTCP (Liquid Thrust Chamber Performance) 2 dimensional computational fluid dynamic code is described. The GUI is written in C++ for a desktop personal computer running under a Microsoft Windows operating environment. Through the use of common and familiar dialog boxes, features, and tools, the user can easily and quickly create and modify input files for the LTCP code. In addition, old input files used with the LTCP code can be opened and modified using the GUI. The application is written in C++ for a desktop personal computer running under a Microsoft Windows operating environment. The program and its capabilities are presented, followed by a detailed description of each menu selection and the method of creating an input file for LTCP. A cross reference is included to help experienced users quickly find the variables which commonly need changes. Finally, the system requirements and installation instructions are provided.

Ball, Robert↗

NASA NTRS1996

Computer Program to Obtain Ordinates for NACA Airfoils

Computer programs to produce the ordinates for airfoils of any thickness, thickness distribution, or camber in the NACA airfoil series were developed in the early 1970's and are published as NASA TM X-3069 and TM X-3284. For analytic airfoils, the ordinates are exact. For the 6-series and all but the leading edge of the 6A-series airfoils, agreement between the ordinates obtained from the program and previously published ordinates is generally within 5 x 10(exp -5) chord. Since the publication of these programs, the use of personal computers and individual workstations has proliferated. This report describes a computer program that combines the capabilities of the previously published versions. This program is written in ANSI FORTRAN 77 and can be compiled to run on DOS, UNIX, and VMS based personal computers and workstations as well as mainframes. An effort was made to make all inputs to the program as simple as possible to use and to lead the user through the process by means of a menu.

Ladson, Charles L.↗