Search NASA⌕ Search

SEARCH · Search NASA

Results for “COMPUTER PROGRAM DOCUMENTATION”

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 883 records · Page 49

Flammability, Odor, Offgassing, and Compatibility Requirements and Test Procedures for Materials in Environments that Support Combustion

This handbook establishes NASA program requirements for evaluation, testing, and selection of materials to preclude unsafe conditions related to flammability, odor, offgassing, and fluid compatibility. Materials intended for use in space vehicles, specified test facilities, and specified ground support equipment (GSE) must meet the requirements of this document. Additional materials performance requirements may be specified in other program or NASA center specific documentation. Responsible NASA centers materials organizations must include applicable requirements of this document in their materials control programs. Materials used in habitable areas of spacecraft, including the materials of the spacecraft, stowed equipment, and experiments, must be evaluated for flammability, odor, and offgassing characteristics. All materials used in other areas must be evaluated for flammability characteristics. In addition, materials that are exposed to liquid oxygen (LOX), gaseous oxygen (GOX), and other reactive fluids' must be evaluated for compatibility with the fluid in their use application. Materials exposed to pressurized breathing gases also must be evaluated for odor and offgassing characteristics. The worst-case anticipated use environment (most hazardous pressure, temperature, material thickness, and fluid exposure conditions) must be used in the evaluation process. Materials that have been shown to meet the criteria of the required tests are acceptable for further consideration in design. Whenever possible, materials should be selected that have already been shown to meet the test criteria in the use environment. Existing test data are compiled in the NASA Marshall Space Flight Center (MSFC) Materials and Processes Technical Information System (MAPTIS) and published periodically as the latest revision of a joint document with Johnson Space Center (JSC), MSFC-HDBK-527/JSC 09604. MAPTIS can be accessed by computer datalink. Systems containing materials that have not been tested or do not meet the criteria of the required tests must be verified to be acceptable in the use configuration by analysis or testing. This verification rationale must be documented and submitted to the responsible NASA center materials organization for approval.

Source record↗

Detection and avoidance of errors in computer software

The acceptance test errors of a computer software project to determine if the errors could be detected or avoided in earlier phases of development. GROAGSS (Gamma Ray Observatory Attitude Ground Support System) was selected as the software project to be examined. The development of the software followed the standard Flight Dynamics Software Development methods. GROAGSS was developed between August 1985 and April 1989. The project is approximately 250,000 lines of code of which approximately 43,000 lines are reused from previous projects. GROAGSS had a total of 1715 Change Report Forms (CRFs) submitted during the entire development and testing. These changes contained 936 errors. Of these 936 errors, 374 were found during the acceptance testing. These acceptance test errors were first categorized into methods of avoidance including: more clearly written requirements; detail review; code reading; structural unit testing; and functional system integration testing. The errors were later broken down in terms of effort to detect and correct, class of error, and probability that the prescribed detection method would be successful. These determinations were based on Software Engineering Laboratory (SEL) documents and interviews with the project programmers. A summary of the results of the categorizations is presented. The number of programming errors at the beginning of acceptance testing can be significantly reduced. The results of the existing development methodology are examined for ways of improvements. A basis is provided for the definition is a new development/testing paradigm. Monitoring of the new scheme will objectively determine its effectiveness on avoiding and detecting errors.

Kinsler, Les↗

Planetary Geologic Mapping Handbook - 2009

Geologic maps present, in an historical context, fundamental syntheses of interpretations of the materials, landforms, structures, and processes that characterize planetary surfaces and shallow subsurfaces (e.g., Varnes, 1974). Such maps also provide a contextual framework for summarizing and evaluating thematic research for a given region or body. In planetary exploration, for example, geologic maps are used for specialized investigations such as targeting regions of interest for data collection and for characterizing sites for landed missions. Whereas most modern terrestrial geologic maps are constructed from regional views provided by remote sensing data and supplemented in detail by field-based observations and measurements, planetary maps have been largely based on analyses of orbital photography. For planetary bodies in particular, geologic maps commonly represent a snapshot of a surface, because they are based on available information at a time when new data are still being acquired. Thus the field of planetary geologic mapping has been evolving rapidly to embrace the use of new data and modern technology and to accommodate the growing needs of planetary exploration. Planetary geologic maps have been published by the U.S. Geological Survey (USGS) since 1962 (Hackman, 1962). Over this time, numerous maps of several planetary bodies have been prepared at a variety of scales and projections using the best available image and topographic bases. Early geologic map bases commonly consisted of hand-mosaicked photographs or airbrushed shaded-relief views and geologic linework was manually drafted using mylar bases and ink drafting pens. Map publishing required a tedious process of scribing, color peel-coat preparation, typesetting, and photo-laboratory work. Beginning in the 1990s, inexpensive computing, display capability and user-friendly illustration software allowed maps to be drawn using digital tools rather than pen and ink, and mylar bases became obsolete. Terrestrial geologic maps published by the USGS now are primarily digital products using geographic information system (GIS) software and file formats. GIS mapping tools permit easy spatial comparison, generation, importation, manipulation, and analysis of multiple raster image, gridded, and vector data sets. GIS software has also permitted the development of project-specific tools and the sharing of geospatial products among researchers. GIS approaches are now being used in planetary geologic mapping as well (e.g., Hare and others, 2009). Guidelines or handbooks on techniques in planetary geologic mapping have been developed periodically (e.g., Wilhelms, 1972, 1990; Tanaka and others, 1994). As records of the heritage of mapping methods and data, these remain extremely useful guides. However, many of the fundamental aspects of earlier mapping handbooks have evolved significantly, and a comprehensive review of currently accepted mapping methodologies is now warranted. As documented in this handbook, such a review incorporates additional guidelines developed in recent years for planetary geologic mapping by the NASA Planetary Geology and Geophysics (PGG) Program s Planetary Cartography and Geologic Mapping Working Group s (PCGMWG) Geologic Mapping Subcommittee (GEMS) on the selection and use of map bases as well as map preparation, review, publication, and distribution. In light of the current boom in planetary exploration and the ongoing rapid evolution of available data for planetary mapping, this handbook is especially timely.

Tanaka, K. L.↗

Exploration Medical Capability IMPACT Medical Database – Medical Item Database (MedID) Content Development Methods

The Informing Mission Planning via Analysis of Complex Tradespaces (IMPACT) project encompasses a suite of computational tools that are used to inform systematic trade study evaluations and research prioritizations regarding the optimization of spaceflight medical systems, including the provision of risk assessment metrics, for a given design reference mission (DRM). The IMPACT Medical Database (IMPACT-MD) is the component that virtually houses the clinical and engineering data for medical conditions, capabilities, and resources used to support these analyses. In addition, IMPACT-MD also provides data to the associated SysML model to support the Level 2, Level 3, and Level 4 requirements development needed for IMPACT. IMPACT-MD contains an internal Evidence Library (EL) sub-component that hosts the clinical evidence, treatment and outcome metric data, and incidence data for each medical condition identified for exploration-class missions. Furthermore, a separate Medical Item Database (MedID) sub-component hosts the engineering data and physical attributes (e.g., mass, volume, power, etc.) associated with each medical resource item identified to address the requisite medical conditions. The IMPACT project is conducted under the Exploration Medical Capability (ExMC) element of the Human Research Program (HRP) within NASA's Space Operations Mission Directorate (SOMD). The reader is referred to the documents in Appendix A for a more complete overview of the IMPACT tool suite and functionality as well as further detail on any associated aspects of the project. The primary purpose of this document is to describe the methods utilized in the collection and verification of engineering data content during the project development phase for the MedID sub-component of the IMPACT-MD project. Engineering content data (both existing and new/future) will be stored in IMPACT-MD for use by the IMPACT project. This document will detail the content development and data credibility for the engineering data housed within the MedID subcomponent of IMPACT-MD, which is used to inform the IMPACT 1.0 project deliverables.

Exploration Medical Capability↗

FTMP (Fault Tolerant Multiprocessor) programmer's manual

The Fault Tolerant Multiprocessor (FTMP) computer system was constructed using the Rockwell/Collins CAPS-6 processor. It is installed in the Avionics Integration Research Laboratory (AIRLAB) of NASA Langley Research Center. It is hosted by AIRLAB's System 10, a VAX 11/750, for the loading of programs and experimentation. The FTMP support software includes a cross compiler for a high level language called Automated Engineering Design (AED) System, an assembler for the CAPS-6 processor assembly language, and a linker. Access to this support software is through an automated remote access facility on the VAX which relieves the user of the burden of learning how to use the IBM 4381. This manual is a compilation of information about the FTMP support environment. It explains the FTMP software and support environment along many of the finer points of running programs on FTMP. This will be helpful to the researcher trying to run an experiment on FTMP and even to the person probing FTMP with fault injections. Much of the information in this manual can be found in other sources; we are only attempting to bring together the basic points in a single source. If the reader should need points clarified, there is a list of support documentation in the back of this manual.

Feather, F. E.↗

NASA Glenn's Acoustical Testing Laboratory Awarded Accreditation by the National Voluntary Laboratory Accreditation Program

NASA Glenn Research Center's Acoustical Testing Laboratory (ATL) provides a comprehensive array of acoustical testing services, including sound pressure level, sound intensity level, and sound-power-level testing per International Standards Organization (ISO)1 3744. Since its establishment in September 2000, the ATL has provided acoustic emission testing and noise control services for a variety of customers, particularly microgravity space flight hardware that must meet International Space Station acoustic emission requirements. The ATL consists of a 23- by 27- by 20-ft (height) convertible hemi/anechoic test chamber and a separate sound-attenuating test support enclosure. The ATL employs a personal-computer-based data acquisition system that provides up to 26 channels of simultaneous data acquisition with real-time analysis (ref. 4). Specialized diagnostic tools, including a scanning sound-intensity system, allow the ATL's technical staff to support its clients' aggressive low-noise design efforts to meet the space station's acoustic emission requirement. From its inception, the ATL has pursued the goal of developing a comprehensive ISO 17025-compliant quality program that would incorporate Glenn's existing ISO 9000 quality system policies as well as ATL-specific technical policies and procedures. In March 2003, the ATL quality program was awarded accreditation by the National Voluntary Laboratory Accreditation Program (NVLAP) for sound-power-level testing in accordance with ISO 3744. The NVLAP program is administered by the National Institutes of Standards and Technology (NIST) of the U.S. Department of Commerce and provides third-party accreditation for testing and calibration laboratories. There are currently 24 NVLAP-accredited acoustical testing laboratories in the United States. NVLAP accreditation covering one or more specific testing procedures conducted in accordance with established test standards is awarded upon successful completion of an intensive onsite assessment that includes proficiency testing and documentation review. The ATL NVLAP accreditation currently applies specifically to its ISO 3744 soundpower- level determination procedure (see the photograph) and supporting ISO 17025 quality system, although all ATL operations are conducted in accordance with its quality system. The ATL staff is currently developing additional procedures to adapt this quality system to the testing of space flight hardware in accordance with International Space Station acoustic emission requirements.<

Akers, James C.↗

Aerothermodynamic Testing of the Crew Exploration Vehicle in the LaRC 20-Inch Mach 6 and 31-Inch Mach 10 Tunnels

An experimental wind tunnel program is being conducted in support of a NASA wide effort to develop a Space Shuttle replacement and to support the Agency s long term objective of returning to the Moon and Mars. This article documents experimental measurements made on several scaled ceramic heat transfer models of the proposed Crew Exploration Vehicle Crew Module. The experimental data highlighted in this article are to be used to assess numerical tools that will be used to generate the flight aerothermodynamic database. Global heat transfer images and heat transfer distributions were obtained over a range of freestream Reynolds numbers and angles of attack with the phosphor thermography technique. Heat transfer data were measured on the forebody and afterbody and were used to infer the heating on the vehicle as well as the boundary layer state on the forebody surface. Several model support configurations were assessed to minimize potential support interference. In addition, the ability of the global phosphor thermography method to provide quantitative heating measurements in the low temperature environment of the capsule base region was assessed. While naturally fully developed turbulent levels were not obtained on the forebody, the use of boundary layer trips generated fully developed turbulent flow. Laminar and turbulent computational results were shown to be in good agreement with the data. Backshell testing demonstrated the ability to obtain data in the low temperature region as well as demonstrating the lack of significant model support hardware influence on heating.

Berger, Karen T.↗

Aerothermodynamic Testing of the Crew Exploration Vehicle in the LaRC 20-Inch Mach 6 and 31-Inch Mach 10 Tunnels

An experimental wind tunnel program is being conducted in support of a NASA wide effort to develop a Space Shuttle replacement and to support the Agency s long term objective of returning to the Moon and Mars. This report documents experimental measurements made on several scaled ceramic heat transfer models of the proposed Crew Exploration Vehicle Crew Module. The experimental data highlighted in this test report are to be used to assess numerical tools that will be used to generate the flight aerothermodynamic database. Global heat transfer images and heat transfer distributions were obtained over a range of freestream Reynolds numbers and angles of attack with the phosphor thermography technique. Heat transfer data were measured on the forebody and afterbody and were used to infer the heating on the vehicle as well as the boundary layer state on the forebody surface. Several model support configurations were assessed to minimize potential support interference. In addition, the ability of the global phosphor thermography method to provide quantitative heating measurements in the low temperature environment of the capsule base region was assessed. While naturally fully developed turbulent levels were not obtained on the forebody, the use of boundary layer trips generated fully developed turbulent flow. Laminar and turbulent computational results were shown to be in good agreement with the data. Backshell testing demonstrated the ability to obtain data in the low temperature region as well as demonstrating the lack of significant model support hardware influence on heating.

Berger, Karen T.↗

Hardware Interface Description for the Integrated Power, Avionics, and Software (iPAS) Space Telecommunications Radio Ssystem (STRS) Radio

The Space Telecommunications Radio System (STRS) provides a common, consistent framework for software defined radios (SDRs) to abstract the application software from the radio platform hardware. The STRS standard aims to reduce the cost and risk of using complex, configurable and reprogrammable radio systems across NASA missions. To promote the use of the STRS architecture for future NASA advanced exploration missions, NASA Glenn Research Center (GRC) developed an STRS-compliant SDR on a radio platform used by the Advance Exploration System program at the Johnson Space Center (JSC) in their Integrated Power, Avionics, and Software (iPAS) laboratory. The iPAS STRS Radio was implemented on the Reconfigurable, Intelligently-Adaptive Communication System (RIACS) platform, currently being used for radio development at JSC. The platform consists of a Xilinx ML605 Virtex-6 FPGA board, an Analog Devices FMCOMMS1-EBZ RF transceiver board, and an Embedded PC (Axiomtek eBox 620-110-FL) running the Ubuntu 12.4 operating system. Figure 1 shows the RIACS platform hardware. The result of this development is a very low cost STRS compliant platform that can be used for waveform developments for multiple applications.The purpose of this document is to describe how to develop a new waveform using the RIACS platform and the Very High Speed Integrated Circuits (VHSIC) Hardware Description Language (VHDL) FPGA wrapper code and the STRS implementation on the Axiomtek processor.

Flight Computer↗

Bumper: A Tool for Analyzing Spacecraft Micrometeoroid and Orbital Debris Risk

“Bumper” is NASA’s computer program for analyzing spacecraft micrometeoroid and orbital debris (MMOD) risk. Bumper was developed in the late-1980s and has been continuously used and maintained since. The user base has grown from a few government entities to now include numerous commercial entities as well. The NASA Johnson Space Center (JSC) Hypervelocity Impact Technology (HVIT) Team is responsible for all aspects of the Bumper software. Bumper has been used to characterize MMOD risk on hundreds of spacecraft. All of the International Space Station (ISS) modules, visiting vehicles and numerous external components and systems have been analyzed. Bumper was used to analyze each of the Space Shuttle missions since STS-50. The Orion Multi-Purpose Crew Vehicle (MPCV) MMOD shielding is being developed using Bumper as well. Bumper has also been used on numerous telescopes (Hubble, James Webb, and Fermi Gamma-ray Space Telescopes), scientific probes (Stardust, New Horizons, Parker Solar Probe), and Earth observation satellites (Landsat, Joint Polar Satellite System). Bumper is also being used to analyze the micrometeoroid risk and support design of the Deep Space Gateway (DSG) and Mars Sample Return (MSR) missions. The HVIT Bumper Configuration Control Board (CCB) ensures that all changes to the code are approved, reviewed, and documented. Most of the changes are made to add new MMOD damage “ballistic limit equations” (BLEs). BLEs are typically added in response to completion of a hypervelocity impact (HVI) test series and development of an associated BLE. Other less frequent changes include updates of the debris or meteoroid environment models, feature enhancements, and feature retirement. Some BLEs are commercially sensitive and/or proprietary, so the CCB also manages code user-version control and software distribution. The current version – “Bumper 3” – is a FORTRAN executable that utilizes a 64-bit architecture. Bumper 3 has numerous features that make it a powerful tool for analyzing spacecraft MMOD risk. Bumper uses the latest orbital debris and micrometeoroid environment models. Bumper also easily processes large spacecraft geometry models, recognizes hidden surfaces, permits BLE assignment by name or number, and conducts quality checks of the spacecraft geometry model. Bumper 3 can also be used to estimate the effects of particle penetration through thin, high-standoff distance hardware components such as solar arrays and radiators. This is done using a special HVIT-developed technique know as the “3-Part Analysis.” The paper introduces the Bumper 3 MMOD risk analysis code and provides an example MMOD risk assessment showing Bumper’s role in the overall MMOD protection design process.

Lear, Dana M.↗

Clearance Sensitivity Mitigation in Small Core Compressors

As future aircraft become lighter and more aerodynamically efficient, thrust requirements will decrease, reducing the core size of the engine. Furthermore, in the pursuit of improved fuel burn, engine overall pressure ratio and bypass ratio will increase, further driving down engine core size. These drivers together mean that the core size, or corrected mass flow rate at the compressor exit, for future single-aisle aircraft applications will shrink below 3.0 lb/s. Traditionally, this small core compressor size is in the domain of axi-centrifugal designs, machines that are typically less efficient and limited to pressure ratios of ~25 due to stress and thermomechanical fatigue in the centrifugal impeller. In this light, NASA, Pratt & Whitney and the Raytheon Technologies Research Center embarked upon a program to develop technologies to enable an all-axial high-pressure compressor with a core size below 3.0 lb/s and an overall pressure ratio greater than 50. One of the challenges with an all-axial high-pressure compressor at this core size is the small span at the rear of the compressor. As core size is scaled down, the rotor tip clearances do not scale with span, leading to significant efficiency penalties. This paper documents a numerical and experimental effort to mitigate this penalty through design optimization and technology insertion, enabling an estimated 5 to 10% fuel burn reduction relative to 2020 best-in-class. The experimental program consisted of two builds of a high-speed rig: a baseline build and a second build to insert technology to manage large rotor tip gap/span ratios. The results demonstrated a reduction in the sensitivity of the compressor to large clearance ratios, which would be likely at the end-of-life of a small core application. The test campaign demonstrated that, with the insertion of technology, small core compressors can maintain a similar efficiency to current best-in-class large core size compressors. In addition to advancing the state-of-the-art of technology, the program also advanced the modeling standards for multistage compressors with large clearance-to-span ratios. The validation of this approach is described in the paper.

Axial Compressors↗

Math Description Engine Software Development Kit

The Math Description Engine Software Development Kit (MDE SDK) can be used by software developers to make computer-rendered graphs more accessible to blind and visually-impaired users. The MDE SDK generates alternative graph descriptions in two forms: textual descriptions and non-verbal sound renderings, or sonification. It also enables display of an animated trace of a graph sonification on a visual graph component, with color and line-thickness options for users having low vision or color-related impairments. A set of accessible graphical user interface widgets is provided for operation by end users and for control of accessible graph displays. Version 1.0 of the MDE SDK generates text descriptions for 2D graphs commonly seen in math and science curriculum (and practice). The mathematically rich text descriptions can also serve as a virtual math and science assistant for blind and sighted users, making graphs more accessible for everyone. The MDE SDK has a simple application programming interface (API) that makes it easy for programmers and Web-site developers to make graphs accessible with just a few lines of code. The source code is written in Java for cross-platform compatibility and to take advantage of Java s built-in support for building accessible software application interfaces. Compiled-library and NASA Open Source versions are available with API documentation and Programmer s Guide at http:/ / prim e.jsc.n asa. gov.

Shelton, Robert O.↗

Scalable Asset Discovery, Vulnerability Scanning, and Penetration Testing for Remote Sites and Wireless Spectrums Utilizing an Embedded Linux Plug - PwniPlug and the Raspberry Pi B+ as a Sample Pen Test

All devices attached to the NASA KSC network are subject to security vulnerability scanning and/or penetration testing. In today's changing environment, vulnerable and/or unprotected systems can easily be overlooked. Systems that are not properly managed can become a potential threat to the operational integrity of our systems and networks. This includes all NASA (internal and external) information systems within NASA KSC Internet Protocol (IP) address space, and NASA KSC facilities. The Office of the Chief Information Officer (OCIO) recommends that all NASA Centers and information systems be subject to penetration testing on a regular interval in accordance with the guidelines identified by the National Institute of Standards and Technology (NIST). (ITS-HBK-2810.04-02A) Protecting information and equipment at NASA is an area of increasing concern. In addition to the CPU's on the network; Supervisory, Control and Data Acquisition (SCADA) systems are especially vulnerable because these systems have lacked standards, use embedded controllers with little computational power and informal software, are connected to physical processes, have few operators, and are increasingly also being connected to corporate networks. The scope of work is comprised of several individual components which together build upon previous work by Drew Branch, NASA KSC Intern. The Pwn Plug is the selected COTS (Commercial-Off-The-Shelf) device chosen to test simplification of mandatory IT Security tasks. The device will be utilized to provide services to NASA KSC and enable an assessment of infrastructure soundness and regulatory compliance in an efficient, economical, and business responsive manner. The Pwn Plug is designed as a pen testing appliance which provides a hardware platform that can support commercial penetration testing efforts at significantly reduced costs. The expected outcomes are: 1) External Penetration Testing, 2) Social Engineering, 3) Procedural Documentation, 4) Recommended Remediation Action Plan, 5) System Retest & Remediation Attestation and 6) Final Reports, out briefing and Presentation. Due to physical and material constraints beyond intern and mentor control, the project was redefined as a working pen-test scenario. Limitations of lab availability and tools dictated an academic exercise. This report was developed within the scenario guidelines suggested by the project mentor. The guidelines were to be creative in developing a Pen Test program for a client.

Penetration Testing↗

Waveform Developer's Guide for the Integrated Power, Avionics, and Software (iPAS) Space Telecommunications Radio System (STRS) Radio

The Space Telecommunications Radio System (STRS) provides a common, consistent framework for software defined radios (SDRs) to abstract the application software from the radio platform hardware. The STRS standard aims to reduce the cost and risk of using complex, configurable and reprogrammable radio systems across NASA missions. To promote the use of the STRS architecture for future NASA advanced exploration missions, NASA Glenn Research Center (GRC) developed an STRS-compliant SDR on a radio platform used by the Advance Exploration System program at the Johnson Space Center (JSC) in their Integrated Power, Avionics, and Software (iPAS) laboratory. The iPAS STRS Radio was implemented on the Reconfigurable, Intelligently-Adaptive Communication System (RIACS) platform, currently being used for radio development at JSC. The platform consists of a Xilinx(Trademark) ML605 Virtex(Trademark)-6 FPGA board, an Analog Devices FMCOMMS1-EBZ RF transceiver board, and an Embedded PC (Axiomtek(Trademark) eBox 620-110-FL) running the Ubuntu 12.4 operating system. The result of this development is a very low cost STRS compliant platform that can be used for waveform developments for multiple applications. The purpose of this document is to describe how to develop a new waveform using the RIACS platform and the Very High Speed Integrated Circuits (VHSIC) Hardware Description Language (VHDL) FPGA wrapper code and the STRS implementation on the Axiomtek processor.

Software Defined Radio↗

The Roles of Verification, Validation and Uncertainty Quantification in the NASA Standard for Models and Simulations

The National Aeronautics and Space Administration (NASA) recently issued an interim version of the Standard for Models and Simulations (M&S Standard) [1]. The action to develop the M&S Standard was identified in an internal assessment [2] of agency-wide changes needed in the wake of the Columbia Accident [3]. The primary goal of this standard is to ensure that the credibility of M&S results is properly conveyed to those making decisions affecting human safety or mission success criteria. The secondary goal is to assure that the credibility of the results from models and simulations meets the project requirements (for credibility). This presentation explains the motivation and key aspects of the M&S Standard, with a special focus on the requirements for verification, validation and uncertainty quantification. Some pilot applications of this standard to computational fluid dynamics applications will be provided as illustrations. The authors of this paper are the members of the team that developed the initial three drafts of the standard, the last of which benefited from extensive comments from most of the NASA Centers. The current version (number 4) incorporates modifications made by a team representing 9 of the 10 NASA Centers. A permanent version of the M&S Standard is expected by December 2007. The scope of the M&S Standard is confined to those uses of M&S that support program and project decisions that may affect human safety or mission success criteria. Such decisions occur, in decreasing order of importance, in the operations, the test & evaluation, and the design & analysis phases. Requirements are placed on (1) program and project management, (2) models, (3) simulations and analyses, (4) verification, validation and uncertainty quantification (VV&UQ), (5) recommended practices, (6) training, (7) credibility assessment, and (8) reporting results to decision makers. A key component of (7) and (8) is the use of a Credibility Assessment Scale, some of the details of which were developed in consultation with William Oberkampf, David Peercy and Timothy Trocano of Sandia National Laboratories. The focus of most of the requirements, including those for VV&UQ, is on the documentation of what was done and the reporting, using the Credibility Assessment Scale, of the level of rigor that was followed. The aspects of one option for the Credibilty Assessment Scale are (1) code verification, (2) solution verification, (3) validation, (4) predictive capability, (5) technical review, (6) process control, and (7) operator and analyst qualification.

Zang, Thomas A.↗

An Intern Experience with NASA’s Artemis Program

“3...2...1...Go For Launch”. Nasa’s Kennedy Space Center is projected to launch the first mission of theArtemis Program by the end of this year, 2021. I have had the opportunity to contribute directly to this mission through my internship with their Engineering organization from January to August of 2021.Within their Engineering organization, I am an intern for the Avionics branch. Throughout this experience I have completed two projects with one project still in progress. These projects allowed me to work directly with the Orion vehicle’s software and hardware power ups, checkouts, and tests. I became familiarized with the engineering concepts that allowed this advanced technology to perform as intended.In addition, I became acquainted with the operations and tasks that are completed during a LaunchCountdown, both at a detailed level as well as a higher managerial level. Lastly, I worked directly with the software algorithm that detects and responds to onboard faults and failures. I have analyzed and made conclusions based on data and documentation, allowing my team to benefit from a condensed, centralized informational file. In addition to my technical experience, I have learned a significant amount about how the Kennedy Space Center operates, it’s history, and the history of the agency. The education I received from the Engineering department at Texas A&M University not only allowed me to obtain this internship, but provided me with the required background in computer and electrical engineering principles to be successful in this organization.

Sarah Bianco↗

Considerations for Implementing Voice-Controlled Spacecraft Systems Through a Human-Centered Design Approach

As computational power and speech recognition algorithms improve, the consumer market will see better-performing speech recognition applications. The cell phone and Internet-related service industry have further enhanced speech recognition applications using artificial intelligence and statistical data-mining techniques. These improvements to speech recognition technology (SRT) may one day help astronauts on future deep space human missions that require control of complex spacecraft systems or spacesuit applications by voice. Though SRT and more advanced speech recognition techniques show promise, use of this technology for a space application such as vehicle/habitat/spacesuit requires careful considerations. There are still recognition challenges to overcome such as background noise, human speech variability, and task loading. However, implemented correctly, a voice-controlled spacecraft system (VCSS) can provide a useful, natural and efficient form of human-machine communications during complex tasks such as when the hands and eyes are busy or as an aid for vehicle situational awareness inquiries or collaborative human-robot tasks. This document provides considerations and guidance for the use of SRT in VCSS applications for space missions, specifically in command-and-control (C2) applications where the commanding is user-initiated. First, current SRT limitations as known at the time of this report are given. Then, highlights of SRT used in the space program provide the reader with a history of some of the human spaceflight applications and research. Next, an overview of the speech production process and the intrinsic variations of speech are provided. Finally, general guidance and considerations are given for development of a VCSS using a human-centered design approach for space applications that includes vocabulary selection and performance testing, as well as VCSS considerations for C2 dialogue management design, feedback, error handling, and evaluation/usability testing. Available from

Salazar, George A.↗

Clearance Sensitivity Mitigation in Small Core Compressors

As future aircraft become lighter and more aerodynamically efficient, thrust requirements will decrease, reducing the core size of the engine. Furthermore, in the pursuit of improved fuel burn, engine overall pressure ratio and bypass ratio will increase, further driving down engine core size. These drivers together mean that the core size, or corrected mass flow rate at the compressor exit, for future single-aisle aircraft applications will shrink below 3.0 lbm/s. Traditionally, this small core compressor size is in the domain of axi-centrifugal designs, machines that are typically less efficient and limited to pressure ratios of ~25 due to stress and thermomechanical fatigue in the centrifugal impeller. In this light, NASA, Pratt & Whitney and the Raytheon Technologies Research Center embarked upon a program to develop technologies to enable an all-axial high-pressure compressor with a core size below 3.0 lbm/s and an overall pressure ratio greater than 50. One of the challenges with an all-axial high-pressure compressor at this core size is the small span at the rear of the compressor. As core size is scaled down, the rotor tip clearances do not scale with span, leading to significant efficiency penalties. This paper documents a numerical and experimental effort to mitigate this penalty through design optimization and technology insertion, enabling an estimated 5 to 10% fuel burn reduction relative to 2020 best-in-class. The experimental program consisted of two builds of a high-speed rig: a baseline build and a second build to insert technology to manage large rotor tip gap/span ratios. The results demonstrated a reduction in the sensitivity of the compressor to large clearance ratios, which would be likely at the end-of-life of a small core application. The test campaign demonstrated that, with the insertion of technology, small core compressors can maintain a similar efficiency to current best-in-class large core size compressors. In addition to advancing the state-of-the-art of technology, the program also advanced the modeling standards for multistage compressors with large clearance-to-span ratios. The validation of this approach is described in the paper.

Axial Compressors↗