Search NASA⌕ Search

SEARCH · Search NASA

Results for “software engineering release engineering”

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 73 records · Page 4

High-Rate Delay Tolerant Networking (HDTN) Software Requirements Analysis

This document serves as a detailed analysis of the main networking protocols implemented by HDTN. Sources of the protocol specifications include Internet Engineering Task Force (IETF) Request for Comments (RFC) and Consultative Committee for Space Data Systems (CCSDS) standards. The focus of this report is to derive software requirements suitable for NASA Procedural Requirements 7150.2D Class B compliance, including requirements traceability and software verification and validation, from the source specifications. This analysis will be incorporated into the finalized HDTN Software Requirements Specification (SRS) but does not encompass the full scope of the HDTN SRS. Requirements in this document are considered draft. The complete requirements will include bundle application requirements, interface requirements, computer resource requirements, software quality factors, and additional requirements as determined by the project. This document is publicly released to the greater community to receive feedback and foster collaboration opportunities.

Rachel Dudukovich↗

Building an experience factory for maintenance

This paper reports the preliminary results of a study of the software maintenance process in the Flight Dynamics Division (FDD) of the National Aeronautics and Space Administration/Goddard Space Flight Center (NASA/GSFC). This study is being conducted by the Software Engineering Laboratory (SEL), a research organization sponsored by the Software Engineering Branch of the FDD, which investigates the effectiveness of software engineering technologies when applied to the development of applications software. This software maintenance study began in October 1993 and is being conducted using the Quality Improvement Paradigm (QIP), a process improvement strategy based on three iterative steps: understanding, assessing, and packaging. The preliminary results represent the outcome of the understanding phase, during which SEL researchers characterized the maintenance environment, product, and process. Findings indicate that a combination of quantitative and qualitative analysis is effective for studying the software maintenance process, that additional measures should be collected for maintenance (as opposed to new development), and that characteristics such as effort, error rate, and productivity are best considered on a 'release' basis rather than on a project basis. The research thus far has documented some basic differences between new development and software maintenance. It lays the foundation for further application of the QIP to investigate means of improving the maintenance process and product in the FDD.

Valett, Jon D.↗

A Database for Propagation Models and Conversion to C++ Programming Language

The telecommunications system design engineer generally needs the quantification of effects of the propagation medium (definition of the propagation channel) to design an optimal communications system. To obtain the definition of the channel, the systems engineer generally has a few choices. A search of the relevant publications such as the IEEE Transactions, CCIR's, NASA propagation handbook, etc., may be conducted to find the desired channel values. This method may need excessive amounts of time and effort on the systems engineer's part and there is a possibility that the search may not even yield the needed results. To help the researcher and the systems engineers, it was recommended by the conference participants of NASA Propagation Experimenters (NAPEX) XV (London, Ontario, Canada, June 28 and 29, 1991) that a software should be produced that would contain propagation models and the necessary prediction methods of most propagation phenomena. Moreover, the software should be flexible enough for the user to make slight changes to the models without expending a substantial effort in programming. In the past few years, a software was produced to fit these requirements as best as could be done. The software was distributed to all NAPEX participants for evaluation and use, the participant reactions, suggestions etc., were gathered and were used to improve the subsequent releases of the software. The existing database program is in the Microsoft Excel application software and works fine within the guidelines of that environment, however, recently there have been some questions about the robustness and survivability of the Excel software in the ever changing (hopefully improving) world of software packages.

Kantak, Anil V.↗

Hybrid Modeling Improves Health and Performance Monitoring

Scientific Monitoring Inc. was awarded a Phase I Small Business Innovation Research (SBIR) project by NASA's Dryden Flight Research Center to create a new, simplified health-monitoring approach for flight vehicles and flight equipment. The project developed a hybrid physical model concept that provided a structured approach to simplifying complex design models for use in health monitoring, allowing the output or performance of the equipment to be compared to what the design models predicted, so that deterioration or impending failure could be detected before there would be an impact on the equipment's operational capability. Based on the original modeling technology, Scientific Monitoring released I-Trend, a commercial health- and performance-monitoring software product named for its intelligent trending, diagnostics, and prognostics capabilities, as part of the company's complete ICEMS (Intelligent Condition-based Equipment Management System) suite of monitoring and advanced alerting software. I-Trend uses the hybrid physical model to better characterize the nature of health or performance alarms that result in "no fault found" false alarms. Additionally, the use of physical principles helps I-Trend identify problems sooner. I-Trend technology is currently in use in several commercial aviation programs, and the U.S. Air Force recently tapped Scientific Monitoring to develop next-generation engine health-management software for monitoring its fleet of jet engines. Scientific Monitoring has continued the original NASA work, this time under a Phase III SBIR contract with a joint NASA-Pratt & Whitney aviation security program on propulsion-controlled aircraft under missile-damaged aircraft conditions.

Source record↗

Uranus Global Reference Atmospheric Model (Uranus-GRAM) 2024: User Guide

Engineers and mission planners designing vehicles that pass through Uranus’ atmosphere require an atmospheric model that calculates the mean values and variations of atmospheric properties. The Uranus Global Reference Atmospheric Model(Uranus-GRAM)is an engineering- oriented model that provides this information based on data from Voyager observations. Uranus- GRAM is designed to offer mission planners the flexibility to select input parameters such as time, latitude, and longitude. Uranus-GRAM outputs atmospheric constituent data and mean values for atmospheric density, temperature, pressure, and zonal wind along a user defined path. Uranus-GRAM also provides dispersions of density and zonal wind. Uranus-GRAM is one option in the GRAM Suite that shares a common software core with the other planetary GRAMs while maintaining Uranus specific models. Additionally, documentation, including this User Guide, a Programmer’s Manual, and trajectory code interfaces has been made available with the software release. This Technical Memorandum summarizes the atmospheric data model in Uranus-GRAM and provides a guide for the user to obtain, set up, and run the code in various configurations. Section 2 describes the input atmospheric data files and how they are used in Uranus-GRAM. Section 3 explains the process to obtain the Uranus-GRAM code, the data files, and how to set up and run the program. Appendices A through E provide additional details regarding the Uranus-GRAM input and output files. Appendix F provides a history of Uranus-GRAM revisions.

atmospheric models↗

Verification and Validation in a Rapid Software Development Process

The high cost of software production is driving development organizations to adopt more automated design and analysis methods such as rapid prototyping, computer-aided software engineering (CASE) tools, and high-level code generators. Even developers of safety-critical software system have adopted many of these new methods while striving to achieve high levels Of quality and reliability. While these new methods may enhance productivity and quality in many cases, we examine some of the risks involved in the use of new methods in safety-critical contexts. We examine a case study involving the use of a CASE tool that automatically generates code from high-level system designs. We show that while high-level testing on the system structure is highly desirable, significant risks exist in the automatically generated code and in re-validating releases of the generated code after subsequent design changes. We identify these risks and suggest process improvements that retain the advantages of rapid, automated development methods within the quality and reliability contexts of safety-critical projects.

Callahan, John R.↗

Overview of the SAE G-11 RMSL (Reliability, Maintainability, Supportability, and Logistics) Division Activities and Technical Projects

The SAE G-11 RMSL (Reliability, Maintainability, Supportability, and Logistics) Division activities include identification and fulfillment of joint industry, government, and academia needs for development and implementation of RMSL technologies. Four Projects in the Probabilistic Methods area and two in the area of RMSL have been identified. These are: (1) Evaluation of Probabilistic Technology - progress has been made toward the selection of probabilistic application cases. Future effort will focus on assessment of multiple probabilistic softwares in solving selected engineering problems using probabilistic methods. Relevance to Industry & Government - Case studies of typical problems encountering uncertainties, results of solutions to these problems run by different codes, and recommendations on which code is applicable for what problems; (2) Probabilistic Input Preparation - progress has been made in identifying problem cases such as those with no data, little data and sufficient data. Future effort will focus on developing guidelines for preparing input for probabilistic analysis, especially with no or little data. Relevance to Industry & Government - Too often, we get bogged down thinking we need a lot of data before we can quantify uncertainties. Not True. There are ways to do credible probabilistic analysis with little data; (3) Probabilistic Reliability - probabilistic reliability literature search has been completed along with what differentiates it from statistical reliability. Work on computation of reliability based on quantification of uncertainties in primitive variables is in progress. Relevance to Industry & Government - Correct reliability computations both at the component and system level are needed so one can design an item based on its expected usage and life span; (4) Real World Applications of Probabilistic Methods (PM) - A draft of volume 1 comprising aerospace applications has been released. Volume 2, a compilation of real world applications of probabilistic methods with essential information demonstrating application type and timehost savings by the use of probabilistic methods for generic applications is in progress. Relevance to Industry & Government - Too often, we say, 'The Proof is in the Pudding'. With help from many contributors, we hope to produce such a document. Problem is - not too many people are coming forward due to proprietary nature. So, we are asking to document only minimum information including problem description, what method used, did it result in any savings, and how much?; (5) Software Reliability - software reliability concept, program, implementation, guidelines, and standards are being documented. Relevance to Industry & Government - software reliability is a complex issue that must be understood & addressed in all facets of business in industry, government, and other institutions. We address issues, concepts, ways to implement solutions, and guidelines for maximizing software reliability; (6) Maintainability Standards - maintainability/serviceability industry standard/guidelines and industry best practices and methodologies used in performing maintainability/ serviceability tasks are being documented. Relevance to Industry & Government - Any industry or government process, project, and/or tool must be maintained and serviced to realize the life and performance it was designed for. We address issues and develop guidelines for optimum performance & life.

Singhal, Surendra N.↗

Free-Flowing Solutions for CFD

Licensed to over 1,500 customers worldwide, an advanced computational fluid dynamics (CFD) post-processor with a quick learning curve is consistently providing engineering solutions, with just the right balance of visual insight and hard data. FIELDVIEW is the premier product of JMSI, Inc., d.b.a. Intelligent Light, a woman-owned, small business founded in 1994 and located in Lyndhurst, New Jersey. In the early 1990s, Intelligent Light entered into a joint development contract with a research based company to commercialize the post-processing FIELDVIEW code. As Intelligent Light established itself, it purchased the exclusive rights to the code, and structured its business solely around the software technology. As a result, it is enjoying profits and growing at a rate of 25 to 30 percent per year. Advancements made from the earliest commercial launch of FIELDVIEW, all the way up to the recently released versions 8 and 8.2 of the program, have been backed by research collaboration with NASA's Langley Research Center, where some of the world's most progressive work in transient (also known as time-varying) CFD takes place.

Source record↗

Universal Responses of Cyclic-Oxidation Models Studied

Oxidation is an important degradation process for materials operating in the high-temperature air or oxygen environments typical of jet turbine or rocket engines. Reaction of the combustion gases with the component material forms surface layer scales during these oxidative exposures. Typically, the instantaneous rate of reaction is inversely proportional to the existing scale thickness, giving rise to parabolic kinetics. However, more realistic applications entail periodic startup and shutdown. Some scale spallation may occur upon cooling, resulting in loss of the protective diffusion barrier provided by a fully intact scale. Upon reheating, the component will experience accelerated oxidation due to this spallation. Cyclic-oxidation testing has, therefore, been a mainstay of characterization and performance ranking for high-temperature materials. Models simulate this process by calculating how a scale spalls upon cooling and regrows upon heating (refs. 1 to 3). Recently released NASA software (COSP for Windows) allows researchers to specify a uniform layer or discrete segments of spallation (ref. 4). Families of model curves exhibit consistent regularity and trends with input parameters, and characteristic features have been empirically described in terms of these parameters. Although much insight has been gained from experimental and model curves, no equation has been derived that can describe this behavior explicitly as functions of the key oxidation parameters.

Smialek, James L.↗

Micrometeoroid and Orbital Debris (MMOD) Testing, Ballistic Limit Definition and Risk Assessment of the Exploration Extravehicular Mobility Unit (xEMU)

A well-known hazard associated with exposure to the space environment is the risk of failure due to an impact from a micrometeoroid and orbital debris (MMOD) particle. As NASA prepares to return astronauts to the moon with the Artemis program, the next generation of spacesuit is in development to support future extravehicular activities (EVAs.) An MMOD impact to the spacesuit is of great concern as a large leak could prevent an astronaut from safely reaching an airlock in time resulting in a loss of life. The exploration extravehicular mobility unit (xEMU) must meet MMOD requirements for multiple environments including those in low earth orbit (LEO) as well as the meteoroid and secondary lunar regolith ejecta environments found on the lunar surface. The subject of this paper is an internal xEMU configuration design developed by NASA Johnson Space Center (JSC) personnel. The xEMU shares similarities with the legacy Extravehicular Mobility Unit (EMU) spacesuit that is currently used for ISS EVAs, however differences in the layup (e.g., materials, thicknesses, and layers) of the fabric environmental protection garment (EPG), portable life support system (xPLSS) and helmet required an extensive test program to determine ballistic performance. Over 100 hypervelocity impact (HVI) tests were performed by the NASA/JSC HVIT and White Sands Test Facility (WSTF) teams on the xEMU EPG, xPLSS and helmet to generate ballistic limit equations (BLEs) for MMOD impacts. Additionally, over 50 low speed tests (< 1km/s) were performed by the NASA/JSC HVIT and Southwest Research Institute (SwRI) teams on the xEMU EPG, xPLSS and helmet to generate BLEs for lunar ejecta impacts. Post testing, ballistic limit equations (BLEs) used to define the performance of the various regions on the xEMU spacesuit were developed from a generic set of BLEs. The HVI and low speed testing was performed to establish a physical basis for the equations with the coefficients and exponents of the generic BLEs adjusted to fit the test data. The xEMU BLEs were added to the NASA/JSC software application used for spacecraft MMOD risk assessments (BUMPER-3). A finite element model (FEM) of the xEMU spacesuit, which defines the size and shape of the spacesuit as well as the locations of the various shielding configurations, was created based on a solid model provided by the xEMU program office. Using the FEM file and added xEMU BLEs, BUMPER-3 assessments of the xEMU spacesuit for probability of no penetration (PNP) were performed. For the LEO assessment of a typical ISS EVA, the orbital debris and meteoroids environments were defined using the latest engineering models, ORDEM 3.2 and MEM-3 respectively. The lunar surface assessment again used the MEM-3 engineering model to define the meteoroid environment along with the current released lunar surface ejecta model, NASA SP-8013 (developed during the Apollo Program). The Space Team in the Natural Environments Branch at Marshall Space Flight Center (MSFC) will soon release the new Lunar Meteoroid Ejecta Engineering Model (LMEEM), at which time the xEMU lunar surface EVA will be reassessed. Assessment of the MMOD risk for an 8-hour, 2-person EVA in both LEO and on the lunar surface showed that the xEMU spacesuit meets the program technical requirement of 1 in 2500 failure odds. Similar to the legacy EMU spacesuit, the majority of the MMOD risk (96% of the LEO EVA risk and 99% of the lunar surface EVA risk) is concentrated in regions of xEMU that are comprised primarily of softgoods (arms, legs, and gloves) rather than the hardgoods (xPLSS, hard upper torso and helmet).

Micrometeoroid↗

The Completion of a Geosynchronous Earth Orbit Survey with the Eugene Stansbery-Meter Class Autonomous Telescope

The Eugene Stansbery-Meter Class Autonomous Telescope (ES-MCAT) is the primary optical sensor used by the NASA Orbital Debris Program Office (ODPO) to statistically characterize the geosynchronous Earth orbit (GEO) debris environment and support future Orbital Debris Engineering Model (ORDEM) releases. The ES-MCAT completed its first optical survey of the GEO region from 2020 to 2022. The primary goal of this survey was to autonomously collect and process GEO data with calculated photometric and astrometric uncertainties. A pointing plan was developed to provide uniform sampling within the region of interest (ROI) while accounting for predicted downtime due to insufficient observing conditions. Detections are autonomously correlated to the Space Surveillance Network (SSN) catalog to determine if objects are correlated targets (CTs) or uncorrelated targets (UCTs), the latter of which are of interest for modeling the GEO orbital debris environment. To assess the size detection sensitivity over time and monitor the general performance of the telescope’s optics and software, the optical throughput of the system and limiting magnitudes are evaluated on a routine basis. While the telescope’s ability to operate autonomously and remotely allowed for the GEO survey to continue throughout the COVID-19 pandemic, travel restrictions hampered routine cleaning of the optics during this time, and the primary mirror degraded enough to require recoating. The mirror was removed in 2022, concluding the first GEO survey. The primary mirror received a new coating designed to be more robust against the harsh environment surrounding the ES-MCAT’s location on Ascension Island, accounting for experience gained during operations over the first GEO survey. In early 2023, the recoated primary mirror was reinstalled, and the second GEO survey was initiated. The primary goal of the second GEO survey is to characterize the evolving GEO debris environment with updated optics, software, and pointing strategies while allowing for the inclusion of non-GEO regimes or those that are outside of the ROI. While the pointing method implemented in the first survey allowed for adequate coverage of the ROI over two years, it has been improved to include pointings that avoid the Moon’s position and the galactic plane to reduce software processing time and maximize the detection capabilities of fainter objects. This method also accounts for the changing weather patterns throughout the year and reduces coverage gaps in the ROI. Provided the success of the first two-year GEO survey using autonomous operations, the ODPO is actively collaborating with the United States Space Force (USSF) to make the ES-MCAT a contributing sensor to the SSN. This paper presents results from the first GEO survey including magnitude distributions and orbital parameters for CTs and UCTs. Details are provided for the automated processing pipeline and the optical system throughput for the previous and current primary mirror coatings. In addition, an updated strategy for the second GEO survey to optimize coverage over the ROI is discussed, as are preliminary results from the ongoing second survey.

Corbin Cruz↗

The Completion of a Geosynchronous Earth Orbit Survey with the Eugene Stansbery-Meter Class Autonomous Telescope

The Eugene Stansbery-Meter Class Autonomous Telescope (ES-MCAT) is the primary optical sensor used by the NASA Orbital Debris Program Office (ODPO) to statistically characterize the geosynchronous Earth orbit (GEO) debris environment and support future Orbital Debris Engineering Model (ORDEM) releases. The ES-MCAT completed its first optical survey of the GEO region from 2020 to 2022. The primary goal of this survey was to autonomously collect and process GEO data with calculated photometric and astrometric uncertainties. A pointing plan was developed to provide uniform sampling within the region of interest (ROI) while accounting for predicted downtime due to insufficient observing conditions. Detections are autonomously correlated to the Space Surveillance Network (SSN) catalog to determine if objects are correlated targets (CTs) or uncorrelated targets (UCTs), the latter of which are of interest for modeling the GEO orbital debris environment. To assess the size detection sensitivity over time and monitor the general performance of the telescope’s optics and software, the optical throughput of the system and limiting magnitudes are evaluated on a routine basis. While the telescope’s ability to operate autonomously and remotely allowed for the GEO survey to continue throughout the COVID-19 pandemic, travel restrictions hampered routine cleaning of the optics during this time, and the primary mirror degraded enough to require recoating. The mirror was removed in 2022, concluding the first GEO survey. The primary mirror received a new coating designed to be more robust against the harsh environment surrounding the ES-MCAT’s location on Ascension Island, accounting for experience gained during operations over the first GEO survey. In early 2023, the recoated primary mirror was reinstalled, and the second GEO survey was initiated. The primary goal of the second GEO survey is to characterize the evolving GEO debris environment with updated optics, software, and pointing strategies while allowing for the inclusion of non-GEO regimes or those that are outside of the ROI. While the pointing method implemented in the first survey allowed for adequate coverage of the ROI over two years, it has been improved to include pointings that avoid the Moon’s position and the galactic plane to reduce software processing time and maximize the detection capabilities of fainter objects. This method also accounts for the changing weather patterns throughout the year and reduces coverage gaps in the ROI. Provided the success of the first two-year GEO survey using autonomous operations, the ODPO is actively collaborating with the United States Space Force (USSF) to make the ES-MCAT a contributing sensor to the SSN. This paper presents results from the first GEO survey including magnitude distributions and orbital parameters for CTs and UCTs. Details are provided for the automated processing pipeline and the optical system throughput for the previous and current primary mirror coatings. In addition, an updated strategy for the second GEO survey to optimize coverage over the ROI is discussed, as are preliminary results from the ongoing second survey.

Corbin Cruz↗

Mail LOG: Program operating instructions

The operating instructions for the software package, MAIL LOG, developed for the Scout Project Automatic Data System, SPADS, are provided. The program is written in FORTRAN for the PRIME 300 computer system. The MAIL LOG program has the following four modes of operation: (1) INPUT - putting new records into the data base (2) REVISE - changing or modifying existing records in the data base (3) SEARCH - finding special records existing in the data base (4) ARCHIVE - store or put away existing records in the data base. The output includes special printouts of records in the data base and results from the INPUT and SEARCH modes. The MAIL LOG data base consists of three main subfiles: Incoming and outgoing mail correspondence; Design Information Releases and Releases and Reports; and Drawings and Engineering orders.

Harris, D. K.↗

Micrometeoroid and Orbital Debris (MMOD) Testing, Ballistic Limit Equation Definition and Risk Assessment of the Exploration Extravehicular Mobility Unit (xEMU)

A well-known hazard associated with exposure to the space environment is the risk of failure due to an impact from a micrometeoroid and orbital debris (MMOD) particle. As NASA prepares to return astronauts to the moon with the Artemis program, the next generation of spacesuit is in development to support future extravehicular activities (EVAs.) An MMOD impact to the spacesuit is of great concern as a large leak could prevent an astronaut from safely reaching an airlock in time resulting in a loss of life. The exploration extravehicular mobility unit (xEMU) must meet MMOD requirements for multiple environments including those in low earth orbit (LEO) as well as the meteoroid and secondary lunar regolith ejecta environments found on the lunar surface. The subject of this paper is an internal xEMU configuration design developed by NASA Johnson Space Center (JSC) personnel. This paper will expand on the hypervelocity impact (HVI) testing and ballistic limit equation (BLE) definition work that was partially presented at the 2nd International Orbital De-bris (IOC-II) Conference held in Sugar Land, TX in December 2023. The xEMU shares similarities with the legacy Extravehicular Mobility Unit (EMU) spacesuit that is currently used for ISS EVAs, however differences in the layup (e.g., materials, thicknesses, and layers) of the fabric environmental protection garment (EPG), portable life support system (xPLSS) and helmet required an extensive test program to determine ballistic performance. Over 100 hypervelocity impact (HVI) tests were performed by the NASA/JSC HVIT and White Sands Test Facility (WSTF) teams on the xEMU EPG, xPLSS and helmet to generate ballistic limit equations (BLEs) for MMOD impacts. Additionally, over 50 low speed tests (< 1km/s) were performed by the NASA/JSC HVIT and Southwest Research Institute (SwRI) teams on the xEMU EPG, xPLSS and helmet to generate BLEs for lunar ejecta impacts. Post testing, ballistic limit equations used to define the performance of the various regions on the xEMU spacesuit were developed from a generic set of BLEs. The HVI and low speed testing was performed to establish a physical basis for the equations with the co-efficients and exponents of the generic BLEs adjusted to fit the test data. The xEMU BLEs were added to the NASA/JSC software application used for space-craft MMOD risk assessments (BUMPER-3). A finite element model (FEM) of the xEMU spacesuit, which defines the size and shape of the spacesuit as well as the locations of the various shielding configurations, was created based on a solid model provided by the xEMU program office. Using the FEM file and added xEMU BLEs, BUMPER-3 assessments of the xEMU spacesuit for probability of no penetration (PNP) were performed. For the LEO assessment of a typical ISS EVA, the orbital debris and meteoroids environments were defined using the latest engineering models, ORDEM 3.2 and MEM-3 respectively. The lunar sur-face assessment again used the MEM-3 engineering model to define the meteoroid environ-ment along with the current released lunar surface ejecta model, NASA SP-8013 (developed during the Apollo Program). The Space Team in the Natural Environments Branch at Mar-shall Space Flight Center (MSFC) will soon release the new Lunar Meteoroid Ejecta Engineering Model (LMEEM), at which time the xEMU lunar surface EVA will be reassessed. Assessment of the MMOD risk for an 8-hour, 2-person EVA in both LEO and on the lunar surface showed that the xEMU spacesuit meets the program technical requirement of 1 in 2500 failure odds. Similar to the legacy EMU spacesuit, the majority of the MMOD risk (96% of the LEO EVA risk and 99% of the lunar surface EVA risk) is concentrated in regions of xEMU that are comprised primarily of softgoods (arms, legs, and gloves) rather than the hardgoods (xPLSS, hard upper torso and helmet).

Micrometeoroid↗

Autonomous Ocean World Exploration: Advancement of a Virtual Testbed

The search for life (extinct or extant) and potentially habitable bodies in our solar system and beyond is one of the 12 priority science questions outlined in the National Acadamies’ 2022 decadal survey [5]. Extraterrestrial destinations containing liquid water present an opportunity to search for life as we know it, and in recent years an increasing number of such locations have been discovered within our solar system. Several Jovian moons—Europa, Ganymede, and Callisto [10]—and the Saturnian moons Enceladus [8] and Titan [9] are known or suspected to harbor massive subsurface oceans. Of these "ocean worlds", Europa is the focus of at least one planned NASA orbiter mission, Europa Clipper [4], and an early lander mission concept, the Europa Lander [2, 3]. Whereas most robotic missions to the Moon and Mars (e.g. orbiters, rovers, landers) to date have had ground controllers on Earth tightly involved in mission operations, missions to more distant worlds will require a high degree of onboard autonomy due to long communication lags and blackouts, harsh environments (radiation, cold), and more limited battery and hardware life. The past decade has seen great advances in both AI technologies and computing scalability and performance that offer promising solutions for spacecraft autonomy and motivate the software system and research programs described in this paper. The Ocean Worlds Autonomy Testbed for Exploration, Research, and Simulation (OceanWATERS) [1], which has been in development at the NASA Ames Research Center since 2018, is a virtual environment for testing lander autonomy solutions. It is built on the Robot Operating System (ROS), runs on consumer-grade Linux workstations, and was released as open source in 2020. OceanWATERS provides a physical and visual simulation of a prototypical lander in a Europa-like environment (Figure 1). The lander was modeled after requirements and specifications made in JPL’s Europa Lander Study of 2016 [3]. Simulated lander systems include stereo cameras and spotlights mounted on an antenna mast that pans and tilts, a 6 degrees of freedom (DoF) robotic arm with a force-torque sensor and two interchangeable end effectors, and a battery pack power system. The environment consists of multiple terrain models including a highly detailed model sourced from the FROST dataset [11], simulation of surrounding planetary bodies based on an ephemeris model, and lighting from the sun with associated surface illumination, reflectance, and shadows. Operations supported by OceanWATERS include panoramic and directed imaging of the environment and lander workspace, Cartesian and joint-level arm commanding, grinding of the terrain surface (e.g. digging a trench), and scooping of ground material (Figure 2) which can be discarded or collected as science samples in a receptacle that can be emptied (science operations themselves are not simulated). These operations are realized as ROS Actions and are complimented by a wide selection of telemetry that is continually produced by each lander subsystem. The power system model is driven by the open-source Generic Software Architecture for Prognostics (GSAP) [11] that predicts the battery’s remaining useful life and other characteristics. As a testbed for high-level autonomy, OceanWATERS provides an execution framework based on PLEXIL [12], an open-source plan specification language and execution engine developed largely at Ames. NASA's initial development of OceanWATERS, as well the Ocean Worlds Lander Autonomy Testbed (OWLAT) [6], a complimentary physical testbed developed at JPL, was the first step in a plan for realizing candidate onboard autonomy solutions for such planetary landers. In 2020 NASA solicited applications for its Autonomous Robotics Research for Ocean Worlds (ARROW) program, and in 2021 the similar Concepts for Ocean worlds Life Detection Technology (COLDTech) program. Collectively six research teams, based in universities and companies across the United States, were awarded grants to develop and demonstrate autonomy solutions on OceanWATERS and OWLAT. These 1–2-year projects have now finished or are nearing completion, and a wide variety of autonomy challenges in ocean world surface missions were addressed. Prototyped and demonstrated solutions have included autonomous discovery, response and adaptation to system faults and unexpected environmental events, world model synthesis through perception, plan synthesis using learned models, methods to optimize sample target selection and prioritize science data transmission, extension of PLEXIL for stochastic decision-making, and an integration of a model of JPL’s mission-ready COLDArm [7]. Technologies used in these projects include many forms of machine learning, causal reasoning, automated planning, Markov decision processes, formal methods, and other advanced techniques. A more detailed summary of the ARROW and COLDTech projects is given herein. OceanWATERS has had significant enhancements since its open-source release in 2020. Many of its new features were driven or shaped by feedback from the ARROW and COLDTech teams and requirements of their projects. In support of enabling autonomous adaptation to spacecraft faults (a specific capability solicited by both programs), a fault injection and detection framework was developed that supports a wide and growing range of fault types such as locked joints, image loss, and battery failures. The power system model was completed and integrated into the simulator, starting as a single-cell battery model and later upgraded to a multi-cell model with associated faults such as cell disconnection. Arm/terrain interaction was improved by adding a force-torque sensor and associated faults, and an analytic dig force model based on the Balovnev bucket force equations. Environment fidelity was increased by modeling terrain deformation resulting from digging and scooping; visual improvements were made in textures, lighting, and shadows. To facilitate interoperation with OWLAT, a unified command and telemetry interface between the testbeds was developed at the ROS level, along with a PLEXIL interface. The number of lander operations was greatly expanded (e.g. with Cartesian-based arm and antenna movement), and a framework was designed for users to build their own lander actions. A GUI for PLEXIL plan selection was created (Figure 3), and an expansive set of plans were added, such as those that illustrate patterns for fault handling. This paper provides a self-contained high-level description of OceanWATERS, focusing on more detailed coverage of the aforementioned enhancements. It provides a high-level summary of the projects undertaken by participants in the ARROW and COLDTech programs and how these efforts have helped shape OceanWATERS. Finally, potential future work and directions for the testbed are listed, as likely informed by the recent planetary science decadal survey [5].

K Michael Dalal↗

TPSAS-NF1676L-32493-DND

The Committee on Earth Observation Satellites (CEOS) System Engineering Office (SEO) has supported the Open Data Cube (ODC) initiative to provide a data architecture solution that has value to its global users and increases the impact of EO satellite data. ODC is an open-source platform for processing satellite data. We have developed software products and tools around the core ODC that would help users perform machine learning on EO satellite data. The recent United Nations (UN) Sustainable Development Agenda provides a shared blueprint for peace and prosperity for people and for the planet, considering our current situation and helping to create a plan. The core of this agenda is a set of seventeen Sustainable Development Goals (SDGs), which represent an urgent call for action by all countries - both developed and developing - in a global partnership. The CEOS SEO team has recently developed and released a set of innovative Jupyter notebooks addressing UN SDGs 6.6.1 (spatial extents of water-related ecosystems), 11.3.1 (ratio of land consumption rate to population growth rate), and 15.3.1 (proportion of land that is degraded over total land area). These notebooks empower users by providing features that will assist with streamlining analysis ready data retrieval, processing, and visualization. We have recently incorporated several machine learning techniques in these notebooks. In this paper, we present the lessons learned from our experience on classifying land using supervised and unsupervised machine learning techniques using ODC framework for UN SDGs. We identify the current limitations of ODC to seamlessly support machine learning techniques. We propose features that would help machine learning, specifically within the ODC framework. We propose a thematic indexing/loading of data for both unsupervised learning as well as data annotation/labeling pipeline. Currently, ODC supports machine learning by separating data-management from the analysis process. It works as a mechanism to load cubes of data. ODC does not natively support features that are vital in machine learning such as validation splits, fair/balanced sampling, establishing load size constraints, etc. We believe that our proposed features will empower users by providing features that bring machine learning techniques closed to ODC. Enhancements to ODC to better accommodate machine learning techniques can assist in fulfilling UN SDGs such as 6.3.2, 6.4.2, 6.6.1, 11.3.1, 14.1.1, 15.1.1, 15.3.1, and 15.4.2.

Syed R Rizvi↗

Preliminary In-Flight Loads Analysis of In-Line Launch Vehicles using the VLOADS 1.4 Program

To calculate structural loads of in-line launch vehicles for preliminary design, a very useful computer program is VLOADS 1.4. This software may also be used to calculate structural loads for upper stages and planetary transfer vehicles. Launch vehicle inputs such as aerodynamic coefficients, mass properties, propellants, engine thrusts, and performance data are compiled and analyzed by VLOADS to produce distributed shear loads, bending moments, axial forces, and vehicle line loads as a function of X-station along the vehicle's length. Interface loads, if any, and translational accelerations are also computed. The major strength of the software is that it enables quick turnaround analysis of structural loads for launch vehicles during the preliminary design stage of its development. This represents a significant improvement over the alternative-the time-consuming, and expensive chore of developing finite element models. VLOADS was developed as a Visual BASIC macro in a Microsoft Excel 5.0 work book on a Macintosh. VLOADS has also been implemented on a PC computer using Microsoft Excel 7.0a for Windows 95. VLOADS was developed in 1996, and the current version was released to COSMIC, NASA's Software Technology Transfer Center, in 1997. The program is a copyrighted work with all copyright vested in NASA.

Graham, J. B.↗

Low Density Supersonic Decelerator Flight Dynamics Test-1 Flight Design and Targeting

NASA's Low Density Supersonic Decelerator (LDSD) program was established to identify, develop, and eventually qualify to Test [i.e. Technology] Readiness Level (TRL) - 6 aerodynamic decelerators for eventual use on Mars. Through comprehensive Mars application studies, two distinct Supersonic Inflatable Aerodynamic Decelerator (SIAD) designs were chosen that afforded the optimum balance of benefit, cost, and development risk. In addition, a Supersonic Disk Sail (SSDS) parachute design was chosen that satisfied the same criteria. The final phase of the multi-tiered qualification process involves Earth Supersonic Flight Dynamics Tests (SFDTs) within environmental conditions similar to those that would be experienced during a Mars Entry, Descent, and Landing (EDL) mission. The first of these flight tests (i.e. SFDT-1) was completed on June 28, 2014 with two more tests scheduled for the summer of 2015 and 2016, respectively. The basic flight design for all the SFDT flights is for the SFDT test vehicle to be ferried to a float altitude of 120 kilo-feet by a 34 thousand cubic feet (Mcf) heavy lift helium balloon. Once float altitude is reached, the test vehicle is released from the balloon, spun-up for stability, and accelerated to supersonic speeds using a Star48 solid rocket motor. After burnout of the Star48 motor the vehicle decelerates to pre-flight selected test conditions for the deployment of the SIAD system. After further deceleration with the SIAD deployed, the SSDS parachute is then deployed stressing the performance of the parachute in the wake of the SIAD augmented blunt body. The test vehicle/SIAD/parachute system then descends to splashdown in the Pacific Ocean for eventual recovery. This paper will discuss the development of both the test vehicle and the trajectory sequence including design trade-offs resulting from the interaction of both engineering efforts. In addition, the SFDT-1 nominal trajectory design and associated sensitivities will be discussed as well as an overview of the on-board flight software used to trigger and sequence the main flight events necessary to deploy the deceleration technologies. Finally, as-flown performance of the SFDT-1 system will be discussed.

Ivanov, Mark↗