Leveraging the Cloud for HDF1 Software Testing
In this talk we will discuss how we leverage the Cloud for HDF software daily regression testing including testing of the HDF5 parallel library on the Cloud cluster using Orange FS.
CI testing↗
SEARCH · Engineering Papers
Results for “Software 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.
Software Testing and Verification in Climate Model Development
Over the past 30 years most climate models have grown from relatively simple representations of a few atmospheric processes to a complex multi-disciplinary system. Computer infrastructure over that period has gone from punch card mainframes to modem parallel clusters. Model implementations have become complex, brittle, and increasingly difficult to extend and maintain. Existing verification processes for model implementations rely almost exclusively upon some combination of detailed analysis of output from full climate simulations and system-level regression tests. In additional to being quite costly in terms of developer time and computing resources, these testing methodologies are limited in terms of the types of defects that can be detected, isolated and diagnosed. Mitigating these weaknesses of coarse-grained testing with finer-grained "unit" tests has been perceived as cumbersome and counter-productive. In the commercial software sector, recent advances in tools and methodology have led to a renaissance for systematic fine-grained testing. We discuss the availability of analogous tools for scientific software and examine benefits that similar testing methodologies could bring to climate modeling software. We describe the unique challenges faced when testing complex numerical algorithms and suggest techniques to minimize and/or eliminate the difficulties.
Clune, Thomas L.↗
Virtual Infrastructure Twins: Software Testing Platforms for Computing-Instrument Ecosystems
Science ecosystems are being built by federating computing systems and instruments located at geographically distributed sites over wide-area networks. These computing-instrument ecosystems are expected to support complex workflows that incorporate remote, automated AI-driven science experiments. Their realization, however, requires various designs to be explored and software components to be developed, in order to support the orchestration of distributed computations and experiments. It is often too expensive, infeasible, or disruptive for the entire ecosystem to be available during the typically long software development and testing periods. We propose a Virtual Infrastructure Twin (VIT) of the ecosystem that emulates its network and computing components, and incorporates its instrument software simulators. It provides a software environment nearly identical to the ecosystem to support early development and testing, and design space exploration. We present a brief overview of previous digital infrastructure twins that culminated in the VIT concept, including (i) the virtual science network environment for developing software-defined networking solutions, and (ii) the virtual federated science instrument environment for testing the federation software stack and remote instrument control software. We briefly describe VITs for Nion microscope steering and access to GPU systems.
Rao, Nageswara↗
Virtual Infrastructure Twins: Software Testing Platforms for Computing-Instrument Ecosystems
Science ecosystems are being built by federating computing systems and instruments located at geographically distributed sites over wide-area networks. These computing-instrument ecosystems are expected to support complex workflows that incorporate remote, automated AI-driven science experiments. Their realization, however, requires various designs to be explored and software components to be developed, in order to support the orchestration of distributed computations and experiments. It is often too expensive, infeasible, or disruptive for the entire ecosystem to be available during the typically long software development and testing periods. We propose a Virtual Infrastructure Twin (VIT) of the ecosystem that emulates its network and computing components, and incorporates its instrument software simulators. It provides a software environment nearly identical to the ecosystem to support early development and testing, and design space exploration. We present a brief overview of previous digital infrastructure twins that culminated in the VIT concept, including (i) the virtual science network environment for developing software-defined networking solutions, and (ii) the virtual federated science instrument environment for testing the federation software stack and remote instrument control software. We briefly describe VITs for Nion microscope steering and access to GPU systems.
Rao, Nageswara↗
YOLO Test Software v1.4
This is a user manual of the software being developed at Brookhaven National Laboratory to test deep learnings algorithms. (YOLO) You Only Look Once. V1.4 added new features, including Display metric average recall, early termination option and display filename/image.
97 MATHEMATICS AND COMPUTING↗
NOVA/IOPS - MDM/SIO - SL/BIU data transfer test software guide
The NOVA/IOPS (Input-Output Processor Simulator) is used to control all interface testing of the MDM (Multiplexer Demultiplexer) Breadboard S10 10M (serial input-output-input module) and the Matra Space Lab Inerface Unit (SL/BIU). The software handles bookkeeping such as word error rates, types of errors, display of error buffers, data display and test identification.
Source record↗
Single Board Computer Radiation Test Results and Radiation Test Software
Single Board Computers (SBCs) are quickly evolving and gaining capability as their cost comes down. As their footprints, cost, and power requirements decrease, their processing power increases. This makes them very attractive for use on space missions and an enabling technology as spacecraft size decreases and computational demand increases. One of the major challenges electronics face in the space environment is radiation. In 2019, the NASA Johnson Space Center (JSC) tested a selection of SBCs to low Earth orbit (LEO) radiation levels and evaluated their susceptibility and survivability. For this test campaign, JSC developed a Python software suite to better characterize the SBCs performance and intends to share the software.
Pedrotty, Samuel M.↗
Loran-C flight test software
The software package developed for the KIM-1 Micro-System and the Mini-L PLL receiver to simplify taking flight test data is described along with the address and data bus buffers used in the KIM-1 Micro-system. The interface hardware and timing are also presented to describe completely the software programs.
Nickum, J. D.↗
Risk-Based Object Oriented Testing
Software testing is a well-defined phase of the software development life cycle. Functional ("black box") testing and structural ("white box") testing are two methods of test case design commonly used by software developers. A lesser known testing method is risk-based testing, which takes into account the probability of failure of a portion of code as determined by its complexity. For object oriented programs, a methodology is proposed for identification of risk-prone classes. Risk-based testing is a highly effective testing technique that can be used to find and fix the most important problems as quickly as possible.
Rosenberg, Linda H.↗
Orbit Determination and Navigation Software Testing for the Mars Reconnaissance Orbiter
During the extended science phase of the Mars Reconnaissance Orbiter's lifecycle, the operational duties pertaining to navigation primarily involve orbit determination. The orbit determination process utilizes radiometric tracking data and is used for the prediction and reconstruction of MRO's trajectories. Predictions are done twice per week for ephemeris updates on-board the spacecraft and for planning purposes. Orbit Trim Maneuvers (OTM-s) are also designed using the predicted trajectory. Reconstructions, which incorporate a batch estimator, provide precise information about the spacecraft state to be synchronized with scientific measurements. These tasks were conducted regularly to validate the results obtained by the MRO Navigation Team. Additionally, the team is in the process of converting to newer versions of the navigation software and operating system. The capability to model multiple densities in the Martian atmosphere is also being implemented. However, testing outputs among these different configurations was necessary to ensure compliance to a satisfactory degree.
Deep Space Network↗
M-Star ® Software Test and Verification
Savannah River Mission Completion (SRMC) currently manages the risk for retained hydrogen in the Defense Waste Processing Facility (DWPF) vessels by implementing a Retained Hydrogen Program. The current program relies on Sludge Batch (SB) 8 Gas Chromatograph data and on conservative assumptions concerning gas release and retention to determine allowable vessel Quiescent time (Q-time). The authors identified M-Star ® CFD as a software that could simulate processes such as fluid flow, heat transfer, species transport, chemical reactions, particle transport, and retained hydrogen gas release. Preliminary simulation results suggest that more realistic assumptions on gas retention and release may be feasible for the DWPF retained hydrogen program. Because of the desire to use the M-Star ® software to perform analyses that support nuclear safety, SRMC has requested Savannah River National Laboratory (SRNL) to upgrade the software classification level of M-Star ® CFD from level D to level A to perform analyses that support nuclear safety.
08 HYDROGEN↗
Algorithmic Input Generation for More Effective Software Testing.
Abstract not provided.
Epifanovskaya, Laura↗
M-Star® Software Test and Verification for Impeller Mixing in a Tank
Before a sample of the Slurry Mix Evaporator (SME) can be taken, the SME product sampling procedure requires that the agitator power be stable between 20 and 30 kW for at least one hour. The SME transfer to Melter Feed Tank (MFT) procedure also requires the SME agitator power be stabilized between 20 and 30 kW prior to transfer. These requirements are specified to ensure samples are homogeneous, as discussed in the Waste Form Qualification Report. During SME Batch 804, the agitator power dropped to 19 kW and struggled to achieve and maintain 20 kW. It was later discovered that the cause of the power drop was due to one of the bottom blades of the agitator breaking off. Both the sample and the transfer occurred without the power stabilizing between 20 and 30 kW. Therefore, the quality of SME Batch 804 is indeterminate, and homogeneity was questionable.
12 MANAGEMENT OF RADIOACTIVE AND NON-RADIOACTIVE W↗
Algorithmic Input Generation for More Effective Software Testing.
Abstract not provided.
Epifanovskaya, Laura↗
Enhancing Confidence in a Software Ecosystem through Complementary Layers of Software Testing
Explore the source record for details and available documents.
Willenbring, James Michael↗
QUEST/Ada: Query utility environment for software testing of Ada
Results of research and development efforts are presented for Task 1, Phase 2 of a general project entitled, The Development of a Program Analysis Environment for Ada. A prototype of the QUEST/Ada system was developed to collect data to determine the effectiveness of the rule-based testing paradigm. The prototype consists of five parts: the test data generator, the parser/scanner, the test coverage analyzer, a symbolic evaluator, and a data management facility, known as the Librarian. These components are discussed at length. Also presented is an experimental design for the evaluations, an overview of the project, and a schedule for its completion.
Brown, David B.↗
QUEST/Ada (query utility environment for software testing of Ada: The development of a program analysis environment for Ada, task 1, phase 3
The results of research and development efforts of the first six months of Task 1, Phase 3 of the project are presented. The goals of Phase 3 are: (1) to further refine the rule base and complete the comparative rule base evaluation; (2) to implement and evaluate a concurrency testing prototype; (3) to convert the complete (unit-level and concurrency) testing prototype to a workstation environment; and (4) to provide a prototype development document to facilitate the transfer of research technology to a working environment. These goals were partially met and the results are summarized.
Brown, David B.↗
Automated software testing for the common operating environment
Explore the source record for details and available documents.
technical keywords automated testing↗