Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “gateway deployment”

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 55 records · Page 3

Medical Data Architecture Platform and Recommended Requirements for A Medical Data System for Exploration Missions

Minimize or reduce the risk of adverse health outcomes and decrements in performance due to in-flight medical capabilities on human exploration missions. To mitigate this risk, the ExMC MDA project addresses the technical limitations identified in ExMC Gap Med 07: We do not have the capability to comprehensively process medically relevant information to support medical operations during exploration missions. This gap identifies that the current in-flight medical data management includes a combination of data collection and distribution methods that are minimally integrated with on-board medical devices and systems. Furthermore, there are a variety of data sources and methods of data collection. For an exploration mission, the seamless management of such data will enable a more medically autonomous crew than the current paradigm of medical data management on the International Space Station. ExMC has recognized that in order to make informed decisions about a medical data architecture framework, current methods for medical data management must not only be understood, but an architecture must also be identified that provides the crew with actionable insight to medical conditions. This medical data architecture will provide the necessary functionality to address the challenges of executing a self-contained medical system that approaches crew health care delivery without assistance from ground support. Hence, the products derived from the third MDA prototype development will directly inform exploration medical system requirements for Level of Care IV in Gateway missions.In fiscal year 2019, the MDA project developed Test Bed 3, the third iteration in a series of prototypes, that featured integrations with cognition tool data, ultrasound image analytics and core Flight Software (cFS). Maintaining a layered architecture design, the framework implemented a plug-in, modular approach in the integration of these external data sources. An early version of MDA Test Bed 3 software was deployed and operated in a simulated analog environment that was part of the Next Space Technologies for Exploration Partnerships (NextSTEP) Gateway tests of multiple habitat prototypes. In addition, the MDA team participated in the Gateway Test and Verification Demonstration, where the MDA cFS applications was integrated with Gateway-in-a-Box software to send and receive medically relevant data over a simulated vehicle network. This software demonstration was given to ExMC and Gateway Program stakeholders at the NASA Johnson Space Center Integrated Power, Avionics and Software (iPAS) facility. Also, the integrated prototypes served as a vehicle to provide Level 5 requirements for the Crew Health and Performance Habitat Data System for Gateway Missions (Medical Level of Care IV). In the upcoming fiscal year, the MDA project will continue to provide systems engineering and vertical prototypes to refine requirements for medical Level of Care IV and inform requirements for Level of Care V.

Krihak, M.↗

Medical Data Architecture Platform and Recommended Requirements for a Medical Data System for Exploration Missions

The Medical Data Architecture (MDA) project supports the Exploration Medical Capability (ExMC) risk to minimize or reduce the risk of adverse health outcomes and decrements in performance due to in-flight medical capabilities on human exploration missions. To mitigate this risk, the ExMC MDA project addresses the technical limitations identified in ExMC Gap Med 07: We do not have the capability to comprehensively process medically- relevant information to support medical operations during exploration missions. This gap identifies that the current in-flight medical data management includes a combination of data collection and distribution methods that are minimally integrated with on-board medical devices and systems. Furthermore, there are a variety of data sources and methods of data collection. For an exploration mission, the seamless management of such data will enable a more medically autonomous crew than the current paradigm of medical data management on the International Space Station. ExMC has recognized that in order to make informed decisions about a medical data architecture framework, current methods for medical data management must not only be understood, but an architecture must also be identified that provides the crew with actionable insight to medical conditions. This medical data architecture will provide the necessary functionality to address the challenges of executing a self-contained medical system that approaches crew health care delivery without assistance from ground support. Hence, the products derived from the third MDA prototype development will directly inform exploration medical system requirements for Level of Care IV in Gateway missions. In fiscal year 2019, the MDA project developed Test Bed 3, the third iteration in a series of prototypes, that featured integrations with cognition tool data, ultrasound image analytics and core Flight Software (cFS). Maintaining a layered architecture design, the framework implemented a plug-in, modular approach in the integration of these external data sources. An early version of MDA Test Bed 3 software was deployed and operated in a simulated analog environment that was part of the Next Space Technologies for Exploration Partnerships (NextSTEP) Gateway tests of multiple habitat prototypes. In addition, the MDA team participated in the Gateway Test and Verification Demonstration, where the MDA cFS applications was integrated with Gateway-in-a-Box software to send and receive medically relevant data over a simulated vehicle network. This software demonstration was given to ExMC and Gateway Program stakeholders at the NASA Johnson Space Center Integrated Power, Avionics and Software (iPAS) facility. Also, the integrated prototypes served as a vehicle to provide Level 5 requirements for the Crew Health and Performance Habitat Data System for Gateway Missions (Medical Level of Care IV). In the upcoming fiscal year, the MDA project will continue to provide systems engineering and vertical prototypes to refine requirements for medical Level of Care IV and inform requirements for Level of Care V.

Krihak, M.↗

Deployment and Evaluation of SciStream on OLCF's Advanced Computing Ecosystem (ACE)

The growing demand for real-time analysis, experimental steering, and decision-making in scientific workflows has created a need for tightly coupled integrations between experimental facilities and high-performance computing (HPC) systems. The Department of Energy’s Integrated Research Infrastructure (IRI) initiative highlights data streaming as a key capability for enabling memory-to-memory data transfers, bypassing the limitations of traditional store-and-forward models. SciStream is a toolkit developed by researchers at Argonne National Laboratory (ANL) to support such streaming by addressing cross-domain security, delegated authentication, and application transparency. We deployed and evaluated SciStream on the Oak Ridge Leadership Computing Facility’s (OLCF) Advanced Computing Ecosystem (ACE) infrastructure, leveraging the Olivine OpenShift cluster and its high-bandwidth Data Streaming Nodes (DSNs) as gateway nodes. Our evaluation included synthetic streaming workloads derived from IRI science workflows, a streaming simulator, and integration with RabbitMQ to handle low-level messaging. This report documents the deployment process, performance evaluation, and challenges encountered, along with opportunities for future improvements.

97 MATHEMATICS AND COMPUTING↗

Moon to Mars (M2M) Habitation Considerations: A Snap Shot As of January 2022

The following NASA Technical Memorandum (TM) is intended to provide a snapshot in time of NASA’s current considerations (ground rules and assumptions, functional allocations, logistics) for habitation systems for the lunar surface (non-roving) and Mars transits. As NASA continues to refine the reference designs to meet the needs of an evolving architecture, it is expected that this information will also be updated as a result. Where appropriate, relevant publicly released documents will be referenced to provide further detail. NASA’s human lunar exploration plan under the Artemis program calls for achieving the goal of sending the first woman and first person of color to the surface of the Moon in the mid- 2020s and working toward sustainable exploration by the end of the decade. Working with both commercial and international partners, NASA will establish a permanent human presence on the Moon to uncover new scientific discoveries and lay the foundation for private companies to build a lunar economy. Longer duration missions on the lunar surface and in lunar orbit will also serve as a test bed for technologies to support future Mars exploration campaigns. The agency will use what we learn on the Moon to prepare for humanity's next giant leap – sending astronauts to Mars. NASA intends to establish a sustained lunar presence with the development of the Artemis Base Camp to prove technologies and capabilities that will one day enable humans to live and work on Mars, beginning with core elements including the Lunar Terrain Vehicle (LTV), the Pressurized Rover (PR), the lunar Surface Habitat (SH), power systems, and in-situ resource utilization (ISRU) systems. For in space operations and eventual transport of humans to Mars, NASA will utilize a Mars Transit Habitat (TH). Following deployment, the TH will complete a series of longer duration missions and shakedown testing while docked at Gateway, leveraging Gateway’s habitation redundancy for safety measures. Proposed Gateway-TH missions will far exceed the longest duration cislunar human missions to date. They will be the first operational readiness tests of our long-duration deep space systems, and of the split crew (two crew on the surface, two crew in space) operations that are vital to the approach for the first human Mars mission. Both the SH and TH are major architectural elements of NASA’s Moon to Mars (M2M) approach, each with very different concepts of operation. The SH is intended for use on the lunar surface as a home for astronauts, surface operations base, science facility, hub for communications, extravehicular activity (EVA) equipment repair site, waste processing facility, and supply hub. It serves as an enabler for a sustained surface presence and preparation for partial gravity operations during Mars missions. The SH will be designed to be self-sufficient for operations on the lunar surface. The SH will independently provide several functions, including its own power generation, energy storage capability, sleep quarters, hygiene areas, work areas, and dining areas. It will be capable of communicating with surface assets, orbital assets, and directly with Earth ground stations. It is planned to operate with two crew in the habitat for ~28- day stays with crew swap-outs in which the PR crew of two trades places with the habitat crew. During the swap-out, the habitat will nominally support four crew for a short period of time. For contingency scenarios, the habitat must also be capable of supporting four crew for up to 7 days. The TH will be designed to be capable of up to ~1,200-day Mars missions with the ability to carry all food and supplies needed to support a crew of four for this duration. An assumed Mars mission profile for the TH is to carry crew and supplies for ~850-day roundtrips between Earth and Mars orbit that allows 30-day stays on the Martian surface. To test the systems for this long journey, the TH will be used to extend the duration of missions at Gateway, enabling the orbiting outpost to be used as a Mars analog. These analog missions will be accomplished by attaching the TH to Gateway and conducting lunar surface operations from the TH. The TH may also need to perform free-flying shakedown missions to test out all systems prior to leaving for Mars. The habitat provides many critical functions including: a contingency airlock, crew quarters, galley, hygiene areas, safe haven capability, and science equipment. It can receive docked items from either axial end or on a radial port.

Habitat↗

Performance Comparison of Wireless Sensor Network Standard Protocols in an Aerospace Environment: ISA100.11a and ZigBee

Wireless Sensor Networks (WSNs) can provide a substantial benefit in spacecraft systems, reducing launch weight and providing unprecedented flexibility by allowing instrumentation capabilities to grow and change over time. Achieving data transport reliability on par with that of wired systems, however, can prove extremely challenging in practice. Fortunately, much progress has been made in developing standard WSN radio protocols for applications from non-critical home automation to mission-critical industrial process control. The relative performances of candidate protocols must be compared in representative aerospace environments, however, to determine their suitability for spaceflight applications. In this paper, we will present the results of a rigorous laboratory analysis of the performance of two standards-based, low power, low data rate WSN protocols: ZigBee Pro and ISA100.11a. Both are based on IEEE 802.15.4 and augment that standard's specifications to build complete, multi-hop networking stacks. ZigBee Pro targets primarily the home and office automation markets, providing an ad-hoc protocol that is computationally lightweight and easy to implement in inexpensive system-on-a-chip components. As a result of this simplicity, however, ZigBee Pro can be susceptible to radio frequency (RF) interference. ISA100.11a, on the other hand, targets the industrial process control market, providing a robust, centrally-managed protocol capable of tolerating a significant amount of RF interference. To achieve these gains, a coordinated channel hopping mechanism is employed, which entails a greater computational complexity than ZigBee and requires more sophisticated and costly hardware. To guide future aerospace deployments, we must understand how well these standards relatively perform in analog environments under expected operating conditions. Specifically, we are interested in evaluating goodput -- application level throughput -- in a representative crewed environment in the presence of varying levels of 802.11g Wi-Fi traffic. To do so, we use the NASA Johnson Space Center Wireless Habitat Testbed (WHT), a metallic, habitation-sized module designed for co-existence testing of wireless systems. In its quiescent state, the sealed WHT provides an RF-quiet environment to which we can selectively add interfering systems; it also provides a realistic level of multi-path self-interference for systems under investigation. In our test, we deploy two representative five node networks, configured in a star topology with all nodes reporting directly to a WSN gateway. Each ZigBee network WSN node is built using a Texas Instruments (TI) CC2530 system-on-a-chip radio running TI's ZigBee Pro Z-stack. Each ISA100.11a network node is built using a Nivis VersaNode 210 system-on-a-chip radio. In both cases, radios interface with TI MSP430-F5438 microcontroller implementing a common test application. Interference is provided by a D-link 802.11g Wi-Fi router transporting traffic generated using the Iperf network testing tool. For the single-channel ZigBee network, effects of both direct and indirect Wi-Fi interference are evaluated. For the channel-hopping ISA100.11a network, effects of interference from multiple Wi-Fi routers configured in non-overlapping 802.11g channels are evaluated. Our results show that, in general, the more lightweight ZigBee network performs well at low interference levels, but performance degrades as interference increases. Conversely, the more complex and costly ISA100.11a network continues to perform well as Wi-Fi interference levels increase.

Wagner, Raymond S.↗

xPLSS Structural Backplate Design, Manufacture, and Test Overview

NASA Johnson Space Center (JSC) has been developing and building a new detailed design of the Exploration Extravehicular Mobility Unit (xEMU) space suit to support future International Space Station (ISS) and Lunar Artemis missions. The Exploration Portable Life Support System (xPLSS) of the xEMU contains some clever new technologies to meet the requirements to provide Extra Vehicular Activity (EVA) capability on the ISS and the Moon. The suit must interface with and fit through ports and airlocks of at least three vehicles: ISS, Human Landing System (HLS), and Gateway. The first partial xPLSS experimental flight unit called SWME EXPRESS Rack Flight Experiment (SERFE) that was a rack-deployed thermal control system payload on the ISS for two years (2020-2022). The first complete assembly of the xEMU was built as a Design Verification Test (DVT) unit (2022); similar to but more extensive than an Engineering Development Unit (EDU). The xPLSS Backplate serves not only as the structural backbone of the xPLSS and SERFE systems but also contains innovative design features to reduce the: mass, complexity, parts count, number ofseals (and therefore leak potential), and outer dimensions of the entire assembly. This paper provides an overview of these new design features, manufacturing processes, system interfaces, and SERFE/DVT test results of the Backplate as part of the xPLSS/xEMU.

xPLSS↗

xPLSS Structural Backplate Design, Manufacture, and Test Overview

NASA Johnson Space Center (JSC) has been developing and building a new detailed design of the Exploration Extravehicular Mobility Unit (xEMU) space suit to support future International Space Station (ISS) and Lunar Artemis missions. The Exploration Portable Life Support System (xPLSS) of the xEMU contains some clever new technologies to meet the requirements to provide Extra Vehicular Activity (EVA) capability on the ISS and the Moon. The suit must interface with and fit through ports and airlocks of at least three vehicles: ISS, Human Landing System (HLS), and Gateway. The first partial xPLSS experimental flight unit called SWME EXPRESS Rack Flight Experiment (SERFE) that was a rack-deployed thermal control system payload on the ISS for two years (2020-2022). The first complete assembly of the xEMU was built as a Design Verification Test (DVT) unit (2022); similar to but more extensive than an Engineering Development Unit (EDU). The xPLSS Backplate serves not only as the structural backbone of the xPLSS and SERFE systems but also contains innovative design features to reduce the: mass, complexity, parts count, number ofseals (and therefore leak potential), and outer dimensions of the entire assembly. This paper provides an overview of these new design features, manufacturing processes, system interfaces, and SERFE/DVT test results of the Backplate as part of the xPLSS/xEMU.

xPLSS↗

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↗

Application of an automated wireless structural monitoring system for long-span suspension bridges

This paper describes an automated wireless structural monitoring system installed at the New Carquinez Bridge (NCB). The designed system utilizes a dense network of wireless sensors installed in the bridge but remotely controlled by a hierarchically designed cyber-environment. The early efforts have included performance verification of a dense network of wireless sensors installed on the bridge and the establishment of a cellular gateway to the system for remote access from the internet. Acceleration of the main bridge span was the primary focus of the initial field deployment of the wireless monitoring system. An additional focus of the study is on ensuring wireless sensors can survive for long periods without human intervention. Toward this end, the life-expectancy of the wireless sensors has been enhanced by embedding efficient power management schemes in the sensors while integrating solar panels for power harvesting. The dynamic characteristics of the NCB under daily traffic and wind loads were extracted from the vibration response of the bridge deck and towers. These results have been compared to a high-fidelity finite element model of the bridge.

42 ENGINEERING↗

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↗

Dry Saliva Development-Artemis

Prior to the deployment of prolonged deep space missions which may carry increased crew health risks, it is essential to determine the effect that missions beyond the Van Allen Belt will have on physiology. Historically the National Aeronautics and Space Administration (NASA), Human Research Program (HRP) has developed, conducted, and delivered research findings and countermeasures that will maintain the health and safety of crews aboard the International Space Station (ISS) in anticipation of future exploration class missions. To support these objectives, research operations on ISS typically include the collection and storage of human physiological samples and their return to Earth for analysis. Transition to Gateway and Artemis lunar exploration will limit the available up mass and biosample return capability resulting in new challenges to monitor crew health during the mission. The Artemis lunar missions provide a perfect opportunity to assess new technology that could support crew biosample return that is compatible with the severe operational constraints of Artemis mission design. Dried biosample chemistry analysis is a potential technology that can enable the collection of samples and tracking of crew health during these exploration class missions. The development and implementation of dried biosample chemistry technology for tracking immune health, viral reactivation and hormone fluctuations provide a simple alternative strategy for sample collection and sample return (light weight non-conditioned stowage option) for the continuation of human research during Artemis missions. Saliva is established as an informative biosample that has both its own unique available analytes as well as others that are also present in blood. Saliva is already routinely collected from ISS astronauts for the detection of stress hormones and latent virus DNA. The ‘Dry Saliva’ book sample collection/storage protocol, already successfully deployed to ISS, represents a perfect method for collecting biosamples from Gateway and Artemis astronauts because it requires a simple, non-invasive sample collection protocol, minimum volume, and uses non-conditioned storage. We are currently conducting an expanded stability study of the dry saliva analyte platform to include additional stress hormones, cytokines, antimicrobial proteins, and latent virus DNA as well as other markers of immunity and inflammation. Validation testing on parabolic flight will establish collection methods for saliva and blood to dry sampling substrates to finalize the collection protocols for flight. For the new expanded analyte stability study, a short-term stability study with time points out to 14 days has been completed with analysis underway to determine whether additional analytes could be recovered, as well as assessing the best storage conditions for the samples collected. In parallel, a long-term stability study is being conducted out to 1 year to improve the stability of some unstable analytes. To this end, the NASA Johnson Space Center’s Immunology/Virology lab is currently finalizing the saliva dry chemistry platform, including assay compatibility and stability studies. This technology is approved to be implemented, as part of the ‘Biomarkers’ study, during Artemis II through Artemis IV lunar missions.

Mayra Nelman-Gonzalez↗

Real-Time Detection of Hydrogen and Ammonia Isotopologues for Impurity Removal and Recovery of Tritium

To accommodate gas measurements for impurity removal and recovery of tritium, a silver-coated optical or waveguide is employed for collecting Raman scattered signals to determine relative hydrogen and ammonia isotopologue populations in real time. The data and results presented here demonstrate an analytical methodology for the analysis of four ammonia and three hydrogen isotopologues in a hydrogen–deuterium exchange reaction by gas phase Raman spectroscopy. Standard chemometric modeling techniques effectively unravel the signatures of the isotopologues involved observed here; however, a sophisticated quantum chemical approach supports the spectral assignments. An interpretation of the data presented here can emphasize the practicality and reliability of the gaseous monitoring system in complex chemical environments for the hydrogen fuel economy as well as the more distant energy source from a facility that handles tritium. There are still considerable concerns about the measurement of tritium in isotope separation and radiological impurities from gas processing. A common impurity in gas processing is ammonia, which can form readily in the presence of nitrogen and tritium. Substituted ammonia (NQ 3 ), where Q = H, D, or T, is traditionally removed through getters or diffusers along with other non-hydrogen contaminants. A preferable analytical approach is noninvasive and can be deployed for real-time process evaluation in radiological environments.

Ammonia↗

Outcomes of HPC User Support using a Science Gateway AI Assistant

High Performance Computing (HPC) is a vital resource for nuclear energy research, facilitating advanced simulations and complex modeling of the quantification and qualification of advanced reactor technology. However, a common gap in knowledge exists around utilizing HPC systems, particularly for nuclear energy researchers unfamiliar with specific HPC systems. A researcher may be well-versed in using one HPC system and understanding its associated processes. Yet, they might struggle when faced with a different HPC system and its unique processes. HPC support staff play a crucial role in addressing these challenges by providing educational resources and assisting users. However, they also face the challenge of maintaining these systems and ensuring they run efficiently for all users, a responsibility that can be challenging to scale effectively with the increasing demand and expansion of HPC systems. This paper addresses this knowledge gap with an artificial intelligence (AI) assistant that offers on-demand, site-specific HPC support for researchers. Idaho National Laboratory (INL) has deployed an AI assistant that is intended to supplement expert HPC support staff and assist nuclear energy researchers. This paper reports on a four-and-a-half-month study evaluating the integration of an AI assistant within a science gateway, with the goal of enhancing existing HPC support.

97 MATHEMATICS AND COMPUTING↗

Licensing Modernization Project for Advanced Reactor Technologies: FY 2018 Project Status Report

The promise of new nuclear technology and the future of commercial power in the United States (U.S.) are linked to the existence of an efficient and safety-focused regulatory review and licensing process. With an appropriate regulatory framework, reactor suppliers and regulators can design, license, build, and export advanced reactor units more effectively and efficiently and thereby help meet the growing need for clean and reliable energy. To help address the challenge of maintaining compatibility between the regulatory environment and new commercial nuclear plant designs, the U.S. Department of Energy (DOE) is supporting an industry-led effort called the Licensing Modernization Project (LMP). This cost-shared initiative, started in 2016 and scheduled to continue through mid-2019, targets amendment to key elements of the U.S. nuclear power reactor regulatory framework to specifically address licensing barriers in advanced-reactor concepts. The project is focused on updating guidance for certain technical licensing requirements that are largely incompatible with non-light-water reactors (non-LWR) and establish a new pathway for design-safety evaluations and license-application development. Upon completion, the project will have created a new pathway, founded on modern probabilistic assessment techniques, that offers developers, suppliers, regulators, and owner/operatorowner-operators greater clarity and assurance in design and licensing decisions. The LMP employs a team of advanced reactor technology and licensing subject matter experts working closely with U.S. regulators, affected industries, and interested members of the public. The project is managed by Southern Company and supported through a cost share arrangement with DOE. Technical contributions are also provided to the project from the Idaho National Laboratory (INL) Regulatory Development area, the Nuclear Energy Institute (NEI), and the U.S. Nuclear Regulatory Commission (NRC). The LMP identified a suite of high priority issues that provided significant uncertainty within the regulated non-LWR community. It was determined that much of this uncertainty could be retired by issuing updated licensing guidance founded on safety performance demonstrations and modern probabilistic methodologies. The success criteria for the project were established as: • Generate sets of technology inclusive (TI), risk-informed, and performance-based (TI-RIPB) technical requirements, recommendations, and proposals that could be reviewed, amended, and adopted for use by both NRC staff and industry. The proposals would create an optional-use regulatory framework without imposing additional (i.e., mandatory) requirements. • Support LMP the recommended updates of LMP such that they can be finalized, endorsed by NRC, and used by applicants within 5 years. This also supports the DOE advanced- reactor development and deployment goal of completing licensing reviews for technically mature non-LWR concepts sufficient to allow construction to proceed by the early 2030’s. • Further overall programmatic objectives established by DOE’s Gateway for Accelerated Innovation in Nuclear (GAIN) initiative by resolving technology-inclusive policy issues that adversely impact regulatory reviews, siting, permitting, and/or licensing of non-LWRs. This would provide significantly more regulatory certainty for advanced reactor developers.

11 NUCLEAR FUEL CYCLE AND FUEL MATERIALS↗

Integrating System to Edge-of-Network Architecture and Management for SHINES (SEAMS) Technologies of High Penetration Grids

Consistent with the U.S. DOE’s EERE SHINES FOA objectives, the goal of this project was to enable integration from EMS to variable DER in a way that delivered visibility and opportunities for managing and controlling distributed resources using SEAMS technologies. This project implemented several SHINES technologies, which included: (1) three Stem battery systems; (2) six ConnectDER PV collars; (3) two E-Gear PV/Battery storage interfaces; and (4) eight Kitu smart inverter emulators. A Siemens Energy IP DEMS was deployed in a development environment and integrated with the SHINES technologies via OpenADR and IEEE 2030.5 protocols with documented architecture. In the case of IEEE 2030.5, a suite of technologies including a gateway, an API, software and a server from Kitu Systems (the Citadel, Convoy, Kitu Crosslink API, and Kitu Spark) were used to demonstrate that the utility could achieve visibility of distributed energy resources (DER) and control of single and multiple DER systems with a single command. The project also included a LCOE analysis of SHINES technologies compared to traditional system and circuit mitigation measures.

14 SOLAR ENERGY↗

Development of FELIX based readout system for HV-CMOS sensor testbeam

The High Voltage CMOS (HV-CMOS) sensors are extensively investigated by the ATLAS collaboration for the High-Luminosity LHC (HL-LHC) upgrade of the Inner Tracker (ITk) detector. The HV-CMOS technology is a commercial integrated circuit process with the advantages of monolithic readout and fast charge collection. A front-end test platform of CaRIBOu (Control and Readout Itk BOard) and a testbeam Telescope based on the ATLAS IBL (Insertable B-Layer) silicon pixel modules, have been developed for the HV-CMOS sensor study and characterization in testbeam experiments. The Front-End LInk eXchange (FELIX) system is a newapproach to function as the gateway between detector front-end electronics and the commodity switched network in the ATLAS upgrade. A FELIX based readout system has been developed for both the CaRIBOu and the testbeam Telescope. It has been deployed successfully in the testbeam at theCERNSPS H8 beamline in August 2017. The test results show that the readout system is capable of sensor calibration and readout of a high-density pixel detector with high trigger rate in testbeam experiments.

47 OTHER INSTRUMENTATION↗