Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Solution verification”

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 433 records · Page 24
All sourcesNASA NTRSDOE OSTI
NASA NTRS1992

System test approach for the SAX satellite

SAX satellite verification is based on a protoflight approach, in which only one system model is realized at flight standard level, taking into account the utilization of hardware already qualified for other space programs and the necessity to respect the schedule constraints for a scientific objective. In any case, this approach was tailored with some deviations in order to reduce risks inherent in such a choice. The protoflight approach was also pursued at subsystem/unit level in particular for those subsystems and units considered critical from the schedule point of view. Payload Instruments followed the same approach but complete spare units were developed to reduce the risks associated with such an approach. A description of the model philosophy is provided and then, at satellite level, the testing approach and rationale for each model is presented. Finally, a brief description of each test will be given, highlighting objectives, methodologies, and test configurations. Moreover, for the major tests, problems encountered and solutions applied in establishing a correct approach are described.

Giordano, Pietro↗
NASA NTRS2006

Imagine Moving Off the Planet

Moving off the planet will be a defining moment of this century as landing on the Moon was in the last. For that to happen for humans to go where humans cannot go-- simulation is the sole solution. NASA supports simulation for life-cycle activities: design, analysis, test, checkout, operations, review and training. We contemplate time spans of a century and more, teams dispersed to different planets and the need for systems that endure or adapt as missions, teams and technology change. Without imagination such goals are impossible. But with imagination we can go outside our present perception of reality to think about and take action on what has been, is and, especially, what might be. Consciously maturing an imagined, possibly workable, idea through framing it to optimization to design, and building the product provides us with a new approach to innovation and simulation fidelity. We address options, analyze, test and make improvements in how we think and work. Each step includes increasingly exact information about costs, schedule, who will be needed, where, when and how. NASA i integrating such thinking into its Exploration Product Realization Hierarchy for simulation and analysis, test and verification, and stimulus response goals. Technically NASA follows a timeline of studies, analysis, definition, design, development and operations with concurrent documentation. We have matched this Product Realization Hierarchy with a continuum from image to realization that incorporates commitment, current and needed research and communication to ensure superior and creative problem solving as well as advances in simulation. One result is a new approach to collaborative systems. Another is a distributed observer network prototyped using game engine technology bringing advanced 3-D simulation of a simulation to the desktop enabling people to develop shared consensus of its meaning. Much of the value of simulation comes from developing in people their ability to make good decisions and reflexes supporting impressive achievement. Synthesizing imagination systematically into our work - and thus our success - is a challenge. NASA engineers have inventive minds, and the task is determining how best to enable them to devise the simulation and other innovations that will make a story so clear and so intellectually sound that people can carry out the mission for 50-100 years. This demands skills and knowledge traditionally under-respected and under-represented in technology organizations. But we are beginning to see that the process encourages efficiency and enables us to attain more effective results. We have to elicit imaginative, intelligent and effective ways to make better use than ever of the minds we have and will have available. We have to accept the challenge to accomplish tasks among dispersed interdisciplinary teams who must overcome changing priorities and technology, time and distance in order to maximize interactivity and innovation as never before. Attention to the process of innovation is a practical means to increase the efficiency of our intelligence. We have an obligation to reexamine and improve the process by which we approach and exercise innovation as we accept the charge to move off the planet.

Elfrey, Priscilla R.↗
NASA NTRSDate not supplied

X-57 Flight Systems Integration Path

The foundation for a safe and successful flight test of the National Aeronautics and Space Administration (NASA) X-57 Maxwell all-electric experimental airplane, or any X-Plane, is comprehensive system testing on the ground. This test campaign includes verification and validation (V&V) that the integrated system operates as designed and expected, as well as understanding how the system reacts and responds to failures that can occur during flight by performing failure modes and effects testing (FMET). The aircraft should be in the final flight configuration for these test activities because any modifications, even those that appear insignificant, could affect test outcomes. Although the plan was to perform V&V and FMET testing once the airplane was in the flight configuration, due to multiple component redesigns, concurrent software development, and other problems with on-aircraft testing, the X-57 Maxwell never made it into a full-flight configuration. As a result, a build-up approach was followed to test software and hardware as they became ready in order to continue making progress wherever possible. Using this approach revealed problems with the hardware and software faster than waiting for a full-flight configuration, allowing solutions to be found more quickly and in parallel with other project tasks. Other than unloaded motor testing in a lab setting, the only other test setup was on the airplane itself. On-aircraft testing was preferrable in order to test things as close to a flight configuration as possible but was time consuming due to the requirements for testing on the airplane. To overcome some of the on-aircraft barriers, off-aircraft test configurations, such as the Systems Integration Laboratory (SIL) and hardware-in-the-loop (HIL) setups, were used, but each of these setups had limitations to be considered. As a result, solutions found in the SIL or HIL configurations did not always work as expected on the airplane, resulting in an iterative process between on- and off-aircraft testing to find the final solution. Having a dedicated test platform such as an iron bird that closely represents the aircraft - without flight hardware - would have been the most effective off-aircraft test setup, which could have allowed the project to save time and money and potentially reach flight. This paper will highlight the V&V and FMET considerations and testing prerequisites, the build-up approaches to both software and system testing, the benefits and drawbacks to different test configurations, as well as battery testing and operations.

Kassidy M. Mclaughlin↗
NASA NTRSDate not supplied

X-57 Flight Systems Integration Path

The foundation for a safe and successful flight test of the National Aeronautics and Space Administration (NASA) X-57 Maxwell all-electric experimental airplane, or any X-Plane, is comprehensive system testing on the ground. This test campaign includes verification and validation (V&V) that the integrated system operates as designed and expected, as well as understanding how the system reacts and responds to failures that can occur during flight by performing failure modes and effects testing (FMET). The aircraft should be in the final flight configuration for these test activities because any modifications, even those that appear insignificant, could affect test outcomes. Although the plan was to perform V&V and FMET testing once the airplane was in the flight configuration, due to multiple component redesigns, concurrent software development, and other problems with on-aircraft testing, the X-57 Maxwell never made it into a full-flight configuration. As a result, a build-up approach was followed to test software and hardware as they became ready in order to continue making progress wherever possible. Using this approach revealed problems with the hardware and software faster than waiting for a full-flight configuration, allowing solutions to be found more quickly and in parallel with other project tasks. Other than unloaded motor testing in a lab setting, the only other test setup was on the airplane itself. On-aircraft testing was preferrable in order to test things as close to a flight configuration as possible but was time consuming due to the requirements for testing on the airplane. To overcome some of the on-aircraft barriers, off-aircraft test configurations, such as the Systems Integration Laboratory (SIL) and hardware-in-the-loop (HIL) setups, were used, but each of these setups had limitations to be considered. As a result, solutions found in the SIL or HIL configurations did not always work as expected on the airplane, resulting in an iterative process between on- and off-aircraft testing to find the final solution. Having a dedicated test platform such as an iron bird that closely represents the aircraft - without flight hardware - would have been the most effective off-aircraft test setup, which could have allowed the project to save time and money and potentially reach flight. This paper will highlight the V&V and FMET considerations and testing prerequisites, the build-up approaches to both software and system testing, the benefits and drawbacks to different test configurations, as well as battery testing and operations.

Kassidy McLaughlin↗
NASA NTRS1994

Experiences in improving the state of the practice in verification and validation of knowledge-based systems

Knowledge-based systems (KBS's) are in general use in a wide variety of domains, both commercial and government. As reliance on these types of systems grows, the need to assess their quality and validity reaches critical importance. As with any software, the reliability of a KBS can be directly attributed to the application of disciplined programming and testing practices throughout the development life-cycle. However, there are some essential differences between conventional software and KBSs, both in construction and use. The identification of these differences affect the verification and validation (V&V) process and the development of techniques to handle them. The recognition of these differences is the basis of considerable on-going research in this field. For the past three years IBM (Federal Systems Company - Houston) and the Software Technology Branch (STB) of NASA/Johnson Space Center have been working to improve the 'state of the practice' in V&V of Knowledge-based systems. This work was motivated by the need to maintain NASA's ability to produce high quality software while taking advantage of new KBS technology. To date, the primary accomplishment has been the development and teaching of a four-day workshop on KBS V&V. With the hope of improving the impact of these workshops, we also worked directly with NASA KBS projects to employ concepts taught in the workshop. This paper describes two projects that were part of this effort. In addition to describing each project, this paper describes problems encountered and solutions proposed in each case, with particular emphasis on implications for transferring KBS V&V technology beyond the NASA domain.

Culbert, Chris↗
NASA NTRS2013

Software Tools to Support the Assessment of System Health

This presentation provides an overview of three software tools that were developed by the NASA Glenn Research Center to support the assessment of system health: the Propulsion Diagnostic Method Evaluation Strategy (ProDIMES), the Systematic Sensor Selection Strategy (S4), and the Extended Testability Analysis (ETA) tool. Originally developed to support specific NASA projects in aeronautics and space, these software tools are currently available to U.S. citizens through the NASA Glenn Software Catalog. The ProDiMES software tool was developed to support a uniform comparison of propulsion gas path diagnostic methods. Methods published in the open literature are typically applied to dissimilar platforms with different levels of complexity. They often address different diagnostic problems and use inconsistent metrics for evaluating performance. As a result, it is difficult to perform a one ]to ]one comparison of the various diagnostic methods. ProDIMES solves this problem by serving as a theme problem to aid in propulsion gas path diagnostic technology development and evaluation. The overall goal is to provide a tool that will serve as an industry standard, and will truly facilitate the development and evaluation of significant Engine Health Management (EHM) capabilities. ProDiMES has been developed under a collaborative project of The Technical Cooperation Program (TTCP) based on feedback provided by individuals within the aircraft engine health management community. The S4 software tool provides a framework that supports the optimal selection of sensors for health management assessments. S4 is structured to accommodate user ]defined applications, diagnostic systems, search techniques, and system requirements/constraints. One or more sensor suites that maximize this performance while meeting other user ]defined system requirements that are presumed to exist. S4 provides a systematic approach for evaluating combinations of sensors to determine the set or sets of sensors that optimally meet the performance goals and the constraints. It identifies optimal sensor suite solutions by utilizing a merit (i.e., cost) function with one of several available optimization approaches. As part of its analysis, S4 can expose fault conditions that are difficult to diagnose due to an incomplete diagnostic philosophy and/or a lack of sensors. S4 was originally developed and applied to liquid rocket engines. It was subsequently used to study the optimized selection of sensors for a simulation ]based aircraft engine diagnostic system. The ETA Tool is a software ]based analysis tool that augments the testability analysis and reporting capabilities of a commercial ]off ]the ]shelf (COTS) package. An initial diagnostic assessment is performed by the COTS software using a user ]developed, qualitative, directed ]graph model of the system being analyzed. The ETA Tool accesses system design information captured within the model and the associated testability analysis output to create a series of six reports for various system engineering needs. These reports are highlighted in the presentation. The ETA Tool was developed by NASA to support the verification of fault management requirements early in the Launch Vehicle process. Due to their early development during the design process, the TEAMS ]based diagnostic model and the ETA Tool were able to positively influence the system design by highlighting gaps in failure detection, fault isolation, and failure recovery.

Melcher, Kevin J.↗
NASA NTRS2008

Progress of Ongoing NASA Lithium-Ion Cell Verification Testing for Aerospace Applications

A Lithium-ion Verification and Validation Program with the purpose to assess the capabilities of current aerospace lithium-ion (Li-ion) battery cells to perform in a low-earth-orbit (LEO) regime was initiated in 2002. This program involves extensive characterization and LEO life testing at ten different combinations of depth-of-discharge, temperature, and end-of-charge voltage. The test conditions selected for the life tests are defined as part of a statistically designed test matrix developed to determine the effects of operating conditions on performance and life of Li-ion cells. Results will be used to model and predict cell performance and degradation as a function of test operating conditions. Testing is being performed at the Naval Surface Warfare Center/Crane Division in Crane, Indiana. Testing was initiated in September 2004 with 40 Ah cells from Saft and 30 Ah cells from Lithion. The test program has been expanded with the addition of modules composed of 18650 cells from ABSL Power Solutions in April 2006 and the addition of 50 Ah cells from Mine Safety Appliances Co. (MSA) in June 2006. Preliminary results showing the average voltage and average available discharge capacity for the Saft and Lithion packs at the test conditions versus cycles are presented.

McKissock, Barbara I.↗
NASA NTRS2019

Provably Correct Floating-Point Implementation of a Point-In-Polygon Algorithm

The problem of determining whether or not a point lies inside a given polygon occurs in many applications. In air traffic management concepts, a correct solution to the point-in-polygon problem is critical to geofencing systems for Unmanned Aerial Vehicles and in weather avoidance applications. Many mathematical methods can be used to solve the point-in-polygon problem. Unfortunately, a straightforward floating- point implementation of these methods can lead to incorrect results due to round-off errors. In particular, these errors may cause the control flow of the program to diverge with respect to the ideal real-number algorithm. This divergence potentially results in an incorrect point-in- polygon determination even when the point is far from the edges of the polygon. This paper presents a provably correct implementation of a point-in-polygon method that is based on the computation of the winding number. This implementation is mechanically generated from a source- to-source transformation of the ideal real-number specification of the algorithm. The correctness of this implementation is formally verified within the Frama-C analyzer, where the proof obligations are discharged using the Prototype Verification System (PVS).

Moscato, Mariano M.↗
NASA NTRS2012

Modular, Autonomous Command and Data Handling Software with Built-In Simulation and Test

The spacecraft system that plays the greatest role throughout the program lifecycle is the Command and Data Handling System (C&DH), along with the associated algorithms and software. The C&DH takes on this role as cost driver because it is the brains of the spacecraft and is the element of the system that is primarily responsible for the integration and interoperability of all spacecraft subsystems. During design and development, many activities associated with mission design, system engineering, and subsystem development result in products that are directly supported by the C&DH, such as interfaces, algorithms, flight software (FSW), and parameter sets. A modular system architecture has been developed that provides a means for rapid spacecraft assembly, test, and integration. This modular C&DH software architecture, which can be targeted and adapted to a wide variety of spacecraft architectures, payloads, and mission requirements, eliminates the current practice of rewriting the spacecraft software and test environment for every mission. This software allows missionspecific software and algorithms to be rapidly integrated and tested, significantly decreasing time involved in the software development cycle. Additionally, the FSW includes an Onboard Dynamic Simulation System (ODySSy) that allows the C&DH software to support rapid integration and test. With this solution, the C&DH software capabilities will encompass all phases of the spacecraft lifecycle. ODySSy is an on-board simulation capability built directly into the FSW that provides dynamic built-in test capabilities as soon as the FSW image is loaded onto the processor. It includes a six-degrees- of-freedom, high-fidelity simulation that allows complete closed-loop and hardware-in-the-loop testing of a spacecraft in a ground processing environment without any additional external stimuli. ODySSy can intercept and modify sensor inputs using mathematical sensor models, and can intercept and respond to actuator commands. ODySSy integration is unique in that it allows testing of actual mission sequences on the flight vehicle while the spacecraft is in various stages of assembly, test, and launch operations all without any external support equipment or simulators. The ODySSy component of the FSW significantly decreases the time required for integration and test by providing an automated, standardized, and modular approach to integrated avionics and component interface and functional verification. ODySSy further provides the capability for on-orbit support in the form of autonomous mission planning and fault protection.

Cuseo, John↗
NASA NTRS2011

Evolution of the Space Shuttle Primary Avionics Software and Avionics for Shuttle Derived Launch Vehicles

As a result of recommendation from the Augustine Panel, the direction for Human Space Flight has been altered from the original plan referred to as Constellation. NASA s Human Exploration Framework Team (HEFT) proposes the use of a Shuttle Derived Heavy Lift Launch Vehicle (SDLV) and an Orion derived spacecraft (salvaged from Constellation) to support a new flexible direction for space exploration. The SDLV must be developed within an environment of a constrained budget and a preferred fast development schedule. Thus, it has been proposed to utilize existing assets from the Shuttle Program to speed development at a lower cost. These existing assets should not only include structures such as external tanks or solid rockets, but also the Flight Software which has traditionally been a "long pole" in new development efforts. The avionics and software for the Space Shuttle was primarily developed in the 70 s and considered state of the art for that time. As one may argue that the existing avionics and flight software may be too outdated to support the new SDLV effort, this is a fallacy if they can be evolved over time into a "modern avionics" platform. The technology may be outdated, but the avionics concepts and flight software algorithms are not. The reuse of existing avionics and software also allows for the reuse of development, verification, and operations facilities. The keyword is evolve in that these assets can support the fast development of such a vehicle, but then be gradually evolved over time towards more modern platforms as budget and schedule permits. The "gold" of the flight software is the "control loop" algorithms of the vehicle. This is the Guidance, Navigation, and Control (GNC) software algorithms. This software is typically the most expensive to develop, test, and verify. Thus, the approach is to preserve the GNC flight software, while first evolving the supporting software (such as Command and Data Handling, Caution and Warning, Telemetry, etc.). This can be accomplished by gradually removing the "support software" from the legacy flight software leaving only the GNC algorithms. The "support software" could be re-developed for modern platforms, while leaving the GNC algorithms to execute on technology compatible with the legacy system. It is also possible to package the GNC algorithms into an emulated version of the original computer (via Field Programmable Gate Arrays or FPGAs), thus becoming a "GNC on a Chip" solution where it could live forever to be embedded in modern avionics platforms.

Ferguson, Roscoe C.↗
NASA NTRS1993

Development of deterministic transport methods for low energy neutrons for shielding in space

Transport of low energy neutrons associated with the galactic cosmic ray cascade is analyzed in this dissertation. A benchmark quality analytical algorithm is demonstrated for use with BRYNTRN, a computer program written by the High Energy Physics Division of NASA Langley Research Center, which is used to design and analyze shielding against the radiation created by the cascade. BRYNTRN uses numerical methods to solve the integral transport equations for baryons with the straight-ahead approximation, and numerical and empirical methods to generate the interaction probabilities. The straight-ahead approximation is adequate for charged particles, but not for neutrons. As NASA Langley improves BRYNTRN to include low energy neutrons, a benchmark quality solution is needed for comparison. The neutron transport algorithm demonstrated in this dissertation uses the closed-form Green's function solution to the galactic cosmic ray cascade transport equations to generate a source of neutrons. A basis function expansion for finite heterogeneous and semi-infinite homogeneous slabs with multiple energy groups and isotropic scattering is used to generate neutron fluxes resulting from the cascade. This method, called the FN method, is used to solve the neutral particle linear Boltzmann transport equation. As a demonstration of the algorithm coded in the programs MGSLAB and MGSEMI, neutron and ion fluxes are shown for a beam of fluorine ions at 1000 MeV per nucleon incident on semi-infinite and finite aluminum slabs. Also, to demonstrate that the shielding effectiveness against the radiation from the galactic cosmic ray cascade is not directly proportional to shield thickness, a graph of transmitted total neutron scalar flux versus slab thickness is shown. A simple model based on the nuclear liquid drop assumption is used to generate cross sections for the galactic cosmic ray cascade. The ENDF/B V database is used to generate the total and scattering cross sections for neutrons in aluminum. As an external verification, the results from MGSLAB and MGSEMI were compared to ANISN/PC, a routinely used neutron transport code, showing excellent agreement. In an application to an aluminum shield, the FN method seems to generate reasonable results.

Ganapol, Barry↗
NASA NTRS1993

Three-dimensional Navier-Stokes analysis and redesign of an imbedded bellmouth nozzle in a turbine cascade inlet section

Verification of proposed turbopump blading performance will involve evaluation of candidate blades in cascade test facilities. It is necessary to be able to predict the flow fields within these cascades for the results to be applicable to actual engine environments. This work presents the results of a study to predict the flow field for the NASA Lewis Transonic Turbine Blade Cascade Facility, which is similar to those used to evaluate rocket propulsion turbines. A pitchwise nonuniform total pressure distribution was observed at the blade row leading edge plane. A CFD analysis was used to show that the cause of the flow nonuniformity was a pair of vortices that originated in an embedded bellmouth inlet. Further CFD analysis was used to verify that a redesigned inlet section resulted in a flow with acceptable uniformity. A computational analysis was chosen because physical accessibility to the inlet section was limited, and because a computational approach also allows one to examine design changes cheaper and more quickly than an experimental approach would. The PARC code, a general purpose, three-dimensional, Navier-Stokes code with multiblock solution capability, was chosen for the present study. Results are presented detailing the computational requirements needed to accurately predict flows of this nature. Calculations of the original geometry showed total pressure loss regions consistent in strength and in location to experimental measurements. An examination of the results shows that the distortions are caused by a pair of vortices that originate as a result of the interaction of the flow with the imbedded bellmouth. Computations were performed for an inlet geometry which eliminated the imbedded bellmouth by bridging the region between it and the upstream wall. This analysis indicated that eliminating the imbedded bellmouth eliminates the troublesome pair of vortices, resulting in a flow with much greater pitchwise uniformity.

Giel, P. W.↗
NASA NTRS1992

Research in computational fluid dynamics and analysis of algorithms

Recently, higher-order compact schemes have seen increasing use in the DNS (Direct Numerical Simulations) of the Navier-Stokes equations. Although they do not have the spatial resolution of spectral methods, they offer significant increases in accuracy over conventional second order methods. They can be used on any smooth grid, and do not have an overly restrictive CFL dependence as compared with the O(N(exp -2)) CFL dependence observed in Chebyshev spectral methods on finite domains. In addition, they are generally more robust and less costly than spectral methods. The issue of the relative cost of higher-order schemes (accuracy weighted against physical and numerical cost) is a far more complex issue, depending ultimately on what features of the solution are sought and how accurately they must be resolved. In any event, the further development of the underlying stability theory of these schemes is important. The approach of devising suitable boundary clusters and then testing them with various stability techniques (such as finding the norm) is entirely the wrong approach when dealing with high-order methods. Very seldom are high-order boundary closures stable, making them difficult to isolate. An alternative approach is to begin with a norm which satisfies all the stability criteria for the hyperbolic system, and look for the boundary closure forms which will match the norm exactly. This method was used recently by Strand to isolate stable boundary closure schemes for the explicit central fourth- and sixth-order schemes. The norm used was an energy norm mimicking the norm for the differential equations. Further research should be devoted to BC for high order schemes in order to make sure that the results obtained are reliable. The compact fourth order and sixth order finite difference scheme had been incorporated into a code to simulate flow past circular cylinders. This code will serve as a verification of the full spectral codes. A detailed stability analysis by Carpenter (from the fluid Mechanics Division) and Gottlieb gave analytic conditions for stability as well as asymptotic stability. This had been incorporated in the code in form of stable boundary conditions. Effects of the cylinder rotations had been studied. The results differ from the known theoretical results. We are in the middle of analyzing the results. A detailed analysis of the effects of the heating of the cylinder on the shedding frequency had been studied using the above schemes. It has been found that the shedding frequency decreases when the wire was heated. Experimental work is being carried out to affirm this result.

Gottlieb, David↗
NASA NTRS2014

Alternative, Green Processes for the Precision Cleaning of Aerospace Hardware

Precision cleaning is necessary to ensure the proper functioning of aerospace hardware, particularly those systems that come in contact with liquid oxygen or hypergolic fuels. Components that have not been cleaned to the appropriate levels may experience problems ranging from impaired performance to catastrophic failure. Traditionally, this has been achieved using various halogenated solvents. However, as information on the toxicological and/or environmental impacts of each came to light, they were subsequently regulated out of use. The solvent currently used in Kennedy Space Center (KSC) precision cleaning operations is Vertrel MCA. Environmental sampling at KSC indicates that continued use of this or similar solvents may lead to high remediation costs that must be borne by the Program for years to come. In response to this problem, the Green Solvents Project seeks to develop state-of-the-art, green technologies designed to meet KSCs precision cleaning needs.Initially, 23 solvents were identified as potential replacements for the current Vertrel MCA-based process. Highly halogenated solvents were deliberately omitted since historical precedents indicate that as the long-term consequences of these solvents become known, they will eventually be regulated out of practical use, often with significant financial burdens for the user. Three solvent-less cleaning processes (plasma, supercritical carbon dioxide, and carbon dioxide snow) were also chosen since they produce essentially no waste stream. Next, experimental and analytical procedures were developed to compare the relative effectiveness of these solvents and technologies to the current KSC standard of Vertrel MCA. Individually numbered Swagelok fittings were used to represent the hardware in the cleaning process. First, the fittings were cleaned using Vertrel MCA in order to determine their true cleaned mass. Next, the fittings were dipped into stock solutions of five commonly encountered contaminants and were weighed again showing typical contaminant deposition levels of approximately 0.00300g per part. They were then cleaned by the solvent or process being tested and then weighed a third time which allowed for the calculation of the cleaning efficiency of the test solvent or process.Based on preliminary experiments, five solvents (ethanol, isopropanol, acetone, ethyl acetate, and tert-butyl acetate) were down selected for further testing. When coupled with ultrasonic agitation, these solvents removed hydrocarbon contaminants as well as Vertrel MCA and showed improved removal of perfluorinated greases. Supercritical carbon dioxide did an excellent job dissolving each of the five contaminants but did a poor job of removing Teflon particles found in the perfluorinated greases. Plasma cleaning efficiency was found to be dependent on which supply gas was used, exposure time, and gas pressure. Under optimized conditions it was found that breathing air, energized to the plasma phase, was able to remove nearly 100% of the contamination.These findings indicate that alternative cleaning methods are indeed able to achieve precision levels of cleanliness. Currently, our team is working with a commercial cleaning company to get independent verification of our results. We are also evaluating the technical and financial aspects of scaling these processes to a size capable of supporting the future cleaning needs of KSC.

Vertrel MCA↗
NASA NTRS2024

Lessons Learned from Particulate Characterization Laboratory Anomalies

The White Sands Test Facility chemistry laboratory provides quality control for cleanroom operations including cleanliness verification of aerospace hardware by particulate counts and non-volatile residue determinations, particulate counts for liquid hypergolic propellants, gaseous helium and nitrogen propellant pressurizing agents used for ground support equipment and flight test article valve actuation, gaseous oxygen primarily used for component testing, and deionized water for refurbished propellant hardware flushing. Cleanliness verification includes particulate counts and non-volatile residue determinations to industry standard, NASA, and program specifications and levels. Particulate counts are typically to customer-specified specifications and levels including JPR 5322.1H (2016) Levels 50 and 100, Orion (MPCV 70156. Revision H (2018)) Level 100, RPTSTD-8070-0001 Revision 3 (2022), and IEST-STD-CC1246E (2013) Levels 50 and 100. The laboratory issues high pressure filter holders containing membrane filters to test operations personnel, who collect samples by flowing the required volumes of fluid through the filter holder, and the filter holder is returned to the lab for counting. A passing particulate count is required before testing may proceed. Rapid data reduction and issuing of reports indicating a pass or fail of the particulate specification are required. Corrective action and resampling invariably occurs if a sample fails. Consequently, the laboratory must maintain the highest degree of reliability to facilitate quality data used to decide if testing may proceed. Experience and continual improvements have enabled reliability. However, anomalies attributed to lab processes and hardware including filter holders, membranes, and Petri dishes have been encountered. This paper presents a summary of problems, solutions, successes, and lessons learned from particle counting experience for over 35 years.

Lessons Learned↗
NASA NTRS2004

Risk Assessment and Control through Countermeasure System Iplementation for Long-term Crew Exposure to Microgravity

Experience with the International Space Station (ISS) program demonstrates the degree to which engineering design and operational solutions must protect crewmembers from health risks due to long-term exposure to the microgravity environment. Risks to safety and health due to degradation in the microgravity environment include crew inability to complete emergency or nominal activities, increased risk of injury, and inability to complete safe return to the ground due to reduced strength or embrittled bones. These risks without controls slowly increase in probability for the length of the mission and become more significant for increasing mission durations. Countermeasures to microgravity include hardware systems that place a crewmember s body under elevated stress to produce an effect similar to daily exposure to gravity. The ISS countermeasure system is predominately composed of customized exercise machines. Historical treatment of microgravity countermeasure systems as medical research experiments unintentionally reduced the foreseen importance and therefore the capability of the systems to function in a long-term operational role. Long-term hazardous effects and steadily increasing operational risks due to non-functional countermeasure equipment require a more rigorous design approach and incorporation of redundancy into seemingly non- mission-critical hardware systems. Variations in the rate of health degradation and responsiveness to countermeasures among the crew population drastically increase the challenge for design requirements development and verification of the appropriate risk control strategy. The long-term nature of the hazards and severe limits on logistical re-supply mass, volume and frequency complicates assessment of hardware availability and verification of an adequate maintenance and sparing plan. Design achievement of medically defined performance requirements by microgravity countermeasure systems and incorporation of adequate failure tolerance significantly reduces these risks. Future implementation of on-site monitoring hardware for critical health parameters such as bone mineral density would allow greater responsiveness, efficiency, and optimized design of the countermeasures system.

Gernand, Jeremy M.↗
NASA NTRS2013

Ion Exchange Technology Development in Support of the Urine Processor Assembly

The urine processor assembly (UPA) on the International Space Station (ISS) recovers water from urine via a vacuum distillation process. The distillation occurs in a rotating distillation assembly (DA) where the urine is heated and subjected to sub-ambient pressure. As water is removed, the original organics, salts, and minerals in the urine become more concentrated and result in urine brine. Eventually, water removal will concentrate the urine brine to super saturation of individual constituents, and precipitation occurs. Under typical UPA DA operating conditions, calcium sulfate or gypsum is the first chemical to precipitate in substantial quantity. During preflight testing with ground urine, the UPA achieved 85% water recovery without precipitation. However, on ISS, it is possible that crewmember urine can be significantly more concentrated relative to urine from ground donors. As a result, gypsum precipitated in the DA when operating at water recovery rates at or near 85%, causing the failure and subsequent re14 NASA Tech Briefs, September 2013 placement of the DA. Later investigations have demonstrated that an excess of calcium and sulfate will cause precipitation at water recovery rates greater than 70%. The source of the excess calcium is likely physiological in nature, via crewmembers' bone loss, while the excess sulfate is primarily due to the sulfuric acid component of the urine pretreatment. To prevent gypsum precipitation in the UPA, the Precipitation Prevention Project (PPP) team has focused on removing the calcium ion from pretreated urine, using ion exchange resins as calcium removal agents. The selectivity and effectiveness of ion exchange resins are determined by such factors as the mobility of the liquid phase through the polymer matrix, the density of functional groups, type of functional groups bound to the matrix, and the chemical characteristics of the liquid phase (pH, oxidation potential, and ionic strength). Previous experience with ion exchange resins has demonstrated that the most effective implementation for an ion exchange resin is a cartridge, or column, in which the resin is contained. Based on the results of equilibrium and sub-scale dynamic column testing, a possible solution for mitigating the calcium precipitation issue on the ISS has been identified. From an original pool of 13 ion exchange resins, two candidates have been identified that demonstrate substantial calcium removal on the sub-scale. The dramatic reduction in resin performance from published calcium uptake demonstrates the need for thorough evaluation of resins at the low pH and strong oxidizing environment present in the UPA. Chemical variations in the influent (calcium concentrations and pretreatment dosing) appear to have a noticeable impact on the calcium capacity of the resin. Low calcium concentrations and high pretreatment dosing will likely result in a decrease in calcium capacity. Conversely, low pre trea t - ment dosing will likely result in an increase in calcium capacity. In contrast, investigations at a variety of flow rates, length-to-diameter ratios, resin volumes, and flow regimes (continuous versus pulsed) show that changes in physical parameters do not have substantial impacts on resin performance in the very low specific velocity ranges of interest. This result is particularly useful because most commercial applications at higher specific velocities do show a relatively strong relationship between flow and capacity. The lack of a strong relationship will allow more flexibility in the implementation of an ion exchange bed for flight. Verification of subscale tests with flight-scale resin beds is recommended prior to implementation in the on-orbit UPA.

Mitchell, Julie↗
NASA NTRSDate not supplied

Transcriptomics Processing Pipelines for Space Biology: An Open Source and Consensus-Driven Approach

Transcriptomics holds significant value in elucidating the relationship between gene expression, experimental factors, biological factors, and various types of omics data. Enhancing our understanding of these connections is paramount for foundational biology, which plays a pivotal role in devising solutions for challenges pertinent to both space travel and terrestrial life. The NASA GeneLab project, part of the Open Science Data Repository (OSDR.nasa.gov), seeks to accelerate space biology research through cataloging and democratizing ‘omics data, including transcriptomics. Since raw omics data are largely inaccessible to non-bioinformaticians, GeneLab works with the scientific community via the Open Science Analysis Working Groups (AWGs) to develop standard processing pipelines to generate and publish processed data. Unlike raw data, processed data have greater immediate value to diverse users with varying technical backgrounds and computational capabilities. Standardizing processing workflows is essential to match the pace of raw data generation, ensure reproducibility, and enable standardized processed data for comparison across datasets. As of June 2023, transcriptomics studies comprise over half of GeneLab datasets hosted on the OSDR, including data from bulk RNA-seq and Affymetrix or Agilent 1-Channel DNA microarray assays. In collaboration with the AWGs, GeneLab developed consensus processing pipelines for these transcriptomics data types that includes quality control, background correction (microarray only), data normalization and quantification, culminating in the detection and annotation of differentially expressed genes. The work presented here describes Nextflow implementations of GeneLab’s consensus transcriptomics pipelines that automates and accelerates processing of these datasets. In addition to the core data processing, these workflows also include raw data staging and a robust verification and validation program to identify errors in real-time, stop additional downstream computation, and preserve computational resources. These workflows are used to generate GeneLab processed data hosted on the OSDR, and are publicly available as open source software for others to use at: https://github.com/nasa/GeneLab_Data_Processing.

Jonathan Oribello↗