Search NASA⌕ Search

SEARCH · Search NASA

Results for “program verification”

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

Electronics Upgrades to the Green is Clean Phoswich Detector Systems and Programmatic Implementation at LANL - Phase II Completion - 18403

Los Alamos National Laboratory (LANL) radiological facilities produce low-density room trash that, in many cases, is not contaminated with radioactivity. It has been estimated that 50 to 90% of low-density room trash is free of radioactive contamination and eligible for inclusion in LANL's Green is Clean (GIC) program. The GIC program is a verification program for non-regulated waste from radiation controlled areas that has been actively segregated as nonradioactive through the use of the waste generator's acceptable knowledge. The GIC program has employed two large area Phoswich gamma ray detector systems (HERCULES and ZEUS) to verify that GIC candidate low-density waste contains no radioactivity above background. The large area (127 cm{sup 2}) Phoswich detectors consist of a thin NaI front crystal (3 mm thick) that is optically coupled to a thick CsI back crystal (50 mm thick). The scintillation properties of the two crystals are different enough to allow the system's electronic components to identify the origin of any pulse. The original systems utilize Nuclear Instrumentation Module (NIM) electronics to process the detector signals. The electronics currently in use by the systems are out of date and some components are no longer manufactured. In 2015, phase I upgrades to the GIC detector systems were completed. Phase I objectives included identifying more modern commercially available electronics that could replace the NIM electronics. A pulse shape discriminator (PSD) module, the Digital Gamma Finder (DGF) Pixie-4 made by XIA LLC, that fits in a compact National Instruments{sup TM} PXI chassis was identified to replace the majority of the original NIM bin electronics - a single Pixie-4 module replaces four NIM amplifiers and four NIM pulse shape analyzers (PSAs). Another phase I objective was to show that that new PSD could separate out the NaI and CsI detector signals in a manner equivalent to or better than the NIM electronics. Proof of concept was achieved in 2015 when a prototype upgrade system on ZEUS was built and tested and gating parameter settings were determined that successfully separated the NaI and CsI signals. Phase II required establishing a LabVIEW software interface with Pixie-4 electronics in lieu of the manufacturer provided Pixie-4 software called the Pixie Viewer. In addition, phase II included 1) final optimization of the gating parameters on the prototype Pixie-4 ZEUS system, 2) finalizing Requirements, Design and Test Plan documents, 3) LabVIEW software interface quality assurance (QA) testing, 4) setting up the HERCULES system with the Pixie-4 upgrade electronics, 5) check source and background calibration of both systems, 6) absolute efficiency determination on both systems and 7) procedure revisions and implementation of both systems into routine operations. In 2017 phase II was completed including the preparation of detailed Requirements, Design and Test Plan documents. The LabVIEW interface software that communicates and controls the Pixie-4 has been completed, merged with the preexisting LabVIEW operations software and fully tested. Gating parameter optimization, configuration of HERCULES with the Pixie-4 electronics, check source and background calibrations and absolute efficiency determinations have all been performed - quantitative results are presented in the full paper. For performance validation, comparison measurements of actual GIC bags on both the HERCULES system using the old NIM Bin electronics and the ZEUS system using the upgraded Pixie-4 electronics have been done and evaluated. Finally, procedure revisions and implementation of both systems into routine operations is currently in process and planned to be complete by the end of calendar year 2017. (authors)

12 MANAGEMENT OF RADIOACTIVE AND NON-RADIOACTIVE W↗

Block 2 SRM conceptual design studies. Volume 1, Book 2: Preliminary development and verification plan

Activities that will be conducted in support of the development and verification of the Block 2 Solid Rocket Motor (SRM) are described. Development includes design, fabrication, processing, and testing activities in which the results are fed back into the project. Verification includes analytical and test activities which demonstrate SRM component/subassembly/assembly capability to perform its intended function. The management organization responsible for formulating and implementing the verification program is introduced. It also identifies the controls which will monitor and track the verification program. Integral with the design and certification of the SRM are other pieces of equipment used in transportation, handling, and testing which influence the reliability and maintainability of the SRM configuration. The certification of this equipment is also discussed.

Source record↗

Program Correctness, Verification and Testing for Exascale (Corvette)

The goal of this project is to provide tools to assess the correctness of parallel programs written using hybrid parallelism. There is a dire lack of both theoretical and engineering know-how in the area of finding bugs in hybrid or large scale parallel programs, which our research aims to change. In the project we have demonstrated novel approaches in several areas: 1. Low overhead automated and precise detection of concurrency bugs at scale. 2. Using low overhead bug detection tools to guide speculative program transformations for performance. 3. Techniques to reduce the concurrency required to reproduce a bug using partial program restart/replay. 4. Techniques to provide reproducible execution of floating point programs. 5. Techniques for tuning the floating point precision used in codes.

97 MATHEMATICS AND COMPUTING↗

Debris control design achievements of the booster separation motors

The stringent debris control requirements imposed on the design of the Space Shuttle booster separation motor are described along with the verification program implemented to ensure compliance with debris control objectives. The principal areas emphasized in the design and development of the Booster Separation Motor (BSM) relative to debris control were the propellant formulation and nozzle closures which protect the motors from aerodynamic heating and moisture. A description of the motor design requirements, the propellant formulation and verification program, and the nozzle closures design and verification are presented.

Smith, G. W.↗

SU-E-T-442: Sensitivity of Quality Assurance Tools to Delivery Errors On a Magnetic Resonance-Imaging Guided Radiation Therapy (MR-IGRT) System

Purpose: To test the sensitivity of the quality assurance (QA) tools actively used on a clinical MR-IGRT system for potential delivery errors. Methods: Patient-specific QA procedures have been implemented for a commercially available Cobalt-60 MR-IGRT system. The QA tools utilized were a MR-compatible cylindrical diode-array detector (ArcCHECK) with a custom insert which positions an ionization chamber (Exradin A18) in the middle of the device, as well as an in-house treatment delivery verification program. These tools were tested to investigate their sensitivity to delivery errors. For the ArcCHECK and ion chamber, a baseline was established with a static field irradiation to a known dose. Variations of the baseline were investigated which included rotated gantry, altered field size, directional shifts, and different delivery time. In addition, similar variations were tested with the automated delivery verification program that compared the treatment parameters in the machine delivery logs to the ones in the plan. To test the software, a 3-field conformal plan was generated as the baseline. Results: ArcCHECK noted at least a 13% decrease in passing rate from baseline in the following scenarios: gantry rotation of 1 degree from plan, 5mm change in field size, 2mm lateral shift, and delivery time decrease. Ion chamber measurements remained consistent for these variations except for the 5 second decrease in delivery time scenario which resulted in an 8% difference from baseline. The delivery verification software was able to detect and report the simulated errors such as when the gantry was rotated by 0.6 degrees, the beam weighting was changed by a percent, a single multileaf collimator was moved by 1cm, and the dose was changed from 2 to 1.8Gy. Conclusion: The results show that the current tools used for patient specific QA are capable of detecting small errors in RT delivery with presence of magnetic field.

60 APPLIED LIFE SCIENCES↗

eCC++ : A Compiler Construction Framework for Embedded Domain-Specific Languages

eCC++ is a new compiler construction framework for embedding domain-specific programming languages within C++. That is, the host language is C++, the guest language is the DSL to be embedded in C++, and eCC++ is the tool that enables the embedding. The eCC++ framework is composed of three main components: a front-end, an API for program verification based on a functional and declarative intermediate representation (IR), and a Multi-Level Intermediate Representation (MLIR) code generator. The eCC++ front-end consists of a library of C++ classes and operators that can be used to define the guest language. Guest sources are compiled with any standard C++ compiler, and when run, the resulting executable generates an eCC++ IR representation of the program, which can be verified within the eCC++ framework. Finally, eCC++ allows for high-level and domain-specific optimizations before generating MLIR. In summary, eCC++ aims to act as a generic front-end that enables embedding guest languages into C++, and provides necessary compiler technology for program verification, targeting the existing capabilities in the MLIR infrastructure. The paper evaluates the eCC++ expressiveness and usability describing the process of embedding GraphIt, a high-performance graph language in C++.

Gonzalez Tallada, Marc↗

The Space Shuttle's testing gauntlet

The Space Shuttle verification program is detailed, with verification network flowcharts. Performance qualification tests, life endurance tests, structural verification tests, and vibration/dynamic tests of components, subsystems, and major systems at various test levels are dealt with. Ground tests, static firings of the Shuttle main engine, external-tank separation tests, ground vibration tests of vehicle mated to external tank, and main propulsion tests and test scheduling are described. Functions of the Shuttle avionics integration laboratory and electronic systems test laboratory are discussed. Test preparations and procedures for orbital flight testing, launch pad tests, and Shuttle approach- and landing-tests are described.

Mcintosh, G. P.↗

SSME Alternate Turbopump Development Program: Design verification specification for high-pressure fuel turbopump

The design and verification requirements are defined which are appropriate to hardware at the detail, subassembly, component, and engine levels and to correlate these requirements to the development demonstrations which provides verification that design objectives are achieved. The high pressure fuel turbopump requirements verification matrix provides correlation between design requirements and the tests required to verify that the requirement have been met.

Source record↗

Lithium-Ion Verification Test Program

In order to assess the capabilities of current aerospace lithium-ion cells to perform long-term NASA missions, low-earth-orbits (LEO) testing to evaluate long-term cycle life was initiated. A flexible program was developed at NASA Glenn Research Center to enable assessment of technology developments as they occur as well as provide information about different cell vendors and cell designs. Following extensive characterization testing, cells are tested using LEO charge and discharge profiles under ten different combinations of test conditions that were statistically chosen to determine the effects of depth-of-discharge, temperature, and end-of-charge voltage on LEO cycle life. Four cells from each vendor are tested at each specific combination of conditions. Conditions included in the test matrix are depth-of-discharges of 20%, 30, 35%, and 40%; temperatures of 20, 30, and 40 C; and end-of-charge voltages of 3.85 V, 3.95 V, and 4.05 V. Cells are randomly assigned to packs and packs are randomly assigned to test conditions. The capacity of the cells to 3.0 V at the conditions of the test is being periodically measured. The results of this testing will be used to model cell performance and degradation as a function of test operating conditions. Cells are being evaluated in 4-cell series strings with charge voltage limits being applied to individual cells by charge control units designed and built at NASA Glenn Research Center. Testing is being performed at the Naval Surface Warfare Center/Crane Division in Crane, IN. Testing was initiated in September 2004 with 40 Ah cells from Saft and 30 Ah cells from Lithion. The test program is being expanded with the addition of cells from MSA and the addition of small cell modules is being considered. Preliminary results showing voltage, temperature, usable capacity per unit mass, and voltage dispersion as their changes over time for the cells at 20 C is presented.

McKissock, Barbara↗

Deep Impact Extended Mission Challenges for the Validation and Verification Test Program

The Deep Impact Spacecraft was launched on January 12, 2005 as part of NASA's Discovery Program as a radical mission to excavate the interior of a comet. The Spacecraft consisted of two separate entities known as the Flyby and the Impactor, which were commanded to separate prior to comet rendezvous with comet 9P/Tempel 1. The overall mission was deemed a success on July 4, 2005, as the 370-kg Impactor collided with the comet at 10.2 km/s. This event was captured using the camera and infrared spectrometer on the Flyby spacecraft, along with ground-based observatories. Since this event, the Flyby spacecraft has been in hibernation mode and has received only a small amount of maintenance. The Deep Impact Program was managed by the Jet Propulsion Laboratory (JPL), led by Dr. Michael A'Hearn from the University of Maryland in College Park, and built by Ball Aerospace & Technologies Corp. in Boulder, Colorado.

Test Bench↗

Introduction to Penelope

A formal program verification is a (mathematical) proof that a program executed according to its intended model meets some specification. This proves that the algorithm defined by the program is correct in the precise technical sense of being consistent with a particular specification. A program correct in this sense is free from a large and important class of errors, even though its behavior may still produce unintended results--either because the implementation of the programming language itself does not match the model of execution, or because the specification does not correctly express the user's intentions. Penelope is a prototype system for interactively developing and verifying programs that are written in a rich subset of sequential Ada. Penelope can be used to develop a program and its correctness proof incrementally, and in concert with one another. Incrementality is used in a number of ways to help make verification more tractable and more productive. For example, if an already-verified program is modified, one can attempt to prove the modified version by replaying and modifying the original verification. Penelope's specification language, Larch/Ada, belongs to the family of Larch interface languages. Larch/Ada scales up properly, in the sense that it is demonstrably sound to decompose a system hierarchically and reason locally about the implementation of each piece. Penelope has been applied in various demonstration projects--for specification (guidance control, distributed operating systems), verification (of off-the-shelf code), and formal development (by non-expert as well as expert users). Some features of Penelope have been embodied in Ada Wise, a lint-like non-interactive tool that warns of the potential for certain dynamic semantic errors in Ada programs.

Guaspari, David↗

Computer simulated building energy consumption for verification of energy conservation measures in network facilities

A computer program called ECPVER (Energy Consumption Program - Verification) was developed to simulate all energy loads for any number of buildings. The program computes simulated daily, monthly, and yearly energy consumption which can be compared with actual meter readings for the same time period. Such comparison can lead to validation of the model under a variety of conditions, which allows it to be used to predict future energy saving due to energy conservation measures. Predicted energy saving can then be compared with actual saving to verify the effectiveness of those energy conservation changes. This verification procedure is planned to be an important advancement in the Deep Space Network Energy Project, which seeks to reduce energy cost and consumption at all DSN Deep Space Stations.

Plankey, B.↗

HDM/PASCAL Verification System User's Manual

The HDM/Pascal verification system is a tool for proving the correctness of programs written in PASCAL and specified in the Hierarchical Development Methodology (HDM). This document assumes an understanding of PASCAL, HDM, program verification, and the STP system. The steps toward verification which this tool provides are parsing programs and specifications, checking the static semantics, and generating verification conditions. Some support functions are provided such as maintaining a data base, status management, and editing. The system runs under the TOPS-20 and TENEX operating systems and is written in INTERLISP. However, no knowledge is assumed of these operating systems or of INTERLISP. The system requires three executable files, HDMVCG, PARSE, and STP. Optionally, the editor EMACS should be on the system in order for the editor to work. The file HDMVCG is invoked to run the system. The files PARSE and STP are used as lower forks to perform the functions of parsing and proving.

Hare, D.↗

SU-G-TeP4-11: Implementation of a Non-Measurement-Based Patient-Specific IMRT QA Program

Purpose: To implement a comprehensive non-measurement-based verification program for patient-specific IMRT QA Methods: Based on published guidelines, a robust IMRT QA program should assess the following components: 1) accuracy of dose calculation, 2) accuracy of data transfer from the treatment planning system (TPS) to the record-and-verify (RV) system, 3) treatment plan deliverability, and 4) accuracy of plan delivery. Results: We have implemented an IMRT QA program that consist of four components: 1) an independent re-calculation of the dose distribution in the patient anatomy with a commercial secondary dose calculation program: Mobius3D (Mobius Medical Systems, Houston, TX), with dose accuracy evaluation using gamma analysis, PTV mean dose, PTV coverage to 95%, and organ-at-risk mean dose; 2) an automated in-house-developed plan comparison system that compares all relevant plan parameters such as MU, MLC position, beam iso-center position, collimator, gantry, couch, field size settings, and bolus placement, etc. between the plan and the RV system; 3) use of the RV system to check the plan deliverability and further confirm using “mode-up” function on treatment console for plans receiving warning; and 4) implementation of a comprehensive weekly MLC QA, in addition to routine accelerator monthly and daily QA. Among 1200 verifications, there were 9 cases of suspicious calculations, 5 cases of delivery failure, no data transfer errors, and no failure of weekly MLC QA. These 9 suspicious cases were due to the PTV extending to the skin or to heterogeneity correction effects, which would not have been caught using phantom measurement-based QA. The delivery failure was due to the rounding variation of MLC position between the planning system and RV system. Conclusion: A very efficient, yet comprehensive, non-measurement-based patient-specific QA program has been implemented and used clinically for about 18 months with excellent results.

60 APPLIED LIFE SCIENCES↗

Code Verification and Solution Verification framework in pin-resolved neutron transport code MPACT

Program verification in scientific computing encompasses the application of formal and mathematical techniques to a scientific computing code for its credibility, accuracy, and validity. Code Verification identifies bugs and performance issues in the software development stage. Solution Verification assesses the applicability of the code and the accuracy of the solution to problems of interest. Both activities utilize application cases and quantify the error against prescribed acceptance criteria. However, simply executing more application cases does not guarantee stronger or more comprehensive credibility. Here, we establish a verification framework that involves Code Verification and Solution Verification, both of which work together such that the overarching goal of “converge to the correct answer for the intended application” can be reasonably inferred. The application of such a verification framework is demonstrated using the pin-resolved neutron transport code MPACT, where standard unit tests and regression tests are covered, and where the Method of Exact Solutions and the Method of Manufactured Solutions are successfully used. Additionally, the applicability of Method of Manufactured Solutions is extended to the OECD/NEA C5G7 benchmark problems of practical material and geometric configurations. Solution Verification activities are demonstrated on a practical hierarchy of application models of increasing complexity ranging from 2D pin cell problems to 3D assembly problems. The convergence behavior and rate of convergence with respect to each individual variable are studied and provided. This framework can be adapted broadly to other fields involving scientific computing codes.

97 MATHEMATICS AND COMPUTING↗

Columbus pressurized module verification

The baseline verification approach of the COLUMBUS Pressurized Module was defined during the A and B1 project phases. Peculiarities of the verification program are the testing requirements derived from the permanent manned presence in space. The model philosophy and the test program have been developed in line with the overall verification concept. Such critical areas as meteoroid protections, heat pipe radiators and module seals are identified and tested. Verification problem areas are identified and recommendations for the next development are proposed.

Messidoro, Piero↗

Hierarchical Design and Verification for VLSI

The specification and verification work is described in detail, and some of the problems and issues to be resolved in their application to Very Large Scale Integration VLSI systems are examined. The hierarchical design methodologies enable a system architect or design team to decompose a complex design into a formal hierarchy of levels of abstraction. The first step inprogram verification is tree formation. The next step after tree formation is the generation from the trees of the verification conditions themselves. The approach taken here is similar in spirit to the corresponding step in program verification but requires modeling of the semantics of circuit elements rather than program statements. The last step is that of proving the verification conditions using a mechanical theorem-prover.

Shostak, R. E.↗