Engineering Papers⌕ Search

SEARCH · Engineering Papers

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 865 records · Page 48

Multi-Mission System Architecture Platform: Design and Verification of the Remote Engineering Unit

The Multi-Mission System Architecture Platform (MSAP) represents an effort to bolster efficiency in the spacecraft design process. By incorporating essential spacecraft functionality into a modular, expandable system, the MSAP provides a foundation on which future spacecraft missions can be developed. Once completed, the MSAP will provide support for missions with varying objectives, while maintaining a level of standardization that will minimize redesign of general system components. One subsystem of the MSAP, the Remote Engineering Unit (REU), functions by gathering engineering telemetry from strategic points on the spacecraft and providing these measurements to the spacecraft's Command and Data Handling (C&DH) subsystem. Before the MSAP Project reaches completion, all hardware, including the REU, must be verified. However, the speed and complexity of the REU circuitry rules out the possibility of physical prototyping. Instead, the MSAP hardware is designed and verified using the Verilog Hardware Definition Language (HDL). An increasingly popular means of digital design, HDL programming provides a level of abstraction, which allows the designer to focus on functionality while logic synthesis tools take care of gate-level design and optimization. As verification of the REU proceeds, errors are quickly remedied, preventing costly changes during hardware validation. After undergoing the careful, iterative processes of verification and validation, the REU and MSAP will prove their readiness for use in a multitude of spacecraft missions.

Sartori, John↗

Program Overview: Vortex Interaction Aerodynamics Relevant to Military Air Vehicle Performance

A research program has been underway for five years to study vortex interaction aerodynamics that are relevant to military air vehicle performance. The program has been conducted under the auspices of the NATO Science and Technology Organization (STO), Applied Vehicle Technology (AVT) panel by a Task Group with the identification of AVT-316. Seven special sessions have been established to highlight accomplishments from the AVT-316 research. An overview of the AVT-316 program is presented in this paper.

Verification and Validation↗

Expert system decision support for low-cost launch vehicle operations

Progress in assessing the feasibility, benefits, and risks associated with AI expert systems applied to low cost expendable launch vehicle systems is described. Part one identified potential application areas in vehicle operations and on-board functions, assessed measures of cost benefit, and identified key technologies to aid in the implementation of decision support systems in this environment. Part two of the program began the development of prototypes to demonstrate real-time vehicle checkout with controller and diagnostic/analysis intelligent systems and to gather true measures of cost savings vs. conventional software, verification and validation requirements, and maintainability improvement. The main objective of the expert advanced development projects was to provide a robust intelligent system for control/analysis that must be performed within a specified real-time window in order to meet the demands of the given application. The efforts to develop the two prototypes are described. Prime emphasis was on a controller expert system to show real-time performance in a cryogenic propellant loading application and safety validation implementation of this system experimentally, using commercial-off-the-shelf software tools and object oriented programming techniques. This smart ground support equipment prototype is based in C with imbedded expert system rules written in the CLIPS protocol. The relational database, ORACLE, provides non-real-time data support. The second demonstration develops the vehicle/ground intelligent automation concept, from phase one, to show cooperation between multiple expert systems. This automated test conductor (ATC) prototype utilizes a knowledge-bus approach for intelligent information processing by use of virtual sensors and blackboards to solve complex problems. It incorporates distributed processing of real-time data and object-oriented techniques for command, configuration control, and auto-code generation.

Szatkowski, G. P.↗

Engineering support activities for the Apollo 17 Surface Electrical Properties Experiment.

Description of the engineering support activities which were required to ensure fulfillment of objectives specified for the Apollo 17 SEP (Surface Electrical Properties) Experiment. Attention is given to procedural steps involving verification of hardware acceptability to the astronauts, computer simulation of the experiment hardware, field trials, receiver antenna pattern measurements, and the qualification test program.

Cubley, H. D.↗

Automated finite element grid break-up method, a verification of the six node averaging approach

The verification of the nodal averaging method for generating automated finite triangular element grids was demonstrated. This was accomplished with a six node averaging program (SNAP) which was placed on an IBM 2250 vector graphics scope terminal. The advantage of this method is that it is unnecessary to program time consuming geometric division and transition algorithms.

Barten, H. J.↗

Large area sheet task: Advanced Dendritic Web Growth Development

A melt level control system was implemented to provide stepless silicon feed rates from zero to rates exactly matching the silicon consumed during web growth. Bench tests of the unit were successfully completed and the system mounted in a web furnace for operational verification. Tests of long term temperature drift correction techniques were made; web width monitoring seems most appropriate for feedback purposes. A system to program the initiation of the web growth cycle was successfully tested. A low cost temperature controller was tested which functions as well as units four times as expensive.

Duncan, C. S.↗

Creep-fatigue life prediction for engine hot section materials (isotropic)

The objectives of this program are the investigation of fundamental approaches to high temperature crack initiation life prediction, identification of specific modeling strategies and the development of specific models for component relevant loading conditions. A survey of the hot section material/coating systems used throughout the gas turbine industry is included. Two material/coating systems will be identified for the program. The material/coating system designated as the base system shall be used throughout Tasks 1-12. The alternate material/coating system will be used only in Task 12 for further evaluation of the models developed on the base material. In Task II, candidate life prediction approaches will be screened based on a set of criteria that includes experience of the approaches within the literature, correlation with isothermal data generated on the base material, and judgements relative to the applicability of the approach for the complex cycles to be considered in the option program. The two most promising approaches will be identified. Task 3 further evaluates the best approach using additional base material fatigue testing including verification tests. Task 4 consists of technical, schedular, financial and all other reporting requirements in accordance with the Reports of Work clause.

Moreno, V.↗

High resolution microwave spectrometer sounder (HIMSS), volume 1, book 2

The following topics are presented with respect to the high resolution microwave spectrometer sounder (HIMSS) that is to be used as an instrument for NASA's Earth Observing System (EOS): (1) preliminary program plans; (2) contract end item (CEI) specification; and (3) the instrument interface description document. Under the preliminary program plans section, plans dealing with the following subject areas are discussed: spares, performance assurance, configuration management, software implementation, contamination, calibration management, and verification.

Source record↗

AIPS technology survey report

The results of a technology survey conducted for the NASA/JSC by the CSDL during Phase 1 of the NASA Advanced Information Processing System (AIPS) program at the CSDL are discussed. The purpose of the survey was to ensure that all technology relevant to the configuration, design, development, verification, implementation, and validation of an advanced information processing system, whether existing or under development and soon to be available, would be duly considered in the development of the AIPS. The emphasis in the survey was on technology items which were clearly relevant to the AIPS. Requirements were developed which guided the planning of contacts with the outside sources to be surveyed, and established practical limits on the scope and content of the Technology Survey. Subjects surveyed included architecture, software, hardware, methods for evaluation of reliability and performance, and methods for the verification of the AIPS design and the validation of the AIPS implementation. Survey requirements and survey results in each of these areas are presented, including analyses of the potential effects on the AIPS development process of using or not using the surveyed technology items. Another output of the survey was the identification of technology areas of particular relevance to the AIPS and for which further development, in some cases by the CSDL and in some cases by the NASA, would be fruitful. Appendices are provided in which are presented: (1) reports of some of the actual survey interactions with industrial and other outside information sources; (2) the literature list from the comprehensive literature survey which was conducted; (3) reduced-scale images of an excerpt ('Technology Survey' viewgraphs) from the set of viewgraphs used at the 14 April 1983 Preliminary Requirements Review by the CSDL for the NASA; and (4) reduced-scale images of the set of viewgraphs used in the AIPS Technology Survey Review presentation to the NASA monitors by the CSDL at the NASA Langley Research Center on 28 Sep. 1983.

Ogletree, Glenn↗

Main Power Distribution Unit for the Jupiter Icy Moons Orbiter (JIMO)

Around the year 2011, the Jupiter Icy Moons Orbiter (JIMO) will be launched and on its way to orbit three of Jupiter s planet-sized moons. The mission goals for the JIMO project revolve heavily around gathering scientific data concerning ingredients we, as humans, consider essential: water, energy and necessary chemical elements. The JIM0 is an ambitious mission which will implore propulsion from an ION thruster powered by a nuclear fission reactor. Glenn Research Center is responsible for the development of the dynamic power conversion, power management and distribution, heat rejection and ION thrusters. The first test phase for the JIM0 program concerns the High Power AC Power Management and Distribution (PMAD) Test Bed. The goal of this testing is to support electrical performance verification of the power systems. The test bed will incorporate a 2kW Brayton Rotating Unit (BRU) to simulate the nuclear reactor as well as two ION thrusters. The first module of the PMAD Test Bed to be designed is the Main Power Distribution Unit (MPDU) which relays the power input to the various propulsion systems and scientific instruments. The MPDU involves circuitry design as well as mechanical design to determine the placement of the components. The MPDU consists of fourteen relays of four different variations used to convert the input power into the appropriate power output. The three phase system uses 400 Vo1ts(sub L-L) rms at 1000 Hertz. The power is relayed through the circuit and distributed to the scientific instruments, the ION thrusters and other controlled systems. The mechanical design requires the components to be positioned for easy electrical wiring as well as allowing adequate room for the main buss bars, individual circuit boards connected to each component and power supplies. To accomplish creating a suitable design, AutoCAD was used as a drafting tool. By showing a visual layout of the components, it is easy to see where there is extra room or where the components may interfere with one another. By working with the electrical engineer who is designing the circuit, the specific design requirements for the MPDU were determined and used as guidelines. Space is limited due to the size of the mounting plate therefore each component must be strategically placed. Since the MPDU is being designed to fit into a simulated model of the spacecraft systems on the JIMO, components must be positioned where they are easily accessible to be wired to the other onboard systems. Mechanical and electrical requirements provided equally important limits which are combined to produce the best possible design of the MPDU.

Papa, Melissa R.↗

A Scala DSL for RETE-Based Runtime Verification

Runtime verification (RV) consists in part of checking execution traces against formalized specifications. Several systems have emerged, most of which support specification notations based on state machines, regular expressions, temporal logic, or grammars. The field of Artificial Intelligence (AI) has for an even longer period of time studied rule-based production systems, which at a closer look appear to be relevant for RV, although seemingly focused on slightly different application domains, such as for example business processes and expert systems. The core algorithm in many of these systems is the Rete algorithm. We have implemented a Rete-based runtime verification system, named LogFire (originally intended for offline log analysis but also applicable to online analysis), as an internal DSL in the Scala programming language, using Scala's support for defining DSLs. This combination appears attractive from a practical point of view. Our contribution is in part conceptual in arguing that such rule-based frameworks originating from AI may be suited for RV.

matching problem↗

IV&V Assurance Case Design for Artemis II

As human-rated missions like those in NASA’s Artemis program continue to grow in both size and complexity, and the role of software in achieving mission objectives expands dramatically, NASA’s Independent Verification and Validation (IV&V) Teams face evolving challenges in assuring the safety and performance of the safety- and mission-critical embedded software that is essential to landing astronauts on the surface of the Moon by 2024. Key among these challenges is IV&V’s desire to present a cohesive, integrated assurance statement to its stakeholders that encapsulates and summarizes our assurance positions across the integrated Artemis systems and their combined role in support of a safe and successful flight. In order to meet this challenge, the IV&V Teams have begun a transition to using formal assurance case concepts and documentation in the Goal Structuring Notation (GSN) to build an argument in support of software assurance. IV&V recognizes significant benefits to the logical argumentation structure provided by assurance cases and GSN over our current practices for documenting and managing assurance claims. In order to reap these benefits, IV&V is integrating the use of assurance case concepts with our paradigm of follow-the-risk capability based assurance. Because of this, assurance cases created and used by IV&V are distinct from the sort of assurance case created by a development project or embedded software assurance organization. IV&V’s assurance cases depend much less upon standards and regulations, and more on evidence captured by IV&V regarding the environment, requirements, design, and implementation. IV&V constructs an independent network of claims based on an independent decomposition of arguments. Based upon the risk posture of these claims and their associated software and software artifacts, IV&V then develops and executes engineering analyses and testing, which provide evidence to either support or refute the claim. This emerging risk-informed assurance case methodology is being put into practice as IV&V plans for support of the Artemis II mission, the first flight of the Orion capsule and Space Launch System with astronauts on board.

Gerek Whitman↗

IV&V Assurance Case Design for Artemis II

As human-rated missions like those in NASA's Artemis program continue to grow in both size and complexity, and the role of software in achieving mission objectives expands dramatically, NASA's Independent Verification and Validation (IV&V) Teams face evolving challenges in assuring the safety and performance of the safety- and mission-critical embedded software that is essential to landing astronauts on the surface of the Moon by 2024. Key among these challenges is IV&V's desire to present a cohesive, integrated assurance statement to its stakeholders that encapsulates and summarizes our assurance positions across the integrated Artemis systems and their combined role in support of a safe and successful flight. In order to meet this challenge, the IV&V Teams have begun a transition to using formal assurance case concepts and documentation in the Goal Structuring Notation (GSN) to build an argument in support of software assurance. IV&V recognizes significant benefits to the logical argumentation structure provided by assurance cases and GSN over our current practices for documenting and managing assurance claims. In order to reap these benefits, IV&V is integrating the use of assurance case concepts with our paradigm of follow-the-risk capability based assurance. Because of this, assurance cases created and used by IV&V are distinct from the sort of assurance case created by a development project or embedded software assurance organization. IV&V's assurance cases depend much less upon standards and regulations, and more on evidence captured by IV&V regarding the environment, requirements, design, and implementation. IV&V constructs an independent network of claims based on an independent decomposition of arguments. Based upon the risk posture of these claims and their associated software and software artifacts, IV&V then develops and executes engineering analyses and testing, which provide evidence to either support or refute the claim. This emerging risk-informed assurance case methodology is being put into practice as IV&V plans for support of the Artemis II mission, the first flight of the Orion capsule and Space Launch System with astronauts on board.

Whitman, Gerek↗

Data Automata in Scala

The field of runtime verification has during the last decade seen a multitude of systems for monitoring event sequences (traces) emitted by a running system. The objective is to ensure correctness of a system by checking its execution traces against formal specifications representing requirements. A special challenge is data parameterized events, where monitors have to keep track of the combination of control states as well as data constraints, relating events and the data they carry across time points. This poses a challenge wrt. efficiency of monitors, as well as expressiveness of logics. Data automata is a form of automata where states are parameterized with data, supporting monitoring of data parameterized events. We describe the full details of a very simple API in the Scala programming language, an internal DSL (Domain-Specific Language), implementing data automata. The small implementation suggests a design pattern. Data automata allow transition conditions to refer to other states than the source state, and allow target states of transitions to be inlined, offering a temporal logic flavored notation. An embedding of a logic in a high-level language like Scala in addition allows monitors to be programmed using all of Scala's language constructs, offering the full flexibility of a programming language. The framework is demonstrated on an XML processing scenario previously addressed in related work.

runtime verification↗

A research program in advanced information systems

Topics addressed cover: identification of large space structure dynamics; special-purpose architectures for computational fluid dynamics; fault-tolerant processor architectures; data flow techniques; software specification and verification tools; management of software development; software environment for concurrent computing; and parallel algorithms and architectures for the solution of partial differential equations.

Vandervelde, Wallace E.↗

An integrated user-oriented laboratory for verification of digital flight control systems: Features and capabilities

A Digital Flight Control Systems Verification Laboratory (DFCSVL) has been established at NASA Ames Research Center. This report describes the major elements of the laboratory, the research activities that can be supported in the area of verification and validation of digital flight control systems (DFCS), and the operating scenarios within which these activities can be carried out. The DFCSVL consists of a palletized dual-dual flight-control system linked to a dedicated PDP-11/60 processor. Major software support programs are hosted in a remotely located UNIVAC 1100 accessible from the PDP-11/60 through a modem link. Important features of the DFCSVL include extensive hardware and software fault insertion capabilities, a real-time closed loop environment to exercise the DFCS, an integrated set of software verification tools, and a user-oriented interface to all the resources and capabilities.

Defeo, P.↗

Replacement of HCFC-225 Solvent for Cleaning NASA Propulsion Oxygen Systems

Since the 1990's, when the Class I Ozone Depleting Substance (ODS) chlorofluorocarbon‐113 (CFC‐113) was banned, NASA's rocket propulsion test facilities at Marshall Space Flight Center (MSFC) and Stennis Space Center (SSC) have relied upon hydrochlorofluorocarbon‐225 (HCFC‐225) to safely clean and verify the cleanliness of large scale propulsion oxygen systems. Effective January 1, 2015, the production, import, export, and new use of HCFC‐225, a Class II ODS, was prohibited by the Clean Air Act. In 2012 through 2014, leveraging resources from both the NASA Rocket Propulsion Test Program and the Defense Logistics Agency ‐ Aviation Hazardous Minimization and Green Products Branch, test labs at MSFC, SSC, and Johnson Space Center's White Sands Test Facility (WSTF) collaborated to seek out, test, and qualify a replacement for HCFC‐225 that is both an effective cleaner and safe for use with oxygen systems. Candidate solvents were selected and a test plan was developed following the guidelines of ASTM G127, Standard Guide for the Selection of Cleaning Agents for Oxygen Systems. Solvents were evaluated for materials compatibility, oxygen compatibility, cleaning effectiveness, and suitability for use in cleanliness verification and field cleaning operations. Two solvents were determined to be acceptable for cleaning oxygen systems and one was chosen for implementation at NASA's rocket propulsion test facilities. The test program and results are summarized. This project also demonstrated the benefits of cross‐agency collaboration in a time of limited resources.

Mitchell, Mark A.↗