Project Apollo - Analysis of landing point designator operation
Analysis of lunar landing point designator operation
SEARCH · Search NASA
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.
Analysis of lunar landing point designator operation
We give for Machine Learning (ML)-based aeronautical products, a first rigorous characterization of Operational Design Domains (ODDs). Unlike in other application sectors (such as self-driving road vehicles) where ODD development is scenario-based, our approach is data-centric: we propose the dimensions along which the parameters that define an ODD can be explicitly captured, using a top-down approach starting from system specifications, and a bottom-up approach starting from detailed ML Model (MLM) designs. Then we give a categorization of the data that ML-based applications can encounter in operation, identifying their system-level relevance and impact. Specifically, we discuss how those data categories are useful to determine: (1) the requirements necessary to drive the design of MLMs; (2) the potential effects on the MLM and higher levels of the system hierarchy; (3) the learning assurance processes that may be needed, and (4) system architectural considerations. We illustrate the underlying concepts with an example of an aircraft flight envelope. The approach in this paper is one of the cornerstones of a future process guidance for development and certification/approval of safety-related aeronautical products implementing Artificial Intelligence (AI), currently being developed through aviation industry-based consensus, jointly by the SAE G-34 Committee for AI in aviation, and EUROCAE WG-114 for AI.
A description of the Langley thermal protection system test facility is presented. This facility was designed to provide realistic environments and times for testing thermal protection systems proposed for use on high speed vehicles such as the space shuttle. Products from the combustion of methane-air-oxygen mixtures, having a maximum total enthalpy of 10.3 MJ/kg, are used as a test medium. Test panels with maximum dimensions of 61 cm x 91.4 cm are mounted in the side wall of the test region. Static pressures in the test region can range from .005 to .1 atm and calculated equilibrium temperatures of test panels range from 700 K to 1700 K. Test times can be as long as 1800 sec. Some experimental data obtained while using combustion products of methane-air mixtures are compared with theory, and calibration of the facility is being continued to verify calculated values of parameters which are within the design operating boundaries.
Hypersonic 11-inch ceramic-heated wind tunnel - design, operation, and testing
Application of Virtual Reality (VR) technology offers much promise to enhance and accelerate the development of Reusable Launch Vehicle (RLV) infrastructure and operations while simultaneously reducing developmental and operational costs. One of the primary cost areas in the RLV concept that is receiving special attention is maintenance and refurbishment operations. To produce and operate a cost effective RLV, turnaround cost must be minimized. Designing for maintainability is a necessary requirement in developing RLVs. VR can provide cost effective methods to design and evaluate components and systems for maintenance and refurbishment operations. The National Aeronautics and Space Administration (NASA)/Marshall Space Flight Center (MSFC) is beginning to utilize VR for design, operations development, and design analysis for RLVs. A VR applications program has been under development at NASA/MSFC since 1989. The objectives of the MSFC VR Applications Program are to develop, assess, validate, and utilize VR in hardware development, operations development and support, mission operations training and science training. The NASA/MSFC VR capability has also been utilized in several applications. These include: 1) the assessment of the design of the late Space Station Freedom Payload Control Area (PCA), the control room from which onboard payload operations are managed; 2) a viewing analysis of the Tethered Satellite System's (TSS) "end-of-reel" tether marking options; 3) development of a virtual mockup of the International Space Welding Experiment for science viewing analyses from the Shuttle Remote Manipulator System elbow camera and as a trainer for ground controllers; and 4) teleoperations using VR. This presentation will give a general overview of the MSFC VR Applications Program and describe the use of VR in design analyses, operations development, and training for RLVs.
Designs are usually done in a well-lit, air conditioned, comfortable room under idealized assumptions. The reality of the operation is very different. For designers to be able to design systems and procedures that work well under realistic dynamic work conditions, they must understand the reality of the operation and of the operators. The talk discusses the gap between the idealized design and the real operation and proposes a framework, THE Model, for designing systems and procedures fit for real operations.
Design and operation of onboard spacecraft computer
Designed and funded in the pre-'better, faster, cheaper' era, Cassini was built to be the one mission to Saturn for many years to come. Its complement of twelve Orbiter science instruments and the Huygens Probe make Cassini one of the most complex missions ever flown. With a seven-year cruise and Saturn Orbit Insertion now over, Cassini is settling in to perform a very ambitious prime mission over the next four years. This paper provides an overview of the spacecraft design and the mission operations to date.
For most of the history of space exploration, human and robotic programs have been independent, and have responded to distinct requirements. The NASA Vision for Space Exploration calls for the return of humans to the Moon, and the eventual human exploration of Mars; the complexity of this range of missions will require an unprecedented use of automation and robotics in support of human crews. The challenges of human Mars missions, including roundtrip communications time delays of 6 to 40 minutes, interplanetary transit times of many months, and the need to manage lifecycle costs, will require the evolution of a new mission operations paradigm far less dependent on real-time monitoring and response by an Earthbound operations team. Robotic systems and automation will augment human capability, increase human safety by providing means to perform many tasks without requiring immediate human presence, and enable the transfer of traditional mission control tasks from the ground to crews. Developing and validating the new paradigm and its associated infrastructure may place requirements on operations design for nearer-term lunar missions. The authors, representing both the human and robotic mission operations communities, assess human lunar and Mars mission challenges, and consider how human-robot operations may be integrated to enable efficient joint operations, with the eventual emergence of a unified exploration operations culture.
For most of the history of space exploration, human and robotic programs have been independent, and have responded to distinct requirements. The NASA Vision for Space Exploration calls for the return of humans to the Moon, and the eventual human exploration of Mars; the complexity of this range of missions will require an unprecedented use of automation and robotics in support of human crews. The challenges of human Mars missions, including roundtrip communications time delays of 6 to 40 minutes, interplanetary transit times of many months, and the need to manage lifecycle costs, will require the evolution of a new mission operations paradigm far less dependent on real-time monitoring and response by an Earthbound operations team. Robotic systems and automation will augment human capability, increase human safety by providing means to perform many tasks without requiring immediate human presence, and enable the transfer of traditional mission control tasks from the ground to crews. Developing and validating the new paradigm and its associated infrastructure may place requirements on operations design for nearer-term lunar missions. The authors, representing both the human and robotic mission operations communities, assess human lunar and Mars mission challenges, and consider how human-robot operations may be integrated to enable efficient joint operations, with the eventual emergence of a unified exploration operations culture.
For most of the history of space exploration, human and robotic programs have been independent, and have responded to distinct requirements. The NASA Vision for Space Exploration calls for the return of humans to the Moon, and the eventual human exploration of Mars; the complexity of this range of missions will require an unprecedented use of automation and robotics in support of human crews. The challenges of human Mars missions, including roundtrip communications time delays of 6 to 40 minutes, interplanetary transit times of many months, and the need to manage lifecycle costs, will require the evolution of a new mission operations paradigm far less dependent on real-time monitoring and response by an Earthbound operations team. Robotic systems and automation will augment human capability, increase human safety by providing means to perform many tasks without requiring immediate human presence, and enable the transfer of traditional mission control tasks from the ground to crews. Developing and validating the new paradigm and its associated infrastructure may place requirements on operations design for nearer-term lunar missions. The authors, representing both the human and robotic mission operations communities, assess human lunar and Mars mission challenges, and consider how human-robot operations may be integrated to enable efficient joint operations, with the eventual emergence of a unified exploration operations culture.
The Trash Compaction and Processing System (TCPS) aims to reduce volume, biologically safen, physically stabilize, manage effluents, and recover resources from astronaut trash in the International Space Station (ISS). This process involves heating the trash to high temperatures, which in turn releases gaseous contaminants. Effluent management scenarios involve releasing these gases back to the ISS cabin after processing and/or directly venting these gases out to space via the Vacuum Exhaust System (VES). Concerns for recovering the gases back to cabin are crew health, safety, and spacecraft environmental impact. The Heat Melt Compactor (HMC) at NASA Ames Research Center (ARC) serves as a test system that supports TCPS development by conducting risk reduction activities associated with an ISS flight demonstration. Previous gas effluent studies were conducted on the HMC. The results consisted of contaminants from the trash exhaust to exceed Spacecraft Maximum Allowable Concentrations (SMAC), which are selected airborne contaminants that can elicit toxicity symptoms to crewmembers via exposure. The Source Contaminant Control System (SCCS) aims to reduce that risk by converting the contaminants into carbon dioxide (CO2) and water (H2O) vapor. The SCCS is composed of a carbon adsorbent bed, to avoid catalyst poisoning, and a catalytic oxidizer (CatOx), which promotes oxidation of the contaminants to CO2and H2O. In turn, the gases coming out of the SCCS should be compatible to the ISS cabin and systems such as the Trace Contaminant Control System (TCCS). Preparation for SCCS testing alongside the HMC Gen 3 are currently underway at ARC. The main objectives are to evaluate CatOx efficiency by CO2conversion and characterize effectiveness of removal by comparing contaminant results before and after CatOx. This paper will report on the SCCS design, operation, and testing with results.
The Trash Compaction and Processing System (TCPS) aims to reduce volume, biologically safen, physically stabilize, manage effluents, and recover resources from astronaut trash in the International Space Station (ISS). This process involves heating the trash to high temperatures, which in turn releases gaseous contaminants. Effluent management scenarios involve releasing these gases back to the ISS cabin after processing and/or directly venting these gases out to space via the Vacuum Exhaust System (VES). Concerns for recovering the gases back to cabin are crew health, safety, and spacecraft environmental impact. The Heat Melt Compactor (HMC) at NASA Ames Research Center (ARC) serves as a test system that supports TCPS development by conducting risk reduction activities associated with an ISS flight demonstration. Previous gas effluent studies were conducted on the HMC. The results consisted of contaminants from the trash exhaust to exceed Spacecraft Maximum Allowable Concentrations (SMAC), which are selected airborne contaminants that can elicit toxicity symptoms to crewmembers via exposure. The Source Contaminant Control System (SCCS) aims to reduce that risk by converting the contaminants into carbon dioxide (CO2) and water (H2O) vapor. The SCCS is composed of a carbon adsorbent bed, to avoid catalyst poisoning, and a catalytic oxidizer (CatOx), which promotes oxidation of the contaminants to CO2 and H2O. In turn, the gases coming out of the SCCS should be compatible to the ISS cabin and systems such as the Trace Contaminant Control System (TCCS). Preparation for SCCS testing alongside the HMC Gen 3 are currently underway at ARC. The main objectives are to evaluate CatOx efficiency by CO2 conversion and characterize effectiveness of removal by comparing contaminant results before and after CatOx. This paper will report on the SCCS design, operation, and testing with results.
Historically, command management systems (CMS) have been large and expensive spacecraft-specific software systems that were costly to build, operate, and maintain. Current and emerging hardware, software, and user interface technologies may offer an opportunity to facilitate the initial formulation and design of a spacecraft-specific CMS as well as to develop a more generic CMS system. New technologies, in addition to a core CMS common to a range of spacecraft, may facilitate the training and enhance the efficiency of CMS operations. Current mission operations center (MOC) hardware and software include Unix workstations, the C/C++ programming languages, and an X window interface. This configuration provides the power and flexibility to support sophisticated and intelligent user interfaces that exploit state-of-the-art technologies in human-machine interaction, artificial intelligence, and software engineering. One of the goals of this research is to explore the extent to which technologies developed in the research laboratory can be productively applied in a complex system such as spacecraft command management. Initial examination of some of these issues in CMS design and operation suggests that application of technologies such as intelligent planning, case-based reasoning, human-machine systems design and analysis tools (e.g., operator and designer models), and human-computer interaction tools (e.g., graphics, visualization, and animation) may provide significant savings in the design, operation, and maintenance of the CMS for a specific spacecraft as well as continuity for CMS design and development across spacecraft. The first six months of this research saw a broad investigation by Georgia Tech researchers into the function, design, and operation of current and planned command management systems at Goddard Space Flight Center. As the first step, the researchers attempted to understand the current and anticipated horizons of command management systems at Goddard. Preliminary results are given on CMS commonalities and causes of low re-use, and methods are proposed to facilitate increased re-use.
Historically Command Management Systems (CMS) have been large, expensive, spacecraft-specific software systems that were costly to build, operate, and maintain. Current and emerging hardware, software, and user interface technologies may offer an opportunity to facilitate the initial formulation and design of a spacecraft-specific CMS as well as a to develop a more generic or a set of core components for CMS systems. Current MOC (mission operations center) hardware and software include Unix workstations, the C/C++ and Java programming languages, and X and Java window interfaces representations. This configuration provides the power and flexibility to support sophisticated systems and intelligent user interfaces that exploit state-of-the-art technologies in human-machine systems engineering, decision making, artificial intelligence, and software engineering. One of the goals of this research is to explore the extent to which technologies developed in the research laboratory can be productively applied in a complex system such as spacecraft command management. Initial examination of some of the issues in CMS design and operation suggests that application of technologies such as intelligent planning, case-based reasoning, design and analysis tools from a human-machine systems engineering point of view (e.g., operator and designer models) and human-computer interaction tools, (e.g., graphics, visualization, and animation), may provide significant savings in the design, operation, and maintenance of a spacecraft-specific CMS as well as continuity for CMS design and development across spacecraft with varying needs. The savings in this case is in software reuse at all stages of the software engineering process.
The factors that significantly affect the operability of aerospace planes are identified and considered in terms of the development of the National Aerospace Plane (NASP). The aircraftlike vehicle can be affected by variables related to the structure, propulsion, and mechanical elements of the design. The requirements to control the factors are listed including robustness, fuels and propellants, maintainability, autonomy, and development testing. The details of the requirements indicate critical factors such as the strength-to-weight ratios of the materials, propellant-system components that can withstand 5000 consecutive cycles, and low vehicle-failure probabilities. The NASP program is concluded to require: (1) models for quantitative operational assessments; (2) a modular design for the NASP structure; (3) computer-technology integration; and (4) technologies to support and normalize cryogenic operations.
The aerodynamic performances of four stator-blade rows are presented and evaluated. The aerodynamic designs of two of these stators were compromised to reduce noise, a third design was not. On a calculated operating line passing through the design point pressure ratio, the best stator had overall pressure-ratio and efficiency decrements of 0.031 and 0.044, respectively, providing a stage pressure ratio of 1.483 and efficiency of 0.865. The other stators showed some correctable deficiencies due partly to the design compromises for noise. In the end-wall regions blade-element losses were significantly less for the shortest chord studied.
The OSIRIS-REx mission employs a methodical, phased approach to ensure success in meeting the missions science requirements. OSIRIS-REx launches in September 2016, with a backup launch period occurring one year later. Sampling occurs in 2019. The departure burn from Bennu occurs in March 2021. On September 24, 2023, the SRC lands at the Utah Test and Training Range (UTTR). Stardust heritage procedures are followed to transport the SRC to Johnson Space Center, where the samples are removed and delivered to the OSIRIS-REx curation facility. After a six-month preliminary examination period the mission will produce a catalog of the returned sample, allowing the worldwide community to request samples for detailed analysis.Traveling and returning a sample from an Asteroid that has not been explored before requires unique operations consideration. The Design Reference Mission (DRM) ties together space craft, instrument and operations scenarios. The project implemented lessons learned from other small body missions: APLNEAR, JPLDAWN and ESARosetta. The key lesson learned was expected the unexpected and implement planning tools early in the lifecycle. In preparation to PDR, the project changed the asteroid arrival date, to arrive one year earlier and provided additional time margin. STK is used for Mission Design and STKScheduler for instrument coverage analysis.