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 1,315 records · Page 73

A semi-automated system for plotting and computer cataloging of remote sensing imagery

Description of a computer-assisted system for plotting and descriptor-cataloging of aerial imagery - an ingredient of the aerial image data handling system of the NASA Earth Resources Aircraft Project (ERAP). The system under consideration uses two graphic tablets linked interactively with a digital computer as input devices for deriving frame coordinates by correlating image points to map points. The various software programs and operating modes facilitate a semiautomatic plotting of an image by selecting two or more points within the image for matching with map details. The computer performs the scaling and orientation transformations for the calculation of the center and corner coordinates of the frame. Twenty five other descriptors for each frame are fed into a computerized data base requiring a minimum operator's time for verification and correction.

Gnauck, G. E.↗

Use of COTS Batteries on ISS and Shuttle

This presentation focuses on COTS Battery testing for energy content, toxicity, hazards, failures modes and controls for different battery chemistries. It also discusses the current program requirements, challenges with COTS Batteries in manned vehicle COTS methodology, JSC test details, and gives a list of incidents from consumer protection safety commissions. The Battery test process involved testing new batteries for engineering certification, qualification of batteries, flight acceptance, cell and battery, environment, performance and abuse. Their conclusions and recommendations were that: high risk is undertaken with the use of COTS batteries, hazard control verification is required to allow the use of these batteries on manned space flights, failures during use cannot be understood if different scenarios of failure are not tested on the ground, and that testing is performed on small sample numbers due to restrictions on cost and time. They recommend testing of large sample size to gain more confidence in the operation of the hazard controls.

Jeevarajan, Judith A.↗

Develop a Model Component

During my internship at NASA, I was a model developer for Ground Support Equipment (GSE). The purpose of a model developer is to develop and unit test model component libraries (fluid, electrical, gas, etc.). The models are designed to simulate software for GSE (Ground Special Power, Crew Access Arm, Cryo, Fire and Leak Detection System, Environmental Control System (ECS), etc. ~.) before they are implemented into hardware. These models support verifying local control and remote software for End-Item Software Under Test (SUT). The model simulates the physical behavior (function, state, limits and 110) of each end-item and it's dependencies as defined in the Subsystem Interface Table, Software Requirements & Design Specification (SRDS), Ground Integrated Schematic (GIS), and System Mechanical Schematic.(SMS). The software of each specific model component is simulated through MATLAB's Simulink program. The intensiv~ model development life cycle is a.s follows: Identify source documents; identify model scope; update schedule; preliminary design review; develop model requirements; update model.. scope; update schedule; detailed design review; create/modify library component; implement library components reference; implement subsystem components; develop a test script; run the test script; develop users guide; send model out for peer review; the model is sent out for verific~tionlvalidation; if there is empirical data, a validation data package is generated; if there is not empirical data, a verification package is generated; the test results are then reviewed; and finally, the user. requests accreditation, and a statement of accreditation is prepared. Once each component model is reviewed and approved, they are intertwined together into one integrated model. This integrated model is then tested itself, through a test script and autotest, so that it can be concluded that all models work conjointly, for a single purpose. The component I was assigned, specifically, was a fluid component, a discrete pressure switch. The switch takes a fluid pressure input, and if the pressure is greater than a designated cutoff pressure, the switch would stop fluid flow.

Ensey, Tyler S.↗

Experimental verification of the multistage depressed collector design procedure for a high-perveance, helix-type, traveling-wave tube

The validity of a computational procedure for the design of multistage depressed collectors (MDC's) is demonstrated for a traveling wave tube (TWT) with a perveance of .00000123. The MDC is used with spent-beam refocusing to improve substantially the efficiency of the TWT. Reports on this subject have verified, under a variety of operating conditions, the MDC design procedure for TWT's with lower perveance. The design procedure is based on two computer programs that create a mathematical model of the electric and magnetic fields of the TWT refocuser MDC system and its electron beam. The two principal outputs of the analysis are a description of the radiofrequency (RF) performance of the TWT and the trajectories of representatives groups of charges from the input of the TWT to their points of interception on the MDC electrodes.

Dayton, J. A., Jr.↗

Overview of Code Verification

The verified code for the SIFT Executive is not the code that executes on the SIFT system as delivered. The running versions of the SIFT Executive contain optimizations and special code relating to the messy interface to the hardware broadcast interface and to packing of data to conserve space in the store of the BDX930 processors. The running code was in fact developed prior to and without consideration of any mechanical verification. This was regarded as necessary experimentation with the SIFT hardware and special purpose Pascal compiler. The Pascal code sections cover: the selection of a schedule from the global executive broadcast, scheduling, dispatching, three way voting, and error reporting actions of the SIFT Executive. Not included in these sections of Pascal code are: the global executive, five way voting, clock synchronization, interactive consistency, low level broadcasting, and program loading, initialization, and schedule construction.

Source record↗

Automatic specification of reliability models for fault-tolerant computers

The calculation of reliability measures using Markov models is required for life-critical processor-memory-switch structures that have standby redundancy or that are subject to transient or intermittent faults or repair. The task of specifying these models is tedious and prone to human error because of the large number of states and transitions required in any reasonable system. Therefore, model specification is a major analysis bottleneck, and model verification is a major validation problem. The general unfamiliarity of computer architects with Markov modeling techniques further increases the necessity of automating the model specification. Automation requires a general system description language (SDL). For practicality, this SDL should also provide a high level of abstraction and be easy to learn and use. The first attempt to define and implement an SDL with those characteristics is presented. A program named Automated Reliability Modeling (ARM) was constructed as a research vehicle. The ARM program uses a graphical interface as its SDL, and it outputs a Markov reliability model specification formulated for direct use by programs that generate and evaluate the model.

Liceaga, Carlos A.↗

Towards a Compositional SPIN

This paper discusses our initial experience with introducing automated assume-guarantee verification based on learning in the SPIN tool. We believe that compositional verification techniques such as assume-guarantee reasoning could complement the state-reduction techniques that SPIN already supports, thus increasing the size of systems that SPIN can handle. We present a "light-weight" approach to evaluating the benefits of learning-based assume-guarantee reasoning in the context of SPIN: we turn our previous implementation of learning for the LTSA tool into a main program that externally invokes SPIN to provide the model checking-related answers. Despite its performance overheads (which mandate a future implementation within SPIN itself), this approach provides accurate information about the savings in memory. We have experimented with several versions of learning-based assume guarantee reasoning, including a novel heuristic introduced here for generating component assumptions when their environment is unavailable. We illustrate the benefits of learning-based assume-guarantee reasoning in SPIN through the example of a resource arbiter for a spacecraft. Keywords: assume-guarantee reasoning, model checking, learning.

Pasareanu, Corina S.↗

Runtime Verification in Context : Can Optimizing Error Detection Improve Fault Diagnosis

Runtime verification has primarily been developed and evaluated as a means of enriching the software testing process. While many researchers have pointed to its potential applicability in online approaches to software fault tolerance, there has been a dearth of work exploring the details of how that might be accomplished. In this paper, we describe how a component-oriented approach to software health management exposes the connections between program execution, error detection, fault diagnosis, and recovery. We identify both research challenges and opportunities in exploiting those connections. Specifically, we describe how recent approaches to reducing the overhead of runtime monitoring aimed at error detection might be adapted to reduce the overhead and improve the effectiveness of fault diagnosis.

Dwyer, Matthew B.↗

Results of Lunar Impact Observations During Geminid Meteor Shower Events

Meteoroids are natural particles with origins from comets, asteroids, and planets from within the solar system. On average, 33 metric tons (73,000 lb) of meteoroids hit Earth everyday with velocities ranging between 20 and 72 km/s. However, the vast majority of these meteoroids disintegrate in the atmosphere and never make it to the ground. The Moon also encounters the same meteoroid flux, but has no atmosphere to stop them from striking the surface. At such speeds even a small meteoroid has incredible energy. A meteoroid with a mass of only 5 kg can excavate a crater over 9 m across, hurling 75 metric tons (165,000 lb) of lunar soil and rock on ballistic trajectories above the lunar surface. Meteoroids with particle sizes as small as 100 micrometer (1 Microgram) can do considerable damage to spacecraft in Earth's orbit and beyond. Impacts can damage thermal protection systems, radiators, windows, and pressurized containers. Secondary effects might include partial penetration or pitting, local deformation, and surface degradation that can cause a failure upon reentry. The speed, mass, density, and flux of meteoroids are important factors for design considerations and mitigation during operations. Lunar operations (unmanned and manned) are also adversely affected by the meteoroid flux. Ejecta from meteoroid impacts is also part of the lunar environment and must be characterized. Understanding meteoroid fluxes and the associated risk of meteoroids impacting spacecraft traveling in and beyond Earth's orbit is the objective of the Meteoroid Environment Office (MEO) located at Marshall Space Flight Center (MSFC). One of the MEO's programs is meteoroid impact monitoring of the Moon. The large collecting area of the night side of the lunar disk provides statistically significant counts of meteoroids that can provide useful information about the flux of meteoroids in the hundreds of grams to kilograms size range. This information is not only important for characterizing the lunar environment associated with larger lunar impactors, but also provides statistical data for verification and improving meteoroid prediction models. Current meteoroid models indicate that the Moon is struck by a sporadic meteoroid with a mass greater than 1 kg over 260 times per year. This number is very uncertain since observations for objects in this mass range are few. Factors of several times, higher or lower, are easily possible. Meteor showers are also present to varying degrees at certain times of the year. The Earth experiences meteor showers when encountering the debris left behind by comets, which is also the case with 2 the Moon. During such times, the rate of shower meteoroids can greatly exceed that of the sporadic background rate for larger meteoroids. Looking for meteor shower impacts on the Moon at about the same time as they occur on Earth will yield important data that can be fed into meteor shower forecasting models, which can then be used to predict times of greater meteoroid hazard on the Moon. The Geminids are one such meteor shower of interest. The Geminids are a major meteor shower that occur in December with a peak intensity occurring usually during the 13th and 14th of the month and appearing to come from a radiant in the constellation Gemini. The Geminids are interesting in that the parent body of the debris stream is an asteroid, which along with the Quadrantids, are the only major meteor showers not originating from a comet. The Geminids parent body, 3200 Phaethon, is about 5 km in diameter and has an orbit that has a 22deg inclination which intersects the main asteroid belt and has a perihelion less than half of Mercury's perihelion distance. Thus, its orbit crosses those of Mars, Earth, Venus, and Mercury. The Geminid debris stream is by far the most massive as compared to the others. When the Earth passes through the stream in mid-December, a peak intensity of approx. equal 120 meteors per hour can be seen. Because of the Geminids' relatively large intensity and unique origin, it is important to monitor and gain information about the Geminids so as to improve their forecasts and understand their contribution to the meteoroid environment in Earth's orbit and at the Moon. It is the purpose of this Technical Memorandum (TM) to document two lunar observing periods coinciding with the Geminid meteor showers that occurred in 2006 and 2010.

Suggs, R. J.↗

Design for Manufacturing Tool for Automated Fiber Placement Structures - Verification and Validation

A tool has been developed to address the growing Design for Manufacturing needs for composite structures, specifically those manufactured with automated fiber placement. This manufacturing approach presents unique challenges associated with puckers and wrinkling, tow overlaps and gaps, fiber deviation, and laminate strength. Achieving a satisfactory laminate design usually requires finding compromises between those four areas. The developed tool, dubbed the Central Optimizer, assists with the process of balancing competing design metrics in automated fiber placement. This tool was developed under the NASA Advanced Composites Consortium with input from industry partners. Under this program, the Central Optimizer has been exercised on three different structures to verify its functionality and validate ability to improve the design process for automated fiber placement structures.

August T Noevere↗

Spartan service module finite element modeling technique and analysis

Sounding rockets have served as a relatively inexpensive and easy method of carrying experiments into the upper atmosphere. Limited observation time and pointing capabilities suggested the development of a new sounding rocket type carrier compatible with NASA's Space Transportation System. This concept evolved into the Spartan program, now credited with a successful Spartan 101 mission launched in June 1985. The next series of Spartans will use a service module primary structure. This newly designed reusable and universal component in the Spartan carrier system required thorough analysis and evaluation for flight certification. Using advanced finite element modeling techniques, the structure was analyzed and determined acceptable by meeting strict design goals and will be tested for verification of the analytical results.

Lindenmoyer, A. J.↗

Lunar stepping stones to a manned Mars exploration scenario

The initial trips to Mars by humans will be the first real severing of our dependence on Earth's environment. Common sense dictates that a human departure from Earth measured in years, to explore a distant planet, requires systems, techniques, and operations that have solid credibility proven with space experience. The space test and verification experience must occur with Mars-like conditions but under proving-ground conditions with good instrumentation, close monitoring, and fast emergency recovery capabilities. The lunar environment is the only arena that satisfies the requirements of a space recovery capabilities. The lunar environment is the only arena that satisfies the requirements of a space planetary proving-ground. The objective of this scenario is to demonstrate a program planning approach that has human presence at Mars as the goal but, prudently, capitalizes on manned lunar project facilities, operations, and experience to enable a safe journey for the first Mars crews. The emphasis in lunar application objectives is to perform productive science and resources exploitation missions. Most of the Mars mission aspects can be proven in the lunar environment providing 'stepping stones' to conducting the first human mission to travel to Mars and return safely to Earth.

Davidson, W. L.↗

The Formal Semantics of PVS

A specification language is a medium for expressing what is computed rather than how it is computed. Specification languages share some features with programming languages but are also different in several important ways. For our purpose, a specification language is a logic within which the behavior of computational systems can be formalized. Although a specification can be used to simulate the behavior of such systems, we mainly use specifications to state and prove system properties with mechanical assistance. We present the formal semantics of the specification language of SRI's Prototype Verification System (PVS). This specification language is based on the simply typed lambda calculus. The novelty in PVS is that it contains very expressive language features whose static analysis (e.g., typechecking) requires the assistance of a theorem prover. The formal semantics illuminates several of the design considerations underlying PVS, the interaction between theorem proving and typechecking.

Owre, Sam↗

Mars Smart Lander Simulations for Entry, Descent, and Landing

Two primary simulations have been developed and are being updated for the Mars Smart Lander Entry, Descent, and Landing (EDL). The high fidelity engineering end-to-end EDL simulation that is based on NASA Langley's Program to Optimize Simulated Trajectories (POST) and the end-to-end real-time, hardware-in-the-loop simulation testbed, which is based on NASA JPL's (Jet Propulsion Laboratory) Dynamics Simulator for Entry, Descent and Surface landing (DSENDS). This paper presents the status of these Mars Smart Lander EDL end-to-end simulations at this time. Various models, capabilities, as well as validation and verification for these simulations are discussed.

Striepe, S. A.↗

Reconfigurable Hardware Adapts to Changing Mission Demands

A new class of computing architectures and processing systems, which use reconfigurable hardware, is creating a revolutionary approach to implementing future spacecraft systems. With the increasing complexity of electronic components, engineers must design next-generation spacecraft systems with new technologies in both hardware and software. Derivation Systems, Inc., of Carlsbad, California, has been working through NASA s Small Business Innovation Research (SBIR) program to develop key technologies in reconfigurable computing and Intellectual Property (IP) soft cores. Founded in 1993, Derivation Systems has received several SBIR contracts from NASA s Langley Research Center and the U.S. Department of Defense Air Force Research Laboratories in support of its mission to develop hardware and software for high-assurance systems. Through these contracts, Derivation Systems began developing leading-edge technology in formal verification, embedded Java, and reconfigurable computing for its PF3100, Derivational Reasoning System (DRS ), FormalCORE IP, FormalCORE PCI/32, FormalCORE DES, and LavaCORE Configurable Java Processor, which are designed for greater flexibility and security on all space missions.

Source record↗

The Kepler Mission and Eclipsing Binaries

The Kepler Mission is a photometric mission with a precision of 14 ppm (at R=12) that is designed to continuously observe a single field of view (FOV) of greater 100 sq deg in the Cygnus-Lyra region for four or more years. The primary goal of the mission is to monitor greater than 100,000 stars for transits of Earth-size and smaller planets in the habitable zone of solar-like stars. In the process, many eclipsing binaries (EB) will also be detected and light curves produced. To enhance and optimize the mission results, the stellar characteristics for all the stars in the FOV with R less than 16 will have been determined prior to launch. As part of the verification process, stars with transit candidates will have radial velocity follow-up observations performed to determine the component masses and thereby separate eclipses caused by stellar companions from transits caused by planets. The result will be a rich database on EBs. The community will have access to the archive for further analysis, such as, for EB modeling of the high-precision light curves. A guest observer program is also planned to allow for photometric observations of objects not on the target list but within the FOV, since only the pixels of interest from those stars monitored will be transmitted to the ground.

Koch, David↗

Jet Penetration into a Scaled Microfabricated Stirling Cycle Regenerator

The cooler and heater adjacent to the regenerator of a Stirling cycle engine have tubes or channels which form jets that pass into the regenerator while diffusing within the matrix. An inactive part of the matrix, beyond the cores of these jets, does not participate fully in the heat transfer between the flow of working fluid and the regenerator matrix material, weakening the regenerator s ability to exchange heat with the working fluid. The objective of the present program is to document this effect on the performance of the regenerator and to develop a model for generalizing the results. However, the small scales of actual Stirling regenerator matrices (on the order of tens of microns) make direct measurements of this effect very difficult. As a result, jet spreading within a regenerator matrix has not been characterized well and is poorly understood. Also, modeling is lacking experimental verification. To address this, a large-scale mockup of thirty times actual scale was constructed and operated under conditions that are dynamically similar to the engine operation. Jet penetration with round jets and slot jets into the microfabricated regenerator geometry are then measured by conventional means. The results are compared with those from a study of spreading of round jets within woven screen regenerator for further documentation of the comparative performance of the microfabricated regenerator geometry.

Sun, Liyong↗

Virtual Machine Language 2.1

VML (Virtual Machine Language) is an advanced computing environment that allows spacecraft to operate using mechanisms ranging from simple, time-oriented sequencing to advanced, multicomponent reactive systems. VML has developed in four evolutionary stages. VML 0 is a core execution capability providing multi-threaded command execution, integer data types, and rudimentary branching. VML 1 added named parameterized procedures, extensive polymorphism, data typing, branching, looping issuance of commands using run-time parameters, and named global variables. VML 2 added for loops, data verification, telemetry reaction, and an open flight adaptation architecture. VML 2.1 contains major advances in control flow capabilities for executable state machines. On the resource requirements front, VML 2.1 features a reduced memory footprint in order to fit more capability into modestly sized flight processors, and endian-neutral data access for compatibility with Intel little-endian processors. Sequence packaging has been improved with object-oriented programming constructs and the use of implicit (rather than explicit) time tags on statements. Sequence event detection has been significantly enhanced with multi-variable waiting, which allows a sequence to detect and react to conditions defined by complex expressions with multiple global variables. This multi-variable waiting serves as the basis for implementing parallel rule checking, which in turn, makes possible executable state machines. The new state machine feature in VML 2.1 allows the creation of sophisticated autonomous reactive systems without the need to develop expensive flight software. Users specify named states and transitions, along with the truth conditions required, before taking transitions. Transitions with the same signal name allow separate state machines to coordinate actions: the conditions distributed across all state machines necessary to arm a particular signal are evaluated, and once found true, that signal is raised. The selected signal then causes all identically named transitions in all present state machines to be taken simultaneously. VML 2.1 has relevance to all potential space missions, both manned and unmanned. It was under consideration for use on Orion.

Riedel, Joseph E.↗