SEARCH · Search NASA

Results for “Unit 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.

SourceResearch connectionFrom yearThrough year

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 325 records · Page 18

All sources NASA NTRS DOE OSTI

NASA NTRS2017

Geometrically Flexible and Efficient Flow Analysis of High Speed Vehicles Via Domain Decomposition, Part 1: Unstructured-Grid Solver for High Speed Flows

The ability to solve the equations governing the hypersonic turbulent flow of a real gas on unstructured grids using a spatially-elliptic, 2nd-order accurate, cell-centered, finite-volume method has been recently implemented in the VULCAN-CFD code. This paper describes the key numerical methods and techniques that were found to be required to robustly obtain accurate solutions to hypersonic flows on non-hex-dominant unstructured grids. The methods and techniques described include: an augmented stencil, weighted linear least squares, cell-average gradient method, a robust multidimensional cell-average gradient-limiter process that is consistent with the augmented stencil of the cell-average gradient method and a cell-face gradient method that contains a cell skewness sensitive damping term derived using hyperbolic diffusion based concepts. A data-parallel matrix-based symmetric Gauss-Seidel point-implicit scheme, used to solve the governing equations, is described and shown to be more robust and efficient than a matrix-free alternative. In addition, a y+ adaptive turbulent wall boundary condition methodology is presented. This boundary condition methodology is deigned to automatically switch between a solve-to-the-wall and a wall-matching-function boundary condition based on the local y+ of the 1st cell center off the wall. The aforementioned methods and techniques are then applied to a series of hypersonic and supersonic turbulent flat plate unit tests to examine the efficiency, robustness and convergence behavior of the implicit scheme and to determine the ability of the solve-to-the-wall and y+ adaptive turbulent wall boundary conditions to reproduce the turbulent law-of-the-wall. Finally, the thermally perfect, chemically frozen, Mach 7.8 turbulent flow of air through a scramjet flow-path is computed and compared with experimental data to demonstrate the robustness, accuracy and convergence behavior of the unstructured-grid solver for a realistic 3-D geometry on a non-hex-dominant grid.

White, Jeffery A.↗

NASA NTRS2018

Heatshield for Extreme Entry Environment Technology (HEEET) Development and Maturation Status

This poster provides an overview of the requirements, design, development and testing of the 3D (Three Dimensional) Woven TPS (Thermal Protection System) being developed under NASA's Heatshield for Extreme Entry Environment Technology (HEEET) project. Under this current program, NASA is working to develop a TPS capable of surviving entry into Saturn. A primary goal of the project is to build and test an Engineering Test Unit (ETU) to establish a Technical Readiness Level (TRL) of 6 for this technology by 2017.

Extreme Entry Environment↗

NASA NTRS2018

SLS Navigation Model-Based Design Approach

The SLS Program chose to implement a Model-based Design and Model-based Requirements approach for managing component design information and system requirements. This approach differs from previous large-scale design efforts at Marshall Space Flight Center where design documentation alone conveyed information required for vehicle design and analysis and where extensive requirements sets were used to scope and constrain the design. The SLS Navigation Team has been responsible for the Program-controlled Design Math Models (DMMs) which describe and represent the performance of the Inertial Navigation System (INS) and the Rate Gyro Assemblies (RGAs) used by Guidance, Navigation, and Controls (GN&C). The SLS Navigation Team is also responsible for the navigation algorithms. The navigation algorithms are delivered for implementation on the flight hardware as a DMM. For the SLS Block 1-B design, the additional GPS Receiver hardware is managed as a DMM at the vehicle design level. This paper provides a discussion of the processes and methods used to engineer, design, and coordinate engineering trades and performance assessments using SLS practices as applied to the GN&C system, with a particular focus on the Navigation components. These include composing system requirements, requirements verification, model development, model verification and validation, and modeling and analysis approaches. The Model-based Design and Requirements approach does not reduce the effort associated with the design process versus previous processes used at Marshall Space Flight Center. Instead, the approach takes advantage of overlap between the requirements development and management process, and the design and analysis process by efficiently combining the control (i.e. the requirement) and the design mechanisms. The design mechanism is the representation of the component behavior and performance in design and analysis tools. The focus in the early design process shifts from the development and management of design requirements to the development of usable models, model requirements, and model verification and validation efforts. The models themselves are represented in C/C++ code and accompanying data files. Under the idealized process, potential ambiguity in specification is reduced because the model must be implementable versus a requirement which is not necessarily subject to this constraint. Further, the models are shown to emulate the hardware during validation. For models developed by the Navigation Team, a common interface/standalone environment was developed. The common environment allows for easy implementation in design and analysis tools. Mechanisms such as unit test cases ensure implementation as the developer intended. The model verification and validation process provides a very high level of component design insight. The origin and implementation of the SLS variant of Model-based Design is described from the perspective of the SLS Navigation Team. The format of the models and the requirements are described. The Model-based Design approach has many benefits but is not without potential complications. Key lessons learned associated with the implementation of the Model Based Design approach and process from infancy to verification and certification are discussed

Oliver, T. Emerson↗

NASA NTRS2018

PYSAT: Python Satellite Data Analysis Toolkit

A common problem in space science data analysis is combining complementary data sources that are provided and analyzed in different formats and programming languages. The Python Satellite Data Analysis Toolkit (pysat) addresses this issue by providing an open source toolkit that implements the general process of space science data analysis, from beginning to end, in an instrumentindependent manner. This toolkit uses an Instrument object that enables systematic analysis of science data from a variety of platforms within a single interface. Basic functions such as downloading, loading, and cleaning are included for all supported instruments. Common analysis routines are also included, which are instrument and data source independent. A nanokernel is used to provide instrument independence, it is attached to the Instrument object and mediates the systematic and arbitrary modification of loaded data. Pysat uses the nanokernel to improve the rigor of time series analysis, support onthefly orbit determination, and cleanly span file breaks. Pysat's functions and higherlevel scientific analysis features are validated through the use of unit testing. Further adoption by the community provides a set of scientific results produced by a common core, constituting a distributed heritage that supports the validity of the underlying processing and scientific output. These features are used to demonstrate consistency between derived electron density profiles and measured ion drifts, particularly downward ion drifts in the afternoon hours during extreme solar minimum. Pysat builds upon open source Python software that is freely available and encourages communitydriven development.

Stoneback, R.A.↗

NASA NTRS2019

Heatshield for Extreme Entry Environment Technology (HEEET) TPS for Ice Giants Probe Missions

This poster provides an overview of the requirements, design, development and testing of the 3D Woven TPS being developed under NASAs Heatshield for Extreme Entry Environment Technology (HEEET) project. Under this current program, NASA is working to develop a Thermal Protection System (TPS) capable of surviving entry into Saturn. A primary goal of the project is to build and test an Engineering Test Unit (ETU) to establish a Technical Readiness Level (TRL) of 6 for this technology by 2018. Poster also discusses use of HEEET TPS for probe missions to the Ice Giants, Uranus and Neptune.

Extreme Entry Environment↗

NASA NTRS2017

Generating Real-Time Robotics Control Software from SysML

In this paper, we outline an approach for autogenerating real-time robotics control code from hierarchical state machines and hardware configurations encoded in Systems Modeling Language (SysML). We propose a software architecture that provides an abstract SysML layer with access to device state information and a set of primitive device commands, such as move actuator and release brake, allowing a user to build up a complete functional state machine directly in SysML. The SysML diagram is then exported to a standard SCXML file format and subsequently used to auto-generate hardware control code. Once this architecture is in place, the only explicit code elements that need to be written are the primitive device commands, which can be easily unit tested and reused across different systems. The motivation for this work was the need for a test bed that enables the rapid prototyping of mechanisms and control algorithms for a spacecraft that could ultimately be used for preparing Martian rock samples for their return to Earth. To this end, our software system was also designed to allow for the run-time specification of the hardware layout in SysML, with the hardware-level control functions kept agnostic to the specific parameters or communication bus of any particular device. Further, we outline a system for specifying both the state machine and hardware configuration in the MagicDraw IDE in such a way that the system can be simulated before any code is generated. The resultant software system is easy to debug, understand, and allows users to choose how much information is encoded as a visual or text-based representation.

Godart, Peter↗

NASA NTRS2019

Overview of Heatshield for Extreme Entry Environment Technology (HEEET)

The objective of the Heatshield for Extreme Entry Environment Technology (HEEET) projects is to mature a 3-D Woven Thermal Protection System (TPS) to Technical Readiness Level (TRL) 6 to support future NASA missions to destinations such as Venus and Saturn. Destinations that have extreme entry environments with heat fluxes > 3500 W/sq cm and pressures up to 5 atmospheres, entry environments that NASA has not flown since Pioneer-Venus and Galileo. The scope of the project is broad and can be split into roughly four areas, Manufacturing/Integration, Structural Testing and Analysis, Thermal Testing and Analysis and Documentation. Manufacturing/Integration covers from raw materials, piece part fabrication to final integration on a 1-meter base diameter 45-degree sphere cone Engineering Test Unit (ETU). A key aspect of the project was to transfer as much of the manufacturing technology to industry in preparation to support future mission infusion. The forming, infusion and machining approaches were transferred to Fiber Materials Inc. and FMI then fabricated the piece parts from which the ETU was manufactured.

Thermal Protection System↗

NASA NTRS2020

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.↗

NASA NTRSDate not supplied

Accuracy of Center of Pressure Determination via Motion Capture

BACKGROUND: This study was conducted to support the stability assessment for tasks in lunar gravity and exercises on a Vibration Isolation and Stabilization (VIS) system in microgravity based on the dynamic feasibility criterion of whether the calculated position of the center of pressure (COP) falls within the base of support (BOS) which outlines the subject’s feet. Motion capture data combined with biomechanical modeling and simulation allows the forces and moments between the human and the VIS platform to be computed and the position of the COP as well as the location and shape of the BOS to be determined. The goal of this study was to assess the accuracy of the COP trajectory calculated using motion capture-based data. METHODS AND RESULTS: To obtain the dynamic quantities from which COP is calculated, motion capture data is first collected in the 1g lab environment by recording the trajectories of passive retroreflective markers placed on a subject during exercise or performance of a given task. The OpenSim [1] inverse kinematics (IK) tool is used to fit a scaled subject model to recorded marker trajectories while minimizing marker error to obtain joint angles. Then, a custom OpenSim plugin [2] is used to determine the subject’s time-varying moment of inertia and its time derivative, center of mass (CM) position, velocity, and acceleration, as well as the angular momentum and its time derivative relative to the subject’s CM. Some of these quantities are not needed for modeling tasks performed on a stationary lunar surface but, due to the moving exercise platform, are needed to model VIS response to the subject’s motion. Hand positions, used in calculating a cable force if present, are recorded as well. These quantities are used to calculate the total force (F ⃗^((plate) )) and moment (M ⃗^((plate) )) exerted by the lunar surface or the VIS plate on the subject’s shoe soles. COP is then calculated from the following equations: r_x^((cop) )= M_z^((plate) )/F_y^((plate) ) and r_z^((cop) )= 〖-M〗_x^((plate) )/F_y^((plate) ), where the y axis is normal to the surface. COP accuracy for feasibility assessments is then determined by whether it falls within the BOS, which is also computed by the plugin. To study the accuracy of COP calculated from motion capture, we first investigated whether COP remained within the BOS, as it must, for exercises performed in the 1g lab environment. Standard exercises such as back squat and deadlift were analyzed, as well as more explosive exercises including hang clean and press. Cases in which the COP exited the BOS indicated that COP accuracy required further investigation. In this study, an exercise device with cables was used, so cable force modeling accuracy should also be considered. In a separate study, we collected motion capture and force plate data for twenty-seven motions not involving an exercise device. About a third were genuine countermeasures exercises (e.g., hang clean and press), some were relevant for lunar tasks (e.g., object pick up), and the rest were of a “unit test” nature (e.g., swaying back and forth or side to side). Motion capture-based COP positions were compared with force plate measured COP. We found that while force plate measured COP remained within the BOS, motion capture-based COP was observed to briefly exit the BOS on occasion. Techniques to mitigate IK artifacts and filtering of calculated data could be used to improve the agreement of calculated and measured results, resolving excursions from the BOS within this dataset. The mean error between calculated and measured COP was found to be less than 6 mm. Additionally, we derived and investigated equations for the COP in terms of the cable force, cable location, as well as the human CM position, acceleration, and angular momentum with respect to the CM, and analyzed them for sensitivity to errors in individual quantities. Several were found, but the most significant one was that when the vertical force on the feet approaches zero, indicating a near-detachment or ‘jump off’ condition, errors are amplified. This is consistent with the observation that in the absence of pressure, the concept of the center of pressure would become meaningless.

C A Bell↗

NASA NTRS2022

LIF Testing of ETU-2 in VF-5

A visualization of the experimental setup for the Laser-Induced Fluorescence (LIF) diagnostic system applied to AEPS Engineering Test Unit 2 (ETU-2) in the Electric Propulsion and Power Laboratory's (EPPL) Vacuum Facility 5 (VF-5)

LIF↗

NASA NTRS2022

Spatial Characterization of PACE OCI ETU Using Time-Delay Mode

The OCI (Ocean Color Instrument) is the main sensor on the upcoming PACE (Plankton Aerosol Cloud ocean Ecosystem) mission. OCI has two hyperspectral CCD sensors covering 340nm to 885nm and 9 SWIR (Short Wave IR) bands from 940nm to 2260nm. SWIR bands have nominal 1km ground pixel size and CCD bands have native 1/8 km ground pixel size in diagnostic mode that will be aggregated into 1km pixels to improve SNR and meet the data rate constraints. OCI has a rotating telescope that is synchronized to the readout of the CCD and SWIR detectors. Full pre-launch system level testing for the OCI ETU (Engineering Test Unit) was completed in June 2021.With time-delayed scan mode, a sub-pixel level time-delay step is applied to the detector readout. This sub-pixel level time-delay step causes a sub-pixel level shift in the start of the data collection. After collecting time-delay step scans with different step sizes, a scan profile with sub-pixel resolution can be constructed. 1/8 and 1/4 of CCD pixel resolutions were achieved using this mode. In this paper, the OCI time-delayed scan mode will be described as well as how it was used to calculate OCI’s high spatial resolution PSF (Point Spread Function), IFOV (instantaneous Field of View), MTF (Modulation Transfer Function), and BBR (Band to Band Registration).

PACE↗

NASA NTRSDate not supplied

Recent Improvements and Verification of A Full Body Model in Opensim

BACKGROUND: The dynamic feasibility [1,2] criterion, that the subject’s Center of Pressure (COP) be located within the Base of Support (BOS) which outlines the feet, has aided in assessing the stability of human motion recorded on earth while performing the recorded tasks in lunar gravity or as countermeasures exercises on a vibration isolation and stabilization system in microgravity. The convex hull of the BOS on the platform under the subject’s feet was estimated using virtual markers on the feet of the scaled subject model. The COP was calculated using the ground reaction forces and moments determined from motion capture data with biomechanical modeling tools [3]. Occasionally, large-amplitude oscillatory spikes or “artifacts” were observed in the subject’s linear and angular momentum derivatives, affecting some COP data derived from motion capture. The purpose of this investigation was to assess and improve the accuracy of model scaling and BOS estimation as well as to determine the efficacy of model adjustments in mitigating artifacts influencing motion capture-derived ground reaction force and COP results. METHODS: To aid evaluation of proposed process and model updates, motion capture data were collected for two subjects during unit test and range of motion trials, lunar tasks, and countermeasures exercise motions. Markers were added to the full body Plug-in Gait marker set [4] during data collection. New markers were placed on the front, back, sides, and top of the head to improve scaling using distances between marker pairs. Medial elbow markers were added to stabilize the upper arm during OpenSim Inverse Kinematics (IK) [5]. Finally, markers were added on the outer edge of the heels and on the outside edges of the first and last toes on each foot. These additional foot markers were made available to test new automated foot scaling techniques and to calculate the error between the subject’s estimated and recorded BOS. The modified unscaled OpenSim Full Body Rajagopal Model [6,7] was adjusted using some previously investigated techniques [8] to mitigate rapid shifts in joint angles occurring during IK, as these were found to cause the spike artifacts observed in subsequent stages of analysis. Since OpenSim models use Euler angles and rotation sequences, the arm axes of rotation were adjusted, and the pelvis order of rotation was changed to minimize the likelihood of encountering “gimbal lock” during common human motion. The model clavicle, arm, elbow, wrist, pelvis, and ankle angle limits were adjusted to better accommodate the full human range of motion seen in exercise and lunar data. The shoulder joint center was calculated using a “pivoting” algorithm [9], and both shoulder joint center and upper arm markers were included during IK to provide additional shoulder stability on a case-by-case basis. The quality of IK results was assessed by three criteria: minimizing error between recorded motion capture markers and model markers, checking for reasonable rates of change in joint angles between fames (i.e., no IK artifacts), and ensuring the absence of spikes in the inertial forces and angular momentum derivatives calculated using a custom OpenSim plugin [10]. RESULTS: The additional markers placed on the subject during data collection allowed the head and feet to be scaled more accurately using distances between new marker pairs. Scaling with BOS markers placed on the subject and removing the limit on subtalar angle resulted in more accurate BOS determination. Unrealistically large changes in joint angles between frames could be reduced by including clavicle, sternum, and medial elbow markers during IK. In cases with large arm ranges of motion, results could be further improved by running IK using medial elbow and virtual shoulder joint center markers. Model adjustments significantly improved the IK results affecting COP calculation and increased the accuracy of BOS estimation.

C A Bell↗

NASA NTRS2023

Pypromice: A Python Package for Processing Automated Weather Station Data

The pypromice Python package is for processing and handling observation datasets from automated weather stations (AWS). It is primarily aimed at users of AWS data from the Geological Survey of Denmark and Greenland (GEUS), which collects and distributes in situ weather station observations to the cryospheric science research community. Functionality in pypromice is primarily handled using two key open-source Python packages, xarray (Hoyer & Hamman, 2017) and pandas (The pandas development team, 2020). A defined processing workflow is included in pypromice for transforming original AWS observations (Level 0, L0) to a usable, CF-convention-compliant dataset (Level 3, L3) (Figure 1). Intermediary processing levels (L1,L2) refer to key stages in the workflow, namely the conversion of variables to physical measurements and variable filtering (L1), cross-variable corrections and user-defined data flagging and fixing (L2), and derived variables (L3). Information regarding the station configuration is needed to perform the processing, such as instrument calibration coefficients and station type (one-boom tripod or two-boom mast station design, for example), which are held in a toml configuration file. Two example configuration files are provided with pypromice , which are also used in the package’s unit tests. More detailed documentation of the AWS design, instrumentation, and processing steps are described in Fausto et al. (2021).

pypromice↗

NASA NTRSDate not supplied

Design Considerations of an Ascent Abort Monitor Algorithm for Use During Service Module Aborts

In support of human rating the Artemis missions, NASA's Orion program requires continuous abort coverage from liftoff through mission destination. During a portion of the ascent trajectory, the currently achievable abort mode is determined by an Orion algorithm using the onboard navigated vehicle state. This ascent abort monitor determines achievability for Orion's Mode 2 abort, Untargeted Abort Splashdown (UAS), by propagating the current vehicle state through ascent abort events to determine sufficient timing to perform the abort and to a ballistic touchdown point to approximate landing location relative to prescribed keep out boundaries. The algorithm was updated for Artemis 2 to allow the capability to limit loads for the majority of ascent. Performance of the algorithm has been demonstrated and verified through dispersed trajectory analysis with emulated flight software, unit testing, and hardware in the loop testing.

Esteban Guzman↗

DOE OSTI2026

Evaluation of LLVM Flang for Production HPC Applications and Modern Fortran Features

In 2025, LLVM released its first Flang Fortran compiler version considered ready for widespread evaluation. We know of no published assessment of Flang compiling a workload- derived portfolio of high-performance computing (HPC) applications. We address this gap using workload data from the National Energy Research Scientific Computing Center (NERSC), which supports more than 10,000 scientists on approximately 1,000 projects. The NERSC workload analyses identify many Fortran components in heavily used applications. We selected 10 such packages with available source code. We compiled them with Flang 22.1.3 on NERSC’s Perlmutter system. Six compiled without code modifications, though some required build-system changes. Three compiled after minor source edits, mostly to address Fortran standard violations. One built only without OpenMP enabled. We evaluated seven additional packages selected for their use of, or enablement of, standard Fortran parallel features: multi-image execution and do concurrent. Six such codes compiled with most or all unit tests passing.

Rasmussen, Katherine↗

NASA NTRS1977

Flight test results of the strapdown hexad inertial reference unit (SIRU). Volume 2: Test report

Results of flight tests of the Strapdown Inertial Reference Unit (SIRU) navigation system are presented. The fault tolerant SIRU navigation system features a redundant inertial sensor unit and dual computers. System software provides for detection and isolation of inertial sensor failures and continued operation in the event of failures. Flight test results include assessments of the system's navigational performance and fault tolerance. Performance shortcomings are analyzed.

Hruby, R. J.↗

NASA NTRS1990

Current activities in standardization of high-temperature, low-cycle-fatigue testing techniques in the United States

The American Society for Testing and Materials (ASTM) standard E606-80 is the most often used recommended testing practice for low-cycle-fatigue (LCF) testing in the United States. The standard was first adopted in 1977 for LCF testing at room temperature and was modified in 1980 to include high-temperature testing practices. Current activity within ASTM is aimed at extending the E606-80 recommended practices to LCF under thermomechanical conditions, LCF in high-pressure hydrogen, and LCF in metal-matrix composite materials. Interlaboratory testing programs conducted to generate a technical base for modifying E606-80 for the aforementioned LCF test types are discussed.

Verrilli, Michael J.↗

NASA NTRS2026

The Trash Compaction Processing Systems (TCPS) Ground Unit Control Sample Testing

The Trash Compaction Processing System (TCPS) is being developed by NASA and Sierra Space to process crew trash for long-duration missions. The system compacts and thermally processes mixed spacecraft waste to reduce volume and stabilize the material while managing gas and liquid effluents. A Ground Unit (GU) located at Sierra Space in Madison, Wisconsin was used to run a series of tests using standardized control samples representing different trash conditions, including nominal, high liquid, high cloth, benign, and foam. Gas grab samples were collected during processing and analyzed to identify the compounds present in the effluent stream and compare the concentrations to the NASA spacecraft maximum allowable concentrations (SMACs). Additional testing included odor testing at White Sands Test Facility, aerosol measurements, microbiology, and tile characterization. Overall, the compounds detected in the gas samples were well below the SMAC limits for all trash models tested. The results from this testing are being used to help guide the verification approach and test planning for the TCPS Flight Unit that is planned for on-orbit testing on the International Space Station.

Control Samples↗