Results for “Level of Automation” — Page 19

NASA NTRS2012

NASA - easyJet Collaboration on the Human Factors Monitoring Program (HFMP) Study

This is the first annual report jointly prepared by NASA and easyJet on the work performed under the agreement to collaborate on a study of the many factors entailed in flight - and cabin-crew fatigue and documenting the decreases in performance associated with fatigue. The objective of this Agreement is to generate reliable, automated procedures that improve understanding of the levels and characteristics of flight - and cabin-crew fatigue factors, both latent and proximate, whose confluence will likely result in unacceptable flight crew performance. This study entails the analyses of numerical and textual data collected during operational flights. NASA and easyJet are both interested in assessing and testing NASA s automated capabilities for extracting operationally significant information from very large, diverse (textual and numerical) databases, much larger than can be handled practically by human experts.

Srivistava, Ashok N.↗

NASA NTRS2012

On the Transition and Migration of Flight Functions in the Airspace System

Since ~400 BC, when man first replicated flying behavior with kites, up until the turn of the 20th century, when the Wright brothers performed the first successful powered human flight, flight functions have become available to man via significant support from man-made structures and devices. Over the past 100 years or so, technology has enabled several flight functions to migrate to automation and/or decision support systems. This migration continues with the United States NextGen and Europe s Single European Sky (a.k.a. SESAR) initiatives. These overhauls of the airspace system will be accomplished by accommodating the functional capabilities, benefits, and limitations of technology and automation together with the unique and sometimes overlapping functional capabilities, benefits, and limitations of humans. This paper will discuss how a safe and effective migration of any flight function must consider several interrelated issues, including, for example, shared situation awareness, and automation addiction, or over-reliance on automation. A long-term philosophical perspective is presented that considers all of these issues by primarily asking the following questions: How does one find an acceptable level of risk tolerance when allocating functions to automation versus humans? How does one measure or predict with confidence what the risks will be? These two questions and others will be considered from the two most-discussed paradigms involving the use of increasingly complex systems in the future: humans as operators and humans as monitors.

Morris, Allan Terry↗

NASA NTRS2016

Function Allocation between Automation and Human Pilot for Airborne Separation Assurance

Maintaining safe separation between aircraft is a key determinant of the airspace capacity to handle air transportation. With the advent of satellite-based surveillance, aircraft equipped with the needed technologies are now capable of maintaining awareness of their location in the airspace and sharing it with their surrounding traffic. As a result, concepts and cockpit automation are emerging to enable delegating the responsibility of maintaining safe separation from traffic to the pilot; thus increasing the airspace capacity by alleviating the limitation of the current non-scalable centralized ground-based system. In this paper, an analysis of allocating separation assurance functions to the human pilot and cockpit automation is presented to support the design of these concepts and technologies. A task analysis was conducted with the help of Petri nets to identify the main separation assurance functions and their interactions. Each function was characterized by three behavior levels that may be needed to perform the task: skill, rule and knowledge based levels. Then recommendations are made for allocating each function to an automation scale based on their behavior level characterization and with the help of Subject matter experts.

Idris, Husni↗

NASA NTRSDate not supplied

Advanced Air Mobility Operations & Automation Part II Technical Lecture

The Airborne Collision Avoidance System X (ACAS X) is a next-generation collision avoidance tool developed to support different aircraft types and operations. The rotorcraft variant – referred to as ACAS XR – is designed to accommodate existing helicopter platforms as well as in-development, electric vertical takeoff and landing concepts, which are critical to the emerging concept of operations referred to as Advanced Air Mobility. The fundamental role of ACAS XR is to provide Detect and Avoid (DAA) and/or Collision Avoidance (CA) protection against airborne traffic. DAA alerting and guidance in the context of ACAS XR is caution-level and “suggestive,” and is to be used by the pilot if, and when, they decide to maneuver against an identified threat to DAA “well clear.” The CA alerting, by contrast, is warning-level and “directive,” with the pilot required to comply with the associated guidance to prevent a predicted Near Midair Collision (NMAC). The CA alerts generated by ACAS XR are referred to as Resolution Advisories (RAs) consistent with previous CA systems. Unlike earlier CA systems, ACAS XR issues RAs in the horizontal and vertical dimensions as well as multi-axis RAs (referred to as “Blended” RAs). According to the Minimal Operational Performance Standards of DAA systems for Unmanned Aircraft Systems, maneuvers to comply with RAs may be automated, whereas maneuvers based on DAA alerting assume a manual response. The current presentation discusses two human-in-the-loop simulations that presented rotorcraft pilots with ACAS XR alerts and guidance in eVTOL simulators with varying levels of automation. It also presents overviews of these studies as well as how they assisted live flight tests, which will occur throughout 2023.

air taxis↗

NASA NTRSDate not supplied

Helicopter Pilot Assessments of the Airborne Collision Avoidance System XR With Automated Maneuvering

The Airborne Collision Avoidance System X (ACAS X) is a next-generation collision avoidance tool developed to support different aircraft types and operations. The rotorcraft variant – referred to as ACAS XR – is designed to accommodate existing helicopter platforms as well as in-development, electric vertical takeoff and landing concepts, which are critical to the emerging concept of operations referred to as Advanced Air Mobility. The fundamental role of ACAS XR is to provide Detect and Avoid (DAA) and/or Collision Avoidance (CA) protection against airborne traffic. DAA alerting and guidance in the context of ACAS XR is caution-level and “suggestive,” and is to be used by the pilot if, and when, they decide to maneuver against an identified threat to DAA “well clear.” The CA alerting, by contrast, is warning-level and “directive,” with the pilot required to comply with the associated guidance to prevent a predicted Near Midair Collision (NMAC). The CA alerts generated by ACAS XR are referred to as Resolution Advisories (RAs) consistent with previous CA systems. Unlike earlier CA systems, ACAS XR issues RAs in the horizontal and vertical dimensions as well as multi-axis RAs (referred to as “Blended” RAs). According to the Minimal Operational Performance Standards of DAA systems for Unmanned Aircraft Systems, maneuvers to comply with RAs may be automated, whereas maneuvers based on DAA alerting assume a manual response. The current study was a human-in-the-loop simulation that presented rotorcraft pilots with ACAS XR alerts and guidance in a fixed-base eVTOL simulator with varying levels of automation. Objective results showed that pilots complied with all RAs within the expected 5-second time window and responded to DAA alerts quicker than in earlier studies with ACAS XU. Pilots often made larger horizontal deviations during Manual RAs, but often favored vertical and blended maneuvers. No NMACs occurred, and losses of well clear were mainly attributed to the obligation of the pilots and system to maneuver only after the CA phase of the encounter had begun. Other losses were due to pilots’ noncompliance or disregard for ACAS XR’s alerting and guidance. Noncompliance with RAs most frequently occurred when pilots determined they were too close to the terrain to continue to follow Descend RAs, performing vertical maneuvers instead of following Horizontal RAs, or rejecting Horizontal RA updates because they felt that enough maneuvering had been performed. Subjectively, pilots found the DAA and RA alerting and guidance intuitive and useful for VFR helicopter operations. Slightly more pilots preferred the Automated RA condition to the Manual RA condition. Lastly, they also felt that ACAS led to occasional unsafe Descend RAs. Caveats and future implications are discussed.

eVTOL↗

NASA NTRSDate not supplied

Helicopter Pilot Assessments of the Airborne Collision Avoidance System XR With Automated Maneuvering

The Airborne Collision Avoidance System X (ACAS X) is a next-generation collision avoidance tool developed to support different aircraft types and operations. The rotorcraft variant – referred to as ACAS XR – is designed to accommodate existing helicopter platforms as well as in-development, electric vertical takeoff and landing concepts, which are critical to the emerging concept of operations referred to as Advanced Air Mobility. The fundamental role of ACAS XR is to provide Detect and Avoid (DAA) and/or Collision Avoidance (CA) protection against airborne traffic. DAA alerting and guidance in the context of ACAS XR is caution-level and “suggestive,” and is to be used by the pilot if, and when, they decide to maneuver against an identified threat to DAA “well clear.” The CA alerting, by contrast, is warning-level and “directive,” with the pilot required to comply with the associated guidance to prevent a predicted Near Midair Collision (NMAC). The CA alerts generated by ACAS XR are referred to as Resolution Advisories (RAs) consistent with previous CA systems. Unlike earlier CA systems, ACAS XR issues RAs in the horizontal and vertical dimensions as well as multi-axis RAs (referred to as “Blended” RAs). According to the Minimal Operational Performance Standards of DAA systems for Unmanned Aircraft Systems, maneuvers to comply with RAs may be automated, whereas maneuvers based on DAA alerting assume a manual response. The current study was a human-in-the-loop simulation that presented rotorcraft pilots with ACAS XR alerts and guidance in a fixed-base eVTOL simulator with varying levels of automation. Objective results showed that pilots complied with all RAs within the expected 5-second time window and responded to DAA alerts quicker than in earlier studies with ACAS XU. Pilots often made larger horizontal deviations during Manual RAs, but often favored vertical and blended maneuvers. No NMACs occurred, and losses of well clear were mainly attributed to the obligation of the pilots and system to maneuver only after the CA phase of the encounter had begun. Other losses were due to pilots’ noncompliance or disregard for ACAS XR’s alerting and guidance. Noncompliance with RAs most frequently occurred when pilots determined they were too close to the terrain to continue to follow Descend RAs, performing vertical maneuvers instead of following Horizontal RAs, or rejecting Horizontal RA updates because they felt that enough maneuvering had been performed. Subjectively, pilots found the DAA and RA alerting and guidance intuitive and useful for VFR helicopter operations. Slightly more pilots preferred the Automated RA condition to the Manual RA condition. Lastly, they also felt that ACAS led to occasional unsafe Descend RAs. Caveats and future implications are discussed.

eVTOL↗

NASA NTRS1988

Artificial intelligence costs, benefits, risks for selected spacecraft ground system automation scenarios

In response to a number of high-level strategy studies in the early 1980s, expert systems and artificial intelligence (AI/ES) efforts for spacecraft ground systems have proliferated in the past several years primarily as individual small to medium scale applications. It is useful to stop and assess the impact of this technology in view of lessons learned to date, and hopefully, to determine if the overall strategies of some of the earlier studies both are being followed and still seem relevant. To achieve that end four idealized ground system automation scenarios and their attendant AI architecture are postulated and benefits, risks, and lessons learned are examined and compared. These architectures encompass: (1) no AI (baseline), (2) standalone expert systems, (3) standardized, reusable knowledge base management systems (KBMS), and (4) a futuristic unattended automation scenario. The resulting artificial intelligence lessons learned, benefits, and risks for spacecraft ground system automation scenarios are described.

Truszkowski, Walter F.↗

NASA NTRS1988

Artificial intelligence costs, benefits, and risks for selected spacecraft ground system automation scenarios

In response to a number of high-level strategy studies in the early 1980s, expert systems and artificial intelligence (AI/ES) efforts for spacecraft ground systems have proliferated in the past several years primarily as individual small to medium scale applications. It is useful to stop and assess the impact of this technology in view of lessons learned to date, and hopefully, to determine if the overall strategies of some of the earlier studies both are being followed and still seem relevant. To achieve that end four idealized ground system automation scenarios and their attendant AI architecture are postulated and benefits, risks, and lessons learned are examined and compared. These architectures encompass: (1) no AI (baseline); (2) standalone expert systems; (3) standardized, reusable knowledge base management systems (KBMS); and (4) a futuristic unattended automation scenario. The resulting artificial intelligence lessons learned, benefits, and risks for spacecraft ground system automation scenarios are described.

Truszkowski, Walter F.↗

NASA NTRS2008

Generating Customized Verifiers for Automatically Generated Code

Program verification using Hoare-style techniques requires many logical annotations. We have previously developed a generic annotation inference algorithm that weaves in all annotations required to certify safety properties for automatically generated code. It uses patterns to capture generator- and property-specific code idioms and property-specific meta-program fragments to construct the annotations. The algorithm is customized by specifying the code patterns and integrating them with the meta-program fragments for annotation construction. However, this is difficult since it involves tedious and error-prone low-level term manipulations. Here, we describe an annotation schema compiler that largely automates this customization task using generative techniques. It takes a collection of high-level declarative annotation schemas tailored towards a specific code generator and safety property, and generates all customized analysis functions and glue code required for interfacing with the generic algorithm core, thus effectively creating a customized annotation inference algorithm. The compiler raises the level of abstraction and simplifies schema development and maintenance. It also takes care of some more routine aspects of formulating patterns and schemas, in particular handling of irrelevant program fragments and irrelevant variance in the program structure, which reduces the size, complexity, and number of different patterns and annotation schemas that are required. The improvements described here make it easier and faster to customize the system to a new safety property or a new generator, and we demonstrate this by customizing it to certify frame safety of space flight navigation code that was automatically generated from Simulink models by MathWorks' Real-Time Workshop.

Denney, Ewen↗

NASA NTRS1984

Chip level modeling of LSI devices

The advent of Very Large Scale Integration (VLSI) technology has rendered the gate level model impractical for many simulation activities critical to the design automation process. As an alternative, an approach to the modeling of VLSI devices at the chip level is described, including the specification of modeling language constructs important to the modeling process. A model structure is presented in which models of the LSI devices are constructed as single entities. The modeling structure is two layered. The functional layer in this structure is used to model the input/output response of the LSI chip. A second layer, the fault mapping layer, is added, if fault simulations are required, in order to map the effects of hardware faults onto the functional layer. Modeling examples for each layer are presented. Fault modeling at the chip level is described. Approaches to realistic functional fault selection and defining fault coverage for functional faults are given. Application of the modeling techniques to single chip and bit slice microprocessors is discussed.

Armstrong, J. R.↗

DOE OSTI2024

Assembly of CMS Endcap MIP Timing Detector Module at FNAL

The High-Luminosity LHC (HL-LHC) will enable a more detailed exploration of new phenomena thanks to an anticipated increase in collisions where pileup is expected to reach approximately 200 simultaneous interactions. Many CMS systems will be significantly upgraded to prepare for this new era, including the MIP Timing Detector (MTD) project. The MTD is designed to mitigate the effect of pileup and is set to provide a timestamp accurate to 30 ~ 40 picoseconds for every event, ensuring sustained detector performance at HL-LHC. The MTD is divided into two sections, Barrel Timing Layer (BTL) and Endcap Timing Layer (ETL) which utilize different sensor and ASIC technologies due to the difference in active surfaces, irradiation conditions, and installation schedules. The ETL, composed of two double-sided disks, employs the Low Gain Avalanche Detector (LGAD) sensor and the Endcap Timing Readout Chip (ETROC). More than 8,000 modules, each consisting of four LGAD sensors and ETROCs are required for the ETL detector. These modules will be assembled using an automated robotic gantry that guarantees precise placement at a level of 10 micrometers. In addition, the full assembly of ETL modules includes film application with the jig, wire-bonding, encapsulation with the automated dispensing robot for protecting the wire-bonding, and film curing with a vacuum oven. This talk reports on the successfully completed throughput test with mockup components using the gantry and the successful assembly of real functional modules for beam tests at CERN and FNAL, including the first official ETL module.

Apresyan, Artur↗

NASA NTRSDate not supplied

Automated Flight & Contingency Management (AFCM) Power Slide

This single slide presentation gives a summary of the Advanced Air Mobility (AAM) Automated Flight & Contingency Management (AFCM) subproject, at a high level for a potentially non-NASA technical audience.

Advanced Air Mobility↗

NASA NTRS2016

Multifactor Interactions and the Air Traffic Controller: The Interaction of Situation Awareness and Workload in Association with Automation

Air traffic controllers (ATCOs) must maintain a consistently high level of human performance in order to maintain flight safety and efficiency. In current control environments, performance-influencing factors such as workload, fatigue and situation awareness (SA) can co-occur, and interact, to affect performance. However, multifactor influences and the association with performance are under-researched. This study utilized a high fidelity human in the loop enroute air traffic control simulation to investigate the relationship between workload, situation awareness and ATCO performance. The study aimed to replicate and extend Edwards, Sharples, Wilson and Kirwan's (2012) previous study and confirm multifactor interactions with a participant sample of ex-controllers. The study also aimed to extend Edwards et al.'s previous research by comparing multifactor relationships across 4 automation conditions. Results suggest that workload and SA may interact to produce a cumulative impact on controller performance, although the effect of the interaction on performance may be dependent on the context and amount of automation present. Findings have implications for human-automation teaming in air traffic control, and the potential prediction and support of ATCO performance.

Workload↗

NASA NTRS1970

Automated Engineering Design (AED); An approach to automated documentation

The automated engineering design (AED) is reviewed, consisting of a high level systems programming language, a series of modular precoded subroutines, and a set of powerful software machine tools that effectively automate the production and design of new languages. AED is used primarily for development of problem and user-oriented languages. Software production phases are diagramed, and factors which inhibit effective documentation are evaluated.

Mcclure, C. W.↗

NASA NTRS2020

Back to the Future: Surveying the Northern Hemisphere and Reprocessing the Southern TESS Data Set

TESS launched 18 April 2018 to conduct a two-year, near all-sky survey for at least 50 small, nearby exoplanets for which masses can be ascertained and whose atmospheres can be characterized by ground- and space-based follow-on observations. TESS has completed its survey of the southern hemisphere and begun its survey of the northern hemisphere, identifying >1000 candidate exoplanets and unveiling a plethora of exciting non-exoplanet astrophysics results, such as asteroseismology, asteroids, and supernova. The TESS Science Processing Operations Center (SPOC) processes the data downlinked every two weeks to generate a range of data products hosted at the Mikulski Archive for Space Telescopes (MAST). For each sector (~1 month) of observations, the SPOC calibrates the image data for both 30-min Full Frame Images (FFIs) and up to 20,000 pre-selected 2-min target star postage stamps. Data products for the 2-min targets include simple aperture photometry and systematic error-corrected flux time series. The SPOC also conducts searches for transiting exoplanets in the 2-min data for each sector and generates Data Validation time series and associated reports for each transit-like feature identified in the search. Multi-sector searches for exoplanets are conducted periodically to discover longer period planets, including those in the James Webb Continuous Viewing Zone (CVZ), which are observed for up to one year. Starting with Sector 8, scattered light from the Earth and Moon contaminated significant portions of the data in each orbit. We have developed algorithms for automated identification of the scattered light features at the individual target level. Previously, data for all stars on a CCD affected by scattered light were manually excluded. The automated flagging will allow us to retain significantly more data for stars that are not affected by the scattered light even though it is occurring elsewhere on the CCD. We also discuss enhancements to the SPOC pipeline and the newly available FFI light curves. The TESS Mission is funded by NASA's Science Mission Directorate as an Astrophysics Explorer Mission.

Jenkins, Jon M.↗

NASA NTRS2013

Spitzer Telemetry Processing System

The Spitzer Telemetry Processing System (SirtfTlmProc) was designed to address objectives of JPL's Multi-mission Image Processing Lab (MIPL) in processing spacecraft telemetry and distributing the resulting data to the science community. To minimize costs and maximize operability, the software design focused on automated error recovery, performance, and information management. The system processes telemetry from the Spitzer spacecraft and delivers Level 0 products to the Spitzer Science Center. SirtfTlmProc is a unique system with automated error notification and recovery, with a real-time continuous service that can go quiescent after periods of inactivity. The software can process 2 GB of telemetry and deliver Level 0 science products to the end user in four hours. It provides analysis tools so the operator can manage the system and troubleshoot problems. It automates telemetry processing in order to reduce staffing costs.

Stanboli, Alice↗

NASA NTRS2013

Planetary Protection Bioburden Analysis Program

This program is a Microsoft Access program that performed statistical analysis of the colony counts from assays performed on the Mars Science Laboratory (MSL) spacecraft to determine the bioburden density, 3-sigma biodensity, and the total bioburdens required for the MSL prelaunch reports. It also contains numerous tools that report the data in various ways to simplify the reports required. The program performs all the calculations directly in the MS Access program. Prior to this development, the data was exported to large Excel files that had to be cut and pasted to provide the desired results. The program contains a main menu and a number of submenus. Analyses can be performed by using either all the assays, or only the accountable assays that will be used in the final analysis. There are three options on the first menu: either calculate using (1) the old MER (Mars Exploration Rover) statistics, (2) the MSL statistics for all the assays, or This software implements penetration limit equations for common micrometeoroid and orbital debris (MMOD) shield configurations, windows, and thermal protection systems. Allowable MMOD risk is formulated in terms of the probability of penetration (PNP) of the spacecraft pressure hull. For calculating the risk, spacecraft geometry models, mission profiles, debris environment models, and penetration limit equations for installed shielding configurations are required. Risk assessment software such as NASA's BUMPERII is used to calculate mission PNP; however, they are unsuitable for use in shield design and preliminary analysis studies. The software defines a single equation for the design and performance evaluation of common MMOD shielding configurations, windows, and thermal protection systems, along with a description of their validity range and guidelines for their application. Recommendations are based on preliminary reviews of fundamental assumptions, and accuracy in predicting experimental impact test results. The software is programmed in Visual Basic for Applications for installation as a simple add-in for Microsoft Excel. The user is directed to a graphical user interface (GUI) that requires user inputs and provides solutions directly in Microsoft Excel workbooks. This work was done by Shannon Ryan of the USRA Lunar and Planetary Institute for Johnson Space Center. Further information is contained in a TSP (see page 1). MSC- 24582-1 Micrometeoroid and Orbital Debris (MMOD) Shield Ballistic Limit Analysis Program Lyndon B. Johnson Space Center, Houston, Texas Commercially, because it is so generic, Enigma can be used for almost any project that requires engineering visualization, model building, or animation. Models in Enigma can be exported to many other formats for use in other applications as well. Educationally, Enigma is being used to allow university students to visualize robotic algorithms in a simulation mode before using them with actual hardware. This work was done by David Shores and Sharon P. Goza of Johnson Space Center; Cheyenne McKeegan, Rick Easley, Janet Way, and Shonn Everett of MEI Technologies; Mark Manning of PTI; and Mark Guerra, Ray Kraesig, and William Leu of Tietronix Software, Inc. For further information, contact the JSC Innovation Partnerships Office at (281) 483-3809. MSC-24211-1 Spitzer Telemetry Processing System NASA's Jet Propulsion Laboratory, Pasadena, California The Spitzer Telemetry Processing System (SirtfTlmProc) was designed to address objectives of JPL's Multi-mission Image Processing Lab (MIPL) in processing spacecraft telemetry and distributing the resulting data to the science community. To minimize costs and maximize operability, the software design focused on automated error recovery, performance, and information management. The system processes telemetry from the Spitzer spacecraft and delivers Level 0 products to the Spitzer Science Center. SirtfTlmProc is a unique system with automated error notification and recovery, with a real-time continuous service that can go quiescent after periods of inactivity. The software can process 2 GB of telemetry and deliver Level 0 science products to the end user in four hours. It provides analysis tools so the operator can manage the system and troubleshoot problems. It automates telemetry processing in order to reduce staffing costs. This work was done by Alice Stanboli, Elmain M. Martinez, and James M. McAuley of Caltech for NASA's Jet Propulsion Laboratory. For more information, contact iaoffice @jpl.nasa.gov. This software is available for commercial licensing. Please contact Dan Broderick at Daniel.F. Broderick@jpl.nasa.gov. Refer to NPO-47803. NASA Tech Briefs, September 2013 29 This rapid response computer program predicts Orbiter Wing Leading Edge (WLE) damage caused by ice or foam impact during a Space Shuttle launch (Program "IMPACT2"). The program was developed after the Columbia accident in order to assess quickly WLE damage due to ice, foam, or metal impact (if any) during a Shuttle launch. IMPACT2 simulates an impact event in a few minutes for foam impactors, and in seconds for ice and metal impactors. The damage criterion is derived from results obtained from one sophisticated commercial program, which requires hours to carry out simulations of the same impact events. The program was designed to run much faster than the commercial program with prediction of projectile threshold velocities within 10 to 15% of commercial-program values. The mathematical model involves coupling of Orbiter wing normal modes of vibration to nonlinear or linear springmass models. IMPACT2 solves nonlinear or linear impact problems using classical normal modes of vibration of a target, and nonlinear/ linear time-domain equations for the projectile. Impact loads and stresses developed in the target are computed as functions of time. This model is novel because of its speed of execution. A typical model of foam, or other projectile characterized by material nonlinearities, impacting an RCC panel is executed in minutes instead of hours needed by the commercial programs. Target damage due to impact can be assessed quickly, provided that target vibration modes and allowable stress are known. This work was done by Robert Clark, Jr., Paul Cotter, and Constantine Michalopoulos of The Boeing Company for Johnson Space Center. For further information, contact the JSC Innovation Partnerships Office at (281) 483-3809. MSC-24988-1 Wing Leading Edge RCC Rapid Response Damage Prediction Tool (IMPACT2) Lyndon B. Johnson Space Center, Houston, Texas (3) the MSL statistics for only the accountable assays. Other options on the main menu include a data editing form and utility programs that produce various reports requested by the microbiologists and the project, and tools to generate the groupings for the final analyses. The analyses can be carried out in three ways: Each assay can be treated separately, the assays can be collectively treated for the whole zone as a group, or the assays can be collected in groups designated by the JPL Planetary Protection Manager. The latter approach was used to generate the final report because assays on the same equipment or similar equipment can be assumed to have been exposed to the same environment and cleaning. Thus, the statistics are improved by having a larger population, thereby reducing the standard deviation by the square root of N. For each method mentioned above, three reports are available. The first is a detailed report including all the data. This version was very useful in verifying the calculations. The second is a brief report that is similar to the full detailed report, but does not print out the data. The third is a grand total and summary report in which each assay requires only one line. For the first and second reports, most of the calculations are performed in the report section itself. For the third, all the calculations are performed directly in the query bound to the report. All the numerical results were verified by comparing them with Excel templates, then exporting the data from the Planetary Protection Analysis program to Excel.

Beaudet, Robert A.↗

NASA NTRS1986

Report on Computer Programs for Robotic Vision

Collection of programs supports robotic research. Report describes computer-vision software library NASA's Jet Propulsion Laboratory. Programs evolved during past 10 years of research into robotics. Collection includes low- and high-level image-processing software proved in applications ranging from factory automation to spacecraft tracking and grappling. Programs fall into several overlapping categories. Image utilities category are low-level routines that provide computer access to image data and some simple graphical capabilities for displaying results of image processing.

Cunningham, R. T.↗