Search NASA⌕ Search

SEARCH · Search NASA

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.

At least 55 records · Page 3

Acquisition and Implementation of a Comprehensive Environmental Permits Linking Tool at Savannah River Site - 20234

Historically, Savannah River Nuclear Solutions LLC (SRNS) tracked environmental regulatory commitments and the requirements from hundreds of permits at the Savannah River Site (SRS) using several separate methods, making integrated compliance assurance cumbersome and labor-intensive. When SRNS experienced an increase in environmental issues in 2017, SRNS management and U.S. Department of Energy - Savannah River (DOE-SR) management decided a single, proactive approach was needed to capture environmental permit information (including regulations, Consent Orders, DOE Orders, and any other state or federally issued statement of requirements), track the tasks necessary to ensure compliance with these requirements, and thereby mitigate the risk of noncompliance. SRNS developed a list of mandatory objectives that the tool must meet to function as a Comprehensive Environmental Permits Linking Tool (CEPLT). A key requirement was the ability to map Site permits to their governed locations and display the associated requirements at the compliance point (e.g., outfall, stack, waste unit, etc.). Several options included modifying existing onsite resources, building a custom onsite solution, purchasing an off-the-shelf solution, and contracting an offsite developer to build a custom solution. SRNS concluded an off-the-shelf solution with configuration and customization options would provide the flexibility to fit the unique needs of Savannah River Site (SRS) while taking advantage of industry-tested software and providing a reduced deployment timeline. SRNS chose Gensuite{sup R} a, a cloud-based solution that offers numerous a la carte applications in the environmental, health, and safety arenas, as the best candidate. SRNS selected three (3) integrated applications (Compliance Calendar, Permit Manager, and Mapper) to function as the CEPLT. The Compliance Calendar module allows for creation and tracking of regulatory commitment tasks assigned to responsible environmental professionals. Permit Manager organizes permits and other requirement documents, linking the commitments in each to Compliance Calendar tasks and/or implementing procedures. Mapper provides GIS capability for mapping the data from the other two modules to their physical onsite locations. The CEPLT was configured to allow for other SRS Site Tenants to eventually utilize the applications. Additionally, DOE-SR uses the CEPLT to provide an overview of contractor environmental compliance activities and to organize DOE-specific documents and tasks. The CEPLT fulfilled the requirement of meeting current compliance needs as well as providing the ability to grow as new organizations are incorporated and functionality is expanded. SRNS now uses the CEPLT to more effectively manage permit requirements, improve knowledge transfer, and increase the Site's overall protection of the environment, the Site worker, and the public. Possible future uses of the system include integration of mobile applications for timely communication of potential non-compliant conditions and DOE complex-wide deployment allowing for enhanced DOE site and Head Quarters oversight. Implementation of CEPLT will result in cost savings, both in terms of dollars and man-hours. (authors)

12 MANAGEMENT OF RADIOACTIVE AND NON-RADIOACTIVE W↗

Methodology for Building Granular Testing in Multicomponent Scientific Software

Computational science and engineering communities develop complex application software with multiple mathematical models that need to interact with one another. Partly due to complexity of verifying scientific software, and partly because of the way incentives work in science, there has been insufficient testing of these codes. With a spotlight on the results produced with scientific software, and increasing awareness of software testing and verification as a critical contributor to the reliability of these results, testing is gaining more attention by the developing teams. However, many science teams struggle to find a good solution for themselves due either to lack of training or lack of resources within the team. In this experience paper, we describe test development methodologies utilized in two different scenarios: one explains a methodology for building granular tests where none existed before, while the second demonstrates a methodology for selecting test cases that build confidence in the software through a process similar to scaffolding. The common insight from both the experiences is that testing should be a part of software design from the beginning for better software and scientific productivity.

test building, granular testing, Earth system mode↗

Implementation of Plot File Testing in the DYNA3D/ParaDyn Software Quality Assurance Suite

Automated testing of DYNA3D/ParaDyn plot files was added to the DYNA3D/ParaDyn software quality assurance (SQA) test suite. The new capability extracts select data from the plot files generated during each verification run and compares it to the same baseline answers used to verify the problem. Deviations between baseline answers and plot file values are reported in the same manner as solution discrepancies, and differences in precision levels between the baseline answers and plot file results are accounted for. The new testing leverages the existing SQA test suite framework and test problems and the Python Mili reader and minimally increases the overall run time (< 5%) of the SQA test suite. This new capability provides incremental end-toend testing of the most common DYNA3D/ParaDyn simulation workflows.

42 ENGINEERING↗

Virtual Framework for Development and Testing of Federation Software Stack

Softwarization of networked infrastructures combined with containerization of codes promises unprecedented computing capabilities distributed across the federations of computing systems and physical instruments. The development and testing of a software stack that implements these capabilities over an expensive physical production infrastructure is not cost-effective, and in the early stages, may potentially cause service disruptions. To address these aspects, we develop the Virtual Federated Science Instrument Environment (VFSIE), a digital twin of the physical infrastructure that emulates a multi-site federation. Each federated site is emulated using containers and virtual hosts that are connected over local-area networks, and the sites, in turn, are connected over an emulated wide-area network. We describe the framework design and implementation details. We also illustrate its application by emulating a federation of four laboratories that use Jupyter Notebook for computations and the EPICS software system for instrument control.

Al Najjar, Anees↗

Exploring Sustainability in Scientific Software through Code Quality & Test Coverage Metrics

Context: Scientific open-source software (SciOSS) plays a foundational role in research and engineering, yet its long-term sustainability has often been overlooked and remains a significant concern. Objective: This study investigates the long-term sustainability of SciOSS through code and test quality metrics. Method: We analyze CASS Software Portfolio projects, classifying them by sustainability and comparing their code structure, test coverage, and links between code quality and testing across the dataset. Results: Sustainable projects show higher, more consistent test coverage and clearer code-test correlations, while unsustainable ones show weaker patterns. Overall, test coverage is low in scientific software, and high complexity and coupling reduce testability. Conclusion: In this study, we present a practical, data-driven approach for assessing sustainability in scientific software, offering a foundation for evaluating long-term software health and supporting future efforts in quality assurance and sustainability monitoring.

Md mushfiqur rahman, Sheikh [University of Tenness↗

SAS4A/SASSYS-1 Verification and Validation Plan for the Versatile Test Reactor

Software verification and validation (V&V) hold an important role in the safety analysis for nuclear facilities. Codes and models utilized in calculations that demonstrate the safety basis as part of a license application or authorization must demonstrate an acceptable pedigree with regard to key critical characteristics that are comprised of the functional and performance requirements of the software. This document describes the methodology for verification and validation of the SAS4A/SASSYS-1 systems-level liquid-metal safety analysis software in support of DOE authorization of the Versatile Test Reactor (VTR). The overall goal of this V&V effort is to demonstrate the suitability of SAS4A/SASSYS-1 for evaluation of safety performance and characterization of safety margins in VTR. To that end, the V&V methodology will be used to demonstrate the adequacy of the component and physical models of SAS4A/SASSYS-1 for the corresponding VTR design elements. This methodology, which has been derived as a generalized approach to the U.S. NRC’s evaluation model development and assessment process (EMDAP) of Regulatory Guide 1.203, entails four high-level activities: software requirements identification, assessment base development, determination of acceptance, and gap closure. The methodology has been generalized to be suitable for both verification and validation of the software for the VTR project. Several high-level engineering analysis quality assurance measures as well as supporting V&V methodology documentation are also described in this document to help support demonstration of software acceptance. To support initial development of the SAS4A/SASSYS-1 V&V basis, existing verification test problems and systems benchmarks are also identified and briefly described in this document.

21 SPECIFIC NUCLEAR REACTORS AND ASSOCIATED PLANTS↗

Monitoring Helium Cryogen Usage with iFix Software at IB1 Test Facility

At the IB1 facility of the Applied Physics and Superconducting Technology Directorate within the Cryogenic Division at Fermilab, liquid helium is essential to the testing activities. The test stands used require large amounts of Helium to test the thermal and superconducting cavities and magnets. The liquid helium that enters the test stand is monitored through a series of valves and controls to determine the start and stop for monitoring time. There are 3 phases of cryogen usage that must be considered for each stand, cooldown, warming and overnight mode. With a new system in place, cold hour tracking will be more objective and precise within each test stand ensuring better calculations for user s fees that will provide funding for the replenishment of helium and continual operation at IB1.

Trillo, Angelica↗

Monitoring Helium Cryogen Usage with iFix Software at IB1 Test Facility

At the IB1 facility of the Applied Physics and Superconducting Technology Directorate within the Cryogenic Division at Fermilab, Liquid Helium is essential to the testing activities. The test stands require large amounts of Helium to test the thermal and superconducting cavities and magnets. The Liquid Helium that enters the test stand is monitored through a series of valves and controls to determine the start and stop for monitoring time. There are 3 phases of cryogen usage that must be considered for each stand, cooldown, warming and overnight mode. With a new system in place, cold hour tracking will be more objective and precise within each test stand ensuring better calculations for User s fees which are charged to various groups that employ the facility and aid replenishment of Helium and continual operation at IB1.

Trillo, Angelica↗

Software for Tool Design and Testing

Abstract—: The development of software for calculating the cutting parameters in the course of machining or in simulations is discussed. The software developed may be used to create and test new cutting tools.

42 ENGINEERING↗

IBPSA Project 2 BOPTEST: An update on the test cases available in the framework for testing advanced control strategies in buildings

Project 2 develops software infrastructure, test cases, and extensions for the Building Optimization Testing Framework (BOPTEST) to address the expanding needs of building and urban energy system controls through open international collaboration. This paper provides an overview of the new test cases available as of BOPTEST version 0.7.1. Each test case is developed using open-source Modelica libraries and Spawn of EnergyPlus, enabling the creation of high-fidelity building models that incorporate envelope dynamics, Heating Ventilation and Air Conditioning (HVAC) systems, and explicit control representations. Currently, eight test cases are available, with five additional cases under development. These test cases cover a wide range of climates, building types, and HVAC systems. This paper compiles and summarizes test case descriptions, cites original manuscripts that developed them for a more detailed description, and reports baseline control performance metrics. Furthermore, two example applications are presented: one illustrating different levels of control, from supervisory to low-level, and another demonstrating how Model Predictive Control (MPC) solutions must be adapted from continuous to integer to control some building actuators.

Zanetti, Ettore↗

Single-Bar SMT Testing on Alloy 617 using Software Controls

INL has performed simplified model testing using a variable in the software control program to compare with the testing performed at ORNL, which uses hardware to modify the control signal. The INL tests compared well with the ORNL tests, showing similar stress and strain values, as well as similarly shaped hysteresis loops. This demonstrates that possibility of performing simplified model testing without any hardware modifications.

36 MATERIALS SCIENCE↗

Named Data Networking for DER Cybersecurity

We present our research findings on the novel NDN protocol. In this work, we defined key attack scenarios for possible exploitation and detail software security testing procedures to evaluate the security of the NDN software. This work was done in the context of distributed energy resources (DER). The software security testing included an execution of unit tests and static code analyses to better understand the software rigor and the security that has been implemented. The results from the penetration testing are presented. Recommendations are discussed to provide additional defense for secure end-to-end NDN communications.

97 MATHEMATICS AND COMPUTING↗

ComPort: Rigorous Testing Methods to Safeguard Software Porting (Final UW Report)

This report summarizes the University of Washington’s contributions to the ComPort project, Rigorous Testing Methods to Safeguard Software Porting, funded under the U.S. Department of Energy, Office of Science, Office of Advanced Scientific Computing Research (ASCR), award number DE-SC0022081. UW’s work addressed numerics-driven correctness challenges arising in heterogeneous and rapidly evolving computing environments. Our efforts focused on developing interactive analysis tools, correctness-preserving rewriting systems, semantic-aware code-transformation infrastructure, and multi-language support for reproducible numerical experiments.

97 MATHEMATICS AND COMPUTING↗

Method of Test for Evaluating Building Performance Simulation Software

ANSI/ASHRAE Standard 140 Method of Test for Evaluating Building Performance Simulation Software specifies the method to test the core competency of building performance simulation (BPS) software, a broad class of software which includes building energy modeling (BEM) software. Standard 140 has been widely used by BEM software vendors to help diagnose and compare the results from the program with other modeling programs. The Standard is also referenced by codes, standards, government programs, and other incentive programs as a part of minimum requirements for qualifying BEM software. The explanatory information, summary tables and figures in this 140 User’s Manual (referred to as “this Manual”) are provided to help users in implementing various suites of tests specified in Standard 140-2023 (referred to in this manual as “Standard 140” or “the Standard”).

97 MATHEMATICS AND COMPUTING↗