Search NASA⌕ Search

SEARCH · Search NASA

Results for “human errors.”

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 163 records · Page 9
All sourcesNASA NTRSDOE OSTI
NASA NTRS1995

Safety in the operating theatre--part 1: interpersonal relationships and team performance

The authors examine the application of interpersonal human factors training on operating room (OR) personnel. Mortality studies of OR deaths and critical incident studies of anesthesia are examined to determine the role of human error in OR incidents. Theoretical models of system vulnerability to accidents are presented with emphasis on a systems approach to OR performance. Input, process, and outcome factors are discussed in detail.

Non-NASA Center↗
NASA NTRS1990

Human factors of the high technology cockpit

The rapid advance of cockpit automation in the last decade has outstripped the ability of the human factors profession to understand the changes in human functions required. High technology cockpits require less physical (observable) workload, but are highly demanding of cognitive functions such as planning, alternative selection, and monitoring. Furthermore, automation creates opportunity for new and more serious forms of human error, and many pilots are concerned about the possibility of complacency affecting their performance. On the positive side, the equipment works as advertized with high reliability, offering highly efficient, computer-based flight. These findings from the cockpit studies probably apply equally to other industries, such as nuclear power production, other modes of transportation, medicine, and manufacturing, all of which traditionally have looked to aviation for technological leadership. The challenge to the human factors profession is to aid designers, operators, and training departments in exploiting the positive side of automation, while seeking solutions to the negative side. Viewgraphs are given.

Wiener, Earl L.↗
NASA NTRS2010

Space Flight Resource Management for ISS Operations

Although the astronaut training flow for the International Space Station (ISS) spans 2 years, each astronaut or cosmonaut often spends most of their training alone. Rarely is it operationally feasible for all six ISS crewmembers to train together, even more unlikely that crewmembers can practice living together before launch. Likewise, ISS Flight Controller training spans 18 months of learning to manage incredibly complex systems remotely in plug-and-play ground teams that have little to no exposure to crewmembers before a mission. How then do all of these people quickly become a team - a team that must respond flexibly yet decisively to a variety of situations? The answer implemented at NASA is Space Flight Resource Management (SFRM), the so-called "soft skills" or team performance skills. Based on Crew Resource Management, SFRM was developed first for shuttle astronauts and focused on managing human errors during time-critical events (Rogers, et al. 2002). Given the nature of life on ISS, the scope of SFRM for ISS broadened to include teamwork during prolonged and routine operations (O'Keefe, 2008). The ISS SFRM model resembles a star with one competency for each point: Communication, Cross-Culture, Teamwork, Decision Making, Team Care, Leadership/Followership, Conflict Management, and Situation Awareness. These eight competencies were developed with international participation by the Human Behavior and Performance Training Working Group. Over the last two years, these competencies have been used to build a multi-modal SFRM training flow for astronaut candidates and flight controllers that integrates team performance skills into the practice of technical skills. Preliminary results show trainee skill increases as the flow progresses; and participants find the training invaluable to performing well and staying healthy during ISS operations. Future development of SFRM training will aim to help support indirect handovers as ISS operations evolve further with the retirement of the Space Shuttle Program.

Schmidt, Lacey L.↗
NASA NTRS2020

Sketch-to-Solution: A Case Study in RCS Aerodynamic Interaction

Thanks to recent advances in the fields of anisotropic grid adaptation, error estimation, and geometry modeling, a sketch-to-solution work flow is now possible for viscous computational fluid dynamic (CFD) simulations. With this workflow, a CFD application engineer provides geometry, boundary conditions, and flow parameters; and the sketch-to-solution process yields a CFD simulation through automatic, error-based, grid adaptation. To explore the benefits of this nascent capability, a conventional manual grid generation work flow is compared to this new automatic grid generation work flow for a given engineering question: What are the aerodynamic interactions caused by the reaction control system (RCS) on an entry vehicle? This case study indicates that while the automatic grid generation sketch-to- solution process is not yet mature, it is preferred over a manual grid generation work flow because it greatly reduces manual labor, eliminates many opportunities for human error, and provides grid sensitivity information.

Bill Kleb↗
NASA NTRSDate not supplied

Manual Crew Override of Vehicle Landings Following G-Transitions

BACKGROUND Manual control during exploration spaceflight consists of both planned automated supervisory control and unplanned crew override. This crew override capability is critical to enable overall mission success during landing contingencies. However, the introduction of manual override capabilities must be implemented to enable crews to mitigate risks introduced by human error. Adaptive changes in the sensorimotor system can manifest during g-transitions as spatial disorientation. While training and landing aids enable successful landing through disorientation, these adaptive changes may increase cognitive demand that needs to be accounted for in the manual control strategy. It is important to characterize these effects as soon as possible following the G-transition to develop appropriate countermeasures. METHODS The following study seeks to inform the risk associated with altered sensorimotor and vestibular function impacting critical mission tasks. We aim to characterize the effects of short and long-duration weightlessness on manual control following G-transitions using simulated lunar landing on a six-degree-of-freedom (6DOF) motion base, a fixed base simulation, and a supervisory control tablet task. The primary goal is to understand the impact of spaceflight on crew ability to perform manual crew override and supervisory control. This aim will be assessed by comparing pre- versus postflight simulation performance in crewmembers assigned to either short duration (< 30 day) or long duration (~6- month) missions to the International Space Station (ISS). We hypothesize there will be postflight increases in the percent time that pilots are outside of the acceptable range for recommended vehicle state parameters and the reaction time for secondary cognitive tasks. Ground-based control subjects, who are demographically matched to the crew considering age (± 5 years) and gender, will undergo the same testing schedule as the crew to examine the effects of flight phase independent of microgravity exposure. The second aim is to examine how adaptive changes in vestibular and cognitive function relate to changes in manual crew override proficiency. Crew performance for a sensorimotor perceptual test battery will evaluate motion perception tracking, roll nulling, and/or vection sensitivity using the 6DOF motion base. We hypothesize that a higher severity of vestibular alterations will be associated with increased percent time outside of guidance limits. Motion sickness severity and sleepiness will also be evaluated. To determine the impact of “just-in-time” training, the third aim seeks to compare performance during on-board lunar landing tasks conducted late in-flight to early postflight. We hypothesize that proficiency on the “just-in-time” laptop trainer late in mission will be positively correlated with early postflight proficiency on the same task. The final aim will establish assessments of performance, training protocols, and the learning progression in a ground-control cohort of first-time users. RESULTS The assessment of the learning progression associated with the piloting task on the motion base system with thirty ground subjects will be reported. Learning curves will be established across four distinct sessions and within session considering trial difficulty. The difficulty of the landing task can be modulated with the landing divert distance and cross or downrange difficulty. Results may include changes in performance across multiple trials of a multi-attribute lunar tablet supervisory control task. Preliminary investigations of eighteen subjects who completed vestibular threshold and motion perception tasks offer expected performance ranges for upcoming preflight crew evaluations. The results yielded an average roll threshold of 0.46 ± 0.30 deg/s and an average roll nulling root mean square error performance of 2.52 ± 0.52 deg/s. RELEVANCE This project will deliver an operational demonstration of crew monitoring capability following spaceflight and identify potential deficits that may require remediation. Comparison of individual vestibular and cognitive changes with crew performance will help better characterize the manual control risks associated with sensorimotor alterations. Ground testing will evaluate learning progression, refine training protocols, and serve as a control cohort for comparisons to crew performance. ACKNOWLEDGEMENTS: The authors acknowledge contributions from Draper, the Dynamic Skills Trainer (DST) Lab, and the Software, Robotics, and Simulation Division toward the development of the lunar landing simulation platforms. This project is funded by the Human Health Countermeasures Element.

Hannah M. Weiss↗
NASA NTRS1985

Cockpit automation - In need of a philosophy

Concern has been expressed over the rapid development and deployment of automatic devices in transport aircraft, due mainly to the human interface and particularly the role of automation in inducing human error. The paper discusses the need for coherent philosophies of automation, and proposes several approaches: (1) flight management by exception, which states that as long as a crew stays within the bounds of regulations, air traffic control and flight safety, it may fly as it sees fit; (2) exceptions by forecasting, where the use of forecasting models would predict boundary penetration, rather than waiting for it to happen; (3) goal-sharing, where a computer is informed of overall goals, and subsequently has the capability of checking inputs and aircraft position for consistency with the overall goal or intentions; and (4) artificial intelligence and expert systems, where intelligent machines could mimic human reason.

Wiener, E. L.↗
NASA NTRS2016

Investigating the Simulink Auto-Coding Process

Model based program design is the most clear and direct way to develop algorithms and programs for interfacing with hardware. While coding "by hand" results in a more tailored product, the ever-growing size and complexity of modern-day applications can cause the project work load to quickly become unreasonable for one programmer. This has generally been addressed by splitting the product into separate modules to allow multiple developers to work in parallel on the same project, however this introduces new potentials for errors in the process. The fluidity, reliability and robustness of the code relies on the abilities of the programmers to communicate their methods to one another; furthermore, multiple programmers invites multiple potentially differing coding styles into the same product, which can cause a loss of readability or even module incompatibility. Fortunately, Mathworks has implemented an auto-coding feature that allows programmers to design their algorithms through the use of models and diagrams in the graphical programming environment Simulink, allowing the designer to visually determine what the hardware is to do. From here, the auto-coding feature handles converting the project into another programming language. This type of approach allows the designer to clearly see how the software will be directing the hardware without the need to try and interpret large amounts of code. In addition, it speeds up the programming process, minimizing the amount of man-hours spent on a single project, thus reducing the chance of human error as well as project turnover time. One such project that has benefited from the auto-coding procedure is Ramses, a portion of the GNC flight software on-board Orion that has been implemented primarily in Simulink. Currently, however, auto-coding Ramses into C++ requires 5 hours of code generation time. This causes issues if the tool ever needs to be debugged, as this code generation will need to occur with each edit to any part of the program; additionally, this is lost time that could be spent testing and analyzing the code. This is one of the more prominent issues with the auto-coding process, and while much information is available with regard to optimizing Simulink designs to produce efficient and reliable C++ code, not much research has been made public on how to reduce the code generation time. It is of interest to develop some insight as to what causes code generation times to be so significant, and determine if there are architecture guidelines or a desirable auto-coding configuration set to assist in streamlining this step of the design process for particular applications. To address the issue at hand, the Simulink coder was studied at a foundational level. For each different component type made available by the software, the features, auto-code generation time, and the format of the generated code were analyzed and documented. Tools were developed and documented to expedite these studies, particularly in the area of automating sequential builds to ensure accurate data was obtained. Next, the Ramses model was examined in an attempt to determine the composition and the types of technologies used in the model. This enabled the development of a model that uses similar technologies, but takes a fraction of the time to auto-code to reduce the turnaround time for experimentation. Lastly, the model was used to run a wide array of experiments and collect data to obtain knowledge about where to search for bottlenecks in the Ramses model. The resulting contributions of the overall effort consist of an experimental model for further investigation into the subject, as well as several automation tools to assist in analyzing the model, and a reference document offering insight to the auto-coding process, including documentation of the tools used in the model analysis, data illustrating some potential problem areas in the auto-coding process, and recommendations on areas or practices in the current Ramses model that should be further investigated. Several skills were required to be built up over the course of the internship project. First and foremost, my Simulink skills have improved drastically, as much of my experience had been modeling electronic circuits as opposed to software models. Furthermore, I am now comfortable working with the Simulink Auto-coder, a tool I had never used until this summer; this tool also tested my critical thinking and C++ knowledge as I had to interpret the C++ code it was generating and attempt to understand how the Simulink model affected the generated code. I had come into the internship with a solid understanding of Matlab code, but had done very little in using it to automate tasks, particularly Simulink tasks; along the same lines, I had rarely used shell script to automate and interface with programs, which I gained a fair amount of experience with this summer, including how to use regular expression. Lastly, soft-skills are an area everyone can continuously improve on; having never worked with NASA engineers, which to me seem to be a completely different breed than what I am used to (commercial electronic engineers), I learned to utilize the wealth of knowledge present at JSC. I wish I had come into the internship knowing exactly how helpful everyone in my branch would be, as I would have picked up on this sooner. I hope that having gained such a strong foundation in Simulink over this summer will open the opportunity to return to work on this project, or potentially other opportunities within the division. The idea of leaving a project I devoted ten weeks to is a hard one to cope with, so having the chance to pick up where I left off sounds appealing; alternatively, I am interested to see if there are any opening in the future that would allow me to work on a project that is more in-line with my research in estimation algorithms. Regardless, this summer has been a milestone in my professional career, and I hope this has started a long-term relationship between JSC and myself. I really enjoy the thought of building on my experience here over future summers while I work to complete my PhD at Missouri University of Science and Technology.

Gualdoni, Matthew J.↗
NASA NTRS2013

MPST Software: grl_pef_check

This innovation is a tool used to verify and validate spacecraft sequences at the predicted events file (PEF) level for the GRAIL (Gravity Recovery and Interior Laboratory, see http://www.nasa. gov/mission_pages/grail/main/index. html) mission as part of the Multi-Mission Planning and Sequencing Team (MPST) operations process to reduce the possibility for errors. This tool is used to catch any sequence related errors or issues immediately after the seqgen modeling to streamline downstream processes. This script verifies and validates the seqgen modeling for the GRAIL MPST process. A PEF is provided as input, and dozens of checks are performed on it to verify and validate the command products including command content, command ordering, flight-rule violations, modeling boundary consistency, resource limits, and ground commanding consistency. By performing as many checks as early in the process as possible, grl_pef_check streamlines the MPST task of generating GRAIL command and modeled products on an aggressive schedule. By enumerating each check being performed, and clearly stating the criteria and assumptions made at each step, grl_pef_check can be used as a manual checklist as well as an automated tool. This helper script was written with a focus on enabling the user with the information they need in order to evaluate a sequence quickly and efficiently, while still keeping them informed and active in the overall sequencing process. grl_pef_check verifies and validates the modeling and sequence content prior to investing any more effort into the build. There are dozens of various items in the modeling run that need to be checked, which is a time-consuming and errorprone task. Currently, no software exists that provides this functionality. Compared to a manual process, this script reduces human error and saves considerable man-hours by automating and streamlining the mission planning and sequencing task for the GRAIL mission.

Call, Jared A.↗
NASA NTRSDate not supplied

Supervisory Control with Dual Tasking in Post G-Transition Vehicle Landings

BACKGROUND Landing during exploration spaceflight may consist of both planned automated supervisory control and unplanned crew override. Supervisory control, particularly when performed under cognitive load with additional monitoring tasks, is essential for ensuring overall mission success during landing contingencies. Evaluating performance in a relevant Human Landing System (HLS) supervisory landing task after long-duration microgravity exposure can help identify potential risks from human error and sensorimotor alterations. Adaptive changes in the sensorimotor system can manifest during g-transitions as spatial disorientation. Although training and landing aids facilitate successful landings despite disorientation, these adaptive changes may heighten cognitive demand, which must be considered in the landing strategy. It is important to characterize these effects as soon as possible following the G-transition while the sensorimotor system remains in a state of adaptive flux to inform appropriate countermeasures. METHODS A Multi-attribute Lunar Table Battery (MALTB) task was developed for an iOS tablet device to provide flexible crew testing and training capabilities in-flight and on the ground. Elements of the tablet task were derived from the Multi-Attribute Task Battery (MATB, Cegarra et al. 2020). The task requires crew members to study a map of a planned landing site and memorizing the terrain and surface landmarks to inform potential divert maneuvers during landing. The user will oversee a series of approaches through touchdown simulations on the tablet with an external camera view of the Lunar surface. The primary responsibility of the crew member will be to execute a divert if the guidance recommended site is erroneous (e.g., the guidance projected landing target is not within 10m of the planned landing site center), or the projected landing site is no longer suitable due to surface obstacles. Considering vehicle maneuverability and fuel reserves, the divert capabilities will diminish as the task progresses. In cases where a divert is initiated, a new landing target will need to be designated by the user and will be evaluated for the proximity to the original pre-planned site. A secondary operational monitoring task will challenge the user's cognitive reserve by requiring the user to maintain several gauges within acceptable limits and respond to a visual indicator while completing the landing approach. Outcome measures include distance from the planned landing site to the user-initiate divert landing location, ground slope at the new landing site, time to divert, the ability to accomplish the secondary monitoring tasks, and perceived workload. The tablet task is being evaluated in a ground-based study to determine the learning effect of first-time users. The tablet task will be utilized in a flight study to test performance multiple times postflight. Future potential testing in-flight have been identified for capsules with iOS tablet devices. Multi-attribute Lunar Table Battery Task MALTB comprises video footage of thirty distinct landing conditions. The landing scenarios feature various landing sites (n = 3), hazardous object sizes (n = 6), sun azimuth degrees (n = 4), camera modes (i.e., fixed or gimbaled), and navigation bias (i.e., true or false). Each seventy second trial uses a sixty-degree constant glideslope trajectory. The application architecture and layout include user identification setup and data storing, a guided walkthrough of the task and interface components, practice mode for task familiarization, and a modified Bedford workload scale administered following task completion. The time-based dependent measures are saved locally to the iOS Files application and post-processing scripts have been developed to evaluate the remaining measures of performance. RELEVANCE This project will deliver an operational demonstration of crew monitoring capability following spaceflight and identify potential deficits that may require remediation. Comparison of individual vestibular and cognitive changes with crew performance will help better characterize the landing risks associated with sensorimotor alterations. ACKNOWLEDGEMENTS: This project is funded by NASA’s Human Research Program Human Health Countermeasures Element. REFERENCES Cegarra J, Valery B, Avril E, Calmettes C, Navarro J (2020) OpenMATB: A Multi-Attribute Task Battery promoting task customization, software extensibility and experiment replicability. Behav Res Methods 52:1980-1990 doi: 10.3758/s13428-020-01364-w

Matthew McDonnell↗
NASA NTRS1971

Cloud-free resolution element statistics program

Computer program computes number of cloud-free elements in field-of-view and percentage of total field-of-view occupied by clouds. Human error is eliminated by using visual estimation to compute cloud statistics from aerial photographs.

Liley, B.↗
NASA NTRS1971

Application of system safety to rail transit systems

Management emphasis on system safety in the rapid transit industry includes the granting and use of funds by the Federal Government according to systematic analysis of safety hazards in advance. Likelihood predictions that those hazards will be activated by exposure of the system to a system failure, a human error, external conditions, or combinations of these aspects determine alternatives to the assumption of risk and recommend corrections before the system is operational. Rigorous safety analyses are projected to assure operational safety for prolonged periods under varied maintenance conditions; these analysis encompass station accident possibilities as well as train-person collisions, car equipment and design, traffic control systems, and tunnel design problems.

Thomas DeW. Styles↗
NASA NTRS1974

Automatic PCM guard-band selector and calibrator

Automatic method for selection of proper guard band eliminates human error and speeds up calibration process. There is also an option which allows a single channel to be calibrated, independently of other channels. Entire system is designed on 3- by 4-inch printed-circuit cards and may be used with any pulse code modulation system.

Noda, T. T.↗
NASA NTRS1974

Apparatus for microbiological sampling

An automatic apparatus is described for microbiologically sampling surface using a cotton swab which eliminates human error. The apparatus includes a self-powered transport device, such as a motor-driven wheeled cart, which mounts a swabbing motor drive for a crank arm which supports a swab in the free end thereof. The swabbing motor is pivotably mounted and an actuator rod movable responsive to the cart traveling a predetermined distance provides lifting of the swab from the surface being sampled and reversal of the direction of travel of the cart.

Wilkins, J. R.↗
NASA NTRS1977

Remote water-monitoring system

General-purpose, water-quality sampling process detects microorganisms and integrates sampling, sample preservation, and sample analysis. System overcomes difficulties in correlation of surface measurements with remote measurements and minimizes human error in handling of samples and instrumentation.

Grana, D. C.↗
NASA NTRS1976

Retrospective studies of operating problems in air transport

An epidemiological model for the study of human errors in aviation is presented. In this approach, retrospective data are used as the basis for formulation of hypotheses as to system factors which may have contributed to such errors. Prospective experimental studies of aviation operations are also required in order to prove or disprove the hypotheses, and to evaluate the effectiveness of intervention techniques designed to solve operational problems in the aviation system.

Billings, C. E.↗