Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “automated 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 181 records · Page 10

Aerospace Cognitive Engineering Laboratory (ACELAB) Simulator for Electric Vertical Takeoff and Landing (eVOTL) Research and Development

A new generation of aerospace innovators are looking for ways to quickly and efficiently transport people in a safe and environmentally friendly manner. In the not-too-distant future, passengers and goods are expected to routinely fly aboard a new breed of cleaner, smarter air vehicles. This represents a new and significant challenge to the Federal Aviation Agency (FAA) which is responsible for aircraft certification, pilot licensing, operating approval and airspace integration. To help streamline this process, NASA has formulated its Advanced Air Mobility (AAM) project to provide research capabilities for development and evaluation of these new concepts and an environment where industry and regulators can work together to understand the requirements and work toward consensus standards for the new market. This paper will describe the development of the Aerospace Cognitive Engineering Lab Rapid Automation Test (ACELeRATE) simulator. ACELeRATE is an adaptable fixed-base aircraft simulator focused on the investigation of the performance and interaction of pilots and increasingly automated aircraft systems. ACELeRATE can be re-configured to support various simulation environments. The simulator includes a simple reconfigurable cockpit placed within a 10-foot spherical dome with a cluster of real-time image generators, high-resolution displays and highly realistic scenery with the surrounding digital terrain and required cultural area details (e.g., hangars, runways, ramp areas, taxiways, test range apparatus, buildings with designated rooftop landing areas, and other man-made 3D structures). This paper will also describe the various hardware and software tools employed in the ACELeRATE simulator, including engineering tools used by NASA for electric Vertical Takeoff and Landing (eVTOL) vehicle equations of motion, wind-model simulation in an urban environment, as well as the various modeling techniques and tools used to quickly generate highly realistic 3D terrain models for low level flight including urban terrain and obstacle depictions.

AAM Simulation Cockpit↗

Interactive specification acquisition via scenarios: A proposal

Some reactive systems are most naturally specified by giving large collections of behavior scenarios. These collections not only specify the behavior of the system, but also provide good test suites for validating the implemented system. Due to the complexity of the systems and the number of scenarios, however, it appears that automated assistance is necessary to make this software development process workable. Interactive Specification Acquisition Tool (ISAT) is a proposed interactive system for supporting the acquisition and maintenance of a formal system specification from scenarios, as well as automatic synthesis of control code and automated test generation. This paper discusses the background, motivation, proposed functions, and implementation status of ISAT.

Hall, Robert J.↗

Computer automation of ultrasonic testing

Report describes a prototype computer-automated ultrasonic system developed for the inspection of weldments. This system can be operated in three modes: manual, automatic, and computer-controlled. In the computer-controlled mode, the system will automatically acquire, process, analyze, store, and display ultrasonic inspection data in real-time. Flaw size (in cross-section), location (depth), and type (porosity-like or crack-like) can be automatically discerned and displayed. The results and pertinent parameters are recorded.

Yee, B. G. W.↗

Fault injection based automatic testing - Practice and examples

This report addresses the problem of ascertaining the quantitative properties of dependable distributed systems. The approach is based on fault injection experimentation with two distinct real-time workloads using a fault-injection-based automated testing environment. Experimental results are presented which indicate dependability properties (e.g., error detection coverage, error latency) based on a limited number of fault injections.

Segall, Z.↗

Development and Implementation of a CTF Code Verification Suite.

CTF is a thermal hydraulic subchannel code developed to predict light water reactor (LWR) core behavior. It is a version of Coolant Boiling in Rod Arrays (COBRA) developed by Oak Ridge National Laboratory (ORNL) and North Carolina State University (NCSU) and used in the Consortium for the Advanced Simulation of LWRs (CASL). Here, the existing CTF code verification matrix is expanded, which ensures that the code is a faithful representation of the underlying mathematical model. The suite of code verification tests are mapped to the underlying conservation equations of CTF and significant gaps are addressed. As such, five new problems are incorporated: isokinetic advection, conduction, pressure drop, convection, and pipe boiling. Convergence behavior and numerical errors are quantified for each of the tests and all tests converge at the correct rate to their corresponding analytic solution. A new verification utility that generalizes the code verification process is used to incorporate these problems into the CTF automated test suite.

22 GENERAL STUDIES OF NUCLEAR REACTORS↗

Persistent Elevated Soot Emissions Induced by Clustered Stochastic Preignition Events

Stochastic Preignition (SPI) is an abnormal combustion phenomenon that can occur in spark-ignition engines particularly under high-load operation. SPI is characterized by uncontrolled initiation of combustion prior to spark discharge, an abnormal combustion process that can lead to severe knock events and significant engine damage. SPI has been associated with fuel properties, lubricant composition, and engine design and operation. Here, in this work, a single-cylinder test engine with a dry-sump oil system was utilized to study the SPI response of E10 and E25 fuels with a range of Reid Vapor Pressure (RVP). An automated test procedure was employed, consisting of ten square-waved load profile segments, with each segment composed of 5 min of low-load operation followed by 25 min of sustained high-load operation. These tests were replicated across multiple days of testing including a lubricant triple flush between tests, and an online Fuel in Oil diagnostic measurement. Exhaust particulate emissions were continuously measured by an AVL microsoot sensor (MSS). Elevated particulate matter emissions were observed to occur concurrently with SPI events as blooms of soot. Particularly after clustered events (i.e., multiple SPI cycles occurring within 10 consecutive engine cycles), high soot emissions were observed to persist over several days of sequential operation despite daily lubricant changes, a complete warm-up procedure, and sustained low-load operation between test segments. This result implies that the particulate emissions trends may be dominated by deposit-based effects, where higher load operation is needed to alter deposition and formation processes. The observed soot blooms were also found to correspond to a reduction in the engine fueling and the fuel engine oil dilution rate despite the engine exhaust remaining at stoichiometric exhaust operation. These observations suggest that post-SPI events, pathways for lubricant migration and consumption into the combustion chamber may occur until these pathways are closed from deposit formation or ring dynamics during extended operation. These observed sooting propensity persisted with all fuels tests, but a linear correlation was observed between the summation of soot and particulate matter index (PMI) value for each fuel as well as SPI events, proving that PMI is a crucial fuel property for reducing SPI.

Splitter, Derek [Oak Ridge National Laboratory (OR↗

Recent Productivity Improvements to the National Transonic Facility

Productivity gains have recently been made at the National Transonic Facility wind tunnel at NASA Langley Research Center. A team was assigned to assess and set productivity goals to achieve the desired operating cost and output of the facility. Simulations have been developed to show the sensitivity of selected process productivity improvements in critical areas to reduce overall test cycle times. The improvements consist of an expanded liquid nitrogen storage system, a new fan drive, a new tunnel vent stack heater, replacement of programmable logic controllers, an increased data communications speed, automated test sequencing, and a faster model changeout system. Where possible, quantifiable results of these improvements are presented. Results show that in most cases, improvements meet the productivity gains predicted by the simulations.

Popernack, Thomas G., Jr.↗

Helping System Engineers Bridge the Peaks

In our experience at NASA, system engineers generally follow the Twin Peaks approach when developing safety-critical systems. However, iterations between the peaks require considerable manual, and in some cases duplicate, effort. A significant part of the manual effort stems from the fact that requirements are written in English natural language rather than a formal notation. In this work, we propose an approach that enables system engineers to leverage formal requirements and automated test generation to streamline iterations, effectively "bridging the peaks". The key to the approach is a formal language notation that a) system engineers are comfortable with, b) is supported by a family of automated V&V tools, and c) is semantically rich enough to describe the requirements of interest. We believe the combination of formalizing requirements and providing tool support to automate the iterations will lead to a more efficient Twin Peaks implementation at NASA.

Requirements↗

Controller Verification of a Smart-Grid Compatible 200 kHz Single-stage Photovoltaic Microinverter

This paper presents control system design, implementation, and experimental validation of a single-stage 400 W, 200 kHz solar photovoltaic (PV) microinverter using hardware-in-the-loop (HIL) and hardware testing. The selected circuit topology is based on a Gallium Nitride (GaN) direct-matrix based dual active bridge (DAB) converter with a low voltage active power decoupler (APD) circuit. Control performance is verified, smart-grid compatibility is tested, and circuit operation is confirmed. Controller HIL (CHIL) is shown to aid in a complex power electronics system design by 1) enabling detailed control development prior to hardware implementation, 2) expanding the use of automated testing, and 3) increasing confidence in control performance prior to prototype testing. Altogether, these factors make HIL a valuable tool in complex power electronic designs.

14 SOLAR ENERGY↗

Test Driven Development of Scientific Models

Test-Driven Development (TDD) is a software development process that promises many advantages for developer productivity and has become widely accepted among professional software engineers. As the name suggests, TDD practitioners alternate between writing short automated tests and producing code that passes those tests. Although this overly simplified description will undoubtedly sound prohibitively burdensome to many uninitiated developers, the advent of powerful unit-testing frameworks greatly reduces the effort required to produce and routinely execute suites of tests. By testimony, many developers find TDD to be addicting after only a few days of exposure, and find it unthinkable to return to previous practices. Of course, scientific/technical software differs from other software categories in a number of important respects, but I nonetheless believe that TDD is quite applicable to the development of such software and has the potential to significantly improve programmer productivity and code quality within the scientific community. After a detailed introduction to TDD, I will present the experience within the Software Systems Support Office (SSSO) in applying the technique to various scientific applications. This discussion will emphasize the various direct and indirect benefits as well as some of the difficulties and limitations of the methodology. I will conclude with a brief description of pFUnit, a unit testing framework I co-developed to support test-driven development of parallel Fortran applications.

Clune, Thomas L.↗

Requirements-Driven Log Analysis Extended Abstract

Imagine that you are tasked to help a project improve their testing effort. In a realistic scenario it will quickly become clear, that having an impact is diffcult. First of all, it will likely be a challenge to suggest an alternative approach which is significantly more automated and/or more effective than current practice. The reality is that an average software system has a complex input/output behavior. An automated testing approach will have to auto-generate test cases, each being a pair (i; o) consisting of a test input i and an oracle o. The test input i has to be somewhat meaningful, and the oracle o can be very complicated to compute. Second, even in case where some testing technology has been developed that might improve current practice, it is then likely difficult to completely change the current behavior of the testing team unless the technique is obviously superior and does everything already done by existing technology. So is there an easier way to incorporate formal methods-based approaches than the full edged test revolution? Fortunately the answer is affirmative. A relatively simple approach is to benefit from possibly already existing logging infrastructure, which after all is part of most systems put in production. A log is a sequence of events, generated by special log recording statements, most often manually inserted in the code by the programmers. An event can be considered as a data record: a mapping from field names to values. We can analyze such a log using formal methods, for example checking it against a formal specification. This separates running the system for analyzing its behavior. It is not meant as an alternative to testing since it does not address the important in- put generation problem. However, it offers a solution which testing teams might accept since it has low impact on the existing process. A single person might be assigned to perform such log analysis, compared to the entire testing team changing behavior.

log analysis↗

Test Driven Development of Scientific Models

Test-Driven Development (TDD), a software development process that promises many advantages for developer productivity and software reliability, has become widely accepted among professional software engineers. As the name suggests, TDD practitioners alternate between writing short automated tests and producing code that passes those tests. Although this overly simplified description will undoubtedly sound prohibitively burdensome to many uninitiated developers, the advent of powerful unit-testing frameworks greatly reduces the effort required to produce and routinely execute suites of tests. By testimony, many developers find TDD to be addicting after only a few days of exposure, and find it unthinkable to return to previous practices.After a brief overview of the TDD process and my experience in applying the methodology for development activities at Goddard, I will delve more deeply into some of the challenges that are posed by numerical and scientific software as well as tools and implementation approaches that should address those challenges.

Overview of TDD Process↗

Seascape Interface Control Document (V.1)

This paper serves as the Interface Control Document (ICD) for the Seascape automated test harness developed at Sandia National Laboratories. The primary purposes of the Seascape system are: (1) provide a place for accruing large, curated, labeled data sets useful for developing and evaluating detection and classification algorithms (including, but not limited to, supervised machine learning applications) (2) provide an automated structure for specifying, running and generating reports on algorithm performance. Seascape uses GitLab, Nexus, Solr, and Banana, open source codes, together with code written in the Python language, to automatically provision and configure computational nodes, queue up jobs to accomplish algorithms test runs against the stored data sets, gather the results and generate reports which are then stored in the Nexus artifact server.

97 MATHEMATICS AND COMPUTING↗

Seascape Interface Control Document (V. 2)

This paper serves as the Interface Control Document (ICD) for the Seascape automated test harness developed at Sandia National Laboratories. The primary purposes of the Seascape system are: (1) provide a place for accruing large, curated, labeled data sets useful for developing and evaluating detection and classification algorithms (including, but not limited to, supervised machine learning applications) (2) provide an automated structure for specifying, running and generating reports on algorithm performance. Seascape uses GitLab, Nexus, Solr, and Banana, open source codes, together with code written in the Python language, to automatically provision and configure computational nodes, queue up jobs to accomplish algorithms test runs against the stored data sets, gather the results and generate reports which are then stored in the Nexus artifact server.

97 MATHEMATICS AND COMPUTING↗

Seascape Interface Control Document

This paper serves as the Interface Control Document (ICD) for the Seascape automated test harness developed at Sandia National Laboratories. The primary purposes of the Seascape system are: (1) provide a place for accruing large, curated, labeled data sets useful for developing and evaluating detection and classification algorithms (including, but not limited to, supervised machine learning applications) (2) provide an automated structure for specifying, running and generating reports on algorithm performance. Seascape uses GitLab, Nexus, Solr, and Banana, open source software, together with code written in the Python language, to automatically provision and configure computational nodes, queue up jobs to accomplish algorithms test runs against the stored data sets, gather the results and generate reports which are then stored in the Nexus artifact server.

97 MATHEMATICS AND COMPUTING↗

Development of automated electromagnetic compatibility test facilities at Marshall Space Flight Center

The efforts to automate the electromagentic compatibility (EMC) test facilites at Marshall Flight Center were examined. A battery of nine standard tests is to be integrated by means of a desktop computer-controller in order to provide near real-time data assessment, store the data acquired during testing on flexible disk, and provide computer production of the certification report.

Harrison, Cecil A.↗

Oculomotor Assessment of Diurnal Arousal Variations

Saccadic and pupillary responses are reliable indices of arousal decrement (e.g. fatigue), that might be exploited to improve work schedule guidelines. In this study, we tested the sensitivity of a short 30-s oculomotor test to detect diurnal arousal variations. Twelve participants (5 females, 7 males, 37.7+-11.9 years) volunteered to be assessed every hour (66+-20 min) for three consecutive working days, during their regular office-hours. We used a fully automated testing system, the FIT 2000 Fitness Impairment Tester (Pulse Medical Instruments Inc., Rockville, MD, USA), to measure and record saccadic peak velocity, pupil diameter, and latency and amplitude of the pupillary light reflex. In addition, we collected subjective levels of arousal using the Stanford Sleepiness Scale, and body core temperature. We analyzed the data using a linear mixed model approach for longitudinal data. Both saccadic velocity and subjective alertness decreased over the course of a day, while body core temperature increased (all p-values.05). The data also weakly suggested an increase of the pupil diameter (p 07). The findings support the use of oculomotor indices in the assessment of arousal and fatigue in applied settings.

saccadic velocity↗

Results of accelerated thermal cycle tests of solar cells modules

Various candidate solar panel designs were evaluated, both theoretically and experimentally, with respect to their thermal cycling survival capability, and in particular with respect to an accelerated simulation of thermal cycles representative of Viking '75 mission requirements. The experimental results were obtained on 'mini-panels' thermally cycled in a newly installed automated test facility herein described. The resulting damage was analyzed physically and theoretically, and on the basis of these analyses the panel design was suitably modified to significantly improve its ability to withstand the thermal environment. These successful modifications demonstrate the value of the complementary theoretical-experimental approach adopted, and discussed in detail in this paper.

Berman, P.↗