Search NASA⌕ Search

SEARCH · Search NASA

Results for “Automated Strategies”

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.

392 records · Page 22

Automated Tracking of Shallow Maritime Clouds on Geostationary Imagery to Extract Lifecycle Characteristics

Shallow moist convection is ubiquitous throughout the tropics and represents a key player in boundary layer processes. Satellites have provided valuable insight on shallow clouds, such as size, structure, and geographical coverage, from static views of recurring cloud fields. But determining why certain cloud features appear and persist for different periods requires a time-evolving view of their behaviors. Geostationary satellites provide a unique opportunity to follow the time evolution of individual convective features, given their enhanced spatial and temporal sampling. A cloud-tracking tool was developed to identify properties of cloud lifecycle from the NASA Cloud, Aerosol, and Monsoon Processes Philippines Experiment (CAMP2EX) field campaign of 2019. The mission conducted intensive sampling of shallow cumulus in the West Pacific Ocean, in tandem with Rapid Scan imagery from the Advanced Himawari Imager (AHI) on the Japan Meteorological Agency’s (JMA) Himawari-8 satellite. Shallow cumulus were segmented according to thresholds in 0.5-km visible reflectance and with blurring techniques. Despite being limited to daytime hours, the segmentations yielded the best resolution available for capturing cloud initiation, growth, and decay. The tracking procedure is based on a computer vision package that includes Kalman filters for motion prediction, object overlap search, and the Hungarian (or Kuhn-Munkres) matching algorithm for track designation. AHI radiances available within the tracked cloud boundaries are assembled to form individual spectral histories. The resulting catalog provides thousands of cloud histories for domains measuring only a few degrees in latitude and longitude. We present an overview of the cloud-tracking tool and its results for cloud fields sampled throughout CAMP2EX by the airborne P-3. Cloud tracks were selected from about 10 flights to form ensembles, specific groups of tracks occurring in a region with airborne sampling. Cloud lifecycle properties, including duration and maximum area, are calculated for all ensemble members, and analyzed for cloud behavior and P-3 coincidences. By following this strategy, we quantitatively assess the degree of airborne sampling for specific cloud classes defined by the lifecycle calculations. We can summarize which cloud classes had more sampling, the stage of development during sampling, and general differences in character (e.g., isolated congestus vs. cold-pool producer).

Cloud Tracking↗

Astrobee: Improving Capabilities for Free Flying Robotic Technology Demonstrations

The Astrobee Project has completed three years operating inside the ISS. Three Astrobee Free Flyers reached the ISS in April 2019 and are currently hosting a variety of users. During this time, Astrobee has advanced the state of the art in free-flying robots on ISS, operated over 100 sessions, logged over 750 hours of free-flyer operation, and made several capability improvements. Astrobee’s primary objective is to provide a highly flexible and capable free-flying robotic research platform to enable future guest scientist investigations. However, Astrobee is also demonstrating the feasibility of intra-vehicular robots (IVR) for performing key caretaking functions within exploration vehicles as part of NASA’s Moon-to-Mars exploration strategy. IVR capabilities will be especially vital during uncrewed mission phases. For example, current plans call for the lunar Gateway to be uncrewed >85% of the time. Astrobee’s baseline implementation supports free-flying camera and sensor survey use cases. Astrobee guest scientists can deploy software updates and hardware payloads to extend its capabilities. Astrobee is continuously improving its navigation robustness, general flight software maturity, and ISS interior maps, both through the baseline Astrobee operations and with the help of the ISAAC project. Astrobee began with mapping, localization, and operations in the Japanese Experiment Module (JEM), and has expanded to mapping in Node 2 and the US Lab. Astrobee has improved localization and operational robustness through improved mapping processes, algorithm updates (Soussan 2022) that reduce the occurrences of lost localization as well as developed recovery techniques to return to a good localization fix when loss of localization does occur. Future guest science experiments currently in development could demonstrate cargo transfer, fault isolation, free flyer and stationary robot collaboration, microgravity fluid transfer, and new docking mechanisms, among others. This presentation will focus on 1) Astrobee technical capabilities 2) What Astrobee can provide to a guest science experiment 3) Astrobee’s recent improvements 4) Possibilities for using Astrobee for future investigations. Soussan, R., Kumar, V., Coltin, B. and Smith, T. (2022) AstroLoc: An Efficient and Robust Localizer for a Free-flying Robot, Proc. Int. Conf. Rob. Autom. (ICRA) [to appear]

Astrobee↗

Science Goal Driven Observing: A Step Towards Maximizing Science Returns and Spacecraft Autonomy

In the coming decade, the drive to increase the scientific returns on capital investment and to reduce costs will force automation to be implemented in many of the scientific tasks that have traditionally been manually overseen. Thus, spacecraft autonomy will become an even greater part of mission operations. While recent missions have made great strides in the ability to autonomously monitor and react to changing health and physical status of spacecraft, little progress has been made in responding quickly to science driven events. The new generation of space-based telescopes/observatories will see deeper, with greater clarity, and they will generate data at an unprecedented rate. Yet, while onboard data processing and storage capability will increase rapidly, bandwidth for downloading data will not increase as fast and can become a significant bottleneck and cost of a science program. For observations of inherently variable targets and targets of opportunity, the ability to recognize early if an observation will not meet the science goals of variability or minimum brightness, and react accordingly, can have a major positive impact on the overall scientific returns of an observatory and on its operational costs. If the observatory can reprioritize the schedule to focus on alternate targets, discard uninteresting observations prior to downloading, or download them at a reduced resolution its overall efficiency will be dramatically increased. We are investigating and developing tools for a science goal monitoring (SGM) system. The SGM will have an interface to help capture higher-level science goals from scientists and translate them into a flexible observing strategy that SGM can execute and monitor. SGM will then monitor the incoming data stream and interface with data processing systems to recognize significant events. When an event occurs, the system will use the science goals given it to reprioritize observations, and react appropriately and/or communicate with ground systems - both human and machine - for confirmation and/or further high priority analyses.

Koratkar, Anuradha↗

An Overview of Current Capabilities and Research Activities in the Airspace Operations Laboratory at NASA Ames Research Center

The Airspace Operations Laboratory at NASA Ames conducts research to provide a better understanding of roles, responsibilities, and requirements for human operators and automation in future air traffic management (ATM) systems. The research encompasses developing, evaluating, and integrating operational concepts and technologies for near-, mid-, and far-term air traffic operations. Current research threads include efficient arrival operations, function allocation in separation assurance and efficient airspace and trajectory management. The AOL has developed powerful air traffic simulation capabilities, most notably the Multi Aircraft Control System (MACS) that is used for many air traffic control simulations at NASA and its partners in government, academia and industry. Several additional NASA technologies have been integrated with the AOL's primary simulation capabilities where appropriate. Using this environment, large and small-scale system-level evaluations can be conducted to help make near-term improvements and transition NASA technologies to the FAA, such as the technologies developed under NASA's Air Traffic Management Demonstration-1 (ATD-1). The AOL's rapid prototyping and flexible simulation capabilities have proven a highly effective environment to progress the initiation of trajectory-based operations and support the mid-term implementation of NextGen. Fundamental questions about accuracy requirements have been investigated as well as realworld problems on how to improve operations in some of the most complex airspaces in the US. This includes using advanced trajectory-based operations and prototype tools for coordinating arrivals to converging runways at Newark airport and coordinating departures and arrivals in the San Francisco and the New York metro areas. Looking beyond NextGen, the AOL has started exploring hybrid human/automation control strategies as well as highly autonomous operations in the air traffic control domain. Initial results indicate improved capacity, low operator workload, good situation awareness and acceptability for controllers teaming with autonomous air traffic systems. While much research and development needs to be conducted to make such concepts a reality, these approaches have the potential to truly transform the airspace system towards increased mobility, safe and efficient growth in global operations and enabling many of the new vehicles and operations that are expected over the next decades. This paper describes how the AOL currently contributes to the ongoing air transportation transformation.

simulation↗

A vision architecture for the extravehicular activity retriever

The Extravehicular Activity Retriever (EVAR) is a robotic device currently being developed by the Automation and Robotics Division at the NASA Johnson Space Center to support activities in the neighborhood of the Space Shuttle or Space Station Freedom. As the name implies, the Retriever's primary function will be to provide the capability to retrieve tools, equipment or other objects which have become detached from the spacecraft, but it will also be able to rescue a crew member who may have become inadvertently de-tethered. Later goals will include cooperative operations between a crew member and the Retriever such as fetching a tool that is required for servicing or maintenance operations. This report documents a preliminary design for a Vision System Planner (VSP) for the EVAR that is capable of achieving visual objectives provided to it by a high level task planner. Typical commands which the task planner might issue to the VSP relate to object recognition, object location determination, and obstacle detection. Upon receiving a command from the task planner, the VSP then plans a sequence of actions to achieve the specified objective using a model-based reasoning approach. This sequence may involve choosing an appropriate sensor, selecting an algorithm to process the data, reorienting the sensor, adjusting the effective resolution of the image using lens zooming capability, and/or requesting the task planner to reposition the EVAR to obtain a different view of the object. An initial version of the Vision System Planner which realizes the above capabilities using simulated images has been implemented and tested. The remaining sections describe the architecture and capabilities of the VSP and its relationship to the high level task planner. In addition, typical plans that are generated to achieve visual goals for various scenarios will be discussed. Specific topics to be addressed will include object search strategies, repositioning of the EVAR to improve the quality of information obtained from the sensors, complementary usage of the sensors and redundant capabilities.

Magee, Michael↗

A vision system planner for increasing the autonomy of the Extravehicular Activity Helper/Retriever

The Extravehicular Activity Retriever (EVAR) is a robotic device currently being developed by the Automation and Robotics Division at the NASA Johnson Space Center to support activities in the neighborhood of the Space Shuttle or Space Station Freedom. As the name implies, the Retriever's primary function will be to provide the capability to retrieve tools and equipment or other objects which have become detached from the spacecraft, but it will also be able to rescue a crew member who may have become inadvertently de-tethered. Later goals will include cooperative operations between a crew member and the Retriever such as fetching a tool that is required for servicing or maintenance operations. This paper documents a preliminary design for a Vision System Planner (VSP) for the EVAR that is capable of achieving visual objectives provided to it by a high level task planner. Typical commands which the task planner might issue to the VSP relate to object recognition, object location determination, and obstacle detection. Upon receiving a command from the task planner, the VSP then plans a sequence of actions to achieve the specified objective using a model-based reasoning approach. This sequence may involve choosing an appropriate sensor, selecting an algorithm to process the data, reorienting the sensor, adjusting the effective resolution of the image using lens zooming capability, and/or requesting the task planner to reposition the EVAR to obtain a different view of the object. An initial version of the Vision System Planner which realizes the above capabilities using simulated images has been implemented and tested. The remaining sections describe the architecture and capabilities of the VSP and its relationship to the high level task planner. In addition, typical plans that are generated to achieve visual goals for various scenarios are discussed. Specific topics to be addressed will include object search strategies, repositioning of the EVAR to improve the quality of information obtained from the sensors, and complementary usage of the sensors and redundant capabilities.

Magee, Michael↗

Communication Research in Aviation and Space Operations: Symptoms and Strategies of Crew Coordination

The day-to-day operators of today's aerospace systems work under increasing pressures to accomplish more with less. They work in operational systems which are complex, technology-based, and high-risk; in which incidents and accidents have far-reaching and costly consequences. For these and other reasons, there is concern that the safety net formerly built upon redundant systems and abundant resources may become overburdened. Although we know that human ingenuity can overcome incredible odds, human nature can also fail in unpredictable ways. Over the last 20 years, a large percentage of aviation accidents and incidents have been attributed to human errors rather than hardware or environmental factors alone. A class of errors have been identified which are not due to a lack of individual, technical competencies. Rather, they are due to the failure of teams to utilize readily available resources or information in a timely fashion. These insights began a training revolution in the aviation industry called Cockpit Resource Management, which later became known as Crew Resource Management (CRM) as its concepts and applications extended to teams beyond the flightdeck. Then, as now, communication has been a cornerstone in CRM training since crew coordination and resource management largely resides within information transfer processes--both within flightcrews, and between flightcrews and the ground operations teams that support them. The research I will describe takes its roots in CRM history as we began to study communication processes in order to discover symptoms of crew coordination problems, as well as strategies of effective crew management. On the one hand, communication is often the means or the tool by which team members manage their resources, solve problems, maintain situational awareness and procedural discipline. Conversely, it is the lack of planning and resource management, loss of vigilance and situational awareness, and non-standard communications that are implicated in accidents and incidents. NASA/Ames Crew Factors researchers have been developing a model of effective crew coordination in order to understand the sources of performance breakdowns, and to develop effective solutions and interventions. Because communication is a primary mechanism by which information is received and transmitted, and because it is observable behavior, we focus on these group processes in order to identify patterns of communication that distinguish effective from less effective crew performance. Since a prime objective is to develop training recommendations for enhancing communication skills, we interpret our findings in the context of relevant task and environmental conditions, role and procedural constraints, and the normal real-time parameters of flight operations. Another research objective is to consider how communication and coordination can be enhanced through design. For example, flight deck and hardware design as well as procedural and software design may greatly influence the efficiency with which crews communicate and coordinate their work. In addition, teams and tasks may be designed, organized, and trained so that team interactions with each other are based upon appropriately shared knowledge, procedures and situation awareness. In short, we are interested in enhancing communication practices through (1) the training of specific communication skills, and (2) the design of equipment, tasks, procedures, and teams that optimize smooth, unambiguous communication processes. Two examples of communication research will be described; one in aviation and one in space operations. The first example is a high-fidelity full mission simulation study which investigates the affect of flightdeck automation on crew coordination and communication (contrasting crew performance in the DC-9 vs. MD88). Additional information is contained in the original extended abstract.

Kanki, Barbara G.↗

Wings: A New Paradigm in Human-Centered Design

Many aircraft accidents/incidents investigations cite crew error as a causal factor (Boeing Commercial Airplane Group 1996). Human factors experts suggest that crew error has many underlying causes and should be the start of an accident investigation and not the end. One of those causes, the flight deck design, is correctable. If a flight deck design does not accommodate the human's unique abilities and deficits, crew error may simply be the manifestation of this mismatch. Pilots repeatedly report that they are "behind the aircraft" , i.e., they do not know what the automated aircraft is doing or how the aircraft is doing it until after the fact. Billings (1991) promotes the concept of "human-centered automation"; calling on designers to allocate appropriate control and information to the human. However, there is much ambiguity regarding what it mean's to be human-centered. What often are labeled as "human-centered designs" are actually designs where a human factors expert has been involved in the design process or designs where tests have shown that humans can operate them. While such designs may be excellent, they do not represent designs that are systematically produced according to some set of prescribed methods and procedures. This paper describes a design concept, called Wings, that offers a clearer definition for human-centered design. This new design concept is radically different from current design processes in that the design begins with the human and uses the human body as a metaphor for designing the aircraft. This is not because the human is the most important part of the aircraft (certainly the aircraft would be useless without lift and thrust), but because he is the least understood, the least programmable, and one of the more critical elements. The Wings design concept has three properties: a reversal in the design process, from aerodynamics-, structures-, and propulsion-centered to truly human-centered; a design metaphor that guides function allocation and control and display design; and a deliberate distinction between two fundamental functions of design, to complement and to interpret human performance. The complementary function extends the human's capabilities beyond his or her current limitations - this includes sensing, computation, memory, physical force, and human decision making styles and skills. The interpretive (or hermeneutic, Hollnagel 1991) function translates information, functionality, and commands between the human and the aircraft. The Wings design concept allows the human to remain aware of the aircraft through natural interpretation. It also affords great improvements in system performance by maximizing the human's natural abilities and complementing the human's skills in a natural way. This paper will discuss the Wings design concept by describing the reversal in the traditional design process, the function allocation strategy of Wings, and the functions of complementing and interpreting the human.

Schutte, Paul C.↗

Use Computer-Aided Tools to Parallelize Large CFD Applications

Porting applications to high performance parallel computers is always a challenging task. It is time consuming and costly. With rapid progressing in hardware architectures and increasing complexity of real applications in recent years, the problem becomes even more sever. Today, scalability and high performance are mostly involving handwritten parallel programs using message-passing libraries (e.g. MPI). However, this process is very difficult and often error-prone. The recent reemergence of shared memory parallel (SMP) architectures, such as the cache coherent Non-Uniform Memory Access (ccNUMA) architecture used in the SGI Origin 2000, show good prospects for scaling beyond hundreds of processors. Programming on an SMP is simplified by working in a globally accessible address space. The user can supply compiler directives, such as OpenMP, to parallelize the code. As an industry standard for portable implementation of parallel programs for SMPs, OpenMP is a set of compiler directives and callable runtime library routines that extend Fortran, C and C++ to express shared memory parallelism. It promises an incremental path for parallel conversion of existing software, as well as scalability and performance for a complete rewrite or an entirely new development. Perhaps the main disadvantage of programming with directives is that inserted directives may not necessarily enhance performance. In the worst cases, it can create erroneous results. While vendors have provided tools to perform error-checking and profiling, automation in directive insertion is very limited and often failed on large programs, primarily due to the lack of a thorough enough data dependence analysis. To overcome the deficiency, we have developed a toolkit, CAPO, to automatically insert OpenMP directives in Fortran programs and apply certain degrees of optimization. CAPO is aimed at taking advantage of detailed inter-procedural dependence analysis provided by CAPTools, developed by the University of Greenwich, to reduce potential errors made by users. Earlier tests on NAS Benchmarks and ARC3D have demonstrated good success of this tool. In this study, we have applied CAPO to parallelize three large applications in the area of computational fluid dynamics (CFD): OVERFLOW, TLNS3D and INS3D. These codes are widely used for solving Navier-Stokes equations with complicated boundary conditions and turbulence model in multiple zones. Each one comprises of from 50K to 1,00k lines of FORTRAN77. As an example, CAPO took 77 hours to complete the data dependence analysis of OVERFLOW on a workstation (SGI, 175MHz, R10K processor). A fair amount of effort was spent on correcting false dependencies due to lack of necessary knowledge during the analysis. Even so, CAPO provides an easy way for user to interact with the parallelization process. The OpenMP version was generated within a day after the analysis was completed. Due to sequential algorithms involved, code sections in TLNS3D and INS3D need to be restructured by hand to produce more efficient parallel codes. An included figure shows preliminary test results of the generated OVERFLOW with several test cases in single zone. The MPI data points for the small test case were taken from a handcoded MPI version. As we can see, CAPO's version has achieved 18 fold speed up on 32 nodes of the SGI O2K. For the small test case, it outperformed the MPI version. These results are very encouraging, but further work is needed. For example, although CAPO attempts to place directives on the outer- most parallel loops in an interprocedural framework, it does not insert directives based on the best manual strategy. In particular, it lacks the support of parallelization at the multi-zone level. Future work will emphasize on the development of methodology to work in a multi-zone level and with a hybrid approach. Development of tools to perform more complicated code transformation is also needed.

Jin, H.↗

A METHOD TO REDUCE BIOBURDEN IN ASTROMATERIALS CURATION FACILITIES WITHOUT INTRODUCING UNWANTED CONTAMINATION

Introduction: NASA curates its Astromaterials collections in cleanrooms that are carefully monitored for particulate, inorganic and trace metal contamination. Current sample collections are not particularly susceptible to organic contamination or biological alteration. However, new collections like those from the OSIRIS-REx and Hayabusa2 missions will have organic contamination requirements and are susceptible to biodegradation. It will be necessary sterilize or at least disinfect curation labs, as well as tools and equipment in a manner that does not introduce additional contamination and does not affect the samples 1. Current curation cleaning procedures utilize isopropyl alcohol which offers some bioburden reduction, but is not effective against spore-forming bacteria or fungal spores 2. We present a modified disinfection method that uses ultrapure hydrogen peroxide to reduce bioburden inside curation labs and glove boxes without introducing contamination or damaging curation equipment. We tested this method in the meteorite processing lab as well as on a glovebox being cleaned for use in processing ANGSA (Apollo Next Generation Sample Analysis) samples and present the results of those tests. We discuss the limitations of this method and describe potential situations in which it will not be applicable. The CDC guidelines for disinfection andsterilization in healthcare facilities discusses over 15different methods for reducing bioburden in hospitalsettings 3. The most common method, steamsterilization, is well suited to sterilizing curationprocessing tools but cannot easily be used to sterilizecleanroom surfaces or large equipment likegloveboxes. Chemical sterilization with bleach(NaOCl) is also a common strategy in healthcare andpharmaceutical settings that presents materialcompatibility issues as well as serious inorganiccontamination concerns for curation facilities.Introducing a new source of Na and Cl into curationlabs is not acceptable. Other chemical methods likeethylene oxide, formaldehyde, iodophors andquaternary ammonium compounds could introduceorganic and inorganic contamination. We chose tofocus on hydrogen peroxide because it is generallycompatible with commonly used curation materialslike stainless steel, aluminum and Teflon and becauseit decomposes to oxygen and water. The CDCguidelines for hydrogen peroxide specify using a 7.5wt% solution at 25 ̊C with a contact time of 30 minutesfor high level disinfection and 6 hours for sterilization.High level disinfection is defined as a technique thatwill kill all microorganisms except large numbers ofbacterial spores 3. Methods: We prepared a solution of 7.5 wt%hydrogen peroxide from a stock solution of ultrapure30 wt% peroxide (JT Baker) and curation gradeultrapure water. This ultrapure water is already used incuration cleaning procedures and thus is not consideredand additional source of contamination. We conducteda materials compatibility test by exposing unanodizedand anodized 6061 T6 Al alloy to the peroxide solutionfor up to six hours and periodically inspecting thesurfaces for visible defects. We used this peroxide todisinfect the floor of the meteorite processing lab andthe interior of a curation glovebox by exposing thesesurfaces to the peroxide solution for 30 min. Thesurfaces were swabbed with a dry macrofoam swabbefore (Puritan Brand 2518051PFRNDFD) and afterperoxide treatment to collect microbes present on thesurfaces. Microbes were extracted by sonication fromthe swab into 15 ml of PBS (phosphate buffered saline)and inoculated onto the following media: TSA (trypticsoy agar) BA (blood agar), R2A (Reasoners 2 agar),Potato Dextrose Agar, Saboraud Dextrose Agar andSaboraud Dextrose Agar with 0.1 mg/ mlchloramphenicol. Four TSA plates and two BA plateswere inoculated with 0.1 ml of PBS each andincubated at 35 and 37 for 48 hours. Two R2A°C°Cplates (0.1 ml of PBS each) were incubated at 25 .°CThe remaining plates were inoculated with 0.2ml ofPBS and incubated at 30 ̊C for seven days. Afterincubation bacterial and fungal isolates were countedand transferred to new plates for identification usingthe VITEK24 automated system or by sequencing aportion of the barcode gene (16S rRNA for bacteria,small subunit gene for fungi) on an ABI 3500 Sangersequencer. Negative controls consisted of swabs thatwere opened in the sampling environment andanalyzed alongside the experimental samples.Results: A 6 hour exposure to hydrogen peroxideresulted in visible pitting on un-anodized 6061 Al, butnot on anodized surfaces. No visible pitting occurredafter a 30 minute exposure. Therefore, we decided tolimit our experimental tests to 30 min. exposures. 17bacterial CFU (colony forming units) representing 4distinct organisms were isolated from the meteorite processing lab floor prior to hydrogen peroxidetreatment. We were unable culture any organisms afterperoxide treatment. In the glovebox we were able toculture three bacterial CFU representing three distinctspecies, including a spore forming bacterium prior todisinfection with peroxide. After the peroxidetreatment we were unable to culture any organisms.Routine monitoring of the meteorite processing lab andthe glovebox did not indicate any increase in unwantedinorganic contamination after these peroxidetreatments. Discussion: A 30 minute treatment with 7.5 wt%peroxide appears to be an effective method forreducing bioburden on typical cleanroom surfaces. Themethod does not introduce unwanted organic orinorganic contamination and is compatible withcommonly used curation materials like stainless steel,Teflon and anodized aluminum alloys. Special careshould be taken with un-anodized aluminum.Prolonged exposure to hydrogen peroxide can causepitting on this material. We recommend using thismethod to disinfect curation labs and equipment whenbiological alteration is a concern. This method iseffective at room temperature and cannot be used todisinfect labs and equipment where the ambienttemperature is < 0 ̊C. Astromaterials samples shouldbe removed from the area where disinfection is tooccur. Hydrogen peroxide is a powerful oxidizingagent and will react with any organic carbon present inthe sample. References: [1.] Mccubbin, F. M. et al.Sp. Sci Rev(2019) doi:10.1007/s11214-019-0615-9. [2.] Mogul, R.et al.Astrobiology 18, ast.2017.1814 (2018). [3.]Rutala, W. A. & Weber, D. J. Guideline for Disinfection and Sterilization in Healthcare Facilities, 2008. [4.] Pincus, D. H. in Encyclopedia of Rapid Microbiological Methods (2005).

A. B. Regberg↗

Human Performance Contributions to Safety in Commercial Aviation

Every day in aviation, pilots, air traffic controllers, and other front-line personnel perform countless correct judgments and actions in a variety of operational environments. These judgments and actions are often the difference between an accident and a non-event. Ironically, data on these behaviors are rarely collected or analyzed. Data-driven decisions about safety management and design of safety-critical systems are limited by the available data, which influence how decision makers characterize problems and identify solutions. Large volumes of data are collected on the failures and errors that result in infrequent incidents and accidents, but in the absence of data on behaviors that result in routine successful outcomes, safety management and system design decisions are based on a small sample of nonrepresentative safety data. This assessment aimed to find and document “safety successes” made possible by human operators. With many Aeronautics Research Mission Directorate (ARMD) Programs and Projects focusing on increased automation and autonomy and decreased human involvement, failure to fully consider the human contributions to successful system performance in civil aviation represents a significant risk — a risk that has not been recognized to date. Without understanding how humans contribute to safety, any estimate of predicted safety of autonomous capabilities is incomplete and inherently suspect. Furthermore, understanding the ways in which humans contribute to safety can promote strategic interactions among safety technologies, functions, procedures and the people using them. Without this understanding, the full benefits of an integrated, optimized human/technology or autonomous system will not be realized. Historically, safety has been consistently defined in terms of the occurrence of accidents or recognized risks (i.e., in terms of things that go wrong). These adverse outcomes are explained by identifying their causes, and safety is restored by eliminating or mitigating these causes. An alternative to this approach is to focus on what goes right and identify how to replicate that process. Focusing on the rare cases of failures attributed to “human error” provides little information about why human performance routinely prevents adverse events. Hollnagel has proposed that things go right because people continuously adjust their work to match their operating conditions. These adjustments become increasingly important as systems continue to grow in complexity. Thus, the definition of safety should reflect not only “avoiding things that go wrong” but “ensuring that things go right.” The basis for safety management requires developing an understanding of everyday activities. However, few mechanisms to monitor everyday work exist in the aviation domain, which limits opportunities to learn how designs function in reality. This concept of safety thinking and safety management is reflected in the emerging field of resilience engineering. According to Hollnagel, a system is resilient if it can sustain required operations under expected and unexpected conditions by adjusting its functioning prior to, during, or following changes, disturbances, and opportunities. To explore “positive” behaviors that contribute to resilient performance in commercial aviation, the assessment team examined a range of existing sources of data about pilot and air traffic control (ATC) tower controller performance, including subjective interviews with domain experts and objective aircraft flight data records. These data were used to identify strategies that support resilient performance, methods for exploring and refining those strategies in existing data, and proposed methods for capturing and analyzing new data.

Null, Cynthia H.↗

TRIDENT Drill Validation at Mars and Lunar Analog Field Sites

Drilling on Earth is typically a human-intensive activity. Drilling on other planets is further complicated by the lack of prior local field surveys of their target area, hence blindly drilling into uncertain target rocks. Field conditions on the Moon or Mars are also different than for shallow drilling on Earth: lower temperatures and pressures, less power available, low masses (hence less weight-on-bit). Given the cost of transport from Earth, no drilling muds or working fluids are likely to be available to carry away cuttings. And impact-gardened regolith and dust vary mechanically and texturally from most terrestrial soils. The Regolith and Ice Drill for Exploration of New Terrains (TRIDENT) is a rotary-percussive 1m-class drill from Honeybee Robotics. It is low-power (rotary and percussive actuators are 200 W each) and lightweight (<20 kg) with the maximum weight on bit limited to 200 N. TRIDENT has been manifested for the Volatiles Investigating Polar Exploration Rover (VIPER) and PRIME-1 lunar south pole missions in 2024, has previously been field tested at a hot, dry analog site in the Atacama Desert, and in lunar conditions in thermal vacuum chamber tests. TRIDENT was also part of the 2019 Icebreaker Mars Discovery proposal, as well as in the Mars Life Explorer concept. During ARADS tests, drill control and fault recovery automation software enabled hands-off operations of a rover-mounted TRIDENT drill. TRIDENT Drill Analog Site Validation: Past TRIDENT tests in thermal vacuum (TVAC) chambers targeted containers of manufactured lunar simulants with added volatiles. 2022 TRIDENT ambient testing at NASA Ames drilled into cemented lunar simulant materials. Low cuttings-permeability led to cuttings buildup, and drill choking and binding was observed. The Atacama analog site in ARADS had desiccated unconsolidated sediments that did not challenge the TRIDENT design. However, lunar polar regolith is expected to be diverse and heterogeneous with varying clast sizes, with abundant impactites and perhaps subsurface ice deposits. Neither the simulants nor Atacama testing had completely covered the TRIDENT-targeted field characteristics, motivating further analog tests prior to the planned lunar missions. To gain more insight into the behavior of the TRIDENT hardware in diverse impactites and subsurface ice, and to verify the software automation in that environment, in August 2023 TRIDENT was brought to Haughton Crater, a field analog site in the Canadian Arctic. In September 2023 the same drill was brought to the Bishop Tuff in southern California to verify whether drilling binding behaviors previously seen in lunar simulant testing would be observed in naturally occurring fine-grained massive layers. The ~22 Ma Haughton Crater impact structure is located at 75 ̊22’ N, 89 ̊41’ W, on northwestern Devon Island, Nunavut, Canada. Numerous deposits of pale-grey crater-fill polymictic impact-melt breccia are found within the crater with a typical thickness reaching ~125 m or greater and covering ~60 km -2 . An approximately 600m-thick permafrost layer is also present with ice typically found within 0.5-0.6m of the surface. The volcanic tableland north of Bishop, CA exposes densely welded tuff laid down during the eruption that created the Long Valley Caldera at approximately 0.76 Ma. Extensional faults and the Owens River gorge expose cross-sections across the plateau. The area is viewed as an analog site for Mars features believed to be of pyroclastic origin. Results: Haughton Crater.Drilling tests were conducted 8-13 August 2023 at a previously undisturbed area separated 5-10 m from past years’ Drill Hill test sites (75.4208, -089.7613). In six days, TRIDENT drilled 8 holes to nearly 1 m depth each, totaling 7.80 m. The active layer/ice boundary was at ~67 cm depth, with a total of approximately 2.4 m drilled into ice or ice-cemented impact breccia. During drilling, five drill fault states were observed and successfully recovered. Holes 23-1, 4 and 7 were drilled under manual control, using Honeybee’s Thorax user interface. Holes 23-5, 6, and 8 were drilled with the Ames IBexec automated drilling control software. TRIDENT was observed to have little difficulty in the thawed uncemented impact breccia above the active layer boundary, but required percussion to make slower headway in the ice-cemented breccia. In Hole 23-7 (Fig.1), drilling slowed down in a massive unit just above the active-layer boundary (perhaps a large rock extending into the ice-cementation?), with only 7cm progress made in 27 minutes of high auger torque and constant percussion, leading to a choking fault and then a binding fault. A similar pattern had been observed in TRIDENT Rio Tinto test data from 2017 [6] as well as in the 2022laboratory tests.Bishop Tuff.A team from NASA Ames and the US Geological Survey deployed the same TRIDENT drill to Bishop Sites 1B and 1C (37.4203, -118.4289; 37.4265, -118.4215) on 13-16 September 2023, on the Bishop Tuff plateau. A third drill site was used 17-18 September 2023(37.4598, -118.3667) in an abandoned pumice mine. Four holes (totaling 2.5m depth) were drilled into the fine-grained, meters-thick tuff units at Sites 1B and 1C, and a further two boreholes (totaling 1.98m depth) were made at the pumice site. Drill behavior in the tuff below 10 cm depth was similar to that seen at 65-74 cm depth in Haughton Hole 23-7 (Fig. 1) and that seen in the 2022 lab simulant drilling. Drill safety torque limits were exceeded multiple times resulting in drill stops downhole. These freezes then required external added torques (with a pipe wrench) to resume rotation, to unstick the drill for withdrawal. To prevent this choking and binding behavior we found that more-frequent cuttings removal was necessary, e.g., reducing the “drill bite” size from the nominal 10 cm to 2 cm per bite --bringing the auger up to the surface more frequently, as seen in Bishop Site 1C Hole 2 (Fig.2). This permitted slow progress without drill binding and without external interventions. Conversely, TRIDENT drilling in the more porous pumice target material showed no cuttings buildup issue, and single bites as large as 40 cm were demonstrated. Discussion: We observed that TRIDENT easily penetrated unconsolidated heterogeneous soils (both above the active layer boundary at Haughton and previously in the Atacama). Cemented or consolidated targets that were cuttings-permeable (icy impact breccia, pumice) required more energy applied and percussion. However, in non-cuttings-permeable targets (welded microporous tuff, cemented simulants, boulder) TRIDENT was observed to be prone to excessive cuttings accumulation leading to choking/binding faults and stalling. The wedge cutting bit, used by TRIDENT in field tests and in its flight versions, pulverizes the target rock and creates fine cuttings that ideally are transported up the auger spirals for removal. In porous, fractured or vesicular target materials (such as at the Bishop pumice site) a significant portion of the cuttings are pushed aside, but for non-fractured, microporous targets the cuttings remain in the borehole and accumulate. Rock powder is relatively incompressible as a working fluid at only 100-200N downward force (TRIDENT limits) and hence eventual drilling progress slows or stops. Our recommended strategy for improving TRIDENT cuttings removal in massive target units with low cuttings-permeability is to reduce TRIDENT bite sizes when encountering these units, from 10cm to as little as 1-2cm, to effectively bail the accumulating cuttings. This approach was demonstrated to reduce choking and allowed slow progress to continue in cuttings-impermeable microporous target units (viz. the Bishop tuff in our September 2023 tests or cemented simulants in 2022 ambient tests).

robotic drilling↗

NASA Delay Tolerant Networks: Operational, Evolving, an Ready for Expansion

The future of humanity’s presence beyond Earth depends on the successful commercialization of space. For commercialization to succeed, companies need cost-efficient architectures to support their business models and minimize risks for human capital, design, development, and operations. An ongoing challenge to any space enterprise is the reality that terrestrial network technologies are insufficient to provide reliable communications between assets in space. Whether you need to ensure your valuable data is safely transmitted to the ground or reliably delivered between platforms in orbit, ensuring data integrity over intermittent communication links is a necessity. Current solutions to space communications rely heavily on manual recording, storing, and retrieval of data from spacecraft. The current standard in space communication protocols, Consultative Committee for Space Data Systems (CCSDS) Space Packet standard, is reliant on inflexible network architectures based around mission-critical infrastructure to ensure data delivery. However, by automating the recording, storing, retrieval, and verification of data with Delay Tolerant Networks (DTN), the operator is freed from the dependence on manual data management and expensive mission critical infrastructure. NASA has been developing delay tolerant systems since the late 1990’s. Multiple DTN implementations have been established during that time, each suited to different use cases. Most notably, the DTN deployment for the International Space Station (ISS) includes demonstration of two DTN technologies: Interplanetary Overlay Network (ION) and Delay Tolerant Network Marshall Enterprise (DTNME). Beyond ISS, there are even more NASA DTN deployments being considered. Now that DTN implementations are maturing, it is appropriate to reflect upon these decades of work, review the integration and performance of the existing ISS deployment, and explore the future possibilities for DTN deployment industry-wide. The ISS DTN deployment is a complex architecture consisting of different DTN implementations for the onboard and ground network environments. The ION DTN implementation is being used in the on-board network. The Huntsville Operations Support Center (HOSC) DTN implementation, DTNME, is used by the ground network supporting ISS and will soon be a second onboard gateway too. The two implementations work cooperatively to provide high fidelity data services to flight operations users and payload developers across the globe. Though the two implementations yield a quality service, limitations are evident. Data rate, data storage, and device management are constrained by the services themselves and the complex nature of the deployment. Evolution of operations concepts will improve system capabilities and stability, but significant improvement will require additional development to the implementations themselves and to the overall deployment architecture. Taking advantage of the ongoing development and operation of the ISS DTN service will be central to the success of the future evolutions of NASA DTN deployments while demonstrating the benefits of DTN’s low-cost reliable data communication protocols for the growing commercial space industry. A broad effort on DTN integration and support is necessary to promote expansion beyond existing applications. NASA is developing several useful DTN implementations across a number of different systems: ION, DTNME, High-Rate DTN (HDTN), Bundle Protocol Library (BPLib), and others. To prevent fragmentation, DTN implementation teams need to communicate, collaborate, and integrate with one another to build a solid operational foundation for new DTN deployments. The establishment of a group that can assist new DTN users with understanding the purpose of each DTN implementation, provide best practices, and serve as a general knowledge base is paramount. Potential use of DTN on Gateway and other future NASA missions further drives the need for streamlined communication between DTN implementation teams. A well-integrated and highly engaged NASA DTN working group should help provide system architects the best DTN solutions for future commercial space efforts. This paper will first review the history of DTN implementations, explore the shortcoming of current space networking solutions given available limits in technology, and therefore establish the need for Delay Tolerant Networking in space communications. Secondly, the authors will explore NASA’s array of DTN implementations and highlight their usefulness to space applications. Thirdly, this paper will establish general DTN implementation distinguishing factors. Fourthly, the authors will discuss attempts to create a generic DTN comparison matrix, and the authors will review potential future topics in DTN innovation and collaboration, highlighting several key future efforts. Finally, this paper will describe how the institution of a NASA DTN Working Group will benefit DTN adoption across the governmental and commercial space sector. The goal of this paper is to encourage enthusiasm for DTN, share strategies for improving DTN on both current and future applications, promote the collaboration of DTN implementation groups within the international space operations community, and open the conversations about DTN, priorities, complexities, and innovation to the wider spaceflight industry.

DTN↗

NASA Delay Tolerant Networks: Operational, Evolving, an Ready for Expansion

The future of humanity’s presence beyond Earth depends on the successful commercialization of space. For commercialization to succeed, companies need cost-efficient architectures to support their business models and minimize risks for human capital, design, development, and operations. An ongoing challenge to any space enterprise is the reality that terrestrial network technologies are insufficient to provide reliable communications between assets in space. Whether you need to ensure your valuable data is safely transmitted to the ground or reliably delivered between platforms in orbit, ensuring data integrity over intermittent communication links is a necessity. Current solutions to space communications rely heavily on manual recording, storing, and retrieval of data from spacecraft. The current standard in space communication protocols, Consultative Committee for Space Data Systems (CCSDS) Space Packet standard, is reliant on inflexible network architectures based around mission-critical infrastructure to ensure data delivery. However, by automating the recording, storing, retrieval, and verification of data with Delay Tolerant Networks (DTN), the operator is freed from the dependence on manual data management and expensive mission critical infrastructure. NASA has been developing delay tolerant systems since the late 1990’s. Multiple DTN implementations have been established during that time, each suited to different use cases. Most notably, the DTN deployment for the International Space Station (ISS) includes demonstration of two DTN technologies: Interplanetary Overlay Network (ION) and Delay Tolerant Network Marshall Enterprise (DTNME). Beyond ISS, there are even more NASA DTN deployments being considered. Now that DTN implementations are maturing, it is appropriate to reflect upon these decades of work, review the integration and performance of the existing ISS deployment, and explore the future possibilities for DTN deployment industry-wide. The ISS DTN deployment is a complex architecture consisting of different DTN implementations for the onboard and ground network environments. The ION DTN implementation is being used in the on-board network. The Huntsville Operations Support Center (HOSC) DTN implementation, DTNME, is used by the ground network supporting ISS and will soon be a second onboard gateway too. The two implementations work cooperatively to provide high fidelity data services to flight operations users and payload developers across the globe. Though the two implementations yield a quality service, limitations are evident. Data rate, data storage, and device management are constrained by the services themselves and the complex nature of the deployment. Evolution of operations concepts will improve system capabilities and stability, but significant improvement will require additional development to the implementations themselves and to the overall deployment architecture. Taking advantage of the ongoing development and operation of the ISS DTN service will be central to the success of the future evolutions of NASA DTN deployments while demonstrating the benefits of DTN’s low-cost reliable data communication protocols for the growing commercial space industry. A broad effort on DTN integration and support is necessary to promote expansion beyond existing applications. NASA is developing several useful DTN implementations across a number of different systems: ION, DTNME, High-Rate DTN (HDTN), Bundle Protocol Library (BPLib), and others. To prevent fragmentation, DTN implementation teams need to communicate, collaborate, and integrate with one another to build a solid operational foundation for new DTN deployments. The establishment of a group that can assist new DTN users with understanding the purpose of each DTN implementation, provide best practices, and serve as a general knowledge base is paramount. Potential use of DTN on Gateway and other future NASA missions further drives the need for streamlined communication between DTN implementation teams. A well-integrated and highly engaged NASA DTN working group should help provide system architects the best DTN solutions for future commercial space efforts. This paper will first review the history of DTN implementations, explore the shortcoming of current space networking solutions given available limits in technology, and therefore establish the need for Delay Tolerant Networking in space communications. Secondly, the authors will explore NASA’s array of DTN implementations and highlight their usefulness to space applications. Thirdly, this paper will establish general DTN implementation distinguishing factors. Fourthly, the authors will discuss attempts to create a generic DTN comparison matrix, and the authors will review potential future topics in DTN innovation and collaboration, highlighting several key future efforts. Finally, this paper will describe how the institution of a NASA DTN Working Group will benefit DTN adoption across the governmental and commercial space sector. The goal of this paper is to encourage enthusiasm for DTN, share strategies for improving DTN on both current and future applications, promote the collaboration of DTN implementation groups within the international space operations community, and open the conversations about DTN, priorities, complexities, and innovation to the wider spaceflight industry.

DTN↗