Search NASA⌕ Search

SEARCH · Search NASA

Results for “robust execution”

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.

285 records · Page 16

Improved Collision-Detection Method for Robotic Manipulator

An improved method has been devised for the computational prediction of a collision between (1) a robotic manipulator and (2) another part of the robot or an external object in the vicinity of the robot. The method is intended to be used to test commanded manipulator trajectories in advance so that execution of the commands can be stopped before damage is done. The method involves utilization of both (1) mathematical models of the robot and its environment constructed manually prior to operation and (2) similar models constructed automatically from sensory data acquired during operation. The representation of objects in this method is simpler and more efficient (with respect to both computation time and computer memory), relative to the representations used in most prior methods. The present method was developed especially for use on a robotic land vehicle (rover) equipped with a manipulator arm and a vision system that includes stereoscopic electronic cameras. In this method, objects are represented and collisions detected by use of a previously developed technique known in the art as the method of oriented bounding boxes (OBBs). As the name of this technique indicates, an object is represented approximately, for computational purposes, by a box that encloses its outer boundary. Because many parts of a robotic manipulator are cylindrical, the OBB method has been extended in this method to enable the approximate representation of cylindrical parts by use of octagonal or other multiple-OBB assemblies denoted oriented bounding prisms (OBPs), as in the example of Figure 1. Unlike prior methods, the OBB/OBP method does not require any divisions or transcendental functions; this feature leads to greater robustness and numerical accuracy. The OBB/OBP method was selected for incorporation into the present method because it offers the best compromise between accuracy on the one hand and computational efficiency (and thus computational speed) on the other hand.

Leger, Chris↗

Thermal Protection System to Enable Ice Giant Aerocapture Mission for Delivering Both an Orbiter and an In Situ Probe

The Ice Giants have been identified as high priority science destinations in the last Decadal Survey [1] and could benefit from aerocapture as the primary method for orbit insertion [2]. A mass-efficient aerocapture system will enable the delivery of an orbiter along with an atmospheric probe (for in situ measurements to anchor global data collected by the orbiter) and possibly a lander at Triton [3]. Aerocapture could be executed either using low L/D rigid aeroshell with lift modulation (LMA) [4] or using deployable aeroshell using drag modulation (DMA) [3]. Nearly two decades ago, a NASA-funded team performed Neptune-Triton aerocapture studies with a mid-L/D lifting configuration [5] for achieving orbit using LMA. This study showed aerocapture challenges. Due to very high peak entry conditions combined with very high heat-load, a suite of TPS materials was required and this suite was deemed problematic from a qualification perspective, due test facility limitations. In the past 20 years, progress made in GN&C for lift-guided entry missions such as MSL, Orion EFT1, Mars 2020 and the upcoming Artemis missions, and the expertise in blunt body aerodynamics at large scale (~ 5m) has led the EDL community to conclude that aerocapture is a “go do” engineering activity and most technologies are in hand to propose missions with aerocapture [6] [7]. Aerocapture using DMA, currently in development, is an option for Ice Giant Missions. While DMA is simpler in some sense, due to ballistic entry and no need for lift-guided maneuvering, it has challenges and it’s maturity is lower. LMA and DMA both require one or more ablative Thermal Protection System (TPS) materials for the rigid aeroshell element. The ablative TPS needs to be robust and mass efficient due to the high heat loads and size of the rigid aeroshell. Currently, there are capable ablative thermal protection materials, e.g., Heatshield for Extreme Entry Environments Technology (HEEET), 3-D woven Mid-Density Carbon- Phenolic (3MDCP), and PICA (Phenolic-Impregnated Carbon Ablator) that are mature, i.e., at TRL 6 or higher. NASA also invested in Conformal PICA that was matured to TRL 5. Our goal is to evaluate the applicability of high TRL TPS and consider other design options. We first establish bounding aerocapture trajectories for a wide range of arrival conditions and the associated aerothermal environment. Based on the environments, we then determine the predicted TPS mass for the aeroshell [4]. In this presentation, we will outline the process by which we establish bounding aerocapture trajectories for hyperbolic excess velocities ranging from 27 km/s to 35 km/s, which are shown to be a range of velocities that can reduce the trip time from ~14 years to 8 years. The above velocity range translates to ~12 km/s to ~24 km/s arrival velocities at the planetary entry interface [2]. The velocity reduction required to achieve orbit ranges between ~2.5 km/s to 9.5 km/s for both Neptune and Triton. Propulsive insertion alone, due to the amount of fuel required to achieve the required velocity reduction, limits the science returned [2]. We establish the bounding aerocapture trajectories for a low L/D (~ 0.4) configuration for three different ballistic coefficients. The ballistic coefficient range is determined from three different aeroshell diameters of 3m, 4m and 5m and with an entry system mass of 2200 kg. With the above range of design parameters, we then determine conservative/bounding estimates of aerothermal environments by using a combination of CFD simulations and stagnation point heating estimates [7]. This engineering approach allows us to first assess the TPS need vs. TPS capability and determine the applicability of existing TPS. Once an applicable suite of TPS is determined, the TPS thickness and mass are computed. We show that the TPS mass fraction can be as low as 5% to as high as 20%, depending on total trip time reduction and other design parameters for a range of TPS. This is a large range for TPS mass fraction. We show PICA and HEEET can indeed enable aerocapture missions, but the missions incur a mass penalty. TPS mass savings, can be further reduced with the use of conformal PICA. Advancing the development of Conformal PICA to make it robust across the entire aerothermal environment (peak heat-flux, pressure and shear) range will result in TPS mass fractions of < 10% for Ice Giant aerocapture missions such as the Neptune-Triton mission. Aerocapture allows for not only shortening the trip time but enables larger mass to be placed in orbit. Furthermore, probes deployed from orbit will benefit in reduced entry environments allowing for a lower risk TPS implementation as compared to mission designs where the probe is released prior to orbit insertion. One of the challenges for the Ice Giant community is to ensure mission designs that maximize science and allow flexibility in the placement of the entry probe. The traditional approach to release the probe ahead of the orbiter may not optimize returned science. In this presentation, we will make the case for mature TPS such as HEEET and PICA. While these materials can enable aerocapture missions, completing the development of conformal PICA and extending Conformal PICA to be more robust, will have significant impact to TPS mass efficiency and significantly enhance science return for future Gas- and Ice-Giant missions.

E Venkatapathy↗

Simple, Scalable, Script-Based Science Processor (S4P)

The development and deployment of data processing systems to process Earth Observing System (EOS) data has proven to be costly and prone to technical and schedule risk. Integration of science algorithms into a robust operational system has been difficult. The core processing system, based on commercial tools, has demonstrated limitations at the rates needed to produce the several terabytes per day for EOS, primarily due to job management overhead. This has motivated an evolution in the EOS Data Information System toward a more distributed one incorporating Science Investigator-led Processing Systems (SIPS). As part of this evolution, the Goddard Earth Sciences Distributed Active Archive Center (GES DAAC) has developed a simplified processing system to accommodate the increased load expected with the advent of reprocessing and launch of a second satellite. This system, the Simple, Scalable, Script-based Science Processor (S42) may also serve as a resource for future SIPS. The current EOSDIS Core System was designed to be general, resulting in a large, complex mix of commercial and custom software. In contrast, many simpler systems, such as the EROS Data Center AVHRR IKM system, rely on a simple directory structure to drive processing, with directories representing different stages of production. The system passes input data to a directory, and the output data is placed in a "downstream" directory. The GES DAAC's Simple Scalable Script-based Science Processing System is based on the latter concept, but with modifications to allow varied science algorithms and improve portability. It uses a factory assembly-line paradigm: when work orders arrive at a station, an executable is run, and output work orders are sent to downstream stations. The stations are implemented as UNIX directories, while work orders are simple ASCII files. The core S4P infrastructure consists of a Perl program called stationmaster, which detects newly arrived work orders and forks a job to run the appropriate executable (registered in a configuration file for that station). Although S4P is written in Perl, the executables associated with a station can be any program that can be run from the command line, i.e., non-interactively. An S4P instance is typically monitored using a simple Graphical User Interface. However, the reliance of S4P on UNIX files and directories also allows visibility into the state of stations and jobs using standard operating system commands, permitting remote monitor/control over low-bandwidth connections. S4P is being used as the foundation for several small- to medium-size systems for data mining, on-demand subsetting, processing of direct broadcast Moderate Resolution Imaging Spectroradiometer (MODIS) data, and Quick-Response MODIS processing. It has also been used to implement a large-scale system to process MODIS Level 1 and Level 2 Standard Products, which will ultimately process close to 2 TB/day.

Lynnes, Christopher↗

Clinical Outcome Metrics for Optimization of Robust Training

Introduction: The emphasis of this research is on the Human Research Program (HRP) Exploration Medical Capability's (ExMC) "Risk of Unacceptable Health and Mission Outcomes Due to Limitations of In-Flight Medical Capabilities." Specifically, this project aims to contribute to the closure of gap ExMC 2.02: We do not know how the inclusion of a physician crew medical officer quantitatively impacts clinical outcomes during exploration missions. The experiments are specifically designed to address clinical outcome differences between physician and non-physician cohorts in both near-term and longer-term (mission impacting) outcomes. Methods: Medical simulations will systematically compare success of individual diagnostic and therapeutic procedure simulations performed by physician and non-physician crew medical officer (CMO) analogs using clearly defined short-term (individual procedure) outcome metrics. In the subsequent step of the project, the procedure simulation outcomes will be used as input to a modified version of the NASA Integrated Medical Model (IMM) to analyze the effect of the outcome (degree of success) of individual procedures (including successful, imperfectly performed, and failed procedures) on overall long-term clinical outcomes and the consequent mission impacts. The procedures to be simulated are endotracheal intubation, fundoscopic examination, kidney/urinary ultrasound, ultrasound-guided intravenous catheter insertion, and a differential diagnosis exercise. Multiple assessment techniques will be used, centered on medical procedure simulation studies occurring at 3, 6, and 12 months after initial training (as depicted in the following flow diagram of the experiment design). Discussion: Analysis of procedure outcomes in the physician and non-physician groups and their subsets (tested at different elapsed times post training) will allow the team to 1) define differences between physician and non-physician CMOs in terms of both procedure performance (pre-IMM analysis) and overall mitigation of the mission medical impact (IMM analysis); 2) refine the procedure outcome and clinical outcome metrics themselves; 3) refine or develop innovative medical training products and solutions to maximize CMO performance; and 4) validate the methods and products of this experiment for operational use in the planning, execution, and quality assurance of the CMO training process The team has finalized training protocols and developed a software training/testing tool in collaboration with Butler Graphics (Detroit, MI). In addition to the "hands on" medical procedure modules, the software includes a differential diagnosis exercise (limited clinical decision support tool) to evaluate the diagnostic skills of participants. Human subject testing will occur over the next year.

Ebert, D.↗

Automated Detection of Spurious Signals in VLBI Phase Calibration Data

In this memorandum, a set of processing strategies for automatic masking of phase calibration tones is outlined as implemented in the software package PIMA in the task Generate Phase Calibration Mask, or GEPM. The task relies on a robust procedure of cleaning phase calibration data before employing several mathematical strategies designed to selectively identify spurious signals from phase calibration tones. These strategies were derived as more rigorous implementations of heuristics traditionally used by analysts in manually identifying problematic phase calibration data. The task is intended to automate the process of generating a phase calibration mask and in so doing increase the speed and regularity of VLBI analysis. At the outset of the project, a series of goals were identified to evaluate the success of this mask generation. This included the development of an algorithm to identify and mask short-term (defined as less than 10 seconds in length) spurious signals affecting phase calibration data, the development of an algorithm to identify and mask phase calibration tones affected by constant radio-frequency interference, the implementation of a detection scheme for identifying large jumps in phase calibration phase caused by clock breaks, and finally a method of reporting phase calibration health metrics to the user. Processing of over 10 experiments has demonstrated that the final form of the task GEPM as detailed in this technical memorandum satisfies each of these conditions and satisfactorily performs the task of automatic phase calibration data masking, although the wide variety in quality and characteristics of phase calibration data makes a single solution to the problem quite difficult. A series of user inputs have therefore been defined to assist analysts in tailoring automatic masking to specific stations and phase calibration generators. The vast majority of applicable code was written in FORTRAN to increase execution speed and ease of interfacing with the existing code base in PIMA, but a wrapper function in Python was also written to allow for a simpler method of interacting with GEPM and inputting relevant parameters. In addition to this report, thorough documentation was added to the already existing repositories associated with PIMA as a whole.

Geodesy↗

TAE Plus: A conceptual view of TAE in the space station era

The use of the Transportable Applications Executive (TAE) for prototyping user interfaces has been the prime force behind the new TAE research and development work. The Data Systems Technology Division at GSFC is developing prototypes of user interfaces for different functions involved in the operation, analysis and data communication of space station payloads. TAE is a valuable prototyping tool because it enables a developer to build an entire application user interface model and run it without writing a single line of application code. One force driving new development is the need to update TAE's user interface to support the latest interactive graphic device technology. The current TAE, TAE Classic, uses interface techniques designed for an 80x24 character monochrome alphanumeric terminal, but does not effectively utilize features such as windowing, graphics, color, and selection devices available on newer workstations. To meet our needs, development of a TAE Plus began in FY-86 and involves augmenting TAE with three different sets of tools: a user interface toolkit; an application toolkit; and run-time service subroutines. A phased approach is being used to develop TAE Plus. In the first phase, we have met the needs of the user community and provided some support for rapid prototyping by developing a TAE Facelift, which adds an enhanced TAE interface (with windowing, mouse interaction, pull-down menus, etc.) to a select set of graphic workstations. The TAE Facelift allows many new concepts to be tested quickly for feedback and performance. In the second phase, a fully-integrated user interface management system, TAE Plus, will be built that supports the separation of interface from application, with the concomitant ability to prototype and rapidly change interfaces. This robust functionality will support, in an integrated manner, an application's development cycle from the prototype step through to the fully operational system.

Szczur, Martha↗

NASA Utilization of Space Nuclear Systems for Robotic and Human Exploration Missions: Response to EO 13972: Promoting Small Nuclear Reactors for National Defense and Space Exploration

Space Nuclear Systems (SNS) technology development offers a wide range of capabilities to support NASA’s current and future missions. Executive Order (EO) 13972, “Promoting Small Modular Reactors for National Defense and Space Exploration” [1], issued 5 January 2021, directs NASA to define requirements for NASA utilization of nuclear energy systems for human and robotic exploration missions through 2040 and analyze the costs and benefits of such requirements.” Although it is premature to define requirements and cost for future exploration missions that have not yet been formulated, this report describes planned objectives and missions by 2040 that are enabled or enhanced by nuclear systems while taking into account a number of unique considerations for nuclear energy in the space environment. Nuclear energy systems are enabling for space missions and critical capabilities where conventional forms of energy production are impractical or impossible due to mass constraints, mission duration, or distance from the Sun. Space nuclear technologies available or in development for use by 2040 utilize radioisotope decay or nuclear fission and fall into three categories: heat, power, and propulsion. Current applications utilize radioisotope power systems that provide consistent and reliable performance in the sub-kilowatt power range. More advanced SNS can enable new mission objectives where high energy density solutions are critical, or where access to solar solutions is prohibitive. Higher power radioisotope and fission systems are under development within NASA for a wide variety of human exploration and science mission applications. Planned missions designed to use radioisotope systems include Dragonfly, a rotorcraft that will explore the surface of Titan, and Persephone, a mission concept for a Pluto orbiter. Nuclear fission systems have the key advantage of providing significantly higher power, lower mass solutions from tens to even thousands of kilowatts. Fission power is enabling to a sustained human presence on the Moon and developing a robust lunar economy. Fission propulsion is enabling for missions within and beyond cis-lunar space. This report examines NASA-envisioned mission applications and associated performance needs for SNS over the next twenty years leading to 2040 along with the unique technical considerations posed by space nuclear technology development. This includes engineering and operational logistics for ground handling, thermal management, survival of the space environment, operational safety, power requirements, and service longevity. Safety to the public, the NASA work force, and agency assets remains a top priority for NASA and particular attention is given to this aspect in the design, hardware assembly, ground operation, launch, and mission operation of an SNS. NASA relies on the Department of Energy as nuclear authority and its legacy of rigorous safety procedures as standards for ground development, test, transportation, and launch site operation. The principal concern is preventing unintended radiological release to the public or environment. Radioisotope system experience has established processes, including ground operation, transportation, and launch, that are considered directly applicable to emerging fission systems; however, fission systems have unique design needs that impact the safety and performance requirements. High efficiency power conversion from both fission and radioisotope systems requires high operating temperatures necessitating both passive and active thermal management to maintain safe and nominal operating conditions. Effective cooling and waste heat rejection have special considerations for space applications, whether in zero-g or reduced gravity. Fluid and heat transfer within the reactor system is not anticipated to be impacted by reduced or zero-g environments. Cryogenic working fluids and propellant supplies utilized in some space nuclear applications will need low mass, high capacity cryocoolers to meet the long-term storage and near zero-boiloff needs. Integrated, high power density SNS capable of being packaged in a single vehicle is a key consideration for NASA. Due to concerns for complexity and reliability, in space reactor assembly and reactor refueling are not current design considerations. Expanding into a new era for space exploration depends on mass-efficient, high-energy solutions to power deep-space vehicles, operate in harsh environments, and increase mission flexibility. NASA nuclear technology investments are targeting power for surface operations and propulsion for fast-transit, deep-space missions, all with the ability to reliably operate without the need for repair or refueling. NASA’s goals, enabled by nuclear technologies, provide for exciting advances in scientific objectives and human exploration, ushering in a new space age that enables a human presence on bodies beyond our Earth.

nuclear↗

Gateway Autonomy for Enabling Deep Space Exploration

The Gateway spacecraft is an important stepping-stone to exploration of the solar system, integrating commercial and international partners into a tightly coupled system, enabling cislunar activities, and implementing key technologies for missions to Mars. Autonomy is a capability area necessary to handle long communication outages where intervention from Earth is impossible, to prepare to operate with long communication delays that will be common in interplanetary travel, and to make spaceflight more affordable and accessible by reducing sustaining operations costs. The Gateway Concept of Operations states that one of Gateway’s goals is to “focus on infrastructure and systems that will allow autonomous operations aboard the Gateway with robotics, automated systems, advanced communications, and distributed computing.” Gateway’s Vehicle Systems Manager (VSM) and associated Autonomous Spacecraft Management Architecture (ASMA) are key products towards delivering autonomous capability. The primary functions of the control architecture are Mission Management and Timeline Execution, Resource Management, Fault Management, and Vehicle Control and Operation (VCO). In each of these areas, there is an initial level of capability to be delivered at launch, with plans to continue development and grow to greater capability. The initial deployment of VSM will focus on maintaining vehicle safety by focusing on full fault management capabilities and deploying only enough resource and timeline planning functionality to support that. The final deployment of VSM will add significant planning and control optimization functionality to support nominal operations for up to 21 days without ground support, even accommodating fault and failure conditions. While the VSM is the vehicle-level representation of autonomous reasoning, distributed automation is essential to provide the right scope and abstraction of information to process. Module and system support of automation and simplicity of interfaces are two important design paradigms that Gateway is focusing on to garner a systems approach to autonomy. Distribution of reasoning can increase complexity, so Gateway is also taking a strict hierarchical approach to information flow and decision making. VSM is not the only capability necessary to achieve an autonomous spacecraft. Robotics support for maintenance of the spacecraft will be essential to provide continued vehicle functionality even when crew is not present. Technical and programmatic challenges exist when implementing autonomous robotics operations. These challenges include sufficient network flexibility to support data transfer to the rest of the vehicle to coordinate module-to-module robotic walk-offs and finding the proper interfaces to allow sufficient dexterity. Communication system upgrades planned for Gateway include Delay Tolerant Networking to best utilize the complex network of relays that will be part of mature cislunar operations. Distributed computing and management will provide failure tolerance, robustness, and growth of capabilities while still allowing significant reuse of heritage software on heritage systems as well as reuse of common applications across a spacecraft to minimize new development, but this requires adherence to key standards and interfaces. The Gateway program has demonstrated significant progress towards these capabilities and has identified challenges other spacecraft developers should be aware of from the start.

Molly Anderson↗

Gateway Autonomy for Enabling Deep Space Exploration

The Gateway spacecraft is an important stepping-stone to exploration of the solar system, integrating commercial and international partners into a tightly coupled system, enabling cislunar activities, and implementing key technologies for missions to Mars. Autonomy is a capability area necessary to handle long communication outages where intervention from Earth is impossible, to prepare to operate with long communication delays that will be common in interplanetary travel, and to make spaceflight more affordable and accessible by reducing sustaining operations costs. The Gateway Concept of Operations states that one of Gateway’s goals is to “focus on infrastructure and systems that will allow autonomous operations aboard the Gateway with robotics, automated systems, advanced communications, and distributed computing.” Gateway’s Vehicle Systems Manager (VSM) and associated Autonomous Spacecraft Management Architecture (ASMA) are key products towards delivering autonomous capability. The primary functions of the control architecture are Mission Management and Timeline Execution, Resource Management, Fault Management, and Vehicle Control and Operation (VCO). In each of these areas, there is an initial level of capability to be delivered at launch, with plans to continue development and grow to greater capability. The initial deployment of VSM will focus on maintaining vehicle safety by focusing on full fault management capabilities and deploying only enough resource and timeline planning functionality to support that. The final deployment of VSM will add significant planning and control optimization functionality to support nominal operations for up to 21 days without ground support, even accommodating fault and failure conditions. While the VSM is the vehicle-level representation of autonomous reasoning, distributed automation is essential to provide the right scope and abstraction of information to process. Module and system support of automation and simplicity of interfaces are two important design paradigms that Gateway is focusing on to garner a systems approach to autonomy. Distribution of reasoning can increase complexity, so Gateway is also taking a strict hierarchical approach to information flow and decision making. VSM is not the only capability necessary to achieve an autonomous spacecraft. Robotics support for maintenance of the spacecraft will be essential to provide continued vehicle functionality even when crew is not present. Technical and programmatic challenges exist when implementing autonomous robotics operations. These challenges include sufficient network flexibility to support data transfer to the rest of the vehicle to coordinate module-to-module robotic walk-offs and finding the proper interfaces to allow sufficient dexterity. Communication system upgrades planned for Gateway include Delay Tolerant Networking to best utilize the complex network of relays that will be part of mature cislunar operations. Distributed computing and management will provide failure tolerance, robustness, and growth of capabilities while still allowing significant reuse of heritage software on heritage systems as well as reuse of common applications across a spacecraft to minimize new development, but this requires adherence to key standards and interfaces. The Gateway program has demonstrated significant progress towards these capabilities and has identified challenges other spacecraft developers should be aware of from the start.

Molly Anderson↗

Conjunction Assessment and Deconfliction Paradigm for Co-Located Satellite Constellations With on-Spacecraft “Autonomous” Flight Dynamics Control

Satellite constellations that employ on-spacecraft flight dynamics and conjunction assessment (CA) approaches face particular challenges. First, they must arrange to obtain and upload to the constellation satellite close approach information, such as Conjunction Data Messages, so that their on-board systems will have the data they need to make informed CA decisions. Second, given current latencies in obtaining CA screening information, such systems often cannot obtain dedicated screenings of their proposed maneuvers before they are executed. Third, they usually cannot engage in real time with owner/operators (O/Os) with whom they may come into conjunction, relying instead on pre-arranged courses of action that may or may not fit a given situation well. Despite these difficulties, it is nonetheless possible, as operators such as SpaceX have demonstrated, to operate safely using on-board CA calculations, in the presence of a largely collaborative operating environment. The situation breaks down, however, when two constellations that operate with such a paradigm are placed in the same orbital region and will experience conjunctions with each other. Each may have a vague idea of where the other’s satellites are, or perhaps even a somewhat precise idea if they exchange O/O ephemerides, but neither will know the other’s more immediate maneuver intentions, especially for situations in which they are in a high-risk conjunction with each other and a mitigation maneuver is required. As there is no formalized way for these automated systems to ascertain each other’s intentions for this type of conjunction, it is quite possible that each spacecraft may choose a maneuver that results in the two objects’ colliding. An opportunity to develop a solution to this problem was presented by the NASA “Starling” project, a small experimental constellation developed to demonstrate autonomous satellite control and constellation reconfiguration and for which a launch was obtained that, serendipitously, will place this constellation close to the SpaceX Starlink constellation. Because the NASA constellation is experimental, an extended mission part of the mission has been negotiated to implement and test mechanisms for resolving the problem of co-located constellations with on-board flight dynamics control. For the last eighteen months, a consortium among NASA Ames (the Starling satellite providers), NASA CARA (the Agency organization responsible for conjunction assessment), Space X, and the Department of Commerce (in observer status) has met regularly to assemble a concept of operations for a robust solution to this problem and has developed a prototype ground node that will serve as a needed CA screening and information dispensary. The approach and methods, as well as the active employment of the developed ground node, will be tested both in simulation before actual use and then in actual spacecraft operations, which are anticipated to begin in January 2024. This paper will describe the co-located autonomously-controlled constellation problem and the developed solution in detail, outlining what ground node (i.e., government) infrastructure and features are required, what particular capabilities are needed by the constellations themselves in order to make use of this deconfliction paradigm, and the migration path forward to allow such a capability set to be incorporated by the Department of Commerce’s space traffic coordination system.

Conjunction Assessment↗

Building an Economical and Sustainable Lunar Infrastructure to Enable Lunar Industrialization

A new concept study was initiated to examine the architecture needed to gradually develop an economical, evolvable and sustainable lunar infrastructure using a public/private partnerships approach. This approach would establish partnership agreements between NASA and industry teams to develop a lunar infrastructure system that would be mutually beneficial. This approach would also require NASA and its industry partners to share costs in the development phase and then transfer operation of these infrastructure services back to its industry owners in the execution phase. These infrastructure services may include but are not limited to the following: lunar cargo transportation, power stations, communication towers and satellites, autonomous rover operations, landing pads and resource extraction operations. The public/private partnerships approach used in this study leveraged best practices from NASA's Commercial Orbital Transportation Services (COTS) program which introduced an innovative and economical approach for partnering with industry to develop commercial cargo services to the International Space Station. This program was planned together with the ISS Commercial Resupply Services (CRS) contracts which was responsible for initiating commercial cargo delivery services to the ISS for the first time. The public/private partnerships approach undertaken in the COTS program proved to be very successful in dramatically reducing development costs for these ISS cargo delivery services as well as substantially reducing operational costs. To continue on this successful path towards installing economical infrastructure services for LEO and beyond, this new study, named Lunar COTS (Commercial Operations and Transport Services), was conducted to examine extending the NASA COTS model to cis-lunar space and the lunar surface. The goals of the Lunar COTS concept are to: 1) develop and demonstrate affordable and commercial cis-lunar and surface capabilities, such as lunar cargo delivery and surface power generation, in partnership with industry; 2) incentivize industry to establish economical and sustainable lunar infrastructure services to support NASA missions and initiate lunar commerce; and 3) encourage creation of new space markets for economic growth and benefit. A phased-development approach was also studied to allow for incremental development and demonstration of capabilities needed to build a lunar infrastructure. This paper will describe the Lunar COTS concept goals, objectives and approach for building an economical and sustainable lunar infrastructure. It will also describe the technical challenges and advantages of developing and operating each infrastructure element. It will also describe the potential benefits and progress that can be accomplished in the initial phase of this Lunar COTS approach. Finally, the paper will also look forward to the potential of a robust lunar industrialization environment and its potential effect on the next 50 years of space exploration.

Zuniga, Allison F.↗

Studying Turbulence Using Numerical Simulation Databases: Proceedings of the Summer Program - No. 7

The Seventh Summer Program of the Center for Turbulence Research took place in the four-week period, July 5 to July 31, 1998. This was the largest CTR Summer Program to date, involving thirty-six participants from the U. S. and nine other countries. Thirty-one Stanford and NASA-Ames staff members facilitated and contributed to most of the Summer projects. A new feature, and perhaps a preview of the future programs, was that many of the projects were executed on non-NASA computers. These included supercomputers located in Europe as well as those operated by the Departments of Defense and Energy in the United States. In addition, several simulation programs developed by the visiting participants at their home institutions were used. Another new feature was the prevalence of lap-top personal computers which were used by several participants to carry out some of the work that in the past were performed on desk-top workstations. We expect these trends to continue as computing power is enhanced and as more researchers (many of whom CTR alumni) use numerical simulations to study turbulent flows. CTR's main role continues to be in providing a forum for the study of turbulence for engineering analysis and in facilitating intellectual exchange among the leading researchers in the field. Once again the combustion group was the largest. Turbulent combustion has enjoyed remarkable progress in using simulations to address increasingly complex and practically more relevant questions. The combustion group's studies included such challenging topics as fuel evaporation, soot chemistry, and thermonuclear reactions. The latter study was one of three projects related to the Department of Energy's ASCI Program (www.llnl.gov/asci); the other two (rocket propulsion and fire safety) were carried out in the turbulence modeling group. The flow control and acoustics group demonstrated a successful application of the so-called evolution algorithms which actually led to a previously unknown forcing strategy for jets yielding increased spreading rate. A very efficient algorithm for flow in complex geometries with moving boundaries based on the immersed boundary forcing technique was tested with very encouraging results. Also a new strategy for the destruction of aircraft trailing vortices was introduced and tested. The Reynolds Averaged Modeling (RANS) group demonstrated that the elliptic relaxation concept for RANS calculations is also applicable to transonic flows with shocks; however, prediction of laminar/turbulent transition remains an important pacing item. A large fraction of the LES effort was devoted to the development and testing of a new algorithmic procedure (as opposed to phenomenological model) for subgrid scale modeling based on regularized de-filtering of the flow variables. This appears to be a very promising approach, and a significant effort is currently underway to assess its robustness in high Reynolds number flows and in conjunction with numerical methods for complex flows. As part of the Summer Program two review tutorials were given on Turbulent structures in hydrocarbon pool fires (Sheldon Tieszen), and Turbulent combustion modeling: from RANS to LES via DNS (Luc Vervisch); and two seminars entitled Assessment of turbulence models for engineering applications (Paul Durbin) and Subgrid-scale modeling for non-premixed, turbulent reacting flows (James Riley) were presented. A number of colleagues from universities, government agencies, and industry attended the final presentations of the participants on July 31 and participated in the discussions. There are twenty-six papers in this volume grouped in five areas. Each group is preceded with an overview by its coordinator.

Source record↗

High-Order Methods in NASA’s Next Generation of Computational Fluid Dynamics Tools

The missions of the National Aeronautics and Space Administration (NASA) routinely produce unique requirements and challenges for development and application of Computational Fluid Dynamics (CFD) methods. NASA presently embodies four distinct Mission Directorates: Aeronautics Research, Exploration Systems, Science, and Space Operations. These missions generate requirements for systems that operate in a wide variety of environments. They range from the high-speed flight of aerodynamically optimized vehicles operating in the earth’s atmosphere to spacecraft designed for missions that don’t favor aerodynamic optimization, some operating in the atmosphere of planets and planetary moons such as Mars and Venus or Saturn’s moon Titan. Systems supporting these vehicles, such as rocket and jet propulsion, reaction control systems, fluid and thermal transfer systems, etc. can also generate their own unique set of flow phenomena that challenge today’s CFD methodology. Through the NASA Engineering and Safety Center (NESC), NASA annually conducts state-of-the-discipline assessments in fifteen distinct engineering disciplines. These assessments are performed by the NASA Technical Fellows that lead Technical Discipline Teams (TDT) of recognized experts in these fifteen areas. In the Aerosciences discipline, three topics have been identified as the top challenges for the discipline: aero-plume interaction prediction, unsteady separated flows, and aerothermodynamic prediction. These challenge areas are defined by the Agency’s high-risk projects and problems on which the NESC is requested to perform independent testing, analysis, and assessments. When viewed as a whole, these tests, analyses, and assessments provide a clear view of the recurring technical challenges facing Agency engineers and researchers and can be used to guide future research and technology development. The present state-of-the-art in the application of CFD at NASA is the use of Reynolds-Averaged Navier- Stokes (RANS) solvers, primarily executed in a steady-state mode of operation. In isolated cases, Unsteady RANS (URANS) solvers have been employed when steady RANS solutions produce poorly converging or oscillating results or in cases, such as aeroelastic analysis, which require unsteady aerodynamic simulation. For most traditional external and internal aerodynamic flows, structured overset grids or unstructured grids are employed to minimize geometric modeling and grid generation times. Grid adaptation, primarily as a series of coarse-grain intermediate processing steps is also seeing use on particularly complex flow problems and configurations. In the case of aerothermodynamic flows, engineers have been forced to continue to employ structured grid techniques as the present unstructured grid methodology has proven inadequate in the prediction of surface heating. In the area of aero-plume interaction modeling, two-gas, frozen chemistry simulation is generally the state-of-the- art, with some production solvers capable of predicting flows with only a single gas component. Prediction of flows falling into the afore-mentioned top Aerosciences technical challenges have severely stressed the present state-of-the-art in CFD prediction and for some problems, such as unsteady separated flows and aero-plume interaction cases, engineers have begun employing Large Eddy Simulation (LES) and Hybrid RANS/LES techniques. In some isolated aero-propulsion interaction cases, chemically reacting flow simulations have been applied. These methods are highly evolutionary and engineers have little experience in their application, so they cannot be heavily relied upon in today’s application environment. Therefore, this leads one to muse over which numerical technologies will be included in the CFD tools that will be employed 30 years in the future. This presentation will describe specific technical problems that have stressed NASA’s traditional CFD methods to their breaking point and will link these issues to the Agency’s top Aerosciences technical challenges. The discussion will then shift to the characteristics of future CFD solvers that will be required to attack these challenges and how these characteristics differ from the present state-of-the- art. High-order methods certainly appear to have a place in the development of future CFD tools and some of the physical characteristics of our most challenging problems suggest that high-order methods are the only way to effectively solve them. But there are some relatively severe implementation issues that face these methods, particularly in the area of general applicability and robust operation as an engineering tool. Desired characteristics of next-generation CFD solvers will be discussed and the author’s view of which emerging numerical technologies might be employed to address these attributes will also be presented

David M Schuster↗

Reducing Risk of InSight Surface Operations Through High-Fidelity Command Sequence Modeling

Simulating spacecraft behavior is crucial for the success of deep space missions, and failure to do so may result in damages to or the loss of the spacecraft. Many previous deep space missions have made use of ground-simulation of sequenced commanding, at speeds far greater than real time, to predict spacecraft state over time through the execution of onboard sequences. This type of modeling can be done at any fidelity, and most missions have opted to decrease fidelity to reduce cost and complexity. However, NASA’s Interior Exploration using Seismic Investigations, Geodesy and Heat Transport (InSight) mission expanded the scope of ground modeling considerably, which has led to numerous benefits over past implementations. This paper will discuss the process and products that InSight created, as well as the lessons learned from successfully operating the spacecraft on Mars. InSight is the first JPL mission to expand the scope of ground modeling to include the uplink of files from Earth to the spacecraft, rather than making the simplification that any command sequences already exist onboard the spacecraft. The advantages of modeling the uplink of files are numerous. First, it allows for accurate modeling of the onboard filesystem of the spacecraft at all points in time, meaning that all file loads and deletions throughout the mission are modeled at the exact moment they are predicted to actually happen. Second, operators can be more certain that dependencies between sequences are not broken due to the dynamic nature of the filesystem as files are deleted, copied, and uplinked. Lastly, spacecraft filesystem tracking allows for management of sequences prior to uplink, limiting the uplink to only new sequences. The onboard filesystem model became crucial to mission success, emphasizing the importance of investing in accurate models before the need for them arises. During daily tactical operations of a spacecraft on Mars, a model is only useful if the results can be interpreted quickly. In this fast-paced environment, it is essential that command products are modeled and reviewed, errors are found and diagnosed, and new command products are redelivered, remodeled, re-reviewed in a timely manner. It is impossible to review the entire model and therefore the results of the model must be condensed and presented in a fashion that is intuitive, easy-to-navigate, complete, and trustworthy. InSight developed a number of innovative sequence review products that are designed to provide operators with the information required to quickly assess the validity of command products and diagnose potential issues. Together, these products provide a complete, yet succinct picture of the command and sequence model to the operators and facilitate a quick assessment of all sequence command products. This paper will cover planning and sequencing innovations made during InSight surface operations, and will compare the tools, processes, and results to those on other missions. Additionally, the paper will cover the flexible, yet robust nature of the planning and sequencing system architecture and how that flexibility allowed for rapid development and response to the unpredictability of Mars.

Cloutier, Kyle↗

A Comparison Between Orion Automated and Space Shuttle Rendezvous Techniques

The Orion spacecraft will replace the space shuttle and will be the first human spacecraft since the Apollo program to leave low earth orbit. This vehicle will serve as the cornerstone of a complete space transportation system with a myriad of mission requirements necessitating rendezvous to multiple vehicles in earth orbit, around the moon and eventually beyond . These goals will require a complex and robust vehicle that is, significantly different from both the space shuttle and the command module of the Apollo program. Historically, orbit operations have been accomplished with heavy reliance on ground support and manual crew reconfiguration and monitoring. One major difference with Orion is that automation will be incorporated as a key element of the man-vehicle system. The automated system will consist of software devoted to transitioning between events based on a master timeline. This effectively adds a layer of high level sequencing that moves control of the vehicle from one phase to the next. This type of automated control is not entirely new to spacecraft since the shuttle uses a version of this during ascent and entry operations. During shuttle orbit operations however many of the software modes and hardware switches must be manually configured through the use of printed procedures and instructions voiced from the ground. The goal of the automation scheme on Orion is to extend high level automation to all flight phases. The move towards automation represents a large shift from current space shuttle operations, and so these new systems will be adopted gradually via various safeguards. These include features such as authority-to-proceed, manual down modes, and functional inhibits. This paper describes the contrast between the manual and ground approach of the space shuttle and the proposed automation of the Orion vehicle. I will introduce typical orbit operations that are common to all rendezvous missions and go on to describe the current Orion automation architecture and contrast it with shuttle rendezvous techniques and circumstances. The shuttle rendezvous profile is timed to take approximately 3 days from orbit insertion to docking at the International Space Station (ISS). This process can be divided into 3 phases: far-field, mid-field and proximity operations. The far-field stage is characterized as the most quiescent phase. The spacecraft is usually too far to navigate using relative sensors and uses the Inertial Measurement Units (IMU s) to numerically solve for its position. The maneuvers are infrequent, roughly twice per day, and are larger than other burns in the profile. The shuttle uses this opportunity to take extensive ground based radar updates and keep high fidelity orbit states on the ground. This state is then periodically uplinked to the shuttle computers. The targeting solutions for burn maneuvers are also computed on the ground and uplinked. During the burn the crew is responsible for setting the shuttle attitude and configuring the propulsion system for ignition. Again this entire process is manually driven by both crew and ground activity. The only automatic processes that occur are associated with the real-time execution of the burn. The Orion automated functionality will seek to relieve the workload of both the crew and ground during this phase

Ruiz, Jose O,↗