Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Software Requirements”

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 199 records · Page 11
All sourcesNASA NTRSDOE OSTI
DOE OSTI2025

AutoUncertainties: A Python Package for Uncertainty Propagation

Propagation of uncertainties is of great utility in the experimental sciences. While the rules of (linear) uncertainty propagation are straightforward, managing many variables with uncertainty information can quickly become complicated in large scientific software stacks. Often, this requires programmers to keep track of many variables and implement custom error propagation rules for each mathematical operator and function. The Python package AutoUncertainties, described here, provides a solution to this problem.

97 MATHEMATICS AND COMPUTING↗
DOE OSTI2020

VersaBuild: A Novel, Multi-scale, Versatile 3d Printer Concept

Our team has identified and attempted to solve a major challenge limiting the increased deployment of additive manufacturing in full-scale production environments. As engineers desire for greater flexibility of design grows, and as the diversity of properties achievable and materials usable in additive manufacturing increases, additive manufacturing becomes increasingly valuable and useful. However, the machines used to produce AM parts have largely stagnated in terms of configurability, technology, and design. We have conceptualized a system which enables a single machine to provide the functionality of multiple machines, with minimal operator changes. The gap that was identified by the team was the lack of a system that could accept user-configurable changes to the print resolution and printbed size. This would enable manufacturers flexibility in the size, quality, and quantity of parts produced in a facility of a given size. Significant floorspace savings could be achieved in a facility deploying our proposed solution due to the flexibility of the machine, lowering operational cost. Our envisioned design is similar in concept to a standard Delta robot, which is a three-armed robot that is used in many industrial applications. However, we intend for our design to have extensible delta arms that include position sensing, allowing for a greater range of motion and thus print volume while maintaining precise control over the printhead position. Some of the key risks associated with are system are caused by the novelty of the concept. Our system must undergo significant R&D and requires a fully integrated software, electrical, and mechanical system to be developed.

42 ENGINEERING↗
DOE OSTI2021

Ultra low background time projection alpha particle detector ( Phase II Final Scientific/Technical Report)

When alpha particles are emitted into a gas they create an ionization track of gas ions and electrons. In our commercial UltraLo instrument we apply a voltage between a planar sample and an anode, integrate the anode signal as it collects the electrons, and distinguish between alphas emitted from the sample and elsewhere (anode, sidewalls) by the duration and shape of the resultant signal. The major contributors limiting the instrument’s lower detection limit are cosmic rays that pass through the detector close to the sample and Rn decays that produce charge tracks the originate in the gas and end on the sample. In this work we proposed to identify and reject these events by converting the anode into a multi-pixel array and operating in time projection mode. Cosmic rays would be eliminated by generating charge on many pixels, while charge collection asymmetry would distinguish between sample events (Bragg curve up) and Rn events (Bragg curve down). We therefore proposed to modify an UltraLo by pixilating its anode, developing low noise, low power multiplexed electronics to track each pixel’s signal individually, and develop analysis software to make the required discriminations.

46 INSTRUMENTATION RELATED TO NUCLEAR SCIENCE AND ↗
DOE OSTI2023

Basic Research Needs in The Science of Scientific Software Development and Use: Investment in Software is Investment in Science

Increasingly powerful and affordable computing has revolutionized scientific and scholarly discovery across a broad range of fields. Computing relies on software, which has been rapidly growing in scope, diversity, and complexity. At the same time, the methods, processes, and tools used to produce and utilize this essential software are often ad hoc, and the study and improvement of them are often done without the benefit of direct funding or prioritization. Consequently, concerns are growing about the productivity of the developers and users of scientific software, its sustainability, and the trustworthiness of the results that it produces. Increased investment, especially in the characterization and improvement of how scientific software is developed and used, is important for sustaining and improving the impact of software as the scope and complexity of scientific efforts expand. Without this investment, we face the risk of diminishing returns on our software investments because the demands for increased functionality, usability, reliability, and more will not be sufficiently met. The US Department of Energy Office of Science (DOE/SC) is at the forefront of modern software-enabled scientific discovery across numerous areas of computational, experimental, and observational science, including major investments in national user facilities that support these activities. For many years, DOE/SC software investments have provided tremendous value to the scientific community. We want to continue and further improve the value of DOE/SC software efforts by using a scientific approach to understanding and improving how scientific software is developed and used. In December 2021, the DOE/SC Office of Advanced Scientific Computing Research (ASCR) convened a workshop on basic research needs for the Science of Scientific-Software Development and Use (SSSDU). Through keynote presentations, lightning talks, and breakout groups, which built on insights from 124 pre-workshop position papers, participants discussed the current practice of software development, maintenance, evolution, and use, and considered how the scientific method could be used to examine these practices and develop more evidence-based approaches to enhance the impact of software and computing on all areas of science. Workshop participants identified three priority research directions (PRDs) and three important crosscutting themes that center on the following overarching insight: Software has become an essential part of modern science, impacting discoveries, policy, and technological development. To maintain and improve confidence in science delivered via software, we must improve the processes and tools that help us create and use software, and this enhancement requires a deep understanding of the diverse array of teams and individuals doing the work.

97 MATHEMATICS AND COMPUTING↗
DOE OSTI2020

Validation of SAS4A/SASSYS-1 for Steady-State Single-Phase Natural Circulation

The development of numerical software for engineering applications requires the validation of the code against experimental benchmark datasets. To support the validation of SAS4A/SASSYS-1 in simulating the single-phase natural circulation within nuclear reactor systems, high-precision steady-state experiments are performed to capture single-phase natural circulation phenomena on an existing scaled facility with comprehensive instrumentation. Forced convection tests are designed precisely capturing the facility’s critical thermal-hydraulic parameters required for one-dimensional modeling, and a comprehensive single-phase natural circulation dataset is obtained with well-documented experimental uncertainty and facility description. Analysis and discussion based on the finalized dataset confirm the dataset’s ability in capturing dominant phenomena and address important physical interpretation of parameters. The dataset reported in this project provides a valuable benchmark resource for the validation of system analysis codes under single-phase natural circulation inside nuclear reactors. Validation of SAS4A/SASSYS-1 is then performed against the obtained benchmark dataset to confirm the capability of its physics model in simulating the steady-state single-phase natural circulation. The experimental facility is modeled in the candidate code. Solution verification is performed using Richardson-extrapolation-based estimators to quantify and restrict numerical errors from discretization. Numerical uncertainty originating from finite maximum pseudo-transient time is also quantified and restricted. Input uncertainty provided by the benchmark dataset is forward propagated through the candidate code, directly quantifying the simulation output in a Monte Carlo approach. The composition of the output uncertainty is further determined by the estimators of Sobol’ indices through a variance-based sensitivity analysis. With uncertainty quantified for each individual condition, detailed comparison between the simulation results and experimental data is performed covering the whole dataset, which shows consistent agreement for all important quantities. The validation activity reported in this project demonstrates that SAS4A/SASSYS-1 can predict the primary parameters with satisfactorily accuracy under steady-state single-phase natural circulation.

22 GENERAL STUDIES OF NUCLEAR REACTORS↗
DOE OSTI2021

Improving the Cyber and Physical Security Posture of the Electric Sector (Final Report)

Cooperative electric utilities represent an integral part of the larger electric grid and are part of the nation’s critical infrastructure. The National Rural Electric Cooperative Association (NRECA) has a unique relationship with approximately 900 cooperatively owned and operated electric utilities and engaged in a program with the Department of Energy (DOE) to promote a culture of cybersecurity and resiliency within the electric cooperative community. The Rural Cooperative Cybersecurity Capabilities (RC3) Program, funded under a Cooperative Agreement with DOE (Project DE-OE-0000807), focused on improving the cybersecurity and resiliency capabilities of small and mid-sized electric distribution cooperatives. This segment of electric utilities faces many challenges, but also embraces a culture of cooperation that presents opportunities. A customized approach is needed to reach these utilities – one that emphasizes collaboration, more focused and personalized training, use of trusted and familiar experts that can be deployed as needed, software security services that require limited in-house cybersecurity expertise, and shared resource models that enable access to more expensive cybersecurity options.

24 POWER TRANSMISSION AND DISTRIBUTION↗
DOE OSTI2023

SAS4A/SASSYS-1 Verification Testing for Sodium Fast Reactor Applications: Acceptance Testing Report

SAS4A/SASSYS-1 (SAS) is a simulation tool used to perform deterministic analyses of anticipated events as well as design basis and beyond design basis accidents for advanced liquid-metal-cooled nuclear reactors. With its origin as SAS1A in the late 1960s, the SAS series of codes has been under continuous use and development for over forty-five years and represents a critical investment in safety analysis capabilities for the U.S. Department of Energy. To support demonstration of software pedigree and confirm key functional requirements, this report has been generated to provide detailed verification of the software. Although SAS was developed to support the analysis of any liquid-metal-cooled nuclear reactor, the acceptance testing described in this document focuses on the verification of SAS capabilities as they relate to pool-type Sodium Fast Reactors (SFRs). This report includes documentation of the test problem definition, analytical solution(s), computational solution(s), acceptance criteria, comparisons of analytical/computational solutions, and determination of acceptance of the computational solution(s). Deviations from acceptance criteria are noted.

21 SPECIFIC NUCLEAR REACTORS AND ASSOCIATED PLANTS↗
DOE OSTI2024

SAS4A/SASSYS-1 Verification Testing for Sodium Fast Reactor Applications (Acceptance Testing Report)

SAS4A/SASSYS-1 (SAS) is a simulation tool used to perform deterministic analyses of anticipated events as well as design basis and beyond design basis accidents for advanced liquid-metal- cooled nuclear reactors. With its origin as SAS1A in the late 1960s, the SAS series of codes has been under continuous use and development for over fifty years and represents a critical investment in safety analysis capabilities for the U.S. Department of Energy. To support demonstration of software pedigree and confirm key functional requirements, this report has been generated to provide detailed verification of the software. Although SAS was developed to support the analysis of any liquid-metal-cooled nuclear reactor, the acceptance testing described in this document focuses on the verification of SAS capabilities as they relate to pool-type Sodium Fast Reactors (SFRs). This report includes documentation of the test problem definition, analytical solution(s), computational solution(s), acceptance criteria, comparisons of analytical/computational solutions, and determination of acceptance of the computational solution(s). Deviations from acceptance criteria are noted.

22 GENERAL STUDIES OF NUCLEAR REACTORS↗
DOE OSTI2023

Using Eye-Tracking to Quantify Reverse Engineering Expertise

Software reverse engineering (RE) requires analysts to closely read and make decisions about code. Little is known about what makes an analyst successful, making it difficult to train new analysts or design tools to augment existing ones. The goal of this project was to quantify the eye movement behaviors supporting RE and code comprehension more generally. We applied eye-tracking methods from the language comprehension literature to understand where analysts direct their attention over time when completing tasks (e.g., function identification, bug detection). Across three studies, we manipulated aspects of code hypothesized to impact comprehension (e.g., variable name meaningfulness, code complexity) and presentation methods (e.g., line-by-line, free viewing, gaze-contingent moving window) to understand effects on accuracy and gaze patterns. Results showed clear benefits of meaningful variable names, and effects of expertise on global and line-specific viewing patterns. Findings could inspire empirically-supported tool or analytic adaptations that help to reduce analyst workload.

97 MATHEMATICS AND COMPUTING↗
DOE OSTI2022

Cascaded Control for Building HVAC Systems in Practice

Actuator hunting is a widespread and often neglected problem in the HVAC field. Hunting is typically characterized by sustained or intermittent oscillations, and can result in decreased efficiency, increased actuator wear, and poor setpoint tracking. Cascaded control loops have been shown to effectively linearize system dynamics and reduce the prevalence of hunting. This paper details the implementation of cascaded control architectures for Air Handling Unit chilled water valves at three university campus buildings. A framework for implementation the control in existing Building Automation software is developed that requires only a single line of additional code. Results gathered for more than a year show that cascaded control not only eliminates hunting in control loops with documented hunting issues, but provides better tracking and more consistent performance during all seasons. A discussion of efficiency losses due to hunting behavior is presented and illustrated with comparative data. Furthermore, an analysis of cost savings from implementing cascaded chilled water valve control is presented. Field tests show 2.2–4.4% energy savings, with additional potential savings from reduced operational costs (i.e., maintenance and controller retuning).

32 ENERGY CONSERVATION, CONSUMPTION, AND UTILIZATI↗
DOE OSTI2020

The CMIP6 Data Request (DREQ, version 01.00.31)

The data request of the Coupled Model Intercomparison Project Phase 6 (CMIP6) defines all the quantities from CMIP6 simulations that should be archived. This includes both quantities of general interest needed from most of the CMIP6-endorsed model intercomparison projects (MIPs) and quantities that are more specialized and only of interest to a single endorsed MIP.The complexity of the data request has increased from the early days of model intercomparisons, as has the data volume.In contrast with CMIP5, CMIP6 requires distinct sets of highly tailored variables to be saved from each of the more than 200 experiments.This places new demands on the data request information base and leads to a new requirement for development of software that facilitates automated interrogation of the request and retrieval of its technical specifications.The building blocks and structure of the CMIP6 Data Request (DREQ), which have been constructed to meet these challenges, are described in this paper.

54 ENVIRONMENTAL SCIENCES↗
DOE OSTI2021

Aquifer Injection Modeling (AIM) Toolbox User Guide

The Aquifer Injection Modeling Toolbox (“AIM Toolbox”) software was developed by the Pacific Northwest National Laboratory (PNNL) for the U.S. Environmental Protection Agency’s (EPA) to provide a collection of analytical solutions suitable for evaluating the potential extent of the area impacted by subsurface injection operations. Subsurface injection operations are regulated under the EPA’s Underground Injection Control (UIC) program and are typically related to oil/gas development, waste disposal, or subsurface mining or storage. The analytical algorithms provided in the AIM Toolbox each have different approaches/assumptions/focus with respect to the nature and processes in subsurface and the nature of the injection operations. Collectively the set of analysis algorithms provides a broader evaluation of the area that can potentially be impacted by an injection operation. By providing estimates for the injectate plume extent, the software supports technical aspects of planning, evaluation, and overseeing injection activities. That is, the results help assess when further regulatory controls (e.g., monitoring, reporting) may be required and, in the case of disposal into an underground source of drinking water, the extent of the impacted area would require exemption from protection under the Safe Drinking Water Act. The AIM Toolbox software is available as a single-page web application, providing an interface to provide the necessary inputs, and both chart and map panes for visualizing the results. This User Guide describes the AIM Toolbox software, information required, user interactions, and the underlying basis of the calculations.

54 ENVIRONMENTAL SCIENCES↗
DOE OSTI2023

Aquifer Injection Modeling (AIM) Toolbox User Guide

The Aquifer Injection Modeling Toolbox (“AIM Toolbox”) software was developed by the Pacific Northwest National Laboratory (PNNL) for the U.S. Environmental Protection Agency’s (EPA) to provide a collection of analytical solutions suitable for evaluating the potential extent of the area impacted by subsurface injection operations. Subsurface injection operations are regulated under the EPA’s Underground Injection Control (UIC) program and are typically related to oil/gas development, waste disposal, or subsurface mining or storage. The analytical algorithms provided in the AIM Toolbox each have different approaches/assumptions/focus with respect to the nature and processes in subsurface and the nature of the injection operations. Collectively the set of analysis algorithms provides a broader evaluation of the area that can potentially be impacted by an injection operation. By providing estimates for the injectate plume extent, the software supports technical aspects of planning, evaluation, and overseeing injection activities. That is, the results help assess when further regulatory controls (e.g., monitoring, reporting) may be required and, in the case of disposal into an underground source of drinking water, the extent of the impacted area would require exemption from protection under the Safe Drinking Water Act. The AIM Toolbox software is available as a single-page web application, providing an interface to provide the necessary inputs, and both chart and map panes for visualizing the results. This User Guide describes the AIM Toolbox software, information required, user interactions, and the underlying basis of the calculations.

58 GEOSCIENCES↗
DOE OSTI2024

Composable optimization and control toolkit for scientific applications

Applications of Artificial Intelligence (AI) and Machine Learning (ML) can improve the computational efficiency and scientific research output. In order to improve interoperability and reuse of AI/ML software, a composable approach is required. This talk presents a composable approach for scientific workflow development that allows seamless integration of various modules developed by independent researchers. These practices will reduce redundant software development by allowing re-use of workflow modules across projects, teams, departments and facilities. We will present three use cases that follow the composable approach namely, Scientific Optimization and Control Toolkit (SOCT), SciDAC QuantOm workflow, and JLab Nuclear Physics experimental workflows. This talk will dive deeper into SOCT and present the details of the composable code development for optimization and control algorithms using reinforcement learning.

Rajput, Kishansingh↗
DOE OSTI2025

Fiscal Year 2025 Software Quality Assurance Activities for the ARC Software

The continued goal of the ARC SQA project in the Advanced Reactor Technologies program of DOE is to resolve the QA gaps for the ARC software that limit, or prevent, commercialization of the software for industry users. This project started in earnest in fiscal year 2023 which saw the entire code system moved from a SVN repository to a GitLab repository and an associated software quality assurance plan (SQAP) developed and ratified. Most of the QA gaps in the ARC software were identified in collaboration with industry partners and work begin in fiscal year 2023 and continued through 2024 and 2025. The continuous integration testing was extended to RCT, DASSH, and SE2ANL. Minor changes were required to the original continuous integration methodology to make this happen. When full confidence in the methodology is complete, a report will be created to detail the automated regression testing methodology and minor reports will be created to detail the tolerance settings that have been applied to the output for each ARC code. The primary documentation that is missing includes user manuals, user guides, software verification reports, and code coverage assessments. The DASSH, SE2ANL, and SE2RCT manuals were completed this fiscal year. A review of the SE2ANL software identified that it is unrealistic to include updated correlations or different geometry models and it was scheduled for deprecation in favor of DASSH. The SE2ANL manual is essential for SE2RCT as they are similar but quite different in purpose. The only piece of software missing a manual consistent with the source code is NUBOW-3D which is a focus of the coming year. The code coverage report for DIF3D was updated and code coverage reports were created for REBUS, RCT, PERSENT, GAMSRC, and DASSH. Minor coverage issues were identified for all of these pieces of software which did not prevent the work done to transition them to the OneAPI compiler. Because SE2ANL was scheduled for deprecation, it was not transitioned, but it was successfully tested with the OneAPI compiler. This leaves SE2RCT and NUBOW-3D as the only pieces of software not transitioned to OneAPI and further work is required to get SE2RCT to work properly. The SE2RCT software transition will begin early next year while the NUBOW-3D software requires a manual before it can begin. Software verification work has been completed for DIF3D, REBUS, GAMSOR, GAMSRC, VARPOW, EvaluateFlux, and SUMMAR. The PERSENT software verification work was completed this year which was somewhat delayed because of unexpected bugs in the software. The PERSENT manual was updated to detail some of the issues and discuss the bowing reactivity worth feature added in the previous fiscal year. The RCT, DASSH, SE2RCT, and NUBOW-3D software are the only maintained pieces of software without verification reports. The software verification work for DASSH will be a focus in the upcoming fiscal year and it is hoped that some of the test cases created can serve as verification tests for SE2RCT. The NUBOW-3D work will begin when the manual and requirements report are completed. Only minor industry partner software development funds were provided this year. The DASSH software was updated to handle general axial geometry for each assembly and the NUBOW-3D software was updated to incorporate a new input format and better output. Overall progress on resolving the QA gaps has been good this year.

22 GENERAL STUDIES OF NUCLEAR REACTORS↗
DOE OSTI2025

Fiscal Year 2025 Software Quality Assurance Activities for the ARC Software

The continued goal of the ARC SQA project in the Advanced Reactor Technologies program of DOE is to resolve the QA gaps for the ARC software that limit, or prevent, commercialization of the software for industry users. This project started in earnest in fiscal year 2023 which saw the entire code system moved from a SVN repository to a GitLab repository and an associated software quality assurance plan (SQAP) developed and ratified. Most of the QA gaps in the ARC software were identified in collaboration with industry partners and work begin in fiscal year 2023 and continued through 2024 and 2025. The continuous integration testing was extended to RCT, DASSH, and SE2ANL. Minor changes were required to the original continuous integration methodology to make this happen. When full confidence in the methodology is complete, a report will be created to detail the automated regression testing methodology and minor reports will be created to detail the tolerance settings that have been applied to the output for each ARC code. The primary documentation that is missing includes user manuals, user guides, software verification reports, and code coverage assessments. The DASSH, SE2ANL, and SE2RCT manuals were completed this fiscal year. A review of the SE2ANL software identified that it is unrealistic to include updated correlations or different geometry models and it was scheduled for deprecation in favor of DASSH. The SE2ANL manual is essential for SE2RCT as they are similar but quite different in purpose. The only piece of software missing a manual consistent with the source code is NUBOW-3D which is a focus of the coming year. The code coverage report for DIF3D was updated and code coverage reports were created for REBUS, RCT, PERSENT, GAMSRC, and DASSH. Minor coverage issues were identified for all of these pieces of software which did not prevent the work done to transition them to the OneAPI compiler. Because SE2ANL was scheduled for deprecation, it was not transitioned, but it was successfully tested with the OneAPI compiler. This leaves SE2RCT and NUBOW-3D as the only pieces of software not transitioned to OneAPI and further work is required to get SE2RCT to work properly. The SE2RCT software transition will begin early next year while the NUBOW-3D software requires a manual before it can begin. Software verification work has been completed for DIF3D, REBUS, GAMSOR, GAMSRC, VARPOW, EvaluateFlux, and SUMMAR. The PERSENT software verification work was completed this year which was somewhat delayed because of unexpected bugs in the software. The PERSENT manual was updated to detail some of the issues and discuss the bowing reactivity worth feature added in the previous fiscal year. The RCT, DASSH, SE2RCT, and NUBOW-3D software are the only maintained pieces of software without verification reports. The software verification work for DASSH will be a focus in the upcoming fiscal year and it is hoped that some of the test cases created can serve as verification tests for SE2RCT. The NUBOW-3D work will begin when the manual and requirements report are completed. Only minor industry partner software development funds were provided this year. The DASSH software was updated to handle general axial geometry for each assembly and the NUBOW-3D software was updated to incorporate a new input format and better output. Overall progress on resolving the QA gaps has been good this year.

97 MATHEMATICS AND COMPUTING↗
DOE OSTI2021

Software Quality Assurance for EBR-II Fuels Irradiation and Physics Database (FIPD)

The Fuels Irradiation and Physics Database (FIPD) is an ongoing DOE project on archival of the EBR-II metal-alloy fuel irradiation experiments. As part of its use in support of license applications, the Quality Assurance Program Plan (QAPP) was drafted and endorsed by NRC in an effort to demonstrate its compliance with regulatory expectations. Software Quality Assurance (SQA) for the physics portion of FIPD is intended to qualify the calculated quantities such as fuel and cladding temperatures, neutron fluence and axially varying burnup estimates for irradiated fuel elements. This report covers the initial evaluation of SQA status of three neutron physics and thermo-fluid codes (REBUS, RCT and SE2RCT) that form the basis of calculated quantities for as-irradiated characteristics of the tested metallic fuel elements. The report also introduces an SQA plan to address the identified deficiencies. The REBUS, RCT, and SE2RCT codes are all part of the Argonne Reactor Code (ARC) code system. There is considerable knowledge and experience on REBUS and RCT but relatively less on SE2RCT. During FY2021, efforts focused on an assessment of how the data in the EBR-II Physics and Analysis DataBase (PADB) is generated with SE2RCT and used in FIPD. Additional tasks included considerations of uncertainties for power estimates in REBUS and RCT calculations and their impact on the combined RCT methodology. The RCT software usage in FIPD was assessed this year and the input/output details studied. A “requirements” document was created that identifies the key features of the RCT software being used in FIPD that need to have SQA documentation. A brief discussion on the history of RCT and its input is included in this report along with the basic SQA roadmap laid out in the requirements document. The SE2RCT software usage in FIPD is still being studied noting that there is no current manual. As part of the work done this year, two bugs were identified in the SE2RCT software which have a minor impact on the accuracy of the results it produces. No requirements document has been created, but one identified feature of SE2RCT being used that needs verification was its fuel pin temperature calculation. The work completed this year confirms that the approximations which will be included in the software verification report for SE2RCT are accurate. In addition to software quality assurance work for RCT and SE2RCT, an automated verification framework is proposed to simplify the software quality assurance process. The purpose of this framework is to streamline code verification and documentation while minimizing repetitive tasks for code developers and reviewers. The reduction of repeated input (between reference solution, software, and documentation input) throughout the SQA process reduces potential for human errors during the preparation of the supporting software quality records. The automation of the verification and documentation process proposed for this project leverages the existing verification structure already in place for the SAS4A/SASSYS-1 code.

11 NUCLEAR FUEL CYCLE AND FUEL MATERIALS↗
DOE OSTI2022

A Framework for Error-Bounded Approximate Computing, with an Application to Dot Products

Approximate computing techniques, which trade off the computation accuracy of an algorithm for better performance and energy efficiency, have been successful in reducing computation and power costs in several domains. However, error sensitive applications in high-performance computing are unable to benefit from existing approximate computing strategies that are not developed with guaranteed error bounds. While approximate computing techniques can be developed for individual high-performance computing applications by domain specialists, this often requires additional theoretical analysis and potentially extensive software modification. Hence, the development of low-level error-bounded approximate computing strategies that can be introduced into any high-performance computing application without requiring additional analysis or significant software alterations is desirable. In this paper, we provide a contribution in this direction by proposing a general framework for designing error-bounded approximate computing strategies and apply it to the dot product kernel to develop \bf qdot---an error-bounded approximate dot product kernel. Following the introduction of qdot, here we perform a theoretical analysis that yields a deterministic bound on the relative approximation error introduced by qdot. Empirical tests are performed to illustrate the tightness of the derived error bound and to demonstrate the effectiveness of qdot on a synthetic dataset, as well as two scientific benchmarks---the conjugate gradient (CG) and power methods. In some instances, using qdot for the dot products in CG can result in many components being quantized to half precision without increasing the iteration count required for convergence to the same solution as CG using a double precision dot product.

97 MATHEMATICS AND COMPUTING↗