Results for “Software Testing” — Page 52

NASA NTRS2014

GPM Timeline Inhibits For IT Processing

The Safety Inhibit Timeline Tool was created as one approach to capturing and understanding inhibits and controls from IT through launch. Global Precipitation Measurement (GPM) Mission, which launched from Japan in March 2014, was a joint mission under a partnership between the National Aeronautics and Space Administration (NASA) and the Japan Aerospace Exploration Agency (JAXA). GPM was one of the first NASA Goddard in-house programs that extensively used software controls. Using this tool during the GPM buildup allowed a thorough review of inhibit and safety critical software design for hazardous subsystems such as the high gain antenna boom, solar array, and instrument deployments, transmitter turn-on, propulsion system release, and instrument radar turn-on. The GPM safety team developed a methodology to document software safety as part of the standard hazard report. As a result of this process, a new tool safety inhibit timeline was created for management of inhibits and their controls during spacecraft buildup and testing during IT at GSFC and at the launch range in Japan. The Safety Inhibit Timeline Tool was a pathfinder approach for reviewing software that controls the electrical inhibits. The Safety Inhibit Timeline Tool strengthens the Safety Analysts understanding of the removal of inhibits during the IT process with safety critical software. With this tool, the Safety Analyst can confirm proper safe configuration of a spacecraft during each IT test, track inhibit and software configuration changes, and assess software criticality. In addition to understanding inhibits and controls during IT, the tool allows the Safety Analyst to better communicate to engineers and management the changes in inhibit states with each phase of hardware and software testing and the impact of safety risks. Lessons learned from participating in the GPM campaign at NASA and JAXA will be discussed during this session.

Inhibits↗

NASA NTRS2006

Development of a Low-Cost Sub-Scale Aircraft for Flight Research: The FASER Project

An inexpensive unmanned sub-scale aircraft was developed to conduct frequent flight test experiments for research and demonstration of advanced dynamic modeling and control design concepts. This paper describes the aircraft, flight systems, flight operations, and data compatibility including details of some practical problems encountered and the solutions found. The aircraft, named Free-flying Aircraft for Sub-scale Experimental Research, or FASER, was outfitted with high-quality instrumentation to measure aircraft inputs and states, as well as vehicle health parameters. Flight data are stored onboard, but can also be telemetered to a ground station in real time for analysis. Commercial-off-the-shelf hardware and software were used as often as possible. The flight computer is based on the PC104 platform, and runs xPC-Target software. Extensive wind tunnel testing was conducted with the same aircraft used for flight testing, and a six degree-of-freedom simulation with nonlinear aerodynamics was developed to support flight tests. Flight tests to date have been conducted to mature the flight operations, validate the instrumentation, and check the flight data for kinematic consistency. Data compatibility analysis showed that the flight data are accurate and consistent after corrections are made for estimated systematic instrumentation errors.

Owens, Donald B.↗

NASA NTRS2001

Automating Trend Analysis for Spacecraft Constellations

Spacecraft trend analysis is a vital mission operations function performed by satellite controllers and engineers, who perform detailed analyses of engineering telemetry data to diagnose subsystem faults and to detect trends that may potentially lead to degraded subsystem performance or failure in the future. It is this latter function that is of greatest importance, for careful trending can often predict or detect events that may lead to a spacecraft's entry into safe-hold. Early prediction and detection of such events could result in the avoidance of, or rapid return to service from, spacecraft safing, which not only results in reduced recovery costs but also in a higher overall level of service for the satellite system. Contemporary spacecraft trending activities are manually intensive and are primarily performed diagnostically after a fault occurs, rather than proactively to predict its occurrence. They also tend to rely on information systems and software that are oudated when compared to current technologies. When coupled with the fact that flight operations teams often have limited resources, proactive trending opportunities are limited, and detailed trend analysis is often reserved for critical responses to safe holds or other on-orbit events such as maneuvers. While the contemporary trend analysis approach has sufficed for current single-spacecraft operations, it will be unfeasible for NASA's planned and proposed space science constellations. Missions such as the Dynamics, Reconnection and Configuration Observatory (DRACO), for example, are planning to launch as many as 100 'nanospacecraft' to form a homogenous constellation. A simple extrapolation of resources and manpower based on single-spacecraft operations suggests that trending for such a large spacecraft fleet will be unmanageable, unwieldy, and cost-prohibitive. It is therefore imperative that an approach to automating the spacecraft trend analysis function be studied, developed, and applied to missions such as DRACO with the intent that mission operations costs be significantly reduced. The goal of the Constellation Spacecraft Trend Analysis Toolkit (CSTAT) project is to serve as the pathfinder for a fully automated trending system to support spacecraft constellations. The development approach to be taken is evolutionary. In the first year of the project, the intent is to significantly advance the state of the art in current trending systems through improved functionality and increased automation. In the second year, the intent is to add an expert system shell, likely through the adaptation of an existing commercial-off-the-shelf (COTS) or government-off-the-shelf (GOTS) tool to implement some level of the trending intelligence that humans currently provide in manual operations. In the third year, the intent is to infuse the resulting technology into a near-term constellation or formation-flying mission to test it and gain experience in automated trending. The lessons learned from the real missions operations experience will then be used to improve the system, and to ultimately incorporate it into a fully autonomous, closed-loop mission operations system that is truly capable of supporting large constellations. In this paper, the process of automating trend analysis for spacecraft constellations will be addressed. First, the results of a survey on automation in spacecraft mission operations in general, and in trending systems in particular will be presented to provide an overview of the current state of the art. Next, a rule-based model for implementing intelligent spacecraft subsystem trending will be then presented, followed by a survey of existing COTS/GOTS tools that could be adapted for implementing such a model. The baseline design and architecture of the CSTAT system will be presented. Finally, some results obtained from initial software tests and demonstrations will be presented.

Davis, George↗

NASA NTRS2013

Supporting Real-Time Operations and Execution through Timeline and Scheduling Aids

Since 2003, the NASA Ames Research Center has been actively involved in researching and advancing the state-of-the-art of planning and scheduling tools for NASA mission operations. Our planning toolkit SPIFe (Scheduling and Planning Interface for Exploration) has supported a variety of missions and field tests, scheduling activities for Mars rovers as well as crew on-board International Space Station and NASA earth analogs. The scheduled plan is the integration of all the activities for the day/s. In turn, the agents (rovers, landers, spaceships, crew) execute from this schedule while the mission support team members (e.g., flight controllers) follow the schedule during execution. Over the last couple of years, our team has begun to research and validate methods that will better support users during realtime operations and execution of scheduled activities. Our team utilizes human-computer interaction principles to research user needs, identify workflow processes, prototype software aids, and user test these. This paper discusses three specific prototypes developed and user tested to support real-time operations: Score Mobile, Playbook, and Mobile Assistant for Task Execution (MATE).

scheduling↗

NASA NTRS1998

Testing, Requirements, and Metrics

The criticality of correct, complete, testable requirements is a fundamental tenet of software engineering. Also critical is complete requirements based testing of the final product. Modern tools for managing requirements allow new metrics to be used in support of both of these critical processes. Using these tools, potential problems with the quality of the requirements and the test plan can be identified early in the life cycle. Some of these quality factors include: ambiguous or incomplete requirements, poorly designed requirements databases, excessive or insufficient test cases, and incomplete linkage of tests to requirements. This paper discusses how metrics can be used to evaluate the quality of the requirements and test to avoid problems later. Requirements management and requirements based testing have always been critical in the implementation of high quality software systems. Recently, automated tools have become available to support requirements management. At NASA's Goddard Space Flight Center (GSFC), automated requirements management tools are being used on several large projects. The use of these tools opens the door to innovative uses of metrics in characterizing test plan quality and assessing overall testing risks. In support of these projects, the Software Assurance Technology Center (SATC) is working to develop and apply a metrics program that utilizes the information now available through the application of requirements management tools. Metrics based on this information provides real-time insight into the testing of requirements and these metrics assist the Project Quality Office in its testing oversight role. This paper discusses three facets of the SATC's efforts to evaluate the quality of the requirements and test plan early in the life cycle, thus preventing costly errors and time delays later.

Rosenberg, Linda↗

NASA NTRS2008

Tool Support for Parametric Analysis of Large Software Simulation Systems

The analysis of large and complex parameterized software systems, e.g., systems simulation in aerospace, is very complicated and time-consuming due to the large parameter space, and the complex, highly coupled nonlinear nature of the different system components. Thus, such systems are generally validated only in regions local to anticipated operating points rather than through characterization of the entire feasible operational envelope of the system. We have addressed the factors deterring such an analysis with a tool to support envelope assessment: we utilize a combination of advanced Monte Carlo generation with n-factor combinatorial parameter variations to limit the number of cases, but still explore important interactions in the parameter space in a systematic fashion. Additional test-cases, automatically generated from models (e.g., UML, Simulink, Stateflow) improve the coverage. The distributed test runs of the software system produce vast amounts of data, making manual analysis impossible. Our tool automatically analyzes the generated data through a combination of unsupervised Bayesian clustering techniques (AutoBayes) and supervised learning of critical parameter ranges using the treatment learner TAR3. The tool has been developed around the Trick simulation environment, which is widely used within NASA. We will present this tool with a GN&C (Guidance, Navigation and Control) simulation of a small satellite system.

Schumann, Johann↗

DOE OSTI2024

Commissioning of the Mu2e tracker DAQ, planning for the Vertical Slice Test and pre-pattern recognition studies

The primary objective of the Mu2e experiment at Fermilab is to search for the neutrino-less coherent $\mu \rightarrow e$ conversion in the field of an aluminum nucleus ($\mu^- \text{Al} \rightarrow e^- \text{Al}$). The signature of this process is a monochromatic Conversion Electron (CE) with an energy of approximately 104.97 MeV \cite{bartoszek2015mu2e}. Within the Standard Model (SM), the branching ratio for this process, including neutrino masses and oscillation, is expected to be less than $\mathcal{O}(10^{-50})$. This value is far beyond current experimental capabilities. However, models of physics beyond the SM predict much higher relative rates, approaching an observable level. The SINDRUM II experiment set an upper limit on muon conversion at $7 \times 10^{-13}$ (90\% CL) on Au target \cite{SINDRUMII:2006dvw}, and the Mu2e collaboration aims to improve this limit by four orders of magnitude. Observing this process would provide a clear evidence of physics beyond the Standard Model. A brief discussion of the theoretical and experimental aspects is provided in Chapter \ref{intr}. Mu2e adopts a sophisticated experimental setup to achieve its goals, further described in Chapter \ref{mu2echapter}. The central part of the Mu2e detector is the tracker, that consists of 18 tracking stations. The tracker must provide excellent momentum resolution, approximately 1 MeV/c, to distinguish the monochromatic CE signal from the background. To minimize the energy losses, a straw tube tracker will be used \cite{bobbb}. Chapter \ref{chaptertrk} provides an overview of the straw tracker design and its working principles. This Thesis presents a comprehensive study of the Mu2e tracker, covering complementary aspects from initial commissioning to optimization and first steps of the calibration processes. My work at Fermilab has been focused on the complete Data Acquisition (DAQ) testing from both hardware and software perspectives. I was involved in the commissioning of the Mu2e DAQ system and the Vertical Slice Test (VST) of the tracker. The VST encompasses the entire testing chain, from the straws to the readout, and to processed data on disk. I was also focused on the offline analysis, especially on pre-pattern recognition studies, to explore the best methods for identifying $\delta$-electrons during the data taking. Chapter \ref{commissioning} details the commissioning of the tracker DAQ system, emphasizing the importance of understanding of the readout process before the data acquisition. This includes validating the readout logic and firmware through Monte Carlo simulations to confirm functionality and buffering, monitoring the quality of the data from the tracker preamplifiers and front-end electronics, and assessing overall DAQ performance to ensure reliability during future calibration and data-taking. Chapter \ref{planning} discusses the initial steps towards the tracker calibration. The ultimate goal is to perform a time calibration of the first assembled station of the tracker using cosmic muons, aiming for a longitudinal hit position resolution better than 4 cm. This involves determining the signal propagation times and channel-to-channel delays. I performed a Monte Carlo study to determine the impact of the station orientation on the quality of the calibration, in particular on the cosmic track reconstruction, focusing on potential biases that could arise. These studies provide essential insights into the operation, optimization, and calibration of the Mu2e tracker system. Given the high data volume expected during Mu2e operations, estimated at approximately 7 PBytes per year, optimizing memory usage and minimizing CPU consumption are critical. A significant challenge lies in effectively flagging $\delta$-electron hits, which are the primary source of hits in the tracker, without compromising the efficiency of CE hit detection and track reconstruction. A detailed study of pre-pattern recognition and a thorough comparison of two $\delta$-electron flagging algorithms is provided in Chapter \ref{delta}. In Chapter \ref{conclusions}, the findings are concisely summarized, offering a comprehensive synthesis of the research and emphasizing the key insights derived from this study.

43 PARTICLE ACCELERATORS↗

NASA NTRS2005

Testing the Archivas Cluster (Arc) for Ozone Monitoring Instrument (OMI) Scientific Data Storage

The Ozone Monitoring Instrument (OMI) launched on NASA's Aura Spacecraft, the third of the major platforms of the EOS program on July 15,2004. In addition to the long term archive and distribution of the data from OM1 through the Goddard Earth Science Distributed Active Archive Center (GESDAAC), we are evaluating other archive mechanisms that can archive the data in a more immediately available method where it can be used for futher data production and analysis. In 2004, Archivas, Inc. was selected by NASA s Small Business Innovative Research (SBIR) program for the development of their Archivas Cluster (ArC) product. Arc is an online disk based system utilizing self-management and automation on a Linux cluster. Its goal is to produce a low cost solution coupled with the ease of management. The OM1 project is an application partner of the SBIR program, and has deployed a small cluster (5TB) based on the beta Archwas software. We performed extensive testing of the unit using production OM1 data since launch. In 2005, Archivas, Inc. was funded in SBIR Phase II for further development, which will include testing scalability with the deployment of a larger (35TB) cluster at Goddard. We plan to include Arc in the OM1 Team Leader Computing Facility (TLCF) hosting OM1 data for direct access and analysis by the OMI Science Team. This presentation will include a brief technical description of the Archivas Cluster, a summary of the SBIR Phase I beta testing results, and an overview of the OMI ground data processing architecture including its interaction with the Phase II Archivas Cluster and hosting of OMI data for the scientists.

Tilmes, Curt↗

NASA NTRS2004

Validation of autonomous rover functionality for planetary environments

NASAThis paper discusses autonomous rover functionality as it relates to planetary environmental issues and aspects of associated software validation.

functional testing↗

NASA NTRS2019

In-Flight Evaluation of the Traffic Aware Planner on the NASA HU-25A Guardian Aircraft

NASA’s Traffic Aware Planner (TAP) software is a research-prototype decision support tool that provides pilots with time- and fuel-saving route recommendations that optimize their current trajectory. The software runs on a first-of-a-kind system architecture onboard three aircraft in revenue service conducting operational evaluations with a major domestic airline. Therefore, significant NASA-internal testing is required prior to releasing the software to the partner airline. This paper describes a flight test plan that exercises the functionality of the TAP software in a representative operational environment, describes the system architecture developed and implemented for the NASA Langley HU-25A Guardian aircraft to support the test objectives, presents outcomes of the flight test campaign, and discusses use cases that demonstrate the value of flight testing for this activity.Research into flight path optimization of transport aircraft conducted by the National Aeronautics and SpaceAdministration (NASA) has produced an operational concept known as Traffic Aware Strategic Aircrew Requests(TASAR) [1, 2]. This near-term concept [3] provides the aircrew with a flight deck decision support tool known asthe Traffic Aware Planner (TAP). The TAP software leverages a growing number of information sources on the flightdeck to make time- and fuel-saving route optimization recommendations to the aircrew while en route. The aircrewcan then use the suggestions provided by the tool to make route change requests with a greater likelihood of acceptanceby air traffic control (ATC). Since TASAR is a concept intended for the current operational environment, it isintentionally designed to have no safety-critical impact or require any changes to current Federal AviationAdministration (FAA) rules and procedures [4, 5].The research prototype TAP system [6–8], explained further in Section III.C, continually incorporates up-to-dateaircraft state data from onboard avionics, as well as the latest position of surrounding traffic, the most recent windforecast, and the most recent convective weather forecast, in order to calculate candidate trajectory modifications thatimprove upon the current active route. These trajectories account for user-selectable objective functions [3] of reducedfuel burn, reduced flight time, or an airline-derived combination of factors known as trip cost. Previous analyses andsimulations have estimated substantial savings for airlines employing this technique within the U.S. National AirspaceSystem (NAS) [9–11]. Operational evaluations with Alaska Airlines seek to validate these projected benefits usingmeasured data while simultaneously providing benefits to the airline [12, 13].The TAP software has undergone a number of human-in-the-loop simulations [14] and flight test activities[15–17] in order to validate the operational concept, evaluate human factors considerations (e.g., workload, usability,distraction, etc.), and to assess the ability of the software to function in a representative operational environment (e.g.,connected to live avionics data, using in-flight internet connectivity, etc.). However, these simulations and flight testcampaigns did not account for the hardware architecture implemented on the three aircraft for Alaska Airlines’operational evaluations of the TAP software. Therefore, a need was identified to thoroughly test the functionality ofthe software in a similar hardware architecture to that of the partner airline’s aircraft. Information regarding testapparatus and environments used to evaluate TAP prior to testing on the HU-25A can be found in reference [18].A campaign of flight trials on a NASA aircraft, the HU-25A Guardian, was conducted to ensure that the researchprototype TAP system functions well in a configuration similar to the Alaska Airlines aircraft prior to deployment.This airborne, networked environment enables an assessment of the operational factors unique to the flight environment. Additionally, this activity evaluated the effectiveness and benefit of new TAP functionality andoperation in a relevant flight environment while allowing the rapid prototyping of new concepts and features.This paper is organized as follows: Section II discusses the details of the flight test plan, flight profiles, and theduties of personnel involved with conducting flight operations. Section III describes the test platform, avionicsequipage, and system architecture. Section IV presents a discussion of results, and Section V contains concludingremarks.

Underwood, Matthew C.↗

NASA NTRS2012

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

DOE OSTI2026

Field Validation of a Grid-Interactive Efficient Building Software Solution

The U.S. General Services Administration's (GSA's) Green Proving Ground (GPG) program, in partnership with the National Laboratory of the Rockies (NLR), completed a field study of a Grid-Interactive Efficient Buildings (GEB) software solution. The study focused on a single testbed facility to test the GEB functionality of the software solution, along with other features. The testbed facility - a courthouse - is a common building type in GSA's vast building portfolio, offering potentially impactful findings on a scalable level. The study evaluated Prescriptive Data's technology, Nantum OS, a connected building operating system ("GEB Solution") which aggregates multiple sources of previously siloed building data and combines that data with external sources, such as weather information or utility signals, into a single integrated platform. A GEB Solution is a type of Energy Management Information System (EMIS). EMIS is defined as a system of devices, data services, and software applications that communicates with any building system or third-party data source to aggregate and transform data into new capabilities to aid in the optimization of energy use at the building, campus, or agency level. This specific GEB Solution is an EMIS with ASO, automated system optimization, offering supervisory control of certain aspects of the Building Automation System (BAS). Multiple features were evaluated including, but not limited to, Continuous Demand Management to avoid setting new monthly kilowatt (kW) peaks, energy efficiency for reduction of kilowatt hours (kWh) and natural gas consumption, and automated demand response (ADR) for purposes of lowering demand during a utility called Demand Response (DR) event. The testbed facility was the Foley Federal Building and US Courthouse ("Foley Federal Building") located in Las Vegas, NV. This is a 209,496 sq. ft. building constructed in the 1960s with major renovations in 2004. The facility was a good candidate due to the large prevalence of office and courthouse spaces in the GSA portfolio of buildings. It also has many features which allow integration into and control of the building and a strong facilities team to assist with the study. Quantitative and qualitative performance objectives were developed using GSA's GPG GEB project template along with input from the vendor and building facility staff; these are outlined in Table 1. The quantitative performance objectives focused on continuous demand management, energy efficiency, and automated demand response. The qualitative performance objectives focused on the ease of installation and commissioning as well as the operability of the GEB solution. Other performance metrics that are reported on include carbon reduction, cost effectiveness, and occupant acceptance.

32 ENERGY CONSERVATION, CONSUMPTION, AND UTILIZATI↗

NASA NTRS2011

High Level Architecture Distributed Space System Simulation for Simulation Interoperability Standards Organization Simulation Smackdown

Modeling and Simulation plays a very important role in mission design. It not only reduces design cost, but also prepares astronauts for their mission tasks. The SISO Smackdown is a simulation event that facilitates modeling and simulation in academia. The scenario of this year s Smackdown was to simulate a lunar base supply mission. The mission objective was to transfer Earth supply cargo to a lunar base supply depot and retrieve He-3 to take back to Earth. Federates for this scenario include the environment federate, Earth-Moon transfer vehicle, lunar shuttle, lunar rover, supply depot, mobile ISRU plant, exploratory hopper, and communication satellite. These federates were built by teams from all around the world, including teams from MIT, JSC, University of Alabama in Huntsville, University of Bordeaux from France, and University of Genoa from Italy. This paper focuses on the lunar shuttle federate, which was programmed by the USRP intern team from NASA JSC. The shuttle was responsible for provide transportation between lunar orbit and the lunar surface. The lunar shuttle federate was built using the NASA standard simulation package called Trick, and it was extended with HLA functions using TrickHLA. HLA functions of the lunar shuttle federate include sending and receiving interaction, publishing and subscribing attributes, and packing and unpacking fixed record data. The dynamics model of the lunar shuttle was modeled with three degrees of freedom, and the state propagation was obeying the law of two body dynamics. The descending trajectory of the lunar shuttle was designed by first defining a unique descending orbit in 2D space, and then defining a unique orbit in 3D space with the assumption of a non-rotating moon. Finally this assumption was taken away to define the initial position of the lunar shuttle so that it will start descending a second after it joins the execution. VPN software from SonicWall was used to connect federates with RTI during testing and the Smackdown event. HLA software from Pitch Technology and MAK Technology were used to edit and extend FOM and provide HLA services for federation execution. The SISO Smackdown event for 2011 was held in Boston, Massachusetts. The federation execution lasted for one hour, and the event was very successful in catching the attention of university students and faculties.

Li, Zuqun↗

NASA NTRSDate not supplied

Trajectory Simulation Using Multi Model Monte Carlo with Python (MXMCPy)

EDL (Entry, Descent and Landing) is the process from a vehicle approaching a surface to landing on it, such as a Mars rover approaching the planet before landing. POST2 (Program to Optimize Simulated Trajectories 2) is Langley’s primary EDL simulation tool and is used NASA-wide for simulations. POST2 can generate highly accurate results by running a precise, but time consuming, Monte Carlo (MC) simulation hundreds or thousands of times. Though POST2 can produce highly accurate results, it can take unrealistic time spans to generate these results, which has created a need to speed up the simulations. The new NASA software MXMCPy offers various ways to speed up the simulations while getting just as precise results. Instead of running high-precision POST2 simulations many times for traditional MC, MXMCPy can run fewer high-precision POST2 simulations and many less precise POST2 simulations and merge the results. MXMCPy contains 30+ different methods which will each suggest different allocations between model precision levels, which result in results of varying precision based on the POST2 simulation. I created Python and Bash code to automate the 5 steps of MXMCPy’s application to POST2. I also tested the precision of traditional Monte Carlo simulations to MXMCPy aided simulations and found that MXMCPy can achieve substantially more precise solutions at the same computer runtime. I learned Test Driven Development (TDD), a software programming workflow which involves writing computer-automated tests before writing the code which is being tested. These tests are ran every time the code is changed and they can find glitches in the code much quicker than a human can. This programming workflow saved me a lot of time because the automated tests could tell me exactly where the code had stopped working. I plan on using this software development method for future academic and professional software projects. I have greatly enjoyed my work at NASA, so I have been applying to NASA internships and Pathways positions. In addition, I plan on applying what I have learned about Test Driven Development to my computer science courses next semester

James Warner↗

NASA NTRS2015

Schedule Analysis Software Saves Time for Project Planners

Since the early 2000s, a resource management team at Marshall Space Flight Center has developed and improved the Schedule Test and Assessment Tool, a software add-on capable of analyzing, summarizing, and finding logic gaps in project schedules. Companies like Lanham, Maryland-based Vantage Systems Inc. use the tool to manage NASA projects, but it has also been released for free to more than 200 US companies, agencies, and other entities.

Source record↗

NASA NTRSDate not supplied

ARCTRON: A Rapid Experimental Proving Ground for TPS Experiments and Arcjet Technology Development

Innovation in high-enthalpy facilities is fundamentally limited by the cost and risk of experimentation. New concepts for plasma control, diagnostics, facility components, and plasma-material interaction often require repeated iterations that are impractical to perform in production arcjets. As a result, promising ideas may remain unexplored or reach operational facilities only after significant development effort. ARCTRON is being developed as a rapid experimental proving ground where new ideas in plasma science, arcjet engineering, diagnostics, and material response can be conceived, tested, and quantitatively evaluated before transition to large-scale facilities. The platform combines radio-frequency (RF) and DC arc plasma generation, externally applied magnetic fields, configurable gas composition, reduced-pressure operation, laser heating, electrical biasing, and modular diagnostic access. These capabilities permit the plasma source, applied forcing, test article, and measurement configuration to be modified independently, allowing individual physical mechanisms to be isolated more readily than in a traditional test environment. One class of investigations addresses fundamental plasma-surface interaction physics. Conventional material tests often expose a specimen simultaneously to convective heating, reactive species, pressure, shear, radiation, and surface-current effects. The resulting material response may be measured accurately, while the contribution of each mechanism remains difficult to identify. ARCTRON is designed to vary these effects selectively. Plasma chemistry can be changed independently through configurable gas mixtures; magnetic fields and electrical biasing can modify charged-particle transport; laser heating can provide a non-plasma thermal input; and pressure, flow, and discharge mode can be varied over a broad operating space. This enables controlled tests of hypotheses involving surface catalycity, reactive-species transport, plasma-assisted oxidation, electromagnetic effects, shear, and the relative contributions of thermal and chemical loading. A second class of investigations enabled by this approach concerns the engineering of high-enthalpy facilities themselves. Arc-heated facilities are limited by electrode erosion, unstable arc attachment, localized heating, and damage to nozzles and other plasma-facing components. ARCTRON provides a lower-cost environment for testing concepts intended to mitigate these limitations. Candidate investigations include the use of applied magnetic fields to alter current paths and reduce plasma interaction with nozzle walls, ExB forcing to introduce controlled plasma rotation, magnetic or geometric approaches for distributing arc attachment, and alternative electrode or discharge configurations intended to reduce erosion and improve stability. Because the platform is reconfigurable, these concepts can be evaluated through repeated design--build--test cycles before they are considered for implementation in operational facilities. The platform also supports the development and validation of diagnostics that may be difficult to introduce initially into a large arcjet. Current and planned measurements include spatially resolved optical emission spectroscopy, electrostatic probes, fast imaging, pyrometry, calorimetry, laser-induced fluorescence, and absorption spectroscopy. These diagnostics are intended not merely to document a nominal operating condition, but to constrain the local plasma state and its relationship to component or material response. The modular facility geometry allows diagnostic concepts to be tested, calibrated, and compared under repeatable conditions before deployment in more demanding environments. ARCTRON is also supported by an integrated software suite. Automated control and data acquisition allow discharge parameters, gas composition, magnetic fields, diagnostic timing, and test configuration to be recorded as part of each experiment (STARDAC - Software for Testing, Analysis, Research Data, and Control). The Backend for Experiment Analysis, Storage, and Traceability (BEAST) is a database that provides the infrastructure needed to associate heterogeneous measurements with facility configuration, specimen identity, calibration state, geometry, and analysis provenance. This backend is particularly important for exploratory campaigns, in which many related configurations may be tested, and the value of an individual experiment depends on its connection to earlier and subsequent iterations. Complementary analysis capabilities, including computer-vision-based transient response measurements (arcjetCV), three-dimensional surface reconstruction (STARSCAN), and model-based Bayesian inference (SHIELD), and tomography data analysis (TOMATO, PuMA) can be incorporated when required by a specific hypothesis without becoming the focus of every campaign. The central objective of ARCTRON is therefore not to maximize heat flux or reproduce a complete flight environment. Its purpose is to reduce the cost and time required to ask consequential questions about plasma behavior, plasma-facing materials, diagnostics, and arcjet technology. By providing a controlled environment for rapid reconfiguration, mechanism isolation, quantitative measurement, and iterative engineering, ARCTRON can help mature concepts that would otherwise remain too speculative or too risky for evaluation in production facilities. The resulting knowledge can then guide the design of material models, focus test objectives in larger arcjets, reduce facility-development risk, and improve the physical basis of high-enthalpy ground testing. This work will present the ARCTRON architecture, operating modes, diagnostic suite, and digital experimental workflow. Initial experimental results from the first integrated operation of the facility will be presented, including flow characterization, power limitations, and deployment of the initial diagnostic suite. Ongoing development efforts aimed at catalycity characterization, magnetic plasma control, and advanced optical diagnostics will also be discussed, illustrating how the platform supports rapid iteration from concept to experiment.

experimental diagnostics↗

NASA NTRSDate not supplied

ARCTRON: A Rapid Experimental Proving Ground for TPS Experiments and Arcjet Technology Development

Innovation in high-enthalpy facilities is fundamentally limited by the cost and risk of experimentation. New concepts for plasma control, diagnostics, facility components, and plasma-material interaction often require repeated iterations that are impractical to perform in production arcjets. As a result, promising ideas may remain unexplored or reach operational facilities only after significant development effort. ARCTRON is being developed as a rapid experimental proving ground where new ideas in plasma science, arcjet engineering, diagnostics, and material response can be conceived, tested, and quantitatively evaluated before transition to large-scale facilities. The platform combines radio-frequency (RF) and DC arc plasma generation, externally applied magnetic fields, configurable gas composition, reduced-pressure operation, laser heating, electrical biasing, and modular diagnostic access. These capabilities permit the plasma source, applied forcing, test article, and measurement configuration to be modified independently, allowing individual physical mechanisms to be isolated more readily than in a traditional test environment. One class of investigations addresses fundamental plasma-surface interaction physics. Conventional material tests often expose a specimen simultaneously to convective heating, reactive species, pressure, shear, radiation, and surface-current effects. The resulting material response may be measured accurately, while the contribution of each mechanism remains difficult to identify. ARCTRON is designed to vary these effects selectively. Plasma chemistry can be changed independently through configurable gas mixtures; magnetic fields and electrical biasing can modify charged-particle transport; laser heating can provide a non-plasma thermal input; and pressure, flow, and discharge mode can be varied over a broad operating space. This enables controlled tests of hypotheses involving surface catalycity, reactive-species transport, plasma-assisted oxidation, electromagnetic effects, shear, and the relative contributions of thermal and chemical loading. A second class of investigations enabled by this approach concerns the engineering of high-enthalpy facilities themselves. Arc-heated facilities are limited by electrode erosion, unstable arc attachment, localized heating, and damage to nozzles and other plasma-facing components. ARCTRON provides a lower-cost environment for testing concepts intended to mitigate these limitations. Candidate investigations include the use of applied magnetic fields to alter current paths and reduce plasma interaction with nozzle walls, ExB forcing to introduce controlled plasma rotation, magnetic or geometric approaches for distributing arc attachment, and alternative electrode or discharge configurations intended to reduce erosion and improve stability. Because the platform is reconfigurable, these concepts can be evaluated through repeated design--build--test cycles before they are considered for implementation in operational facilities. The platform also supports the development and validation of diagnostics that may be difficult to introduce initially into a large arcjet. Current and planned measurements include spatially resolved optical emission spectroscopy, electrostatic probes, fast imaging, pyrometry, calorimetry, laser-induced fluorescence, and absorption spectroscopy. These diagnostics are intended not merely to document a nominal operating condition, but to constrain the local plasma state and its relationship to component or material response. The modular facility geometry allows diagnostic concepts to be tested, calibrated, and compared under repeatable conditions before deployment in more demanding environments. ARCTRON is also supported by an integrated software suite. Automated control and data acquisition allow discharge parameters, gas composition, magnetic fields, diagnostic timing, and test configuration to be recorded as part of each experiment (STARDAC - Software for Testing, Analysis, Research Data, and Control). The Backend for Experiment Analysis, Storage, and Traceability (BEAST) is a database that provides the infrastructure needed to associate heterogeneous measurements with facility configuration, specimen identity, calibration state, geometry, and analysis provenance. This backend is particularly important for exploratory campaigns, in which many related configurations may be tested, and the value of an individual experiment depends on its connection to earlier and subsequent iterations. Complementary analysis capabilities, including computer-vision-based transient response measurements (arcjetCV), three-dimensional surface reconstruction (STARSCAN), and model-based Bayesian inference (SHIELD), and tomography data analysis (TOMATO, PuMA) can be incorporated when required by a specific hypothesis without becoming the focus of every campaign. The central objective of ARCTRON is therefore not to maximize heat flux or reproduce a complete flight environment. Its purpose is to reduce the cost and time required to ask consequential questions about plasma behavior, plasma-facing materials, diagnostics, and arcjet technology. By providing a controlled environment for rapid reconfiguration, mechanism isolation, quantitative measurement, and iterative engineering, ARCTRON can help mature concepts that would otherwise remain too speculative or too risky for evaluation in production facilities. The resulting knowledge can then guide the design of material models, focus test objectives in larger arcjets, reduce facility-development risk, and improve the physical basis of high-enthalpy ground testing. This work will present the ARCTRON architecture, operating modes, diagnostic suite, and digital experimental workflow. Initial experimental results from the first integrated operation of the facility will be presented, including flow characterization, power limitations, and deployment of the initial diagnostic suite. Ongoing development efforts aimed at catalycity characterization, magnetic plasma control, and advanced optical diagnostics will also be discussed, illustrating how the platform supports rapid iteration from concept to experiment.

experimental diagnostics↗

NASA NTRS1990

Multiversion software reliability through fault-avoidance and fault-tolerance

In this project we have proposed to investigate a number of experimental and theoretical issues associated with the practical use of multi-version software in providing dependable software through fault-avoidance and fault-elimination, as well as run-time tolerance of software faults. In the period reported here we have working on the following: We have continued collection of data on the relationships between software faults and reliability, and the coverage provided by the testing process as measured by different metrics (including data flow metrics). We continued work on software reliability estimation methods based on non-random sampling, and the relationship between software reliability and code coverage provided through testing. We have continued studying back-to-back testing as an efficient mechanism for removal of uncorrelated faults, and common-cause faults of variable span. We have also been studying back-to-back testing as a tool for improvement of the software change process, including regression testing. We continued investigating existing, and worked on formulation of new fault-tolerance models. In particular, we have partly finished evaluation of Consensus Voting in the presence of correlated failures, and are in the process of finishing evaluation of Consensus Recovery Block (CRB) under failure correlation. We find both approaches far superior to commonly employed fixed agreement number voting (usually majority voting). We have also finished a cost analysis of the CRB approach.

Vouk, Mladen A.↗