Search NASA⌕ Search

SEARCH · Search NASA

Results for “Engine Ground Testing”

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 1,477 records · Page 82

X-ray satellite

The projected launch date has been delayed approx. 7 weeks from the planned launch date. The Engineering Model (EM) of the automatic measurement and control system (AMCS) is in the critical phase. The contract change no. 1 to the main contract has been signed. A new version of the welding seam location specifications for the wide field camera (WFC) was proposed by the WFC Consortium. The payload integration plan (PIP) has been signed. Production of the EM/QM prototype and ground station equipment has proceeded according to plan with the exception of some delays. Production of the EM equipment has begun. Preparations for the qualification tests of the EM/QM equipment and the integration of EM equipment has begun. The cause of the delay in the launch date include the combined effects of the postponement of the target date for the EM equipment, along with the fact that only a structural model is available.

Source record↗

Progress in Spacecraft Environment Interactions: International Space Station (ISS) Development and Operations

The set of spacecraft interactions with the space flight environment that have produced the largest impacts on the design, verification, and operation of the International Space Station (ISS) Program during the May 2000 to May 2007 time frame are the focus of this paper. In-flight data, flight crew observations, and the results of ground-based test and analysis directly supporting programmatic and operational decision-making are reported as are the analysis and simulation efforts that have led to new knowledge and capabilities supporting current and future space explorations programs. The specific spacecraft-environment interactions that have had the greatest impact on ISS Program activities during the first several years of flight are: 1) spacecraft charging, 2) micrometeoroids and orbital debris effects, 3) ionizing radiation (both total dose to materials and single event effects [SEE] on avionics), 4) hypergolic rocket engine plume impingement effects, 5) venting/dumping of liquids, 6) spacecraft contamination effects, 7) neutral atmosphere and atomic oxygen effects, 8) satellite drag effects, and 9) solar ultraviolet effects. Orbital inclination (51.6deg) and altitude (nominally between 350 km and 460 km) determine the set of natural environment factors affecting the performance and reliability of materials and systems on ISS. ISS operates in the F2 region of Earth s ionosphere in well-defined fluxes of atomic oxygen, other ionospheric plasma species, solar UV, VUV, and x-ray radiation as well as galactic cosmic rays, trapped radiation, and solar cosmic rays. The micrometeoroid and orbital debris environment is an important determinant of spacecraft design and operations in any orbital inclination. The induced environment results from ISS interactions with the natural environment as well as environmental factors produced by ISS itself and visiting vehicles. Examples include ram-wake effects, hypergolic thruster plume impingement, materials out-gassing, venting and dumping of fluids, and specific photovoltaic (PV) power system interactions with the ionospheric plasma. Vehicle size (L) and velocity (v), combined with the magnitude and direction of the geomagnetic field (B) produce operationally significant magnetic induction voltages (VxB.L) in ISS conducting structure during high latitude flight (>+/- 45deg) during each orbit. In addition, ISS is a large vehicle and produces a deep wake structure from which both ionospheric plasma and neutrals species are largely excluded. ISS must fly in a very limited number of approved flight attitudes, so that exposure of a particular material or system to environmental factors depends upon: 1) location on ISS, 2) ISS flight configuration, 3) ISS flight attitude, and 4) variation of solar exposure (Beta angle), and hence thermal environment, with time. Finally, an induced ionizing radiation environment is produced by trapped radiation and solar/cosmic ray interactions with the relatively massive ISS structural shielding.

Koontz, Steve↗

Pressure-Sensor Assembly Technique

Nielsen Engineering & Research (NEAR) recently developed an ultrathin data acquisition system for use in turbomachinery testing at NASA Glenn Research Center. This system integrates a microelectromechanical- systems- (MEMS-) based absolute pressure sensor [0 to 50 psia (0 to 345 kPa)], temperature sensor, signal-conditioning application-specific integrated circuit (ASIC), microprocessor, and digital memory into a package which is roughly 2.8 in. (7.1 cm) long by 0.75 in. (1.9 cm) wide. Each of these components is flip-chip attached to a thin, flexible circuit board and subsequently ground and polished to achieve a total system thickness of 0.006 in. (0.15 mm). Because this instrument is so thin, it can be quickly adhered to any surface of interest where data can be collected without disrupting the flow being investigated. One issue in the development of the ultrathin data acquisition system was how to attach the MEMS pressure sensor to the circuit board in a manner which allowed the sensor s diaphragm to communicate with the ambient fluid while providing enough support for the chip to survive the grinding and polishing operations. The technique, developed by NEAR and Jabil Technology Services Group (San Jose, CA), is described below. In the approach developed, the sensor is attached to the specially designed circuit board, see Figure 1, using a modified flip-chip technique. The circular diaphragm on the left side of the sensor is used to actively measure the ambient pressure, while the diaphragm on the right is used to compensate for changes in output due to temperature variations. The circuit board is fabricated with an access hole through it so that when the completed system is installed onto a wind tunnel model (chip side down), the active diaphragm is exposed to the environment. After the sensor is flip-chip attached to the circuit board, the die is underfilled to support the chip during the subsequent grinding and polishing operations. To prevent this underfill material from getting onto the sensor s diaphragms, the circuit board is fabricated with two 25- micrometer-tall polymer rings, sized so that the diaphragms fit inside the rings once the chip is attached.

Pruzan, Daniel A.↗

Project Report: Automatic Sequence Processor Software Analysis

The Mission Planning and Sequencing (MPS) element of Multi-Mission Ground System and Services (MGSS) provides space missions with multi-purpose software to plan spacecraft activities, sequence spacecraft commands, and then integrate these products and execute them on spacecraft. Jet Propulsion Laboratory (JPL) is currently is flying many missions. The processes for building, integrating, and testing the multi-mission uplink software need to be improved to meet the needs of the missions and the operations teams that command the spacecraft. The Multi-Mission Sequencing Team is responsible for collecting and processing the observations, experiments and engineering activities that are to be performed on a selected spacecraft. The collection of these activities is called a sequence and ultimately a sequence becomes a sequence of spacecraft commands. The operations teams check the sequence to make sure that no constraints are violated. The workflow process involves sending a program start command, which activates the Automatic Sequence Processor (ASP). The ASP is currently a file-based system that is comprised of scripts written in perl, c-shell and awk. Once this start process is complete, the system checks for errors and aborts if there are any; otherwise the system converts the commands to binary, and then sends the resultant information to be radiated to the spacecraft.

sequencing↗

Advances in High Energy Solid-State Pulsed 2-Micron Lidar Development for Ground and Airborne Wind, Water Vapor and CO2 Measurements

NASA Langley Research Center has a long history of developing 2-micron lasers. From fundamental spectroscopy research, theoretical prediction of new materials, laser demonstration and engineering of lidar systems, it has been a very successful program spanning around two decades. Successful development of 2-micron lasers has led to development of a state-of-the-art compact lidar transceiver for a pulsed coherent Doppler lidar system for wind measurement with an unprecedented laser pulse energy of 250 millijoules in a rugged package. This high pulse energy is produced by a Ho:Tm:LuLiF laser with an optical amplifier. While the lidar is meant for use as an airborne instrument, ground-based tests were carried out to characterize performance of the lidar. Atmospheric measurements will be presented, showing the lidar's capability for wind measurement in the atmospheric boundary layer and free troposphere. Lidar wind measurements are compared to a balloon sonde, showing good agreement between the two sensors. Similar architecture has been used to develop a high energy, Ho:Tm:YLF double-pulsed 2-micron Integrated Differential Absorption Lidar (IPDA) instrument based on direct detection technique that provides atmospheric column CO2 measurements. This instrument has been successfully used to measure atmospheric CO2 column density initially from a ground mobile lidar trailer, and then it was integrated on B-200 plane and 20 hours of flight measurement were made from an altitude ranging 1500 meters to 8000 meters. These measurements were compared to in-situ measurements and National Oceanic and Atmospheric Administration (NOAA) airborne flask measurement to derive the dry mixing ratio of the column CO2 by reflecting the signal by various reflecting surfaces such as land, vegetation, ocean surface, snow and sand. The lidar measurements when compared showed a very agreement with in-situ and airborne flask measurement. NASA Langley Research Center is currently developing a triple-pulsed 2-micron Integrated Differential Absorption Lidar (IPDA) instrument for simultaneous measurement of water vapor and carbon-dioxide column density measurement from an air-borne platform. This presentation will give an overview of the 2 decades of 2-micron coherent and direction detection of laser/lidar development at NASA Langley Research Center and will present the ground and airborne wind and column CO2 measurement intercomparison with in-situ, balloon and flask measurements.

Singh, Upendra N.↗

HYPERFIRE

The two main sub-scale, ground-based rocket aerodynamics testing techniques – hot-fire testing and cold-flow testing – pose a series of tradeoffs. Hot-fire testing is generally much more accurate, but is often burdensome, costly, and requires long lead times due to design work, infrastructure preparation, etc. Cold-flow testing is much less expensive and has a rapid turnaround time, but conventional simulants (e.g., nitrogen, steam) used in cold-flow testing yield less accurate results (i.e., results that are not sufficiently representative of test article performance). While researching methods to optimize such tradeoffs, engineers at NASA’s Stennis Space Center discovered that ethane can be tuned to approximate rocket exhaust plumes generated by several common rocket propellants. This led NASA to develop the HYdrocarbon Propellants Enabling Reproduction of Flows in Rocket Engines (HYPERFIRE), a sub-scale, non-reacting flow test system. HYPERFIRE uses heated ethane to enable physical simulation of rocket engines powered by a broad range of propellants in an inexpensive, accurate, and simple fashion.

sub-scale↗

An Overview of Plume-Surface Interaction Testing and Research

NASA has studied rocket plume-surface interactions caused by spacecraft since the Apollo era to reduce risk to landing vehicles. The study of plume-surface interactions is a multi-discipline effort, spanning aerospace engineering to planetary science. Historical testing for Apollo and Viking produced methods, terms, and datasets that influence the field today. Research conducted over the past two decades has expanded our understanding of plume-surface interaction phenomena, but the problem remains resistant to a robust predictive capability. Contemporary experimental and modeling efforts to understand and retire strategic knowledge gaps will be discussed, with a focus on work conducted under NASA’s Plume-Surface Interaction Project and the upcoming Human Landing System Plume-Surface Interaction Risk Reduction Ground Test.

Wesley A Chambers↗

Is Structured Agile an Oxymoron? Tales from Implementing and Executing Agile in a US Government Environment

To paraphrase a famous quote, "No plan survives contact with the reality." Software (SW) development is often a classic example of this: whatever the plan was for a particular development, it often does not survive contact with technical realities, budget realities, program realities and schedule realities. Traditionally, SW development has followed a waterfall methodology with requirements being rigorously specified before the design, which was completed before the coding and unit testing started, which were in turn finished before validation and verification started. This model of SW engineering derives much from the HW engineering of large systems, and has been the standard methodology used in US government software acquisitions and systems for decades, with highly variable results. US Government SW requirements are built around Waterfall concepts, which assume that the plan will survive contact with reality, or at least that modifications to the plan are relatively small, and relatively few.Because of the inefficiencies and difficulties inherent in Waterfall, the commercial SW world started using a different SW development methodology called Agile more than 20 years ago. Agile believes that a plan should evolve and learn rapidly in response to the realities encountered. At its core, there are a few key elements of Agile:- A small team of people which is highly flexible and adaptive. The team collaborates and interoperates through sophisticated development architectures and release environments- An iterative, incremental development and release approach which is based upon the concept that knowledge comes from experience within the team, and that the team makes decisions based upon what it knows- A team culture which prizes transparency, inspection and adaptation. These values are necessary so that the team experience and decision making is transparent and responsive to the realities encountered during development and testingSo, how to use Agile in a US Government environment? GMSEC (Goddard Mission Services Evolution Center) develops satellite ground system software for NASA and other US Government agencies. The SW developed by the team contains a large code base of many applications used within satellite mission operations centers. It spans the full gamut of SW development types: from SW which is in a classic maintenance and sustainment mode, to new developments with a fairly well understood scope and approach, to new developments whose scope and approach are quite unclear and which require significant research and prototyping. Team members move between all of these different types of SW development. Waterfall was inadequate to the programmatic and technical needs of the team, as well as the various types of SW development being done. The software plan was not surviving contact with the technical and programmatic realities experienced by the team. To address this, the team started a small pilot project in 2016 to test the use of Agile within a small subset of the team for a new web services application. In early 2018, the use of Agile was expanded to the whole team and all the software, but we had to fulfill the NASA SW development requirements. And we needed to do this while still remaining true to the key Agile elements of transparency, inspection and adaption. In order to do this, the team worked very closely with the Software Process Improvement (SPI) team at NASA Goddard, as well as NASA engineering manageme

Beech, Theresa W.↗

Dedicated short range communications used as fail-safe in autonomous navigation

Here in this paper, we have analyzed scenarios for leader-follower vehicle convoys that have the potential to be unsafe, hazardous, or even fatal in order to provide insight on dangerous driving conditions for autonomous vehicle platoons. These scenarios were created in a simulation software called Prescan, and are made to reflect the behavior of the vehicle dynamics and sensor characteristics of a real-world vehicle convoy that is currently being tested at the American Center for Mobility (ACM) and sponsored by the Department of Energy (DOE), National Renewable Energy Laboratory (NREL), the U.S. Army Combat Capabilities Development Command - Ground Vehicle Systems Center (U.S. Army CC-DEVCOM) and the Michigan Department of Transportation (MDOT). The follower vehicle in this study is tested under multiple scenarios, equipped with a Dedicated Short Range vehicle-to-vehicle communication system (DSRC), a radar-based adaptive cruise control system (ACC) and a precision global positioning system (GPS).

42 ENGINEERING↗

Test, Control and Monitor System maintenance plan

The maintenance requirements for Test, Control, and Monitor System (TCMS) and the method for satisfying these requirements prior to First Need Date (FND) of the last TCMS set are described. The method for satisfying maintenance requirements following FND of the last TCMS set will be addressed by a revision to this plan. This maintenance plan serves as the basic planning document for maintenance of this equipment by the NASA Payloads Directorate (CM) and the Payload Ground Operations Contractor (PGOC) at KSC. The terms TCMS Operations and Maintenance (O&M), Payloads Logistics, TCMS Sustaining Engineering, Payload Communications, and Integrated Network Services refer to the appropriate NASA and PGOC organization. For the duration of their contract, the Core Electronic Contractor (CEC) will provide a Set Support Team (SST). One of the primary purposes of this team is to help NASA and PGOC operate and maintain TCMS. It is assumed that SST is an integral part of TCMS O&M. The purpose of this plan is to describe the maintenance concept for TCMS hardware and system software in order to facilitate activation, transition planning, and continuing operation. When software maintenance is mentioned in this plan, it refers to maintenance of TCMS system software.

Buehler, David P.↗

An Overview of the Concept of Operations for Assembly, Integration, Testing and Ground Servicing Developed for the MPCV-ESM Propulsion System

A concept of operations for the Assembly, Integration and Testing (AIT) and the Ground Systems Development Operations (GSDO) of the European Service Module (ESM) propulsion system has been developed. The AIT concept of operations covers all fabrication, integration and testing activities in both Europe and in the United States. The GSDO Program develops the facilities, equipment, and procedures for the loading of hypergolic propellants, the filling of high-pressure gases, and contingency de-servicing operations for the ESM. NASA and ESA along with the Lockheed Martin and Airbus Space and Defense are currently working together for the EM-1 and EM-2 missions in which the ESM will be flown as part of the Orion Multi-Purpose Crew Vehicle (MPCV). The NASA/ESA SM propulsion team is collaborating with the AIT personnel from ESA/Airbus and NASA/Lockheed Martin to ensure successful integration of the European designed Service Module propulsion system, the Lockheed Martin designed Crew Module Adapter and the heritage Space Shuttle Orbital Maneuvering System Engines (OMS-E) being provided as Government Furnished Equipment (GFE). This paper will provide an overview of the current AIT and GSDO concept of operations for the ESM propulsion system.

Ground Servicing↗

NEO Test Stand Analysis

A project within SwampWorks is building a test stand to hold regolith to study how dust is ejected when exposed to the hot exhaust plume of a rocket engine. The test stand needs to be analyzed, finalized, and fabrication drawings generated to move forward. Modifications of the test stand assembly were made with Creo 2 modeling software. Structural analysis calculations were developed by hand to confirm if the structure will hold the expected loads while optimizing support positions. These calculations when iterated through MatLab demonstrated the optimized position of the vertical support to be 98'' from the far end of the stand. All remaining deflections were shown to be under the 0.6'' requirement and internal stresses to meet NASA Ground Support Equipment (GSE) Safety Standards. Though at the time of writing, fabrication drawings have yet to be generated, but are expected shortly after.

Internship↗

MBSE Validation and Verification: Case Study for LADEE

The Lunar Atmosphere Dust Environment Explorer (LADEE) mission orbited the moon in order to measure the density, composition, and time variability of the lunar dust environment. The successful mission launched September 7, 2013 and was de-orbited and impacted the moon's surface on April 17, 2014. The ground-side and onboard flight software for the mission was developed using a “Model-Based Software Engineering” (MBSE) methodology combined with strong reuse of Government and Commercial Off-The Shelf (G/COTS) components. Models of the spacecraft and flight software were developed in a graphical dynamics modeling package. Flight Software requirements were prototyped and refined using the simulated models. After the model was shown to work as desired in the simulation framework, C-code software was automatically generated from the models. The auto-generated software was then tested in real-time Processor-in-the-Loop and Hardware-in-the-Loop test beds. “Traveling Road Show” test beds were used for early integration tests with payloads and other subsystems. Traditional techniques for verifying computational sciences models were used to characterize the spacecraft simulation. A lightweight set of formal methods analysis, static analysis, formal inspection, and code coverage analyses were utilized to further reduce defects in the onboard flight software artifacts. These techniques were applied early and often in the development process, iteratively increasing the capabilities of software and fidelity of vehicle models and test beds.

Model-Based Software Engineering, Validation and V↗

CLINICAL DECISION SUPPORT: PATH TO FUNCTIONAL REQUIREMENTS

Long-duration, deep-space exploration missions present significant challenges to crew health and performance. These challenges include the individual and combined effects of microgravity, radiation exposure, isolation, limited resources (mass, volume, power, data and crew time), limited options for evacuation and those associated with delayed or constrained communications, all of which demand greater crew autonomy. Specifically, as the communication delays intensify the further we explore space, the unqualified need for Earth-independent medical operations focused on autonomous diagnosis, treatment and prevention will be key to mission continuation and success. To augment the requisite knowledge, skills and abilities (KSAs) of a time-constrained crew operating under stressful conditions, combatting fatigue, and facing a potential medical crisis, a robust clinical decision support system (CDSS) is a probable solution that would facilitate, guide and inform Earth-independent medical operations, while assisting crewmembers through various clinical presentations. The Exploration Medical Capability (ExMC) Element of the Human Research Program (HRP) is expanding the boundaries of space medical systems to advance the care of astronauts on future exploration missions beyond low Earth orbit. ExMC is actively identifying and testing next-generation medical care and crew health maintenance technologies. The Clinical Decision Support (CDS) project addresses gap Medical-701 within the Inflight Medical Conditions risk: “Enhance medical capabilities within an exploration medical system.” Though mass, volume, and power will face increasing constraints, the projected computational capabilities of spacecraft systems will increase exponentially as information technology continues to advance this decade and beyond. Hence, data, software and computational resources will play an essential and synergistic role in maintaining crew health, wellness and performance in deep space missions. The focus of the CDS project is to develop recommended requirements for an in-vehicle CDSS that acts as a ‘virtual assistant’ for delivering optimal health, performance and medical care during exploration missions. The CDSS is envisioned as an integrated, software-based tool deployed on a laptop computer or handheld device. The CDSS will assist the crew and ground support when interacting with knowledge/databases (e.g. records, pharmacy, schedule), instrumentation (e.g. imaging, physiological monitoring devices), and habitat (e.g. wellness system, task performance system) and vehicle systems (e.g. environmental system, communication system). In addition, the human interface will employ a context-based approach that accounts for the crew’s situation. Thus, extraneous and clinically/operationally non-relevant information are reduced to avoid an increase in cognitive load. The framework of an ideal spaceflight CDSS is to include core and advanced analytical features that incorporate work from collaborators yet maintain a flexible platform for integrating new technology in the future. In fiscal year 2021 (FY21), the CDS project identified requirements through two primary mechanisms: (i) the development of software implementation prototypes and (ii) the application of systems engineering processes. The CDS project developed and tested a series of increasingly complex system prototypes that were based on use cases derived from the CDSS concept of operations (ConOps). These software implementations yielded insights on CDSS functionality as well as lessons learned that provided the initial requirements for CDSS capability. By applying a systems engineering (SE) approach, medical scenarios provided in the ConOps and the use cases for software implementation underwent functional decomposition to identify CDSS functionality. Also, systems-based modeling language (SysML) tools such as activity diagrams were developed from the same ConOps and use cases to identify CDSS functionality. The lessons learned from software implementation defined both specific requirements and broad areas of requirements. Within these defined broad requirement areas, further analysis of the SE products identified specific capability that resulted in the final functional requirements. In summary, the software prototypes, functional decomposition of the ConOps and use cases, and SysML diagrams provided the basis for the CDSS requirements developed in FY21. In the upcoming year, these requirements will be refined for their final ExMC baseline review in latter FY22.

clinical decision support↗

Clinical Decision Support: Path to Functional Requirements

Long-duration, deep-space exploration missions present significant challenges to crew health and performance. These challenges include the individual and combined effects of microgravity, radiation exposure, isolation, limited resources (mass, volume, power, data and crew time), limited options for evacuation and those associated with delayed or constrained communications, all of which demand greater crew autonomy. Specifically, as the communication delays intensify the further we explore space, the unqualified need for Earth-independent medical operations focused on autonomous diagnosis, treatment and prevention will be key to mission continuation and success. To augment the requisite knowledge, skills and abilities (KSAs) of a time-constrained crew operating under stressful conditions, combatting fatigue, and facing a potential medical crisis, a robust clinical decision support system (CDSS) is a probable solution that would facilitate, guide and inform Earth-independent medical operations, while assisting crewmembers through various clinical presentations. The Exploration Medical Capability (ExMC) Element of the Human Research Program (HRP) is expanding the boundaries of space medical systems to advance the care of astronauts on future exploration missions beyond low Earth orbit. ExMC is actively identifying and testing next-generation medical care and crew health maintenance technologies. The Clinical Decision Support (CDS) project addresses gap Medical-701 within the Inflight Medical Conditions risk: “Enhance medical capabilities within an exploration medical system.” Though mass, volume, and power will face increasing constraints, the projected computational capabilities of spacecraft systems will increase exponentially as information technology continues to advance this decade and beyond. Hence, data, software and computational resources will play an essential and synergistic role in maintaining crew health, wellness and performance in deep space missions. The focus of the CDS project is to develop recommended requirements for an in-vehicle CDSS that acts as a ‘virtual assistant’ for delivering optimal health, performance and medical care during exploration missions. The CDSS is envisioned as an integrated, software-based tool deployed on a laptop computer or handheld device. The CDSS will assist the crew and ground support when interacting with knowledge/databases (e.g. records, pharmacy, schedule), instrumentation (e.g. imaging, physiological monitoring devices), and habitat (e.g. wellness system, task performance system) and vehicle systems (e.g. environmental system, communication system). In addition, the human interface will employ a context-based approach that accounts for the crew’s situation. Thus, extraneous and clinically/operationally non-relevant information are reduced to avoid an increase in cognitive load. The framework of an ideal spaceflight CDSS is to include core and advanced analytical features that incorporate work from collaborators yet maintain a flexible platform for integrating new technology in the future. In fiscal year 2021 (FY21), the CDS project identified requirements through two primary mechanisms: (i) the development of software implementation prototypes and (ii) the application of systems engineering processes. The CDS project developed and tested a series of increasingly complex system prototypes that were based on use cases derived from the CDSS concept of operations (ConOps). These software implementations yielded insights on CDSS functionality as well as lessons learned that provided the initial requirements for CDSS capability. By applying a systems engineering (SE) approach, medical scenarios provided in the ConOps and the use cases for software implementation underwent functional decomposition to identify CDSS functionality. Also, systems-based modeling language (SysML) tools such as activity diagrams were developed from the same ConOps and use cases to identify CDSS functionality. The lessons learned from software implementation defined both specific requirements and broad areas of requirements. Within these defined broad requirement areas, further analysis of the SE products identified specific capability that resulted in the final functional requirements. In summary, the software prototypes, functional decomposition of the ConOps and use cases, and SysML diagrams provided the basis for the CDSS requirements developed in FY21. In the upcoming year, these requirements will be refined for their final ExMC baseline review in latter FY22.

Clinical decision support↗

A Data-Driven Framework for Direct Local Tensile Property Prediction of Laser Powder Bed Fusion Parts

This article proposes a generalizable, data-driven framework for qualifying laser powder bed fusion additively manufactured parts using part-specific in situ data, including powder bed imaging, machine health sensors, and laser scan paths. To achieve part qualification without relying solely on statistical processes or feedstock control, a sequence of machine learning models was trained on 6299 tensile specimens to locally predict the tensile properties of stainless-steel parts based on fused multi-modal in situ sensor data and a priori information. A cyberphysical infrastructure enabled the robust spatial tracking of individual specimens, and computer vision techniques registered the ground truth tensile measurements to the in situ data. The co-registered 230 GB dataset used in this work has been publicly released and is available as a set of HDF5 files. The extensive training data requirements and wide range of size scales were addressed by combining deep learning, machine learning, and feature engineering algorithms in a relay. The trained models demonstrated a 61% error reduction in ultimate tensile strength predictions relative to estimates made without any in situ information. Lessons learned and potential improvements to the sensors and mechanical testing procedure are discussed.

36 MATERIALS SCIENCE↗

The aerodynamic and acoustic characteristics of an over-the-wing target-type thrust reverser model

A static test of a large-scale, over-the-wing (OTW) powered-lift model was performed. The OTW propulsion system had been modified to incorporate a simple target-type thrust reverser as well as the normal rectangular OTW exhaust nozzle. Tests were performed in both the reverse thrust and approach configurations. The thrust reverser noise created by jet turbulence mixing and the OTW approach noise were both low frequency and broadband. When scaled to a 45,400-kg (100,000-lb) aircraft, the thrust reverser and approach configurations produced peak 152-m (500-ft) sideline perceived noise levels of 110 and 105 PNdB, respectively. The aerodynamic performance of the model showed that 50% or greater reverser effectiveness can be achieved without experiencing ingestion of exhaust gas or ground debris into the engine inlets.

Falarski, M. D.↗

Isoelectric focusing in space

The potential of space electrophoresis is conditioned by the fact that all electrophoretic techniques require the suppression of gravity-caused convection. Isoelectric focusing (IEF) is a powerful variant of electrophoresis, in which amphoteric substances are separated in a pH gradient according to their isoelectric points. A new apparatus for large scale IEF, utilizing a recycling principle, has been developed. In the ground-based prototype, laminar flow is provided by a series of parallel filter elements. The operation of the apparatus is monitored by an automated array of pH and ultraviolet absorption sensors under control of a desk-top computer. The apparatus has proven to be useful for the purification of a variety of enzymes, snake venom proteins, peptide hormones, and other biologicals, including interferon produced by genetic engineering techniques. In planning for a possible space apparatus, a crucial question regarding electroosmosis needs to be addressed To solve this problem, simple focusing test modules are planned for inclusion in an early Shuttle flight.

Bier, M.↗